No upgrade possibility from 4.8.0-0.okd-2023-07-28-033101 to any stable version?

[doman18]

I need to test full upgrade from openshift-4.8.0-0.okd-2021-10-24-061736 up to most recent stable version (4.15?). I've installed cluster (3 control planes + 2 workers) on Virtualbox on my laptop with this installer

https://github.com/okd-project/okd/releases/download/4.8.0-0.okd-2021-10-24-061736/openshift-install-linux-4.8.0-0.okd-2021-10-24-061736.tar.gz

and this image
https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/34.20211031.3.0/x86_64/fedora-coreos-34.20211031.3.0-metal.x86_64.raw.xz

But i got 4.8.0-0.okd-2023-07-28-033101 version instead. And now i cannot upgrade it further. I tied to set channel from "stable-4" to "stable-4.8" or "stable-4.9" but there is no available upgrades.

$ oc adm upgrade
Cluster version is 4.8.0-0.okd-2023-07-28-033101

No updates available. You may force an upgrade to a specific release image, but doing so may not be supported and result in downtime or data loss.
$ oc adm upgrade channel stable-4.9
Cluster version is 4.8.0-0.okd-2023-07-28-033101

No updates available. You may force an upgrade to a specific release image, but doing so may not be supported and result in downtime or data loss.

apiVersion: config.openshift.io/v1
kind: ClusterVersion
metadata:
  creationTimestamp: '2024-07-22T06:58:20Z'
  generation: 4
  name: version
  resourceVersion: '336991'
  uid: c222e21a-e791-4e5f-ba05-a71dec4e9ec3
spec:
  channel: stable-4.9
  clusterID: 673679d6-b526-4c8b-b31c-a31ad16e0cdb
  upstream: 'https://amd64.origin.releases.ci.openshift.org/graph'
status:
  availableUpdates: null
  conditions:
    - lastTransitionTime: '2024-07-22T08:16:32Z'
      message: Done applying 4.8.0-0.okd-2023-07-28-033101
      status: 'True'
      type: Available
    - lastTransitionTime: '2024-07-23T12:32:40Z'
      status: 'False'
      type: Failing
    - lastTransitionTime: '2024-07-22T08:16:32Z'
      message: Cluster version is 4.8.0-0.okd-2023-07-28-033101
      status: 'False'
      type: Progressing
    - lastTransitionTime: '2024-07-22T12:13:34Z'
      status: 'True'
      type: RetrievedUpdates
  desired:
    image: >-
      registry.ci.openshift.org/origin/release@sha256:8f1fbc72928a22543985a5b61f0504662a084391ecb5967a1555eb9e7923b4b4
    version: 4.8.0-0.okd-2023-07-28-033101
  history:
    - completionTime: '2024-07-22T08:16:32Z'
      image: >-
        registry.ci.openshift.org/origin/release@sha256:8f1fbc72928a22543985a5b61f0504662a084391ecb5967a1555eb9e7923b4b4
      startedTime: '2024-07-22T06:58:23Z'
      state: Completed
      verified: false
      version: 4.8.0-0.okd-2023-07-28-033101
  observedGeneration: 4
  versionHash: 7pMi_YTn3bY=

EDIT
Ok following this link im trying to "upgrade/downgrade" to desired version (fingers crossed)
https://github.com/okd-project/okd/blob/master/FAQ.md#how-do-i-find-a-valid-upgrade-path

oc adm upgrade --force --allow-explicit-upgrade=true --to-image=registry.ci.openshift.org/origin/release:4.8.0-0.okd-2021-10-24-061736
warning: Using by-tag pull specs is dangerous, and while we still allow it in combination with --force for backward compatibility, it would be much safer to pass a by-digest pull spec instead
warning: The requested upgrade image is not one of the available updates.  You have used --allow-explicit-upgrade to the update to proceed anyway
warning: --force overrides cluster verification of your supplied release image and waives any update precondition failures.
Updating to release image registry.ci.openshift.org/origin/release:4.8.0-0.okd-2021-10-24-061736

[madpearl]

Hi,
It is not possible to jump from 4.8 direct to 4.15, because upgrade process is version (x) to version (x+1). So you can upgrade to 4.9, then to 4.10 ....

[doman18]

Hi, It is not possible to jump from 4.8 direct to 4.15, because upgrade process is version (x) to version (x+1). So you can upgrade to 4.9, then to 4.10 ....

Yes i know. I already have done this with SNO OCP cluster.