MAAS

dhcpd stopped working since refreshed to 3.4.1-14343-g.a552d2522

Bug #2058470 reported by maasuser1 on 2024-03-20

This bug report is a duplicate of: Bug #2058898: dhcpd fails to start after auto refresh in 3.4/edge. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	MAAS	New	Undecided	Unassigned

Bug Description

Snap refreshed 2 MAAS instances to 3.4.1-14343-g.a552d2522 and then the dhcpd on the primary controller stopped working. As a result of this, I also lost the connection to the secondary controller.

maasuser1 (maasuser1) on 2024-03-20

affects:

snapd → maas

Revision history for this message

maasuser1 (maasuser1) wrote on 2024-03-20:

Restart MAAS instance by `snap restart maas.supervisor`, but I did not see any dhcpd-related log in regiond.log or rackd.log.

Revision history for this message

Jacopo Rota (r00ta) wrote on 2024-04-02:

@maasuser1 do NOT use edge. It's not intended to be stable. Use the stable channel instead

Revision history for this message

maasuser1 (maasuser1) wrote on 2024-04-03:

Thanks Jacopo!

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #2058898 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.