missing metadata object when using deploy and multiple branches

[jberkus]

1. install CentOS 7 Atomic Host
2. rebase to CAH continuous
3. rollback
4. do a "deploy version" to roll forward agan
5. fatal error

-bash-4.2# atomic host status
  TIMESTAMP (UTC)         VERSION        ID             OSNAME                 REFSPEC                                                              
* 2016-07-07 21:23:41     7.20160707     cd47a72eb5     centos-atomic-host     centos-atomic-host:centos-atomic-host/7/x86_64/standard              
  2016-08-21 21:08:00     7.2016.52      7c655fe8ce     centos-atomic-host     centos-atomic-continuous:centos-atomic-host/7/x86_64/devel/continuous

GPG: Found 1 signature on the booted deployment (*):

  Signature made Thu 07 Jul 2016 09:34:40 PM UTC using RSA key ID F17E745691BA8335
  Good signature from "CentOS Atomic SIG <security@centos.org>"
-bash-4.2# atomic host deploy 7.2016.52
Resolving version '7.2016.52'
...                    
error: No such metadata object 06efd9d78a08a8bec8b5ffb363d3b1918996a06a362080a39aaa69908e9437d0.commit
-bash-4.2# 

[cgwalters]

Hmm, this might be a variation on #27
Though, something that's important to understand here is that the way deploy works, it searches the history of your current branch, not all branches we happen to know about. And centos-atomic-host:centos-atomic-host/7/x86_64/standard vs centos-atomic-continuous:centos-atomic-host/7/x86_64/devel/continuous are different branches. So it's not expected (today) for deploy to switch branches. We obviously should have a useful error here though.

[cgwalters]

I saw this too just now with atomicws - the missing metadata object was for a BaseCommit, and I didn't have any rpmostree/base/ refs.

[cgwalters]

#452 was the fix for the issue I hit. But I'm not sure that's the same as this one.

How reproducible is this?

[jlebon]

@jberkus Can you confirm whether this is still an issue?

[jlebon]

I don't think I've seen this in a while. Closing as stale.