Bug 1435887

Summary: Failed to run cockpit after upgrade from NGN-3.6 to 4.1 node
Product: [oVirt] ovirt-node Reporter: Huijuan Zhao <huzhao>
Component: Installation & UpdateAssignee: Ryan Barry <rbarry>
Status: CLOSED CURRENTRELEASE QA Contact: Huijuan Zhao <huzhao>
Severity: urgent Docs Contact:
Priority: high    
Version: 4.1CC: bugs, cshao, danken, dguo, dougsland, jiawu, leiwang, mgoldboi, qiyuan, rbarry, sbonazzo, weiwang, yaniwang, ycui, yzhao
Target Milestone: ovirt-4.1.1-1Keywords: TestBlocker
Target Release: 4.1Flags: rule-engine: ovirt-4.1+
rule-engine: blocker+
mgoldboi: planning_ack+
sbonazzo: devel_ack+
cshao: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: imgbased-0.9.19-0.1.el7ev Doc Type: Bug Fix
Doc Text:
Cause: Previously, imgbased did not add users and groups which were present on new layers to the running system. Consequence: Some services which depended on groups being present may fail to start. Fix: imgbased now adds users and groups from the new layers Result: services work as expected
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-21 09:42:32 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:
Bug Depends On:    
Bug Blocks: 1421098    
Attachments:
Description Flags
Sosreport and all logs in /var/log and /tmp none

Description Huijuan Zhao 2017-03-25 14:32:43 UTC 
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.
Comment 1 cshao 2017-03-25 14:41:48 UTC 
Add "testblocker" keyword because this bug block cockpit test after upgrade.
Comment 2 Ying Cui 2017-03-27 12:15:58 UTC 
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.
Comment 3 Red Hat Bugzilla Rules Engine 2017-03-27 15:20:51 UTC 
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.
Comment 5 Huijuan Zhao 2017-04-05 09:40:13 UTC 
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.