Hide Forgot
It works well for me now, please see the following details. [root@atomic-host-001 cloud-user]# atomic host status State: idle Deployments: ● rhel-atomic-host:rhel-atomic-host/7/x86_64/standard Version: 7.3 (2016-10-26 14:24:09) Commit: 90c9735becfff1c55c8586ae0f2c904bc0928f042cd4d016e9e0e2edd16e5e97 OSName: rhel-atomic-host GPGSignature: (unsigned) Unlocked: development [root@atomic-host-001 cloud-user]# rpm -q atomic skopeo docker atomic-1.12.5-2.el7.x86_64 skopeo-0.1.14-0.6.el7.x86_64 docker-1.10.3-57.el7.x86_64 [root@atomic-host-001 cloud-user]# rpm -Uvh skopeo-0.1.17-0.4.git550a480.el7.x86_64.rpm Preparing... ################################# [100%] Updating / installing... 1:skopeo-1:0.1.17-0.4.git550a480.el################################# [ 50%] Cleaning up / removing... 2:skopeo-1:0.1.14-0.6.el7 ################################# [100%] [root@atomic-host-001 cloud-user]# rpm -Uvh atomic-1.13.3-1.el7.x86_64.rpm Preparing... ################################# [100%] Updating / installing... 1:atomic-1:1.13.3-1.el7 ################################# [ 50%] Cleaning up / removing... 2:atomic-1:1.12.5-2.el7 ################################# [100%] [root@atomic-host-001 cloud-user]# rpm -q atomic skopeo atomic-1.13.3-1.el7.x86_64 skopeo-0.1.17-0.4.git550a480.el7.x86_64
Just a record, I met many warning in another RHELAH 7.3 when update atomic and skopeo RPM pacakges w/ AH unlock mode. Lokesh, it seems we also need to fix these. [root@atomic-host-001 cloud-user]# rpm -q atomic skopeo atomic-1.12.5-2.el7.x86_64 skopeo-0.1.14-0.6.el7.x86_64 [root@atomic-host-001 cloud-user]# rpm -Uvh skopeo-0.1.17-0.4.git550a480.el7.x86_64.rpm atomic-1.13.3-1.el7.x86_64.rpm Preparing... ################################# [100%] Updating / installing... 1:skopeo-1:0.1.17-0.4.git550a480.el################################# [ 25%] 2:atomic-1:1.13.3-1.el7 ################################# [ 50%] Cleaning up / removing... 3:atomic-1:1.12.5-2.el7 warning: file /etc/containers/registries.d/default.yaml: remove failed: No such file or directory ################################# [ 75%] 4:skopeo-1:0.1.14-0.6.el7 warning: file /etc/containers/registries.d: remove failed: No such file or directory warning: file /etc/containers/policy.json: remove failed: No such file or directory warning: file /etc/containers: remove failed: No such file or directory ################################# [100%] [root@atomic-host-001 cloud-user]# rpm -q atomic skopeo atomic-1.13.3-1.el7.x86_64 skopeo-0.1.17-0.4.git550a480.el7.x86_64
(In reply to Alex Jia from comment #4) > Just a record, I met many warning in another RHELAH 7.3 when update atomic > and skopeo RPM pacakges w/ AH unlock mode. This isn't something that we would recommend customers do for the atomic/skopeo packages, since they are delivered as part of the ostree compose. Having said that, I tried this using RHELAH 7.3 and the versions of atomic/skopeo that are shipping in 7.3.1 and did not encounter the issue described in comment#4. # atomic host status State: idle Deployments: ● rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard Version: 7.3 (2016-10-26 14:24:09) Commit: 90c9735becfff1c55c8586ae0f2c904bc0928f042cd4d016e9e0e2edd16e5e97 OSName: rhel-atomic-host # rpm -q atomic skopeo atomic-1.12.5-2.el7.x86_64 skopeo-0.1.14-0.6.el7.x86_64 # ostree admin unlock Development mode enabled. A writable overlayfs is now mounted on /usr. All changes there will be discarded on reboot. # rpm -Uhv atomic-1.13.8-1.el7.x86_64.rpm skopeo-0.1.17-0.7.git1f655f3.el7.x86_64.rpm skopeo-containers-0.1.17-0.7.git1f655f3.el7.x86_64.rpm Preparing... ################################# [100%] Updating / installing... 1:skopeo-containers-1:0.1.17-0.7.gi################################# [ 20%] 2:skopeo-1:0.1.17-0.7.git1f655f3.el################################# [ 40%] 3:atomic-1:1.13.8-1.el7 ################################# [ 60%] Cleaning up / removing... 4:atomic-1:1.12.5-2.el7 ################################# [ 80%] 5:skopeo-1:0.1.14-0.6.el7 ################################# [100%]
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2866.html