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.

Bug 1444111

Summary: docker-1.13.1-7.gitcd4c02a.fc27.x86_64 does not pull fedora:25
Product: Red Hat Enterprise Linux 7 Reporter: Jake Hunsaker <jhunsaker>
Component: docker-latestAssignee: Lokesh Mandvekar <lsm5>
Status: CLOSED ERRATA QA Contact: atomic-bugs <atomic-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.3CC: adimania, admiller, amurdaca, ddarrah, dornelas, dwalsh, extras-qa, ichavero, jcajka, jpazdziora, lfriedma, lsm5, lsu, marianne, miminar, nalin, redhat, riek, vbatts
Target Milestone: rcKeywords: Extras, Regression
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: docker-latest-1.13.1-6.gitb7732b0.el7_3 Doc Type: Bug Fix
Doc Text:
Cause: rebasing a patch introduced a bug since a function changed name but we were still using the old one Consequence: unable to pull images with unqualified image name Fix: fix the function usage in code Result: pulling by unqualified image name works again
Story Points: ---
Clone Of: 1439577 Environment:
Last Closed: 2017-05-26 14:53:12 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:
Embargoed:
Bug Depends On: 1439577    
Bug Blocks: 1186913    

Description Jake Hunsaker 2017-04-20 15:18:04 UTC
Cloning to RHEL as we have a customer hitting this on docker-1.13.1-4.

+++ This bug was initially created as a clone of Bug #1439577 +++

Description of problem:

Pulling fedora:25 on rawhide fails.

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

docker-1.13.1-7.gitcd4c02a.fc27.x86_64

How reproducible:

Deterministic.

Steps to Reproduce:
1. dnf install -y docker
2. systemctl start docker
3. docker pull fedora:25

Actual results:

Trying to pull repository docker.io/library/fedora ... 
Trying to pull repository registry.access.redhat.com/fedora ... 
Trying to pull repository docker.io/library/fedora ... 
repository name must be canonical

Expected results:

Trying to pull repository docker.io/library/fedora ... 
sha256:b44cdaee0feafc85cab454e2023807f66725c727655b6bef260aa6d21dd2b068: Pulling from docker.io/library/fedora
bc5187a39b05: Pull complete 
Digest: sha256:b44cdaee0feafc85cab454e2023807f66725c727655b6bef260aa6d21dd2b068
Status: Downloaded newer image for docker.io/fedora:25

Additional info:

This is regression against docker-1.12.6-6.gitae7d637.fc25.x86_64.

--- Additional comment from Antonio Murdaca on 2017-04-10 10:43:10 EDT ---

Fixed by https://github.com/projectatomic/docker/commit/d97e39673ec652aeb58a32ee977a593018e04700

--- Additional comment from Daniel Walsh on 2017-04-10 11:10:59 EDT ---

Do we have a new build?

--- Additional comment from Antonio Murdaca on 2017-04-10 11:15:34 EDT ---

in progress https://koji.fedoraproject.org/koji/buildinfo?buildID=878288

--- Additional comment from Daniel Walsh on 2017-04-10 12:48:19 EDT ---

Fixed in docker-1.13.1-8.gitd97e396.fc27

Comment 7 Antonio Murdaca 2017-04-26 22:13:54 UTC
Fixed in docker-1.13.1

Comment 9 Jan Pazdziora (Red Hat) 2017-04-28 09:15:29 UTC
(In reply to Antonio Murdaca from comment #7)
> Fixed in docker-1.13.1

What is the exact NEVRA? Can you fill in the Fixed In Version field?

I don't see the issue with

docker-client-latest-1.13.1-4.el7.x86_64
docker-common-1.12.6-16.el7.x86_64
docker-latest-1.13.1-4.el7.x86_64
docker-rhel-push-plugin-1.12.6-16.el7.x86_64

Is that expected?

Comment 10 Antonio Murdaca 2017-04-28 10:41:33 UTC
It's fixed in projectatomic/docker repository. I don't know why you aren't seeing this error though, maybe you're running with --signature-verification=false. Lokesh, do you know where a build will be done for 1.13.1?

Comment 11 Jan Pazdziora (Red Hat) 2017-04-28 11:55:48 UTC
(In reply to Antonio Murdaca from comment #10)
> It's fixed in projectatomic/docker repository.

If it's only fixed upstream, the status of the bugzilla should be POST. MODIFIED should be used when the build is in RHEL/Extras dist-git.

> I don't know why you aren't
> seeing this error though, maybe you're running with
> --signature-verification=false.

You are right. It seems to be there by default:

# rpm -Vf /etc/sysconfig/docker-latest
.M.......    /var/lib/docker-latest
# rpm -qf /etc/sysconfig/docker-latest
docker-latest-1.13.1-4.el7.x86_64
# grep signature /etc/sysconfig/docker-latest
OPTIONS='--selinux-enabled --log-driver=journald --signature-verification=false'

Comment 12 Antonio Murdaca 2017-05-01 18:44:41 UTC
Lokesh, please rebuild from docker-1.13.1-rhel

Comment 19 errata-xmlrpc 2017-05-26 14:53:12 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://access.redhat.com/errata/RHBA-2017:1330