Customer wants to boot a VM using the Assisted Installer ISO. The customer originally installed the OpenShift Container Platform cluster using version 4.13, however in the meantime the cluster was updated to 4.16.

As a result, the customer updated the field "osImageVersion" to "4.16.11". This lead to the new ISO being generated as expected. However, when reviewing the "status" of the InfraEnv, they can still see the following URL:

~~~
  isoDownloadURL: 'https://assisted-image-service-multicluster-engine.cluster.example.com/byapikey/<REDACTED>/4.13/x86_64/minimal.iso' 
~~~

Other artifacts are also still showing "?version=4.13":

~~~
    kernel: 'https://assisted-image-service-multicluster-engine.cluster.example.com/boot-artifacts/kernel?arch=x86_64&version=4.13'     rootfs: 'https://assisted-image-service-multicluster-engine.cluster.example.com/boot-artifacts/rootfs?arch=x86_64&version=4.13' 
~~~

Workaround is to downloading the ISO by replacing the version and works as expected.

RHACM 2.10
OpenShift Container Platform 4.16.11

Always at customer side

    1. Create a cluster with an InfraEnv with the "osImageVersion" set to 4.14 (or 4.13)
    2. Update the cluster to the next OpenShift Container Platform version
    3. Update the InfraEnv "osImageVersion" field with the new version (you may need to create the ClusterImageSet)

URLs in the "status" of the InfraEnv are not updated with the new version    

URLs in the "status" of the InfraEnv are updated with the new version

* Discussion in Slack: https://redhat-internal.slack.com/archives/CUPJTHQ5P/p1726483803662359