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

Allow listing crio and kernel versions in machine-os components


    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Undefined Undefined
    • None
    • 4.13.0
    • oc
    • None
    • False
    • Hide



      This is a clone of issue OCPBUGS-3473. The following is the description of the original issue:

      In `oc adm release new` only two components are allowed to be specified:

      • kubernetes
      • machine-os

      These are being extracted from operator labels and displayed on release controller release page. RHCOS version is set in machine-os and links to release browser, which works great for OCP.

      However, for OKD we base our machine-os version on FCOS. After layering has been implemented we specify the base FCOS version in machine-os. OKD is also installing cri-o - and its version is not getting recorded. In some cases OKD machine-os also overrides kernel version (some versions may break e2e tests), so it would be useful to allow `oc` to set cri-o and kernel version labels and have them displayed on release controller

            aguclu@redhat.com Arda Guclu
            openshift-crt-jira-prow OpenShift Prow Bot
            ying zhou ying zhou
            0 Vote for this issue
            3 Start watching this issue