Description of problem: Upgrade from NGN-3.6 to 4.1 node, login 4.1 node, access Admin Console failed: https://$IP:9090/, it reports "Unable to connect". Version-Release number of selected component (if applicable): From: RHVH-3.6-20170217.5-RHVH-x86_64-dvd1.iso To: redhat-virtualization-host-4.1-20170208.0 How reproducible: 100% Steps to Reproduce: 1. Install RHVH 3.6 2. Setup local repos in RHVH 3.6, then upgrade to RHVH 4.1 # yum update 3. Reboot and login RHVH 4.1, connect Admin Console: https://$IP:9090/ Actual results: After step3, connect Admin Console failed: https://$IP:9090/, it reports "Unable to connect". Please refer to attachment for detailed info. Expected results: After step3, should connect Admin Console successful. Additional info:
Created attachment 1256038 [details] screenshot of connect admin console failed
Created attachment 1256039 [details] All logs from host
Can you please add sos report?
(In reply to Sandro Bonazzola from comment #3) > Can you please add sos report? I added it into the attachment "All logs from host": /var/log/sosreport-dell-per730-35.lab.eng.pek2.redhat.com-20170221062651.tar.xz
Add keyword "testblocker" due to it block all cockpit testing.
Hi Huijuan Zhao, (In reply to Huijuan Zhao from comment #0) > Description of problem: > Upgrade from NGN-3.6 to 4.1 node, login 4.1 node, access Admin Console > failed: https://$IP:9090/, it reports "Unable to connect". > > > Version-Release number of selected component (if applicable): > From: > RHVH-3.6-20170217.5-RHVH-x86_64-dvd1.iso > To: > redhat-virtualization-host-4.1-20170208.0 > > > How reproducible: > 100% > > Steps to Reproduce: > 1. Install RHVH 3.6 > 2. Setup local repos in RHVH 3.6, then upgrade to RHVH 4.1 > # yum update > 3. Reboot and login RHVH 4.1, connect Admin Console: > https://$IP:9090/ > > > Actual results: > After step3, connect Admin Console failed: https://$IP:9090/, it reports > "Unable to connect". > Please refer to attachment for detailed info. > > Looks like a cockpit failure: # 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. # systemctl status cockpit.service -l ● cockpit.service - Cockpit Web Service Loaded: loaded (/usr/lib/systemd/system/cockpit.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2017-02-24 19:09:08 CST; 10s ago Docs: man:cockpit-ws(8) Process: 21538 ExecStartPre=/usr/sbin/remotectl certificate --ensure --user=root --group=cockpit-ws --selinux-type=etc_t (code=exited, status=217/USER) Feb 24 19:09:08 localhost.localdomain systemd[1]: Starting Cockpit Web Service... Feb 24 19:09:08 localhost.localdomain systemd[21538]: Failed at step USER spawning /usr/sbin/remotectl: No such process Feb 24 19:09:08 localhost.localdomain systemd[1]: cockpit.service: control process exited, code=exited status=217 Feb 24 19:09:08 localhost.localdomain systemd[1]: Failed to start Cockpit Web Service. Feb 24 19:09:08 localhost.localdomain systemd[1]: Unit cockpit.service entered failed state. Feb 24 19:09:08 localhost.localdomain systemd[1]: cockpit.service failed. > Expected results: > After step3, should connect Admin Console successful. > > > Additional info: Could you please try with an updated rhvh 4.1 image? I didn't reproduce the report with 4.1-20170222.0 image. 1) Install redhat-virtualization-host-3.6-20170216.0.x86_64.squashfs 2) Make available the rpm for upgrade, in external server: # mkdir -p /var/www/html/upgrade # cd /var/www/html/upgrade # wget http://server/redhat-virtualization-host-image-update-4.1-20170222.0.el7_3.noarch.rpm # createrepo . 3) In the installed rhvh 3.6, update: # vi /etc/yum.repos.d/local.repo [local] name = local baseurl = http://192.168.122.1/upgrade enabled = 1 gpgcheck = 0 4) Update and Reboot # yum update # reboot 5) You must have access to the cockpit in the upgraded image: IP_ADDRESS:9090
(In reply to Douglas Schilling Landgraf from comment #6) > > Could you please try with an updated rhvh 4.1 image? I didn't reproduce the > report with 4.1-20170222.0 image. > > 1) Install redhat-virtualization-host-3.6-20170216.0.x86_64.squashfs > > 2) Make available the rpm for upgrade, in external server: > > # mkdir -p /var/www/html/upgrade > # cd /var/www/html/upgrade > # wget > http://server/redhat-virtualization-host-image-update-4.1-20170222.0.el7_3. > noarch.rpm > # createrepo . > > > 3) In the installed rhvh 3.6, update: > > # vi /etc/yum.repos.d/local.repo > [local] > name = local > baseurl = http://192.168.122.1/upgrade > enabled = 1 > gpgcheck = 0 > > 4) Update and Reboot > > # yum update > # reboot > > 5) You must have access to the cockpit in the upgraded image: > IP_ADDRESS:9090 I tried with rhvh-4.1-20170222.0 image according to above steps, no such issue anymore. Can access cockpit successful after update to rhvh4.1 Test version: From: redhat-virtualization-host-3.6-20170216.0.x86_64.squashfs To: redhat-virtualization-host-4.1-20170222.0 imgbased-0.9.13-0.1.el7ev.noarch
Encountered this issue again with new build, so reopen this bug. 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. Please refer to attachment for detailed logs.
Created attachment 1265975 [details] comment 8: Sosreport and all logs in /var/log and /tmp
Hi Huijuan Zhao, (In reply to Huijuan Zhao from comment #9) > Created attachment 1265975 [details] > comment 8: Sosreport and all logs in /var/log and /tmp Please always open a new bug report, as we are talking about different versions of RHVH.
(In reply to Douglas Schilling Landgraf from comment #10) > Hi Huijuan Zhao, > Please always open a new bug report, as we are talking about different > versions of RHVH. Douglas, got it. And already reported a new Bug 1435887 to track the issue in comment 8, so close this bug now.