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.
Hello,
during E2E-Container test of production release architecture[1] there were several failures of Atomic Pull from the Live repository (between 2018-05-26 and 2018-05-28). It's hard to find the cause of these failures. In previous cases there was some error message pointing to TCP failures, but in this case the exception was empty (e == '').
Could you take a look on this and improve error logging?
Thanks,
Pavel
Log:
"""
...
018-05-28T06:01:24+00:00 run_command INFO ssh root.bos.redhat.com /usr/bin/time -v sudo atomic --debug pull registry.access.redhat.com/e2e-container/e2e-container-test-product:7.5-89
2018-05-28T06:01:40+00:00 run_command INFO stdout:Namespace(_class=<class 'Atomic.pull.Pull'>, assumeyes=False, debug=True, func='pull_image', ignore=False, image='registry.access.redhat.com/e2e-container/e2e-container-test-product:7.5-89', profile=False, reg_type=None, src_creds=None, storage=None)
2018-05-28T06:01:40+00:00 run_command INFO stderr:Failed:
2018-05-28T06:01:40+00:00 run_command INFO stderr:Traceback (most recent call last):
2018-05-28T06:01:40+00:00 run_command INFO stderr:File "/bin/atomic", line 185, in <module>
2018-05-28T06:01:40+00:00 run_command INFO stderr:sys.exit(_func())
2018-05-28T06:01:40+00:00 run_command INFO stderr:File "/usr/lib/python2.7/site-packages/Atomic/pull.py", line 64, in pull_image
2018-05-28T06:01:40+00:00 run_command INFO stderr:raise ValueError("Failed: {}".format(e))
2018-05-28T06:01:40+00:00 run_command INFO stderr:ValueError: Failed:
2018-05-28T06:01:40+00:00 run_command INFO stderr:Command exited with non-zero status 1
"""
[1] http://mushroom.eng.bos.redhat.com/E2E-Container/
Atomic Pull Live keeps failing randomly (no error message).
Comment 4Giuseppe Scrivano
2018-06-07 16:23:48 UTC
I am not able to reproduce this issue (I've tried to block the connections while fetching the image) but inspecting the code this looks like the only place where an empty exception can happen:
https://github.com/projectatomic/atomic/pull/1239
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://access.redhat.com/errata/RHBA-2018:2795
Hello, during E2E-Container test of production release architecture[1] there were several failures of Atomic Pull from the Live repository (between 2018-05-26 and 2018-05-28). It's hard to find the cause of these failures. In previous cases there was some error message pointing to TCP failures, but in this case the exception was empty (e == ''). Could you take a look on this and improve error logging? Thanks, Pavel Log: """ ... 018-05-28T06:01:24+00:00 run_command INFO ssh root.bos.redhat.com /usr/bin/time -v sudo atomic --debug pull registry.access.redhat.com/e2e-container/e2e-container-test-product:7.5-89 2018-05-28T06:01:40+00:00 run_command INFO stdout:Namespace(_class=<class 'Atomic.pull.Pull'>, assumeyes=False, debug=True, func='pull_image', ignore=False, image='registry.access.redhat.com/e2e-container/e2e-container-test-product:7.5-89', profile=False, reg_type=None, src_creds=None, storage=None) 2018-05-28T06:01:40+00:00 run_command INFO stderr:Failed: 2018-05-28T06:01:40+00:00 run_command INFO stderr:Traceback (most recent call last): 2018-05-28T06:01:40+00:00 run_command INFO stderr:File "/bin/atomic", line 185, in <module> 2018-05-28T06:01:40+00:00 run_command INFO stderr:sys.exit(_func()) 2018-05-28T06:01:40+00:00 run_command INFO stderr:File "/usr/lib/python2.7/site-packages/Atomic/pull.py", line 64, in pull_image 2018-05-28T06:01:40+00:00 run_command INFO stderr:raise ValueError("Failed: {}".format(e)) 2018-05-28T06:01:40+00:00 run_command INFO stderr:ValueError: Failed: 2018-05-28T06:01:40+00:00 run_command INFO stderr:Command exited with non-zero status 1 """ [1] http://mushroom.eng.bos.redhat.com/E2E-Container/