Hide Forgot
I didn't debug this really, but: # atomic host status State: transaction: Deploy :1.38 /org/projectatomic/rpmostree1/rhel_atomic_host Deployments: ● rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard Version: 7.2.6 (2016-07-29 19:54:25) Commit: b672bf8a457cb28e003dee20c53749636ef5fce3e4743afe4aaad269d3aaa62a OSName: rhel-atomic-host # atomic host deploy 7.2.7 Resolving version '7.2.7' error: Version 7.2.7 not found in rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard # ostree log rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard|head -10 commit 90c9735becfff1c55c8586ae0f2c904bc0928f042cd4d016e9e0e2edd16e5e97 Date: 2016-10-26 14:24:09 +0000 Version: 7.3 (no subject) commit 347c3f5eb641e69fc602878c646cf42c4bcd5d9f36847a1f24ff8f3ec80f17b1 Date: 2016-09-09 18:43:35 +0000 Version: 7.2.7 (no subject) -bash-4.2# ostree log rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard|head -20 commit 90c9735becfff1c55c8586ae0f2c904bc0928f042cd4d016e9e0e2edd16e5e97 Date: 2016-10-26 14:24:09 +0000 Version: 7.3 (no subject) commit 347c3f5eb641e69fc602878c646cf42c4bcd5d9f36847a1f24ff8f3ec80f17b1 Date: 2016-09-09 18:43:35 +0000 Version: 7.2.7 (no subject) commit dae35767902aad07b087d359be20f234d244da79fdd4734cd2fbc3ee39b12cf8 Date: 2016-08-18 16:01:03 +0000 Version: 7.2.6-1 (no subject) commit b672bf8a457cb28e003dee20c53749636ef5fce3e4743afe4aaad269d3aaa62a Date: 2016-07-29 19:54:25 +0000 Version: 7.2.6 (no subject) # atomic host deploy 347c3f5eb641e69fc602878c646cf42c4bcd5d9f36847a1f24ff8f3ec80f17b1 works.
Hmm, seeing the same thing here on 7.2.6-1. Looking into it!
This is in part due to the interaction with subman. We ship a tree with the remote name "rhel-atomic-host" in the refspec. However, when the subman ostree plugin runs, it installs a remote config file with the remote name "rhel-atomic-host-ostree" and clobbers the active deployment's refspec to use the same remote. This means that we end up with two refspecs for the same branch (one from each remote). Then, due to a bug in the deploy related code, we end up using the old "rhel-atomic-host" ref rather than the newly fetched "rhel-atomic-host-ostree" when resolving versions: https://github.com/projectatomic/rpm-ostree/pull/507
Hmm, might be helpful to ship some doc text to detail a workaround for this (e.g. delete the rhel-atomic-host refs before the deploy operation). Should we also backport the upstream patch for 7.3.1 at least? (Assuming it's too late for 7.3.0).
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.