Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-141567

Greenboot-rs service produces a journalctl warning on the first boot

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • CentOS Stream 9, CentOS Stream 10
    • greenboot-rs
    • Yes
    • None
    • rhel-edge
    • 1
    • False
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • None
    • None
    • Known Issue
    • Hide
      Greenboot triggers a warning message during the first boot::
      When booting a system for the first time with the `greenboot-0.16.2-0` package, the system might log a WARNING message stating that boot data is unavailable. This occurs because the initial boot data has not yet been generated. This message is benign and does not affect the system's operation or the health check process. You can safely ignore the warning during the initial boot.
      Show
      Greenboot triggers a warning message during the first boot:: When booting a system for the first time with the `greenboot-0.16.2-0` package, the system might log a WARNING message stating that boot data is unavailable. This occurs because the initial boot data has not yet been generated. This message is benign and does not affect the system's operation or the health check process. You can safely ignore the warning during the initial boot.
    • Done
    • Done
    • Done
    • Not Required
    • None

      What were you trying to do that didn't work?

      Everything works, but the WARN message in the system logs is misleading and should be avoided

      What is the impact of this issue to you?

      Minimal. Trying to prevent support calls / questions from end users.

      Please provide the package NVR for which the bug is seen:

      greenboot-0.16.1-0.el9.x86_64

      How reproducible is this bug?

      100% on the first boot

      Steps to reproduce

      sudo journalctl -xu greenboot-healthcheck

      Expected results

      Clean journalctl logs on the first boot

      Actual results

      Jan 15 06:36:24 cos9-src-greenboot-bootc-host1 greenboot[951]:  WARN  greenboot > journalctl command failed with status:
exit status: 1. Error: Data from the specified boot (-1) is not available: No such boot ID in journal

              saypaulgit Sayan Paul
              ggiguash@redhat.com Gregory Giguashvili
              Sayan Paul Sayan Paul
              Mario Cattamo Mario Cattamo
              Eliane Pereira Eliane Pereira
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: