| mup | Bug #1910473 opened: process_lxd_resources converts numa_nodes dictionary to a list <MAAS:New for ltrager> <https://launchpad.net/bugs/1910473> | 01:50 |
|---|---|---|
| mup | Bug #1910473 changed: process_lxd_resources converts numa_nodes dictionary to a list <MAAS:New for ltrager> <MAAS 2.7:New> <MAAS 2.8:New> <MAAS 2.9:New> <https://launchpad.net/bugs/1910473> | 02:02 |
| mup | Bug #1910473 opened: process_lxd_resources converts numa_nodes dictionary to a list <MAAS:New for ltrager> <MAAS 2.7:New> <MAAS 2.8:New> <MAAS 2.9:New> <https://launchpad.net/bugs/1910473> | 02:05 |
| mup | Bug #1910473 changed: process_lxd_resources converts numa_nodes dictionary to a list <MAAS:New for ltrager> <MAAS 2.7:New> <MAAS 2.8:New> <MAAS 2.9:New> <https://launchpad.net/bugs/1910473> | 02:08 |
| mup | Bug #1910473 opened: process_lxd_resources converts numa_nodes dictionary to a list <MAAS:New for ltrager> <MAAS 2.7:New> <MAAS 2.8:New> <MAAS 2.9:New> <https://launchpad.net/bugs/1910473> | 02:11 |
| mup | Bug #1910473 changed: process_lxd_resources converts numa_nodes dictionary to a list <MAAS:New for ltrager> <MAAS 2.7:New> <MAAS 2.8:New> <MAAS 2.9:New> <https://launchpad.net/bugs/1910473> | 02:14 |
| mup | Bug #1910473 opened: process_lxd_resources converts numa_nodes dictionary to a list <MAAS:New for ltrager> <MAAS 2.7:New> <MAAS 2.8:New> <MAAS 2.9:New> <https://launchpad.net/bugs/1910473> | 02:17 |
| pescobar | any advice about how to deploy MAAS to replace an existing deployment tool? I have posted my question in the forums in case anyone can provide any advice | 11:14 |
| pescobar | https://discourse.maas.io/t/recommended-approach-to-integrate-maas-with-an-existing-dhcp-how-to-migrate-from-a-different-deployment-tool/3711 | 11:14 |
| mup | Bug #1910552 opened: machines fail to boot if MAAS doesn't respond to cloud-init <MAAS:New> <https://launchpad.net/bugs/1910552> | 14:54 |
| mup | Bug #1910552 changed: machines fail to boot if MAAS doesn't respond to cloud-init <MAAS:New> <https://launchpad.net/bugs/1910552> | 14:57 |
| mup | Bug #1910552 opened: machines fail to boot if MAAS doesn't respond to cloud-init <MAAS:New> <https://launchpad.net/bugs/1910552> | 15:00 |
| mup | Bug #1908452 opened: MAAS stops working and deployment fails after `Loading ephemeral` step <MAAS:New> <https://launchpad.net/bugs/1908452> | 15:42 |
| mup | Bug #1908452 changed: MAAS stops working and deployment fails after `Loading ephemeral` step <MAAS:New> <https://launchpad.net/bugs/1908452> | 15:45 |
| mup | Bug #1908452 opened: MAAS stops working and deployment fails after `Loading ephemeral` step <MAAS:New> <https://launchpad.net/bugs/1908452> | 15:48 |
| mup | Bug #1910570 opened: MAAS stucks on reboot ESXI machine <MAAS:New> <https://launchpad.net/bugs/1910570> | 17:24 |
| mup | Bug #1910570 changed: MAAS stucks on reboot ESXI machine <MAAS:New> <https://launchpad.net/bugs/1910570> | 17:27 |
| mup | Bug #1910570 opened: MAAS stucks on reboot ESXI machine <MAAS:New> <https://launchpad.net/bugs/1910570> | 17:36 |
| mup | Bug #1910570 changed: MAAS stucks on reboot ESXI machine <MAAS:New> <https://launchpad.net/bugs/1910570> | 17:39 |
| mup | Bug #1910570 opened: MAAS stucks on reboot ESXI machine <MAAS:New> <https://launchpad.net/bugs/1910570> | 17:45 |
| mup | Bug #1910600 opened: No UEFI boot entry created for VMware ESXi 6.7 <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1910600> | 22:13 |
| mup | Bug #1910600 changed: No UEFI boot entry created for VMware ESXi 6.7 <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1910600> | 22:16 |
| mup | Bug #1910600 opened: No UEFI boot entry created for VMware ESXi 6.7 <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1910600> | 22:34 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!