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

MicroShift service fails if host doesn't have hostname installed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.19.0
    • 4.19.z
    • MicroShift
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 1
    • None
    • None
    • None
    • uShift Sprint 269
    • 1
    • None
    • Release Note Not Required
    • N/A
    • None
    • None
    • None
    • None

      Description of problem:

      I was installing microshift on fresh system where there is no hostname installed, microshift installation completed without any error but when I run the service it failed with following

      Mar 26 07:47:14 127.0.0.1.nip.io microshift[331]: ??? I0326 07:47:14.944652     331 run.go:65] "Version" microshift="4.19.0_0.nightly_2025_03_21_030708_20250325165336_e3d41974b_dirty" base="4.19.0-0.nightly-2025-03-21-030708"
Mar 26 07:47:14 127.0.0.1.nip.io microshift[331]: ??? E0326 07:47:14.945113     331 run.go:72] "command failed" err="failed to fill config's defaults: failed to get all hostnames: error when executing 'hostname -A': fork/exec /bin/hostname: no such file or directory"

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

          built from main branch

      How reproducible:

          If you have hostname installed the uninstall it and try to run the microshift service which will fail. hostname should be part of Require section.

      Actual results:

          Failed to start the service

      Expected results:

          Should able to start service

      Additional info:

              ggiguash@redhat.com Gregory Giguashvili
              prkumar@redhat.com Praveen Kumar
              None
              None
              Rama Kasturi Narra Rama Kasturi Narra
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: