Bug 1691704
| Summary: | [RFE] Ignition support for ovirt vms | |||
|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Juan Manuel Parrilla Madrid <jparrill> | |
| Component: | RFEs | Assignee: | Roy Golan <rgolan> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nisim Simsolo <nsimsolo> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | future | CC: | bugs, emarcus, jcall, kboumedh, mtessun, nsimsolo, pablo.iranzo, rgolan | |
| Target Milestone: | ovirt-4.4.1 | Keywords: | FutureFeature | |
| Target Release: | --- | Flags: | pm-rhel:
ovirt-4.4+
mtessun: planning_ack+ pm-rhel: devel_ack+ pm-rhel: testing_ack+ |
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | rhv-4.4.0-29 | Doc Type: | Enhancement | |
| Doc Text: |
Red Hat Virtualization Manager virtual machines now support ignition configuration, and this feature can be used via the UI or API by any guest OS that supports it, for example, RHCOS or FCOS.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1712746 (view as bug list) | Environment: | ||
| Last Closed: | 2020-08-05 06:24:46 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1712746 | |||
|
Description
Juan Manuel Parrilla Madrid
2019-03-22 09:56:51 UTC
i believe https://gerrit.ovirt.org/#/c/100008 can be used as a workaround The merged patches to the engine supply support over cloud-init cdrom, which is a well known and used method for a long time. Currently the way to use it is to pass the ignition config into the 'custom script' section of the vm init object when creating the vm. If the config file is a valid json file with the ignition key in it, it will be passed to on into the userdata file under the config-2 disk. RHCOS side needs to have the openstack ignition enabled in the kernel so it will boot and try to locate the config-2 disk - its location will be /dev/disk/by-label/config-2 . The ignition provider mounts it and then the config data available to ignition. This means the VM template should be openstack RHCOS image. Regarding fw_cfg, it doesn't have support from qemu at the moment, and moreover I don't see it supporting large ignition config files, where in the case of openshift installation, the bootstrap ignition data is 300k big. Feature page on its way to ovirt-site, please review the pull-request - https://github.com/oVirt/ovirt-site/pull/2021 Feature page https://ovirt.org/develop/release-management/features/virt/coreos-ignition-support.html Reassigned, see https://bugzilla.redhat.com/show_bug.cgi?id=1801153 Verified: ovirt-engine-4.4.1.7-0.3.el8ev vdsm-4.40.22-1.el8ev.x86_64 qemu-kvm-4.2.0-28.module+el8.2.1+7211+16dfe810.x86_64 libvirt-daemon-6.0.0-25.module+el8.2.1+7154+47ffd890.x86_64 Verification scenario: Polarion test plan added to bugzilla external trackers. This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |