Default gateway is not set
Bug #1953388 reported by
Lukas Hejtmanek
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Triaged
|
Medium
|
Unassigned | ||
| 3.3 |
Triaged
|
Medium
|
Unassigned | ||
| maas-ui |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
If a node has more than one network interfaces, default gateway can be set on the first (configured?) interface if you set manual IP configuration. You can alter configuration via CLI to set an interface to have default gateway, but this cannot be done in GUI. It also seems that this property is not cloned when one uses clone from function.
| tags: | added: ui |
Revision history for this message
| Alexsander de Souza (alexsander-souza) wrote | #1 |
| Changed in maas: | |
| status: | New → Incomplete |
| Changed in maas-ui: | |
| importance: | Undecided → Unknown |
Revision history for this message
| Lukas Hejtmanek (xhejtman) wrote | #2 |
Revision history for this message
| Lukas Hejtmanek (xhejtman) wrote | #3 |
| Changed in maas: | |
| status: | Incomplete → Triaged |
| importance: | Undecided → High |
| milestone: | none → next |
Revision history for this message
| Alexsander de Souza (alexsander-souza) wrote | #4 |
| Changed in maas: | |
| importance: | High → Medium |
| milestone: | next → 3.3.0 |
| Changed in maas: | |
| milestone: | 3.3.0 → 3.4.0 |
| Changed in maas: | |
| milestone: | 3.4.0 → 3.4.x |
| Changed in maas-ui: | |
| status: | New → Triaged |
| milestone: | none → 3.4.x |
| importance: | Unknown → Medium |
| tags: | removed: ui |
To post a comment you must log in.
Hi Lukas,
It seems that we have two issues here:
1) you cannot set the default GW using the UI, but can do it from the CLI. This looks like a feature request, so I looped the UI team in to check this.
2) cloning doesn't preserve the GW configuration.
The latter could be a bug, so I will try to reproduce it locally.
What MAAS version are you using?