Activity log for bug #2015450

Date Who What changed Old value New value Message
2023-04-06 07:37:51 Natalia Litvinova bug added bug
2023-04-06 07:39:58 Natalia Litvinova bug added subscriber Canonical Field Critical
2023-04-06 07:48:30 Natalia Litvinova description After the initial MAAS installation and some time passing dhcpd.conf dissappears: cat /var/snap/maas/common/maas/dhcpd.conf cat: /var/snap/maas/common/maas/dhcpd.conf: No such file or directory As you can see in the log - the dhcp service was running before: https://pastebin.canonical.com/p/DvpFqfjXqf/ $ sudo maas status bind9 RUNNING pid 665699, uptime 19:09:53 dhcpd STOPPED Apr 05 02:27 PM dhcpd6 STOPPED Not started http RUNNING pid 623091, uptime 22:05:24 ntp RUNNING pid 622475, uptime 22:05:40 proxy RUNNING pid 631436, uptime 21:59:01 rackd RUNNING pid 621842, uptime 22:05:43 regiond RUNNING pid 621844, uptime 22:05:43 syslog RUNNING pid 622477, uptime 22:05:40 Regiond.log: https://pastebin.canonical.com/p/jT7hqztrGM/ Rackd.log: https://pastebin.canonical.com/p/XWhdRNNsZg/ I've hit this bug 2 times on different stages of the deployment. MAAS version: 3.3.1-13169-g.94920eb1e After the initial MAAS installation and some time passing dhcpd.conf dissappears: cat /var/snap/maas/common/maas/dhcpd.conf cat: /var/snap/maas/common/maas/dhcpd.conf: No such file or directory As you can see in the log - the dhcp service was running before: https://pastebin.canonical.com/p/DvpFqfjXqf/ $ sudo maas status bind9 RUNNING pid 665699, uptime 19:09:53 dhcpd STOPPED Apr 05 02:27 PM dhcpd6 STOPPED Not started http RUNNING pid 623091, uptime 22:05:24 ntp RUNNING pid 622475, uptime 22:05:40 proxy RUNNING pid 631436, uptime 21:59:01 rackd RUNNING pid 621842, uptime 22:05:43 regiond RUNNING pid 621844, uptime 22:05:43 syslog RUNNING pid 622477, uptime 22:05:40 Regiond.log: https://pastebin.canonical.com/p/jT7hqztrGM/ Rackd.log: https://pastebin.canonical.com/p/XWhdRNNsZg/ I've hit this bug 2 times on different stages of the deployment. MAAS version: 3.3.1-13169-g.94920eb1e Currently this bug has no workaround on how to make DHCP alive again and affects the ongoing deployment
2023-04-06 07:57:50 Przemyslaw Hausman bug added subscriber Przemyslaw Hausman
2023-04-13 11:09:02 Igor Brovtsin maas: status New Incomplete
2023-06-13 04:17:13 Launchpad Janitor maas: status Incomplete Expired
2024-04-17 03:52:53 Baby Philip maas: status Expired New
2024-04-18 08:14:31 Jerzy Husakowski maas: status New Incomplete
2024-05-07 07:36:28 Anton Troyanov maas: status Incomplete New
2024-05-07 07:36:30 Anton Troyanov maas: status New Incomplete