Bug 1900759
| Summary: | include qemu-guest-agent by default | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Colin Walters <walters> |
| Component: | RHCOS | Assignee: | Micah Abbott <miabbott> |
| Status: | CLOSED ERRATA | QA Contact: | Michael Nguyen <mnguyen> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.6 | CC: | bbreard, cglombek, dornelas, eslutsky, hpopal, imcleod, jligon, lucab, miabbott, mkalinin, nstielau, ravbrown, rgolan, ymankad |
| Target Milestone: | --- | ||
| Target Release: | 4.7.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
Feature: Inclusion of the qemu-guest-agent in RHCOS
Reason: The qemu-guest-agent can report useful information about RHCOS back to the RHV management interface.
Result: RHV administrators are now able to see rich information about RHCOS nodes.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-02-24 15:35:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1820141 | ||
|
Description
Colin Walters
2020-11-23 16:41:58 UTC
> We need to be sure that there's no conflict with afterburn.
As far as I cant tell, there is no conflict right now with Afterburn.
And from what I can foresee, there is likely no concern for the future too because:
* we are currently thinking of using the oVirt virtio device from Afterburn for first-boot check-in in initramfs. To my understanding, the guest agent runs later than that, in the real rootfs, so they won't conflict over the same resource at the same.
* Afterburn logic is oneshot. If we want to add more oVirt-related logic we can always ensure that its relevant service units are completed before starting the long-running oVirt or QEMU agents.
The `qemu-agent` was added to RHCOS in this PR - https://github.com/openshift/os/pull/451 We need to bump the submodule in our GitLab repo - https://gitlab.cee.redhat.com/coreos/redhat-coreos/-/merge_requests/1187 Should be in the latest 4.7 builds, e.g. https://openshift-release.apps.ci.l2s4.p1.openshiftapps.com/releasestream/4.7.0-0.nightly/release/4.7.0-0.nightly-2020-12-03-103850 tested with release openshift-install-linux-4.7.0-0.nightly-2020-12-04-013308 and oVirt 4.4.2.6 the IP address is reported back to oVirt without any manual intervention. Closing as verified based on https://bugzilla.redhat.com/show_bug.cgi?id=1900759#c5 Can we align FCOS with RHCOS on this? It will make it easier to get oVirt support working on OKD and will give more valuable community feedback (In reply to Sandro Bonazzola from comment #8) > Can we align FCOS with RHCOS on this? It will make it easier to get oVirt > support working on OKD and will give more valuable community feedback You can submit an issue to the FCOS issue tracker asking to include the agent - https://github.com/coreos/fedora-coreos-tracker/issues Though there is a long history of not providing agents in the base OS: https://github.com/coreos/fedora-coreos-tracker/search?q=no+cloud+agents&type=issues FWIW qemu-guest-agent is included in OKD as an extension that is installed by default: https://github.com/openshift/okd-machine-os/blob/8e7e3bee02b1e00ba589564c8729112519469db1/manifests/0000_80_machine-config-operator_05_1_okd-master-extensions.yaml#L14 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633 |