Activity log for bug #1540251

Date Who What changed Old value New value Message
2016-02-01 08:10:56 Timur Nurlygayanov bug added bug
2016-02-01 08:11:28 Timur Nurlygayanov mos: assignee Sergey Kolekonov (skolekonov)
2016-02-01 08:11:34 Timur Nurlygayanov nominated for series mos/9.0.x
2016-02-01 08:11:34 Timur Nurlygayanov bug task added mos/9.0.x
2016-02-01 08:11:34 Timur Nurlygayanov nominated for series mos/8.0.x
2016-02-01 08:11:34 Timur Nurlygayanov bug task added mos/8.0.x
2016-02-01 08:11:39 Timur Nurlygayanov mos/8.0.x: milestone 8.0
2016-02-01 08:11:41 Timur Nurlygayanov mos/9.0.x: milestone 9.0
2016-02-01 08:11:47 Timur Nurlygayanov mos/9.0.x: assignee Sergey Kolekonov (skolekonov)
2016-02-01 08:11:49 Timur Nurlygayanov mos/9.0.x: importance Undecided High
2016-02-01 08:11:50 Timur Nurlygayanov mos/8.0.x: importance Undecided High
2016-02-01 08:11:52 Timur Nurlygayanov mos/8.0.x: status New Confirmed
2016-02-01 08:11:54 Timur Nurlygayanov mos/9.0.x: status New Confirmed
2016-02-01 08:12:16 Timur Nurlygayanov tags linux nova rhel
2016-02-01 08:20:14 Timur Nurlygayanov description Steps To Reproduce: 1. Deploy OpenStack cluster with 3 controllers and 1 compute node (Ubuntu) 2. Add RHEL-based or CentOS-based compute node to the cluster 3. Check the cluster health, it will work fine. 4. Shutdown non-Ubuntu compute node and power on this node 5. Check the hypervisor status and libvirt process status on compute node Expected Result: Compute node should work fine after power cycle. Observed Result: libvirt process is down, hyper visor status is "down": [root@rhel-1 ~]# virsh list error: failed to connect to the hypervisor error: no valid connection error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory Steps To Reproduce: 1. Deploy OpenStack cluster with 3 controllers and 1 compute node (Ubuntu) 2. Add RHEL-based or CentOS-based compute node to the cluster 3. Check the cluster health, it will work fine. 4. Shutdown non-Ubuntu compute node and power on this node 5. Check the hypervisor status and libvirt process status on compute node Expected Result: Compute node should work fine after power cycle. Observed Result: libvirt process is down, hyper visor status is "down": [root@rhel-1 ~]# virsh list error: failed to connect to the hypervisor error: no valid connection error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory We can see that libvirtd is enabled in autostart: [root@rhel-1 ~]# chkconfig libvirtd Note: Forwarding request to 'systemctl is-enabled libvirtd.service'. enabled
2016-02-01 09:07:34 Ivan Berezovskiy mos/9.0.x: assignee Sergey Kolekonov (skolekonov) Victor Ryzhenkin (vryzhenkin)
2016-02-01 09:07:41 Ivan Berezovskiy mos/8.0.x: assignee Sergey Kolekonov (skolekonov) Victor Ryzhenkin (vryzhenkin)
2016-02-03 12:51:37 Dmitry Pyzhov tags linux nova rhel area-mos linux nova rhel
2016-02-03 14:10:11 Roman Podoliaka tags area-mos linux nova rhel area-mos linux non-release nova rhel
2016-02-04 17:49:47 Victor Ryzhenkin mos/8.0.x: status Confirmed In Progress
2016-02-04 17:49:49 Victor Ryzhenkin mos/9.0.x: status Confirmed In Progress
2016-02-18 01:02:43 Victor Ryzhenkin mos/8.0.x: status In Progress Invalid
2016-02-18 01:02:45 Victor Ryzhenkin mos/9.0.x: status In Progress Invalid