[2.5] MAAS doesn't sync resource-pools with RBAC
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Blake Rouse | ||
2.5 |
Fix Released
|
Critical
|
Blake Rouse |
Bug Description
I had a running MAAS that was previously working with Candid and RBAC. I had to completely re-installed candid and upgraded to a new rev of MAAS. After I tried to connect MAAS to new RBAC/Candid, no resource pools are available in RBAC even though they are available in MAAS.
There are no logs. Restarting MAAS yields no logs for RBAC (regiond.log):
2019-01-31 14:33:18 twisted.scripts: [info] twistd 17.9.0 (/usr/bin/python3 3.6.7) starting up.
2019-01-31 14:33:18 twisted.scripts: [info] reactor class: twisted.
2019-01-31 14:33:19 maasserver.
2019-01-31 14:33:19 maasserver.
2019-01-31 14:33:19 maasserver.
2019-01-31 14:33:19 maasserver.
2019-01-31 14:33:20 stderr: [error] request to http://
2019-01-31 14:33:20 maasserver.
2019-01-31 14:33:21 stderr: [error] request to http://
2019-01-31 14:33:22 stderr: [error] request to http://
2019-01-31 14:33:22 twisted.scripts: [info] twistd 17.9.0 (/usr/bin/python3 3.6.7) starting up.
2019-01-31 14:33:22 twisted.scripts: [info] reactor class: twisted.
2019-01-31 14:33:22 -: [info] IPCWorker connection established (HOST:UNIXAddre
2019-01-31 14:33:22 twisted.
2019-01-31 14:33:22 maasserver.
2019-01-31 14:33:22 maasserver.ipc: [info] Worker pid:9267 IPC connected.
2019-01-31 14:33:22 twisted.scripts: [info] twistd 17.9.0 (/usr/bin/python3 3.6.7) starting up.
2019-01-31 14:33:22 twisted.scripts: [info] reactor class: twisted.
2019-01-31 14:33:23 twisted.scripts: [info] twistd 17.9.0 (/usr/bin/python3 3.6.7) starting up.
2019-01-31 14:33:23 twisted.scripts: [info] reactor class: twisted.
2019-01-31 14:33:23 twisted.scripts: [info] twistd 17.9.0 (/usr/bin/python3 3.6.7) starting up.
2019-01-31 14:33:23 twisted.scripts: [info] reactor class: twisted.
2019-01-31 14:33:23 twisted.
2019-01-31 14:33:23 -: [info] IPCWorker connection established (HOST:UNIXAddre
2019-01-31 14:33:23 maasserver.ipc: [info] Worker pid:9267 opened RPC listener on port:5250.
2019-01-31 14:33:23 maasserver.ipc: [info] Worker pid:9266 IPC connected.
2019-01-31 14:33:23 -: [info] IPCWorker connection established (HOST:UNIXAddre
2019-01-31 14:33:23 twisted.
2019-01-31 14:33:23 maasserver.
2019-01-31 14:33:23 twisted.
2019-01-31 14:33:23 -: [info] IPCWorker connection established (HOST:UNIXAddre
2019-01-31 14:33:23 maasserver.
2019-01-31 14:33:23 maasserver.ipc: [info] Worker pid:9268 IPC connected.
2019-01-31 14:33:23 maasserver.ipc: [info] Worker pid:9265 IPC connected.
2019-01-31 14:33:23 maasserver.
2019-01-31 14:33:23 regiond: [info] 127.0.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningser
2019-01-31 14:33:23 twisted.
2019-01-31 14:33:23 maasserver.
2019-01-31 14:33:23 maasserver.ipc: [info] Worker pid:9268 opened RPC listener on port:5252.
2019-01-31 14:33:23 maasserver.ipc: [info] Worker pid:9266 opened RPC listener on port:5251.
2019-01-31 14:33:23 maasserver.ipc: [info] Worker pid:9265 opened RPC listener on port:5253.
2019-01-31 14:33:23 maasserver.ipc: [info] Worker pid:9267 registered RPC connection to ('xrrxcb', '192.168.1.13', 5250).
2019-01-31 14:33:24 regiond: [info] 127.0.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningser
2019-01-31 14:33:24 twisted.
2019-01-31 14:33:24 twisted.
2019-01-31 14:33:24 twisted.
2019-01-31 14:33:24 maasserver.
2019-01-31 14:33:24 maasserver.
2019-01-31 14:33:24 maasserver.
2019-01-31 14:33:24 regiond: [info] 127.0.0.1 POST /MAAS/metadata/
2019-01-31 14:33:24 maasserver.ipc: [info] Worker pid:9266 registered RPC connection to ('xrrxcb', '192.168.1.13', 5251).
2019-01-31 14:33:25 maasserver.ipc: [info] Worker pid:9268 registered RPC connection to ('xrrxcb', '192.168.1.13', 5252).
2019-01-31 14:33:25 maasserver.ipc: [info] Worker pid:9265 registered RPC connection to ('xrrxcb', '192.168.100.1', 5253).
2019-01-31 14:33:25 maasserver.
2019-01-31 14:33:25 regiond: [info] 127.0.0.1 POST /MAAS/metadata/
2019-01-31 14:33:26 maasserver.
2019-01-31 14:33:26 maasserver.
2019-01-31 14:33:26 regiond: [info] 127.0.0.1 POST /MAAS/metadata/
2019-01-31 14:33:26 regiond: [info] 127.0.0.1 POST /MAAS/metadata/
2019-01-31 14:33:27 regiond: [info] 127.0.0.1 POST /MAAS/metadata/
2019-01-31 14:33:27 regiond: [info] 127.0.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningser
2019-01-31 14:33:28 regiond: [info] 127.0.0.1 POST /MAAS/metadata/
2019-01-31 14:33:28 regiond: [info] 127.0.0.1 POST /MAAS/metadata/
2019-01-31 14:33:28 regiond: [info] 127.0.0.1 POST /MAAS/metadata/
2019-01-31 14:33:28 regiond: [info] 127.0.0.1 POST /MAAS/metadata/
2019-01-31 14:33:29 regiond: [info] 127.0.0.1 POST /MAAS/metadata/
2019-01-31 14:33:29 regiond: [info] 127.0.0.1 POST /MAAS/metadata/
2019-01-31 14:33:29 regiond: [info] 127.0.0.1 POST /MAAS/metadata/
2019-01-31 14:33:29 regiond: [info] 127.0.0.1 POST /MAAS/metadata/
2019-01-31 14:33:29 regiond: [info] 127.0.0.1 POST /MAAS/metadata/
2019-01-31 14:33:29 regiond: [info] 127.0.0.1 POST /MAAS/metadata/
2019-01-31 14:33:31 maasserver.
* rack controller maas00 connected
* rack controller maas00 disconnected
* rack controller maas00 disconnected
* rack controller maas00 disconnected
* rack controller maas00 disconnected
2019-01-31 14:33:33 maasserver.dhcp: [info] Successfully configured DHCPv4 on rack controller 'maas00 (xrrxcb)'.
2019-01-31 14:33:33 maasserver.dhcp: [info] Successfully configured DHCPv6 on rack controller 'maas00 (xrrxcb)'.
2019-01-31 14:33:47 regiond: [info] 127.0.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningser
2019-01-31 14:34:11 -: [info] b'/etc/resolv.conf' changed, reparsing
2019-01-31 14:34:11 -: [info] Resolver added ('127.0.0.53', 53) to server list
2019-01-31 14:34:17 regiond: [info] 127.0.0.1 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningser
maas.log:
2019-01-
2019-01-
2019-01-
2019-01-
2019-01-
2019-01-
2019-01-
2019-01-
version 2.5.1-7505-
2019-01-
2019-01-
Related branches
- Blake Rouse (community): Approve
-
Diff: 169 lines (+88/-3)5 files modifiedsrc/maasserver/management/commands/configauth.py (+20/-0)
src/maasserver/models/rbacsync.py (+3/-2)
src/maasserver/models/tests/test_rbacsync.py (+4/-1)
src/maasserver/tests/test_commands_configauth.py (+40/-0)
src/maasserver/tests/test_region_controller.py (+21/-0)
- Alberto Donato (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 169 lines (+88/-3)5 files modifiedsrc/maasserver/management/commands/configauth.py (+20/-0)
src/maasserver/models/rbacsync.py (+3/-2)
src/maasserver/models/tests/test_rbacsync.py (+4/-1)
src/maasserver/tests/test_commands_configauth.py (+40/-0)
src/maasserver/tests/test_region_controller.py (+21/-0)
Changed in maas: | |
importance: | Undecided → Critical |
milestone: | none → 2.5.1 |
Changed in maas: | |
status: | Confirmed → In Progress |
assignee: | Alberto Donato (ack) → Blake Rouse (blake-rouse) |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | 2.5.1 → 2.6.0 |
Changed in maas: | |
milestone: | 2.6.0 → 2.6.0alpha1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
This seems like configauth has a table that keeps the state and knows when it has been run against an RBAC. If we were to re-configure, such as in this case, it would think that it is the same rbac and no updates are send to RBAC.
It seems like any time this is run (configauth) we should be sending all the information again to rbac because, in fact, this could be a re-configuration.