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.
Bug 1346929 - unhelpful error message using 'atomic pull' - ('Connection aborted.', gaierror(-2, 'Name or service not known'))
Summary: unhelpful error message using 'atomic pull' - ('Connection aborted.', gaierro...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: atomic
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Daniel Walsh
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-15 16:30 UTC by Micah Abbott
Modified: 2016-11-04 09:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 09:06:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2628 0 normal SHIPPED_LIVE atomic bug fix and enhancement update 2016-11-03 18:17:14 UTC

Description Micah Abbott 2016-06-15 16:30:08 UTC 
atomic-1.10.5-3.el7.x86_64

Trying to pull an image from the registry using just the name, I see the following:

# atomic pull rhel7/rsyslog
('Connection aborted.', gaierror(-2, 'Name or service not known'))


I'm guessing it is due to the V1 registry.

Perhaps BZ1346619 is related?
Comment 1 Lokesh Mandvekar 2016-06-15 16:42:21 UTC 
I get the same error as in Bug 1343939#c3
Comment 2 Lokesh Mandvekar 2016-06-15 16:48:11 UTC 
(In reply to Lokesh Mandvekar from comment #1)
> I get the same error as in Bug 1343939#c3

This was on rhel 7.2, but on atomic host I can reproduce the issue Micah reported.
Comment 4 Daniel Walsh 2016-06-15 17:35:13 UTC 
Micah try

atomic pull docker:rhel7/rsyslog

The default is currently to pull from ostree.  We have a trello card on this.

https://trello.com/c/Ze2BVEnj/149-3-update-documentation-and-cli-errors-help-message-for-atomic-pull
Comment 5 Micah Abbott 2016-06-15 17:59:41 UTC 
# atomic pull docker:rhel7/rsyslog
Error response from daemon: digest not found

# atomic --version
1.10.5
Comment 6 Daniel Walsh 2016-06-15 18:25:21 UTC 
What does

docker pull rhel7/rsyslog

Give you?
Comment 7 Micah Abbott 2016-06-15 18:32:40 UTC 
# docker pull rhel7/rsyslog
Using default tag: latest
Trying to pull repository registry.access.redhat.com/rhel7/rsyslog ... 
Pulling repository registry.access.redhat.com/rhel7/rsyslog
812347e6911f: Pull complete 
c453594215e4: Already exists 
Status: Downloaded newer image for registry.access.redhat.com/rhel7/rsyslog:latest
registry.access.redhat.com/rhel7/rsyslog: this image was pulled from a legacy registry.  Important: This registry version will not be supported in future versions of docker.
Comment 8 Giuseppe Scrivano 2016-06-22 15:14:21 UTC 
should be fixed with this:

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


bash-4.2# atomic pull rhel7/rsyslog

Unable to interact with a V1 registry.
Comment 9 Daniel Walsh 2016-08-19 22:04:16 UTC 
Fixed in atomic-1.11
Comment 11 Alex Jia 2016-09-18 03:27:56 UTC 
(In reply to Daniel Walsh from comment #9)
> Fixed in atomic-1.11

There is no atomic-1.11 in RHEL7, it works in the latest atomic-1.12.2-2.el7.x86_64.

# atomic pull rhel7/rsyslog
Image rhel7/rsyslog is being pulled to ostree ...
Pulling layer 5bff4c7815612c6776a5e2ddc79b6375fdee9216ede8194d1a1655e844ab2cd4
Pulling layer 99dd41655d8a45c2fb74f9eeb73e327b3ad4796f0ff0d602c575e32e9804baed
Pulling layer 30cf2e26a24f2a8426cbe8444f8af2ecb7023bd468b05c1b6fd0b2797b0f9ff9

# atomic images list | grep rsyslog
   rhel7/rsyslog                                                          latest   01fb001f4305   2016-09-18 11:26                  system
Comment 15 errata-xmlrpc 2016-11-04 09:06:19 UTC 
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-2628.html
Note You need to log in before you can comment on or make changes to this bug.