Description of problem: Configure one NIC with shared mode or Link local mode via cockpit, but the configuration can not be saved after rebooting. Version-Release number of selected component (if applicable): Test version: RHVH-4.3-20191103.0-RHVH-x86_64-dvd1.iso How reproducible: 100% Steps to Reproduce: 1. Install RHVH-4.3-20191103.0-RHVH-x86_64-dvd1.iso 2. Reboot RHVH and login cockpit, enter to "Networking" page 3. Select one NIC and enter setting page 4. Setup IPv4 as "Shared" mode or "Link local" mode, click "Apply" 5. Reboot and check ip address via cockpit again Actual results: 1. In step 5, after rebooting, the Mode("Shared" or "Link local") configured in setp 4 cannot be persisted. Expected results: 1. The Mode("Shared" or "Link local") configured in setp 4 should be persisted. Additional info:
Created attachment 1632429 [details] /var/log
This bug can still be reproduced in the latest 4.3.7 (redhat-virtualization-host-4.3.7-20191113.0.el7_7). Test steps: 1. Install RHVH-4.3-20191113.1-RHVH-x86_64-dvd1.iso 2. Reboot RHVH and login cockpit, enter to "Networking" page 3. Select one NIC and enter setting page 4. Setup IPv4 as "Shared" mode or "Link local" mode, click "Apply" 5. Reboot and check ip address via cockpit again Actual results: 1. In step 5, after rebooting, the Mode("Shared" or "Link local") configured in setp 4 cannot be persisted. Expected results: 1. The Mode("Shared" or "Link local") configured in setp 4 should be persisted. So move bug status to assigned.
Please retest with redhat-virtualization-host-4.3.7-20191115.0.el7_7
This bug has been resolved in redhat-virtualization-host-4.3.7-20191115.0.el7_7. Test steps: 1. Install redhat-virtualization-host-4.3.7-20191115.0.el7_7 2. Reboot RHVH and log in to cockpit, then enter "Networking" page 3. Select one NIC and enter setting page 4. Setup IPv4 as "Shared" mode or "Link local" mode, click "Apply" 5. Reboot and check the ip address via cockpit again Test result: 1. The Mode("Shared" or "Link local") configured in setp 4 can be persisted. So move bug status to VERIFIED.
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-2019:4230
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days