Bug 1391788

Summary: atomic will remove /etc/containers/ after updating
Product: Red Hat Enterprise Linux 7 Reporter: Alex Jia <ajia>
Component: atomicAssignee: Jindrich Novy <jnovy>
Status: CLOSED WONTFIX QA Contact: atomic-bugs <atomic-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 7.4CC: amurdaca, dwalsh
Target Milestone: rcKeywords: Extras, Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-15 07:28:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1389677    
Bug Blocks: 1381736    

Description Alex Jia 2016-11-04 03:29:15 UTC
Description of problem:
When updating atomic RPMs package by rpm -Uvh, the /etc/containers/ will be removed from RHELAH, it will cause many issues such as failure to pull images by atomic(skopeo copy).

Version-Release number of selected component (if applicable):

[root@atomic-host-001 cloud-user]# cat /etc/redhat-release 
Red Hat Enterprise Linux Atomic Host release 7.3

[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 docker skopeo
atomic-1.12.5-2.el7.x86_64
docker-1.10.3-57.el7.x86_64
skopeo-0.1.14-0.6.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. deploy rhel-atomic-cloud-7.3.0-3.x86_64 image in virtual environment and start it
2. download latest skopeo and atomic PRMs packages from brew system
3. rpm -Uvh skopeo* atomic*

Actual results:

[root@atomic-host-001 cloud-user]# ls /etc/containers/
policy.json  registries.d

[root@atomic-host-001 cloud-user]# ls /etc/containers/registries.d/
default.yaml

[root@atomic-host-001 cloud-user]# rpm -Uvh skopeo-0.1.17-0.5.git1f655f3.el7.x86_64.rpm 
Preparing...                          ################################# [100%]
Updating / installing...
   1:skopeo-1:0.1.17-0.5.git1f655f3.el################################# [ 50%]
Cleaning up / removing...
   2:skopeo-1:0.1.14-0.6.el7          ################################# [100%]

[root@atomic-host-001 cloud-user]# ls /etc/containers/
registries.d

NOTE: the /etc/containers/policy.json file is deleted after updating skopeo,
the subsequent atomic pull(skopeo copy) will try to open the file. 
 
[root@atomic-host-001 cloud-user]# rpm -Uvh atomic-1.13.7-2.el7.x86_64.rpm 
Preparing...                          ################################# [100%]
Updating / installing...
   1:atomic-1:1.13.7-2.el7            ################################# [ 50%]
Cleaning up / removing...
   2:atomic-1:1.12.5-2.el7            ################################# [100%]

[root@atomic-host-001 cloud-user]# ls /etc/containers/
ls: cannot access /etc/containers/: No such file or directory

NOTE: the whole /etc/containers/ is deleted after updating atomic. 

Expected results:

We should fix it in 7.3.1

Additional info:

Please also see bug 1381736

Comment 2 Daniel Walsh 2016-11-04 12:01:51 UTC
Lokesh any idea what is causing this?

Comment 3 Daniel Walsh 2016-11-04 12:03:31 UTC
Looks like skopeo-containers owns that file.

Comment 4 Antonio Murdaca 2016-11-04 12:28:54 UTC
Yeah, skopeo-containers should be an atomic dependency now. Isn't it the case?

Comment 5 Lokesh Mandvekar 2017-01-18 18:54:33 UTC
atomic does require skopeo-containers at build time. I'll look into it.

Comment 8 RHEL Program Management 2021-01-15 07:28:16 UTC
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.