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:
The image naming looks like 'sha256:XXXXX' in atomic, but set_scanner() in Atomic/scan.py replaces ':' with '-', the result is atomic scan can't match any image.

Version-Release number of selected component (if applicable):
# rpm -q atomic docker
atomic-1.10.3-2.el7.x86_64
docker-1.10.3-31.el7.x86_64

# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.2 (Maipo)


How reproducible:
always

Steps to Reproduce:
1. atomic install rhel7
2. atomic scan --verbose <rhel7 image id>


Actual results:

# atomic images|grep rhel7
  registry.access.redhat.com/rhel7/rhel-tools           latest   sha256:00211   2016-05-06 17:49   1.27 GB       
  registry.access.redhat.com/rhel7                      latest   sha256:bf203   2016-05-05 12:43   203.43 MB     

# atomic scan --verbose sha256:bf203
sha256-bf203442783741aad6d82b528bcfecd45f40e63c83d981eb5e644a2fa6356e60 did not match any image or container.


Expected results:


Additional info:

I commit a PR to fix this: https://github.com/projectatomic/atomic/pull/415

with the build currently in errata, I'm seeing this:

$ sudo atomic images
global name 'OSTree' is not definedn

Looks like this one got fixed at least. FWIW, I don't get the "did not match any image or container" error anymore. Rather the error I see is the same as Bug 1347037.

Alex could you please check and possibly move this to VERIFIED

(In reply to Lokesh Mandvekar from comment #5)
> Alex could you please check and possibly move this to VERIFIED


Sure, I'm checking and retest.

atomic scan works well w/ image id or full quality image name on  atomic-1.10.5-5.el7.x86_64, so moving the bug to VERIFIED status.

(In reply to Alex Jia from comment #6)
> (In reply to Lokesh Mandvekar from comment #5)
> > Alex could you please check and possibly move this to VERIFIED
> 
> 
> Sure, I'm checking and retest.

thanks to your patch actually.

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-2016:1273