Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Instantiate an untagged Docker images as a container. Most atomic commands stop working and exit with "'NoneType' object is not iterablen"
Version-Release number of selected component (if applicable):
atomic-1.10.5-7.el7.x86_64
How reproducible:
Very
Steps to Reproduce:
1. Run any atomic command that looks at the Docker image cache - For example "atomic diff"
2. See below
3.
With untagged image:
[root@master ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
registry.access.redhat.com/openshift3/ose-pod v3.2.1.17 2d461a3c1330 11 days ago 213.9 MB
registry.access.redhat.com/rhel7/openscap latest fe6f007ba9df 6 weeks ago 362.8 MB
registry.access.redhat.com/openshift3/metrics-heapster 3.2.1 4ab10acec2e5 7 weeks ago 282.4 MB
172.30.0.2:5000/mydemo-1/ticket-monster <none> 3c4082b2f3ab 10 weeks ago 1.275 GB
registry.access.redhat.com/openshift3/ose-haproxy-router v3.2.1.7 8f6c7a324335 3 months ago 498.6 MB
registry.access.redhat.com/openshift3/ose-docker-registry v3.2.1.7 876af4879111 3 months ago 527.8 MB
registry.access.redhat.com/openshift3/metrics-hawkular-metrics 3.2.1 219e26f45297 4 months ago 1.463 GB
registry.access.redhat.com/openshift3/metrics-cassandra 3.2.1 afeae5fccd3f 4 months ago 836 MB
[root@master ~]# atomic diff registry.access.redhat.com/openshift3/ose-pod:v3.2.1.17 registry.access.redhat.com/openshift3/ose-pod:v3.2.1.17 -v
'NoneType' object is not iterablen[root@master ~]#
Without untagged image:
[root@master ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
registry.access.redhat.com/openshift3/ose-pod v3.2.1.17 2d461a3c1330 11 days ago 213.9 MB
registry.access.redhat.com/rhel7/openscap latest fe6f007ba9df 6 weeks ago 362.8 MB
registry.access.redhat.com/openshift3/metrics-heapster 3.2.1 4ab10acec2e5 7 weeks ago 282.4 MB
registry.access.redhat.com/openshift3/ose-haproxy-router v3.2.1.7 8f6c7a324335 3 months ago 498.6 MB
registry.access.redhat.com/openshift3/ose-docker-registry v3.2.1.7 876af4879111 3 months ago 527.8 MB
registry.access.redhat.com/openshift3/metrics-hawkular-metrics 3.2.1 219e26f45297 4 months ago 1.463 GB
registry.access.redhat.com/openshift3/metrics-cassandra 3.2.1 afeae5fccd3f 4 months ago 836 MB
[root@master ~]# atomic diff registry.access.redhat.com/openshift3/ose-pod:v3.2.1.17 registry.access.redhat.com/openshift3/ose-pod:v3.2.1.17 -v
There are no file differences between registry.access.redhat.com/openshift3/ose-pod:v3.2.1.17 and registry.access.redhat.com/openshift3/ose-pod:v3.2.1.17
Additional info:
Comment 5RHEL Program Management
2020-12-15 07:48:27 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.