[OKD 5.0.0-okd-scos.ec.0-7] update channel still "stable-scos-4"

[titou10titou10]

Describe the bug

With version 5.0.0-okd-scos.ec.0, the "update channel" seems wrong as it is still pointing to "stable-scos-4"

apiVersion: config.openshift.io/v1
kind: ClusterVersion
metadata:
  name: version
spec:
  {...}
  channel: stable-scos-4
  clusterID: <redacted>
  upstream: 'https://amd64.origin.releases.ci.openshift.org/graph'
{...}
status:
  history:
    - completionTime: '2026-05-18T20:30:49Z'
      image: 'quay.io/okd/scos-release@sha256:bb36310bb5c70931061113b9bd5604468af3d63cb239bab3dc61f5e95736965a'
      startedTime: '2026-05-18T19:58:44Z'
      state: Completed
      verified: false
      version: 5.0.0-okd-scos.ec.0

Version

No response

Reproducibility

No response

Log Bundle

No response

[darren-oxford]

It currently sits in 4-scos-next, but perhaps an 5-scos-next channel is needed.

[bernhardloos]

This seems to be fixed: https://origin-release.ci.openshift.org/#5-scos-next

[titou10titou10]

@bernhardloos nope

oc get clusterversion -o yaml

apiVersion: config.openshift.io/v1
kind: ClusterVersion
metadata:
  name: version
spec:
  {...}
  channel: stable-scos-4
  upstream: https://amd64.origin.releases.ci.openshift.org/graph
status:
  {...}
  desired:
      image: quay.io/okd/scos-release@sha256:8a460cb0a0991b21d87efc994ba28ed54b1d074b6a231125d83bc1a228d19f88
      version: 5.0.0-okd-scos.ec.0
  history:
  - completionTime: "2026-05-30T14:54:45Z"
    image: quay.io/okd/scos-release@sha256:8a460cb0a0991b21d87efc994ba28ed54b1d074b6a231125d83bc1a228d19f88
    startedTime: "2026-05-30T14:29:06Z"
    state: Completed
    verified: false
    version: 5.0.0-okd-scos.ec.0

[jatinsu]

I think it's due to this: https://github.com/openshift/installer/blob/43ef4b682d30821e3478ac2f6dfd2aa897aca2f0/data/data/manifests/bootkube/cvo-overrides.yaml.template#L9, I already have a PR up to fix this, just waiting for some reviews and we can merge this.