Skip to content

[BUG] Unintended behavior found in secureblue iot greenboot #1942

@ambrosiaforest

Description

@ambrosiaforest

Description

Greenboot fails on the 01-repository_dns_check.sh causing the system to bootloop. This was happening after initial rebase from fedora iot where dnsconfd was failing and wouldn't start until I ran ujust dns-selector reset. Then again when on wifi where it would take a few seconds to connect, which I'm assuming was longer than greenboot liked.

Reproduce

Disconnect internet to ensure dns fails. This will cause it to bootloop because it will fail at 01-repository_dns_check.sh. This also happens when dnsconfd fails like in #1932

Expected

System should boot successfully whether or not dns is actually working.

Actual

System bootloops when dns is not available.

Image

iot-main-hardened 43.20260214.0

Upstream

Had no issues on Fedora iot prior to rebasing to secureblue

Declaration

  • I agree to follow this project's Code of Conduct.
  • I declare that this is not a request for alternate community messaging or social platforms.
  • I declare that I have read the secureblue website and my feature request is in-scope.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions