Bug 1883205 - The redis-32-rhel7 image is not signed
Summary: The redis-32-rhel7 image is not signed
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: redis
Version: unspecified
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: alpha
: 3.6
Assignee: Remi Collet
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-28 12:21 UTC by Shannon Poole
Modified: 2024-03-25 16:36 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-29 15:32:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Shannon Poole 2020-09-28 12:21:15 UTC
Description of problem:

When attempting to deploy the Redis image on openshift with Signature Verification Enabled, it fails with the following message:

> Failed to pull image "registry.redhat.io/rhscl/redis-32-rhel7@sha256:a9bdf52384a222635efc0284db47d12fbde8c3d0fcb66517ba8eefad1d4e9dc9":
>               rpc error: code = Unknown desc = Source image rejected: A signature was required, but no signature exists

It appears that this image is not signed.

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


How reproducible: Always


Steps to Reproduce:
1. Enable Signature Verification in OCP
2. Attempt to deploy registry.redhat.io/rhscl/redis-32-rhel7
3. Observe error

Actual results:
Pod fails to deploy with the above error


Expected results:
Pod should deploy with out error


Additional info:
This image is deployed as part of the Red Hat API Management (3scale) product

Comment 4 Joe Orton 2020-10-29 15:32:59 UTC
The redis 3.2 image is obsoleted since Redis 3.2 in RHSCL was retired in November 2019, see: 
https://access.redhat.com/support/policy/updates/rhscl-rhel7

The Redis 5 image appears to be correctly signed:

https://catalog.redhat.com/software/containers/rhscl/redis-5-rhel7

if the existence of the 3.2 image still blocks use of Quay that needs to be escalated some other way.


Note You need to log in before you can comment on or make changes to this bug.