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 1375653 - Add simple signing support to atomic command
Summary: Add simple signing support to atomic command
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: atomic
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
: 1375578 (view as bug list)
Depends On: 1378291
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-13 15:30 UTC by Lokesh Mandvekar
Modified: 2016-11-04 09:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1375578
Environment:
Last Closed: 2016-11-04 09:06:48 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 Lokesh Mandvekar 2016-09-13 15:30:15 UTC 
+++ This bug was initially created as a clone of Bug #1375578 +++

This bugzilla is for a new feature being added to atomic command to allow users to sign OCI and Docker Images, indicating that the image is "trusted" by the signer.
Comment 2 Lokesh Mandvekar 2016-09-13 15:32:57 UTC 
*** Bug 1375578 has been marked as a duplicate of this bug. ***
Comment 4 Alex Jia 2016-09-22 04:42:02 UTC 
See Also: bug 1378291 and bug 1375891.
Comment 5 Alex Jia 2016-09-26 18:59:38 UTC 
1. atomic sign --sign-by testing                          ------ PASS
2. atomic trust show|add|delete|default testing           ------ PASS
3. atomic push --sign-by testing  <---- got questions


3. atomic push testing 

# docker login -p AtwRPnMfIfUP9pRSDZaSSvrOC_K9l8WZEOa0n-2fFqw -e unused -u unused atomic-registry.usersys.redhat.com:5000
WARNING: login credentials saved in /root/.docker/config.json
Login Succeeded


# atomic push --sign-by "" atomic-registry.usersys.redhat.com:5000/ajia/busybox:latest
Registry Username: 

NOTE: it still prompt users to input AUTH info

# atomic push --sign-by ajia atomic-registry.usersys.redhat.com:5000/ajia/busybox:latest
Registry Username: ajia
Registry Password: 
500 Server Error: Internal Server Error ("no successful auth challenge for http://atomic-registry.usersys.redhat.com:5000/v2/ - errors: [token auth attempt for registry http://atomic-registry.usersys.redhat.com:5000/v2/: http://atomic-registry.usersys.redhat.com:5000/openshift/token?account=ajia request failed with status: 401 Unauthorized]")

NOTE: I have successfully login atomic registry, but it still needs to input AUTH info.


In addition, is it enough to verify this bug w/ above 3 testing, thanks.
Comment 7 Martin Jenner 2016-09-27 18:47:12 UTC 
changing state to verified on ddarrah behalf.
Comment 9 errata-xmlrpc 2016-11-04 09:06:48 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.