Bug 1484610 - ovirt-vmconsole-host-sshd service is not started automatically after upgrade
Summary: ovirt-vmconsole-host-sshd service is not started automatically after upgrade
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-release
Classification: oVirt
Component: Packaging.rpm
Version: 4.1.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.1.6
: 4.1.6
Assignee: Ryan Barry
QA Contact: Huijuan Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-24 01:34 UTC by Huijuan Zhao
Modified: 2017-09-19 10:01 UTC (History)
14 users (show)

Fixed In Version: redhat-release-virtualization-host-4.1-6.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-19 10:01:51 UTC
oVirt Team: Node
Embargoed:
rule-engine: ovirt-4.1+
rbarry: devel_ack+
cshao: testing_ack+

Attachments (Terms of Use)
All logs from host(sosreport, /tmp/imgbased.log, /var/log) (12.80 MB, application/x-gzip)
2017-08-24 01:34 UTC, Huijuan Zhao 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 81015 0 'None' 'MERGED' 'host-node: add ovirt-vmconsole-host-sshd to the preset' 2019-11-27 22:14:31 UTC
oVirt gerrit 81016 0 'None' 'MERGED' 'host-node: add ovirt-vmconsole-host-sshd to the preset' 2019-11-27 22:14:31 UTC

Description Huijuan Zhao 2017-08-24 01:34:49 UTC 
Created attachment 1317348 [details]
All logs from host(sosreport, /tmp/imgbased.log, /var/log)

Description of problem:
ovirt-vmconsole-host-sshd service is not started automatically after upgrade from rhvh-4.1-0.20170808.0 to rhvh-4.1-0.20170816.2


Version-Release number of selected component (if applicable):
From: rhvh-4.1-0.20170808.0
To:   rhvh-4.1-0.20170816.2
      imgbased-0.9.47-0.1.el7ev.noarch

# imgbase layout
rhvh-4.1-0.20170808.0
 +- rhvh-4.1-0.20170808.0+1
rhvh-4.1-0.20170817.0
 +- rhvh-4.1-0.20170817.0+1


How reproducible:
100%


Steps to Reproduce:
1. Install redhat-virtualization-host-4.1-0.20170808.0
2. Register rhvh to rhvm
3. Check ovirt-vmconsole-host-sshd service is active in rhvh
# systemctl status ovirt-vmconsole-host-sshd.service
● ovirt-vmconsole-host-sshd.service - oVirt VM Console SSH server daemon
   Loaded: loaded (/usr/lib/systemd/system/ovirt-vmconsole-host-sshd.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2017-08-23 08:04:38 GMT; 23min ago
4. Setup local repo and update rhvh to rhvh-4.1-0.20170816.2
# yum update
5. Reboot and login new layer rhvh-4.1-0.20170816.2, check ovirt-vmconsole-host-sshd service status in rhvh


Actual results:
1. After step5, ovirt-vmconsole-host-sshd service is not active
# systemctl status ovirt-vmconsole-host-sshd.service
● ovirt-vmconsole-host-sshd.service - oVirt VM Console SSH server daemon
   Loaded: loaded (/usr/lib/systemd/system/ovirt-vmconsole-host-sshd.service; disabled; vendor preset: disabled)
   Active: inactive (dead)


Expected results:
1. After step5, ovirt-vmconsole-host-sshd service should be active automatically after upgrade


Additional info:
When refresh install rhvh-4.1-0.20170816.2, after register rhvh to rhvm, ovirt-vmconsole-host-sshd service is active.
Comment 1 Ryan Barry 2017-08-24 01:47:47 UTC 
I expect this is part of sync_systemd_services in osupdater. I'll hopefully have a patch up tomorrow, but just in case...
Comment 2 Huijuan Zhao 2017-09-01 06:27:49 UTC 
No 4.1.6 build currently, I will verify this issue once there is available 4.1.6 build.
Comment 3 Huijuan Zhao 2017-09-05 06:10:57 UTC 
Test version:
From: rhvh-4.1-0.20170808.0
To:   rhvh-4.1-0.20170831.0
      imgbased-0.9.47-0.1.el7ev.noarch

# imgbase layout
rhvh-4.1-0.20170808.0
 +- rhvh-4.1-0.20170808.0+1
rhvh-4.1-0.20170831.0
 +- rhvh-4.1-0.20170831.0+1


Test steps:
Same as comment 0.

Test results:
After step5, ovirt-vmconsole-host-sshd service is active automatically after upgrade.


So this bug is fixed in rhvh-4.1.6 build rhvh-4.1-0.20170831.0, change the status to VERIFIED.
Note You need to log in before you can comment on or make changes to this bug.