Bug 832517 - 3.1: sshd daemon is not starting correctly after complete the installation of oVirt Node
Summary: 3.1: sshd daemon is not starting correctly after complete the installation of...
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: 3.1 RC
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Fabian Deutsch
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On: 837443
Blocks: 822145
TreeView+ depends on / blocked
 
Reported: 2012-06-15 15:46 UTC by Douglas Schilling Landgraf
Modified: 2016-04-26 14:17 UTC (History)
8 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2012-08-09 11:48:01 UTC


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.