| mup | Bug #1916090 opened: KVM Hosts Deleted off filesystem when VM host/rack connects to a different MAAS <MAAS:Triaged> <https://launchpad.net/bugs/1916090> | 00:07 |
|---|---|---|
| mup | Bug #1916093 opened: Unable to add more than 3 Promox VMs <MAAS:In Progress by ltrager> <https://launchpad.net/bugs/1916093> | 00:07 |
| Hybrid512 | o/ | 09:27 |
| Hybrid512 | I have a strange issue with latest MaaS release and/or openstack Charms (probably Masakari since this is the only one that interacts with MaaS) | 09:28 |
| Hybrid512 | here is the case : I deployed a working Openstack cluster with Masakari enabled | 09:29 |
| Hybrid512 | before, when I was testing Masakari, I just initiated a "reboot" on a compute node and the node simply restarted | 09:29 |
| Hybrid512 | now, when I do the same thing, the node is stuck shutoff (those are physical nodes with MaaS provider) | 09:29 |
| Hybrid512 | Uploaded file: https://uploads.kiwiirc.com/files/23d1f9753428598db8e5430ba8217cd4/pasted.txt | 09:29 |
| Hybrid512 | when I try to start them through MaaS (so through ipmi), the node starts then as soon as it try to start PXE, it simply shutdown itself, it's not even initiating a DHCP request, simply shuting down before the bios ends its initialization phase | 09:30 |
| Hybrid512 | I tried to start those nodes many times through MaaS and it always do the same (nodes are Dell PowerEdge R630) | 09:30 |
| Hybrid512 | only way to start those nodes is to start them from the idrac console | 09:30 |
| Hybrid512 | it might not be a "Charms" related issue since there was also new MaaS releases recently but since there are interaction between the Masakari charm and MaaS, I don't really know where to route that issue | 09:30 |
| Hybrid512 | so any help gladly appreciated | 09:30 |
| === mup_ is now known as mup | ||
| === mup_ is now known as mup | ||
| === NewJorg_ is now known as NewJorg | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!