Created attachment 1266380 [details] Sosreport and all logs in /var/log and /tmp Description of problem: Upgrade from NGN-3.6 to 4.1 node, login 4.1 node, cockpit.service is not active, access Admin Console failed: https://$IP:9090/, it reports "Unable to connect". Test version: From: redhat-virtualization-host-3.6-20170307.0 To: redhat-virtualization-host-4.1-20170323.0 cockpit-ws-126-1.el7.x86_64 Test steps: 1. Install RHVH 3.6 (redhat-virtualization-host-3.6-20170307.0), add it to engine 3.6(3.6 cluster), and add NFS storage to host in engine side. 2. Setup local repos in RHVH 3.6, then upgrade to RHVH 4.1 (redhat-virtualization-host-4.1-20170323.0) # yum update 3. Reboot and login RHVH 4.1, check cockpit status, connect Admin Console: https://$IP:9090/ Actual results: After step3, cockpit.service is not active, connect Admin Console failed: https://$IP:9090/, it reports "Unable to connect". # systemctl status cockpit.service ● cockpit.service - Cockpit Web Service Loaded: loaded (/usr/lib/systemd/system/cockpit.service; static; vendor preset: disabled) Active: failed (Result: start-limit) since Fri 2017-03-24 06:47:31 GMT; 8min ago Docs: man:cockpit-ws(8) Process: 25692 ExecStartPre=/usr/sbin/remotectl certificate --ensure --user=root --group=cockpit-ws --selinux-type=etc_t (code=exited, status=217/USER) Mar 24 06:47:31 dhcp-10-16.nay.redhat.com systemd[1]: cockpit.service failed. Mar 24 06:47:31 dhcp-10-16.nay.redhat.com systemd[1]: start request repeated too quickly for cockpit.service Mar 24 06:47:31 dhcp-10-16.nay.redhat.com systemd[1]: Failed to start Cockpit Web Service. Mar 24 06:47:31 dhcp-10-16.nay.redhat.com systemd[1]: cockpit.service failed. Mar 24 06:47:34 dhcp-10-16.nay.redhat.com systemd[1]: start request repeated too quickly for cockpit.service Mar 24 06:47:34 dhcp-10-16.nay.redhat.com systemd[1]: Failed to start Cockpit Web Service. Mar 24 06:47:34 dhcp-10-16.nay.redhat.com systemd[1]: cockpit.service failed. Mar 24 06:47:34 dhcp-10-16.nay.redhat.com systemd[1]: start request repeated too quickly for cockpit.service Mar 24 06:47:34 dhcp-10-16.nay.redhat.com systemd[1]: Failed to start Cockpit Web Service. Mar 24 06:47:34 dhcp-10-16.nay.redhat.com systemd[1]: cockpit.service failed. # systemctl start cockpit.service Job for cockpit.service failed because the control process exited with error code. See "systemctl status cockpit.service" and "journalctl -xe" for details. Expected results: After step3, cockpit.service should be active, and should connect Admin Console successful.
Add "testblocker" keyword because this bug block cockpit test after upgrade.
Reporting this bug is according to comment 8 and comment 10 in Bug 1425372 - Connect Admin Console failed after upgrade from NGN-3.6 to 4.1 node.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Test version: From: redhat-virtualization-host-3.6-20170404.0 To: redhat-virtualization-host-4.1-20170403.0 imgbased-0.9.20-0.1.el7ev.noarch cockpit-ws-126-1.el7.x86_64 Test steps: 1. Install RHVH 3.6 (redhat-virtualization-host-3.6-20170404.0), add it to engine 3.6(3.6 cluster), and add NFS storage to host in engine side. 2. Setup local repos in RHVH 3.6, then upgrade to RHVH 4.1 (redhat-virtualization-host-4.1-20170403.0) # yum update 3. Reboot and login RHVH 4.1, check cockpit status, connect Admin Console: https://$IP:9090/ Test results: After step3, cockpit.service is active, and connect Admin Console successful. So this bug is fixed in imgbased-0.9.20-0.1.el7ev.noarch, change the status to VERIFIED.