-
Bug
-
Resolution: Done
-
Minor
-
None
-
4.15
-
No
-
0
-
OSDOCS Sprint 261
-
1
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
NodeFeatureDiscovery operand image for 4.15 does not exist
Version-Release number of selected component (if applicable):
4.15
How reproducible:
Always
Steps to Reproduce:
1. Copy the operand image from the example. 2. Try to pull the image using Podman `podman pull registry.redhat.io/openshift4/ose-node-feature-discovery:v4.15`
Actual results:
$ podman pull registry.redhat.io/openshift4/ose-node-feature-discovery:v4.15 Trying to pull registry.redhat.io/openshift4/ose-node-feature-discovery:v4.15... Error: initializing source docker://registry.redhat.io/openshift4/ose-node-feature-discovery:v4.15: reading manifest v4.15 in registry.redhat.io/openshift4/ose-node-feature-discovery: manifest unknown
Expected results:
Image pulled successfully
Additional info:
* If you change the tag to the previous OpenShift version, the image exists and can be pulled successfully: registry.redhat.io/openshift4/ose-node-feature-discovery:v4.14 * It looks like the correct image for 4.15 is registry.redhat.io/openshift4/ose-node-feature-discovery-rhel9:v4.15 - notice the `-rhel9` suffix.
- duplicates
-
OCPBUGS-32427 [enterprise-4.15] Issue in file hardware_enablement/psap-node-feature-discovery-operator.adoc
- Closed