Bootstrap Ignition Config - failing for azure installation

[japecci]

FATAL failed to fetch Bootstrap Ignition Config: failed to fetch dependency of "Bootstrap Ignition Config": failed to fetch dependency of "Worker Machines": failed to generate asset "Release": stable/x86_64: No azure build found

This message is occurring with 4.15, 4.16-scos, and 4.17-scos

Anyone know how to install the new 4.17-scos on azure. I'm using a custom config file and have uploaded my FCOS image 39.20231101.3.0 to azure. Use the ENV var for override OPENSHIFT_INSTALL_OS_IMAGE_OVERRIDE

[krzysztofpolito]

I'm having the same problem. Image "fedora-coreos-39.20231101.3.0-azure.x86_64.vhd" is uploaded as blob to azure, the URL set as OPENSHIFT_INSTALL_OS_IMAGE_OVERRIDE value. It is used, because in the log of openshift-installer I can see:
level=warning msg="Found override for OS Image. Please be warned, this is not advised".

$ ./openshift-install version
./openshift-install 4.17.0-okd-scos.0
built from commit e09aaf186494231de92bd80f02a43db764bd5e27
release image quay.io/okd/scos-release@sha256:a4c786872daa033c942a56ee437b52b1546abfe5f546754845b805a7cff6c0c4
WARNING Release Image Architecture not detected. Release Image Architecture is unknown
release architecture unknown
default architecture amd64

Attaching full log. Please help.
.openshift_install.log

[voipAsteriskGuy]

Hi @japecci @krzysztofpolito I tried the same procedure as you said, and maid it work changing the installing options.
Prooved it on single node cluster, multinode cluster with only 3 control plane and multinode cluster with 3 control plane and 3 workers. tried with version 4.17-scos

These are the steps i followed, let me know if someone test this or if have any doubt about this changes.

1.- edit the file in data/data/coreos/fcos.json and add the azure-disk as recomended in the openshift/installer#4986

2.- just take note that the "release" parameter must be different, it works with something like 39.20231101.30000.0 this is because the validation of the release format at the installation phase.

3.- in hack/build.sh instead of add the tag "okd" must specify the tag "scos" this is to avoid an issue in the fcos bootstrap process to scos.

4.- execute the ./hack/build.sh

5.- add the OPENSHIFT_INSTALL_OS_IMAGE_OVERRIDE as openshift/installer#4986

6.- make the installation process as described in the documentation.

[krzysztofpolito]

Hi @voipAsteriskGuy , thanks for replying.
Which exact OKD version have you installed using this method?

[voipAsteriskGuy]

Hi! @krzysztofpolito the version was:
4.17.0-okd-scos.0
from the ./openshift-install version command:
release image quay.io/okd/scos-release@sha256:a4c786872daa033c942a56ee437b52b1546abfe5f546754845b805a7cff6c0c4

[krzysztofpolito]

Hi @voipAsteriskGuy sorry for pushing, but it's still unclear to me. I assume that you've used the original openshift installer repo (https://github.com/openshift/installer) and branch origin/release-4.17 on it.
In the data/data/coreos/fcos.json, where exactly you added the "rhel-coreos-extensions" json part? Maybe you could attach here the whole modified file (and also the modified hack/build.sh)?
I would be grateful, because I'm struggling with this issue for quite some time.

[voipAsteriskGuy]

Hi @krzysztofpolito, yes i used the installer from https://github.com/openshift/installer and branch origin/release-4.17

in data/data/coreos/fcos.json you have to add rhel-coreos-extensions at the level of artifacts inside x86_64, it shoud look like this:

  "architectures": {
        "x86_64": {
            "rhel-coreos-extensions": {
                "azure-disk": {
                    "release": "39.20231101.30000.0",
                    "url": "https://route/to/fcosimage.vhd"
                }
            },
            "artifacts": {
.
.
.
            },
            "images": {
.
.
.  
            }
}

and in hack/build.sh search for the definition of TAGS and add scos at the end like this:

TAGS="${TAGS:-} scos"