Bug 2037758
Summary: | Update RHV-H with vdsm-4.40.90.5 | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Michal Skrivanek <michal.skrivanek> |
Component: | redhat-virtualization-host | Assignee: | Sandro Bonazzola <sbonazzo> |
Status: | CLOSED ERRATA | QA Contact: | Tamir <tamir> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.4.9 | CC: | ahadas, bugs, cshao, dfodor, pagranat, pelauter, tamir, tgolembi, Yury.Panchenko |
Target Milestone: | ovirt-4.4.9-3 | Keywords: | ZStream |
Target Release: | 4.4.9 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | vdsm-4.40.90.5-1.el8ev | Doc Type: | No Doc Update |
Doc Text: | Story Points: | --- | |
Clone Of: | 2026809 | Environment: | |
Last Closed: | 2022-01-12 14:38:16 UTC | Type: | --- |
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: | 2026809 | ||
Bug Blocks: |
Description
Michal Skrivanek
2022-01-06 13:51:51 UTC
Verified on RHV 4.4.9-6 and RHVH 4.4.9 host. Env: - Engine instance with RHV 4.4.9-6 (ovirt-engine-4.4.9.5-0.1.el8ev.noarch) and RHEL 8.5 installed. - 1 host with redhat-virtualization-host-4.4.9-202201072228_8.5 and with vdsm-4.40.90.5-1.el8ev included. Tests: Check the partner's case: I performed the steps from Veeam's user guide (from page 20): 1. I have downloaded the zip from their website, which can be alternatively retrieved from the following Red Hat server. 2. I have extracted it in /tmp/new_folder in one of the hosts in the env. 3. I ran chmod 755 veeam_rhv_proxy_beta_vm_1.0.1488.* and chown 36:36 veeam_rhv_proxy_beta_vm_1.0.1488.* In Admin Portal: 4. Create a 4.6 data center and a 4.6 cluster. 5. Install the hosts and create a new NFS storage domain. 6. Open the VM import modal, select OVA as the source, fill in the OVA path and host, load, and import the VM. 7. The VM was imported successfully and was unlocked. Results (As Expected): 4. The 4.6 data center and the 4.6 cluster were created. 5. The host was installed and the NFS storage domain was created. 6. The VM import process has started. 7. The VM was imported successfully and was unlocked. Check that the log doesn't contain any mentions of the "'str' object has no attribute 'decode'" error: In Admin Portal: 1. Create a 4.6 data center and a 4.6 cluster. 2. Install the hosts and create a new NFS storage domain. 3. Open the VM import modal, select VMware as the source, fill in the VCenter 7 details, and select a VM to import and import it. 4. Check that in the engine.log and vdsm.log of the host used in the import there aren't any mentions of the "'str' object has no attribute 'decode'" error while the import process runs. 5. Check that the VM was imported successfully. Results (As Expected): 1. The 4.6 data center and the 4.6 cluster were created. 2. The host was installed and the NFS storage domain was created. 3. The VM import process has started. 4. In the engine.log and vdsm.log in the host used in the import there aren't any mentions of the "'str' object has no attribute 'decode'" error while and after the import process. 5. The VM was imported successfully. Check that import from a place with no permissions (root specifically) fails. 1. I have downloaded the zip from their website, which can be alternatively retrieved from the following Red Hat server. 2. I have extracted it in /root in one of the hosts in the env. 3. I ran chmod 755 veeam_rhv_proxy_beta_vm_1.0.1488.* and chown 36:36 veeam_rhv_proxy_beta_vm_1.0.1488.* In Admin Portal: 4. Create a 4.6 data center and a 4.6 cluster. 5. Install the hosts and create a new NFS storage domain. 6. Open the VM import modal, select OVA as the source, fill in the OVA path and host, load, and import the VM. 7. Check that VM import has failed and there isn't a locked instance of it. Results (As Expected): 4. The 4.6 data center and the 4.6 cluster were created. 5. The host was installed and the NFS storage domain was created. 6. The VM import process has started. 7. The VM import has failed and there isn't a locked instance of it. 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 (Important: Red Hat Virtualization Host security and bug fix update [ovirt-4.4.9] Async #2), 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-2022:0133 |