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

error printed greenboot-healthcheck output if system is non ostree-based

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • 4.14.z
    • 4.14
    • MicroShift
    • None
    • No
    • uShift Sprint 245
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, when MicroShift was installed on a non-ostree system, an error was logged during greenboot health check stating that the ostree directory did not exist. MicroShift still started normally. Now, the system properly logs the ostree status as “not an ostree system” and an error message is not produced.
      Show
      Previously, when MicroShift was installed on a non-ostree system, an error was logged during greenboot health check stating that the ostree directory did not exist. MicroShift still started normally. Now, the system properly logs the ostree status as “not an ostree system” and an error message is not produced.
    • Bug Fix
    • Done
    • Release Notes
    • Customer Facing

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

      Description of problem:

      When the print_boot_status function runs in the packaging/greenboot/functions.sh script on non ostree-based host systems, it produces an error in the output of
      
      journalctl -o cat -u greenboot-healthcheck
      
      specifically, the command $(ostree admin status) produces the error
       
      microshift does start properly

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

       

      How reproducible:

      100%

      Steps to Reproduce:

      1. install RHEL 9.2
      2. install microshift rpm package
      3. reboot
      4. check output of journalctl -o cat -u greenboot-healthcheck

      Actual results:

      error: loading sysroot: opendir(ostree/repo): No such file or directory
      

      Expected results:

      error should not be present in greenboot-healthcheck output on non ostree-based systems

      Additional info:

       

              ggiguash@redhat.com Gregory Giguashvili
              openshift-crt-jira-prow OpenShift Prow Bot
              Douglas Hensel Douglas Hensel
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: