Arvados

We have a number of manifests that appear to have been saved in Keep both with and without signatures.

Example: on keep0.qr1hi, file /data/qr1hi-keep-3/keep/058/0584bf86c5ddd2e388a42599547a2b5d:

. 72d9e5f244145c86e7028e6cdc0a2169+63+Abb23956dcf68a64c4a3b33ce90d073bb3d61c842@53cfb638 0:63:md5sum.txt

and /data/qr1hi-keep-1/keep/dd7/dd755dbc8d49a67f4fe7dc843e4f10a6:

. 72d9e5f244145c86e7028e6cdc0a2169+63 0:63:md5sum.txt

The unsigned manifest is (correctly) used for the collection's portable_data_hash:

 2.1.0 :002 > Collection.where("portable_data_hash like '0584bf86c5ddd2e388a42599547a2b5d%'").first
  => nil 
 2.1.0 :003 > Collection.where("portable_data_hash like 'dd755dbc8d49a67f4fe7dc843e4f10a6%'").first
  => #<Collection id: 28837, owner_uuid: "qr1hi-tpzed-5jakibnrp1qpty1", created_at: "2014-10-30 18:25:44", modified_by_client_uuid: nil, modified_by_user_uuid: "qr1hi-tpzed-5jakibnrp1qpty1", modified_at: "2014-10-30 18:25:44", portable_data_hash: "dd755dbc8d49a67f4fe7dc843e4f10a6+54", redundancy: nil, redundancy_confirmed_by_client_uuid: nil, redundancy_confirmed_at: nil, redundancy_confirmed_as: nil, updated_at: "2014-10-30 18:25:44", uuid: "qr1hi-4zz18-p2kl3tt0tnbdqar", manifest_text: ". 72d9e5f244145c86e7028e6cdc0a2169+63 0:63:md5sum.t...", name: nil, description: nil, properties: nil, expires_at: nil> 

This was noticed first in practice with the output collection from a job generated by sguthrie that hung in a busy loop after saving its signed collection manifest in Keep:

2014-11-19_19:38:20.15754 qr1hi-8i9sb-prudm6nvg4xk31x 9212 57 child 10821 on compute16.7 exit 0 success=true
2014-11-19_19:38:20.27926 qr1hi-8i9sb-prudm6nvg4xk31x 9212 57 success in 1242 seconds
2014-11-19_19:38:20.34688 qr1hi-8i9sb-prudm6nvg4xk31x 9212 57 output 7974c67211a123e4f011cce032373ee1+28007813+A7b73a2c6991f2f0c96c5bec99c9d1924e3fa9570@547f66a8