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

Unable to deploy 4.12 spoke clusters(using 4.12 live iso) from 4.14.0-ec.4 hub, bmh stuck in provisioning state due to Failed to update hostname: Command '['chroot', '/mnt/coreos', 'hostnamectl', 'hostname']' returned non-zero exit status 1

    XMLWordPrintable

Details

    • Important
    • No
    • 2
    • Metal Platform 240
    • 1
    • Approved
    • False
    • Hide

      None

      Show
      None
    • 08/08: Approved as an OCP blocker and has a fix posted.

    Description

      Description of problem:

      When deploy 4.12 spoke clusters(using rhcos-412.86.202306132230-0-live.x86_64.iso) or 4.10 spoke clusters from a 4.14.0-ec.4 hub, bmh gets stuck in provisioning state due to Failed to update hostname: Command '['chroot', '/mnt/coreos', 'hostnamectl', 'hostname']' returned non-zero exit status 1. Running `hostnamectl hostname` returns `Unknown operation hostname`. It looks like older versions of hostnamectl do not support the hostname option.

      Version-Release number of selected component (if applicable):

      4.14.0-ec.4

      How reproducible:

      100%

      Steps to Reproduce:

      1. From a 4.14.0-ec.4 hub cluster deploy a 4.12 spoke cluster using rhcos-412.86.202306132230-0-live.x86_64.iso via ZTP procedure
      

      Actual results:

      BMH stuck in provisioning state

      Expected results:

      BMH gets provisioned

      Additional info:

      I also tried using a 4.14 iso image to deploy the 4.12 payload but then kubelet would fail with err="failed to parse kubelet flag: unknown flag: --container-runtime"

      Attachments

        Activity

          People

            rhn-engineering-dtantsur Dmitry Tantsur
            mcornea@redhat.com Marius Cornea
            Jad Haj Yahya Jad Haj Yahya
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: