Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-19824

coreos-bootimages ConfigMap should have 0.0.1-snapshot substituted


    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.15
    • oc / update
    • Moderate
    • No
    • False
    • Hide



      Description of problem:

      In 4.8's installer#4760, the installer began passing oc adm release new ... a manifest so the cluster-version operator would manage a coreos-bootimages ConfigMap in the openshift-machine-config-operator namespace. installer#4797 reported issues with the 0.0.1-snapshot placeholder not getting substituted, and installer#4814 attempted to fix that issue by converting the manifest from JSON to YAML to align with the replacement rexexp. But for reasons I don't understand, that manifest still doesn't seem to be getting replaced.

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

      From 4.8 through 4.15.

      How reproducible:


      Steps to Reproduce:

      With 4.8.0:

      $ oc adm release extract --to manifests quay.io/openshift-release-dev/ocp-release:4.8.0-x86_64
      $ grep releaseVersion manifests/0000_50_installer_coreos-bootimages.yaml

      Actual results:

        releaseVersion: 0.0.1-snapshot

      Expected results:

        releaseVersion: 4.8.0

      or other output that matches the extracted release. We just don't want the 0.0.1-snapshot placeholder.

      Additional info:

      Reproducing in the latest 4.14 RC:

      $ oc adm release extract --to manifests quay.io/openshift-release-dev/ocp-release:4.14.0-rc.2-x86_64
      $ grep releaseVersion manifests/0000_50_installer_coreos-bootimages.yaml
        releaseVersion: 0.0.1-snapshot

            lmohanty@redhat.com Lalatendu Mohanty
            trking W. Trevor King
            Jian Li Jian Li
            0 Vote for this issue
            5 Start watching this issue