Adding a LXD cluster with MAAS running in snap results in an individual host and cluster
Bug #1950827 reported by
Christian Grabowski
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Alexsander de Souza | ||
3.1 |
Fix Released
|
Critical
|
Alexsander de Souza |
Bug Description
Steps to reproduce:
1. Install MAAS snap 3.1/edge
2. Add a LXD cluster using a remote address and certificate
Actual result: there will be both an individual host with the settings configure, and a cluster with one of the members as you configured. Both will have the same configured address.
Expected result: no individual host is present, only clustered hosts are present, including the one configured.
Related branches
~ack/maas:1950827-3.1
- Alberto Donato (community): Approve
-
Diff: 50 lines (+13/-9)2 files modifiedsrc/maasserver/tests/test_vmhost.py (+1/-0)
src/maasserver/vmhost.py (+12/-9)
~alexsander-souza/maas:lp1950827_fix_dup_cluster
Merged
into
maas:master
- Alberto Donato (community): Approve
- MAAS Lander: Approve
-
Diff: 50 lines (+13/-9)2 files modifiedsrc/maasserver/tests/test_vmhost.py (+1/-0)
src/maasserver/vmhost.py (+12/-9)
Changed in maas: | |
status: | New → Triaged |
description: | updated |
Changed in maas: | |
assignee: | nobody → Alexsander de Souza (alexsander-souza) |
status: | Triaged → In Progress |
no longer affects: | maas/3.1 |
Changed in maas: | |
milestone: | 3.1.0-rc1 → none |
Changed in maas: | |
milestone: | none → 3.1.0 |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | 3.1.0 → 3.1.0-rc1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
maas $profile vm-hosts read output:
[
"capabilities" : [],
"memory_ over_commit_ ratio": 1.0,
"storage_ pools": [],
"pod- console- logging"
"available" : {
"cores" : 0,
"memory" : 0,
"local_ storage" : 0
"system_ id": "8w7btg", ...
{
"tags": [
],
},
"version": "",
"host": {