Bug 832517

Summary: 3.1: sshd daemon is not starting correctly after complete the installation of oVirt Node
Product: [Retired] oVirt Reporter: Douglas Schilling Landgraf <dougsland>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.1 RCCC: acathrow, dyasny, fdeutsch, jboggs, mburns, mgoldboi, ovirt-bugs, ovirt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 2.5.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-09 11:48:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 837443    
Bug Blocks: 822145    

Description Douglas Schilling Landgraf 2012-06-15 15:46:00 UTC
Description of problem:

sshd daemon is not starting correctly after complete the installation of oVirt Node.

Here the output of systemctl:

systemctl status sshd.service
      Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)
      Active: failed (Result: exit-code) since Fri, 15 Jun 2012 14:21:23 +0000; 1h 12min ago
      CGroup: name=systemd:/system/sshd.service

Jun 15 14:21:23 localhost.localdomain sshd-keygen[1000]: Generating SSH2 RSA ...

Comment 1 Fabian Deutsch 2012-06-21 16:34:10 UTC
sshd was started before the persisted files were bind-mounted, the following patch starts sshd.service after ovirt-early.service:

http://gerrit.ovirt.org/5595

Tested with
https://gitorious.org/ovirt/ovirt-node-igor-testsuites/blobs/51fa0a8bbea705a4d314bc64691b2094a85b8256/basic.suite
https://gitorious.org/ovirt/ovirt-node-igor-testsuites/blobs/51fa0a8bbea705a4d314bc64691b2094a85b8256/tcs/services_are_running.sh