This bug has not seen any activity in the last 6 months, so it is being
automatically closed.
If you are still experiencing this issue, please feel free to re-open.
MAAS Team
** Changed in: maas
Status: Triaged => Invalid
--
You received this bug notification because you are a member
I re-enabled dhcp replies on my (external to MaaS) DHCP server after
upgrading to MaaS 2.1. This has been running for a few hours now without
experiencing problems. So the initial issue has gone. This report could
be closed or used for tracking the implementation of the probing switch.
** Changed
While the root cause of this issue is still incomplete, I think it would
be good to allow users to disable active DHCP probing. We have other
active network scanning methods in MAAS 2.1, but those can all be
disabled with a global setting (or on an individual subnet).
** Summary changed:
- MaaS
