Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert "pkg/daemon: Add IgnitionVersion to Daemon"
b823087 introduced code to obtain the version of the Ignition binary shipped in the OS root filesystem. That commit contemplated that the version would be used more widely in the MCD, but that hasn't occurred, so its only current use is to log the Ignition version at MCD startup. On balance, I think that code path introduces more risk than value, so this PR backs it out. My reasoning is: 1. By the time this code is invoked, Ignition will never run again, so its version is useful for forensics and not much else. In particular, the version of the Ignition binary in machine-os-content probably doesn't match the one in the bootimage. 2. MCD is invoking the Ignition binary via a private (non-contractual) path in the root filesystem, but Ignition is designed and tested only for use in the initramfs. In practice, `ignition --version` _should_ be harmless since it exits very early in Ignition startup, but see below. 3. If the MCD fails to run the binary, say because the path to Ignition has changed, MCD considers that a fatal error. 4. And indeed, we now have a bug (https://bugzilla.redhat.com/show_bug.cgi?id=1927731) where an `ignition --version` segfault is apparently blocking an upgrade from 4.5 to 4.6, on exactly one customer node. From the stack trace (https://bugzilla.redhat.com/show_bug.cgi?id=1927731#c7), the problem could be in Ignition itself, in the initialization code of a vendored library, or in the Go runtime. As a practical matter, the crash is unlikely to be root-caused. This reverts commit b823087.
- Loading branch information