Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Critical
Fix Version/s: quay-v3.7.9
Affects Version/s: quay-v3.7.4
Component/s: quay
Labels:
- triaged

Blocked:
False
Blocked Reason:
None
Ready:
False
Product:
Quay Enterprise
Release Note Type:
Known Issue
Steps to Reproduce:
Hide

Here are the steps followed by customer:

1. I spawned a LAB with OCS on OpenTLC, then installed OCS Operator and Quay Operator.
> Everything with default values.

2. I created a user in Quay.

3. I pulled 3 images from microsoft from the bastion :

podman pull mcr.microsoft.com/dotnet/aspnet:6.0

podman pull mcr.microsoft.com/dotnet/aspnet:6.0-alpine

podman pull mcr.microsoft.com/dotnet/aspnet@sha256:1f6a6f9e939fc75dccd50133e2ef8fb4a8ac1006d1b50b6e6efcde1e3b88a6fc

4. I retagged and pushed them in the repo of the user I created.

5. And after that it's pretty much sit back and relax.
Show
Here are the steps followed by customer: 1. I spawned a LAB with OCS on OpenTLC, then installed OCS Operator and Quay Operator. > Everything with default values. 2. I created a user in Quay. 3. I pulled 3 images from microsoft from the bastion : podman pull mcr.microsoft.com/dotnet/aspnet:6.0 podman pull mcr.microsoft.com/dotnet/aspnet:6.0-alpine podman pull mcr.microsoft.com/dotnet/aspnet@sha256:1f6a6f9e939fc75dccd50133e2ef8fb4a8ac1006d1b50b6e6efcde1e3b88a6fc 4. I retagged and pushed them in the repo of the user I created. 5. And after that it's pretty much sit back and relax.

Target Version:

quay-v3.7.9

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Clair notification is not working. Clair pod's log shows error:
~~~

{"level":"error","deliverer":"webhook","component":"notifier/Delivery.Deliver","error":"failed to deliver notification: code: 400 status 400 Bad request","time":"2022-06-02T15:22:21Z","message":"encountered error on tick"}

~~~
Quay pod's log shows error:
~~~
nginx stdout | 10.81.10.2 () - - [02/Jun/2022:15:22:01 +0000] "POST /secscan/notification HTTP/1.1" 400 173 "-" "clair/v4" (0.001 465 -)
~~~