[2.5, regression] Incorrect sudoers entry causes active network scanning to hang

Bug #1802379 reported by Mike Pontillo on 2018-11-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
Mike Pontillo
2.4
High
Mike Pontillo

Bug Description

After enabling active network scanning on one of my subnets, I noticed the following statements in the log:

2018-11-08 11:14:10 maasserver: [error] Error while calling ScanNetworks: Unable to get RPC connection for rack controller 'maas' (486gxc).
2018-11-08 11:14:10 maasserver.regiondservices.active_discovery: [info] Active network discovery: Unable to initiate network scanning on any rack controller. Verify that the rack controllers are started and have connected to the region.

It seems that a regression has broken active network scanning, at least on MAAS 2.5. (I haven't tested 2.4.)

Related branches

summary: - [2.5] Regression in active network scanning
+ [2.5, regression] Active network scanning is broken
Changed in maas:
status: Triaged → In Progress

After investigating this, I think this is a change in how the sudoers file works in Xenial vs. Bionic. Thus, we should backport this to MAAS 2.4 as well.

summary: - [2.5, regression] Active network scanning is broken
+ [2.5, regression] Incorrect sudoers entry causes active network scanning
+ to hang
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers