Bug 1780331
| Summary: | Firewalld service not enabled/running after RHV-H upgrade | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Jaroslav Spanko <jspanko> | ||||
| Component: | imgbased | Assignee: | Yuval Turgeman <yturgema> | ||||
| Status: | CLOSED ERRATA | QA Contact: | peyu | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.3.6 | CC: | cshao, dfediuck, lsvaty, mavital, nlevy, pelauter, peyu, qiyuan, sbonazzo, sgoodman, shlei, weiwang, yaniwang, yturgema | ||||
| Target Milestone: | ovirt-4.3.8 | Keywords: | ZStream | ||||
| Target Release: | 4.3.8 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | imgbased-1.1.14 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-02-13 15:43:12 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Jaroslav Spanko
2019-12-05 17:22:13 UTC
Created attachment 1642440 [details]
imgbased
I reproduced this issue. Version-Release number of selected component (if applicable): Layer 1: rhvh-4.2.7.5-0.20181121.0+1 Layer 2: rhvh-4.3.0.7-0.20190512.0+1 Latest Layer: rhvh-4.3.6.5-0.20191108.0+1 Steps to Reproduce: 1. Install RHVH-4.2-20181121.1-RHVH-x86_64-dvd1.iso and reboot 2. Login to RHVH and disable firewalld service # systemctl disable firewalld # systemctl is-enabled firewalld 3. Setup local repo and point to "redhat-virtualization-host-image-update-4.3-20190512.0.el7_6.noarch.rpm" 4. Upgrade RHVH to Layer 2 # yum update 5. Reboot and login to Layer 2, check firewalld service and enable it # systemctl is-enabled firewalld # systemctl enable firewalld # systemctl is-enabled firewalld 6. Set local reop point to "redhat-virtualization-host-image-update-4.3.6-20191108.0.el7_7.noarch.rpm" 7. Upgrade RHVH to the Latest Layer # yum update 8. Reboot and login to the Latest Layer and check firewalld service: # systemctl is-enabled firewalld Actual results: firewalld is not running/enabled in the Latest Layer Expected results: firewalld is running/enabled in the Latest Layer This bug was resolved in redhat-virtualization-host-4.3.8-20191219.0.el7_7 Version-Release number of selected component (if applicable): Layer 1: rhvh-4.2.7.5-0.20181121.0+1 Layer 2: rhvh-4.3.0.7-0.20190512.0+1 Latest Layer: rhvh-4.3.8.1-0.20191219.0+1 Test steps: 1. Install RHVH-4.2-20181121.1-RHVH-x86_64-dvd1.iso and reboot 2. Login to RHVH and disable firewalld service # systemctl disable firewalld # systemctl is-enabled firewalld 3. Setup local repo and point to "redhat-virtualization-host-image-update-4.3-20190512.0.el7_6.noarch.rpm" 4. Upgrade RHVH to Layer 2 # yum update 5. Reboot and login to Layer 2, check firewalld service and enable it # systemctl is-enabled firewalld # systemctl enable firewalld # systemctl is-enabled firewalld 6. Set local reop point to "redhat-virtualization-host-image-update-4.3.8-20191219.0.el7_7.noarch.rpm" 7. Upgrade RHVH to the Latest Layer # yum update 8. Reboot and login to the Latest Layer and check firewalld service: # systemctl is-enabled firewalld Test results: firewalld is running/enabled in the Latest Layer So I move the bug status to "VERIFIED". If this bug does not require documentation, please set the "requires_doc_text" flag to "-". Otherwise, please supply doc text. 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, 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/RHBA-2020:0503 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |