[2.5, regression] Incorrect sudoers entry causes active network scanning to hang
Bug #1802379 reported by
Mike Pontillo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Mike Pontillo | ||
| 2.4 |
Fix Committed
|
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.
It seems that a regression has broken active network scanning, at least on MAAS 2.5. (I haven't tested 2.4.)
Related branches
~mpontillo/maas:fix-active-scanning-sudoers--bug-1802379--2.4
- Mike Pontillo (community): Approve
-
Diff: 9 lines (+1/-0)1 file modifieddebian/extras/99-maas-common-sudoers (+1/-0)
~mpontillo/maas:fix-active-scanning-sudoers--bug-1802379
- Andres Rodriguez (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 9 lines (+1/-0)1 file modifieddebian/extras/99-maas-common-sudoers (+1/-0)
| summary: |
- [2.5] Regression in active network scanning + [2.5, regression] Active network scanning is broken |
| Changed in maas: | |
| status: | Triaged → In Progress |
Revision history for this message
| Mike Pontillo (mpontillo) wrote Re: [2.5, regression] Active network scanning is broken | #1 |
| 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.
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.