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:
When list of images are empty, atomic images will hit a python error 'max() arg is an empty sequence', which is not friendly for users.

Version-Release number of selected component (if applicable):
# rpm -q atomic docker
atomic-1.7-3.git95b28a9.el7.x86_64
docker-1.9.1-9.el7.x86_64

How reproducible:
always.

Steps to Reproduce:
1. make sure no avaiable images in docker
2. atomic images

Actual results:
# docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE

# atomic images
max() arg is an empty sequence

Expected results:
# atomic images
There are no images available.

Additional info:

https://github.com/projectatomic/atomic/pull/260

Fixed in atomic-1.8

This issue has been fixed by the atomic-1.8-3.git958d939.el7 and works well on latest atomic-1.9-4.gitff44c6a.el7.x86_64, so moving the bug to VERIFIED status.

# rpm -q atomic docker python-docker-py
atomic-1.8-3.git958d939.el7.x86_64
docker-1.9.0-9.el7.x86_64
python-docker-py-1.6.0-1.el7.x86_64

[root@hp-dl360g9-03 ~]# atomic images
[root@hp-dl360g9-03 ~]# echo $?
0


[root@hp-dl360g9-03 ~]# rpm -q atomic docker python-docker-py
atomic-1.9-4.gitff44c6a.el7.x86_64
docker-1.9.1-19.el7.x86_64
python-docker-py-1.7.2-1.el7.noarch


[root@hp-dl360g9-03 ~]# atomic images
[root@hp-dl360g9-03 ~]# echo $?
0

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-0527.html