Description of problem: Incorrect upstream-version label "v1.6.0-unstable-410-g09ea881c" is tagged to 4.12 hyperconverged-cluster-operator-container and hyperconverged-cluster-webhook-container. Version-Release number of selected component (if applicable): CNV HCO v4.12.0-769 hyperconverged-cluster-operator v4.12.0-96 How reproducible: 100% Steps to Reproduce: 1. $ oc image info registry-proxy.engineering.redhat.com/rh-osbs/container-native-virtualization-hyperconverged-cluster-operator:v4.12.0-96 --filter-by-os linux/amd64 -o json | jq '.config.config.Labels."upstream-version"' "v1.6.0-unstable-410-g09ea881c" 2. 3. Actual results: Incorrect upstream-version label "v1.6.0-unstable-410-g09ea881c" is tagged to 4.12 hyperconverged-cluster-operator-container and hyperconverged-cluster-webhook-container. Expected results: the build should tag 1.8.0-unstable as upstream version label. Additional info:
Rebuilt to get the correct upstream git tag for HCO images.
Verified via version explorer against build 4.12.0-796 which has HCO v4.12.0-96 I see correct upstream tag: v1.8.0-unstable
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 (Important: OpenShift Virtualization 4.12.0 Images security 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/RHSA-2023:0408