Bug 2042732 - DeploymentConfigs ignore resolve-names annotation
Summary: DeploymentConfigs ignore resolve-names annotation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: ImageStreams
Version: 4.6.z
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.8.z
Assignee: Oleg Bulatov
QA Contact: XiuJuan Wang
URL:
Whiteboard:
Depends On: 2040240
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-20 03:14 UTC by OpenShift BugZilla Robot
Modified: 2022-10-12 02:53 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-01 12:44:33 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift openshift-apiserver pull 271 0 None open [release-4.8] Bug 2042732: Make OriginImageMutators aware of origin objects 2022-01-20 09:53:27 UTC
Red Hat Product Errata RHBA-2022:0278 0 None None None 2022-02-01 12:44:50 UTC

Comment 3 XiuJuan Wang 2022-01-24 02:24:29 UTC
Verified on 4.8.0-0.nightly-2022-01-21-182704

Scenario:
$oc tag docker.io/library/nginx:latest myis:latest
$oc apply -f - <<END
apiVersion: v1
kind: DeploymentConfig
metadata:
  name: mydc
spec:
  replicas: 1
  selector:
    app: mydc
  template:
    metadata:
      annotations:
        alpha.image.policy.openshift.io/resolve-names: '*'
      labels:
        app: mydc
    spec:
      containers:
      - image: myis
        name: mycontainer
END

$oc get dc mydc -o jsonpath='{.spec.template.spec.containers[*].image}{"\n"}'

docker.io/library/nginx@sha256:ee89b00528ff4f02f2405e4ee221743ebc3f8e8dd0bfd5c4c20a2fa2aaa7ede3

Comment 6 errata-xmlrpc 2022-02-01 12:44:33 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 (OpenShift Container Platform 4.8.29 bug fix update), 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-2022:0278


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