[fuel-migrate] sshd filed to start after first reboot of fuel node
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Max Yatsenko |
Bug Description
Steps to reproduce:
Run the fuel-migrate script and check logs of fuel node via RDP.
Observed behaviour:
OpenSSH server daemon failed to start after reboot master node. As a result, fuel-migrate script can't migrate database.
sshd.service logs:
[root@nailgun ~]# journalctl -u sshd.service
-- Logs begin at Fri 2017-07-21 10:09:58 UTC, end at Fri 2017-07-21 10:27:01 UTC. --
Jul 21 10:10:01 nailgun.
-- Logs begin at Fri 2017-07-21 10:09:58 UTC, end at Fri 2017-07-21 10:27:01 UTC. --
Jul 21 10:10:01 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
-- Logs begin at Fri 2017-07-21 10:09:58 UTC, end at Fri 2017-07-21 10:27:01 UTC. --
Jul 21 10:10:01 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Jul 21 10:10:02 nailgun.
Changed in fuel: | |
importance: | Undecided → High |
assignee: | nobody → MOS Maintenance (mos-maintenance) |
milestone: | none → 8.0-updates |
Changed in fuel: | |
assignee: | MOS Maintenance (mos-maintenance) → Max Yatsenko (myatsenko) |
Unfortunatelly this issue was not reproduced,
*to reproduce the issue the following configuration was deployed:
MOS8.0 (with last updates)
1Controller
3Computer+Cinder
*After that the following command was run on master node:
fuel-migrate <compute-node-ip>
*Migration proccess was started.
*When migration process was finished , the following message was appeared in master node console:
Source fuelmaster can be obtained by ssh 10.88.0.72
* I was able to log into NEW master node from compute node and run "fule node" command and etc.
As this bug was not reproduced I set status of the bug as Invalid.
Please be free reopen the issue if this problem appears again.