Bug 1724002
Summary: | Cannot use cloud-init in FIPS mode | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Germano Veit Michel <gveitmic> |
Component: | vdsm | Assignee: | Nobody <nobody> |
Status: | CLOSED ERRATA | QA Contact: | Beni Pelled <bpelled> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.3.0 | CC: | bpelled, kevin.kadak, lsurette, lsvaty, mtessun, rdlugyhe, schandle, srevivo, tbaransk, ycui |
Target Milestone: | ovirt-4.4.0 | Flags: | lsvaty:
testing_plan_complete-
|
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | rhv-4.4.0-29 | Doc Type: | Bug Fix |
Doc Text: |
Previously, cloud-init could not be used on hosts with FIPS enabled. With this update, cloud-init can be used on hosts with FIPS enabled.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-08-04 13:27:06 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: |
Description
Germano Veit Michel
2019-06-26 01:13:34 UTC
sync2jira sync2jira The FIPS-uncompatible hash function has been removed with https://gerrit.ovirt.org/#/c/102698/. Does this fix the problem? (In reply to Tomasz Barański from comment #3) > The FIPS-uncompatible hash function has been removed with > https://gerrit.ovirt.org/#/c/102698/. > > Does this fix the problem? Looks like yes, maybe attach that Gerrit to this bug and ask QE to verify? (In reply to Germano Veit Michel from comment #4) > (In reply to Tomasz Barański from comment #3) > > The FIPS-uncompatible hash function has been removed with > > https://gerrit.ovirt.org/#/c/102698/. > > > > Does this fix the problem? > > Looks like yes, maybe attach that Gerrit to this bug and ask QE to verify? Will do, thanks! It seems that the linked patch fixed the problem. WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops Verified with: - RHV 4.4.0-0.32.master.el8ev - Host with Red Hat Enterprise Linux 8.2 (Ootpa) - libvirt-6.0.0-17.module+el8.2.0+6257+0d066c28.x86_64 - vdsm-4.40.13-1.el8ev.x86_64 Verification steps: 1. Enable FIPS on a host. 2. Connect the host to an engine. 3. Create a new VM with cloud-init parameters. 4. Run the new VM on the FIPS host. Result: - VM ran successfully with the configured cloud-init parameters. 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 (RHV RHEL Host (ovirt-host) 4.4), 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/RHEA-2020:3246 |