MAAS generates netplan with illegal autoconf and accept_ra flags for 22.04

Bug #2018149 reported by Boris Lukashev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Committed
Medium
Alberto Donato

Bug Description

When configuring bonds through the CLI (API), we normally add accept_ra=false autoconf=false parameters - produces:
```
    version: 2
    vlans:
        bond0.223:
            accept_ra: 0
            addresses:
```
Turns out, this is illegal on 22.04:
```
/var/log/cloud-init.log: /etc/netplan/50-cloud-init.yaml:70:13: Error in network definition: unknown key 'accept_ra'
```
which prevents nodes from completing provisioning.
Might be worth implementing a filter for the parameter to exclude it from OS' which don't support it as it completely cuts the node off from comms until placed into rescue mode by maas.

Related branches

Revision history for this message
Lukas Märdian (slyon) wrote :

I guess this should be called "accept-ra: false" instead?
https://netplan.readthedocs.io/en/stable/netplan-yaml/#properties-for-all-device-types

Revision history for this message
Boris Lukashev (rageltman) wrote :

Given that both the generator and consumer of the plan (not to mention the netplan abomination itself) are canonical products, I defer to the Ubuntu experts on how this should be constructed :).

I'm now debugging (trying to rescue-mode) the `autoconf=false` option, having removed accept_ra from my CLI config and rebuilt all VLANs on the bonds, because the nodes are still not coming up with network access in the subnets on VLANs of their bonds...

Is there any CI/CD pipe out there testing outcomes of configuration in terms of applying all combinations of config parameters permissible through the API/CLI to all supported (or at least Canonical) targets? We're at 22.04.2 - was a full complement of tests performed on .0, .1, and .2 of the long-term supported release?

Revision history for this message
Boris Lukashev (rageltman) wrote :

Awesome, so _neither_ of the optional parameters are valid under 22.04...
Autoconf gets written into netplan as:
```
    vlans:
        bond0.222:
            addresses:
            - 10.2.1.22/24
            autoconf: 0
```
which causes
```
/mnt/zfs/var/log/cloud-init-output.log: /etc/netplan/50-cloud-init.yaml:72:13: Error in network definition: unknown key 'autoconf'

```

summary: - MAAS generates netplan with illegal accept_ra flag for 22.04
+ MAAS generates netplan with illegal autoconf and accept_ra flags for
+ 22.04
Revision history for this message
Alberto Donato (ack) wrote :

What version of MAAS are you using? The accept_ra issue (see LP:1927036) should befixed in 3.0.0.

Changed in maas:
status: New → Incomplete
Revision history for this message
Boris Lukashev (rageltman) wrote :

@alberto donato: 3.3/stable snap channel.

Revision history for this message
Alberto Donato (ack) wrote :

Could you please paste the output of

maas $profile machine read $system_id

and

maas $profile machine get-curtin-config $system_id

for the machine configured with the bond?

Changed in maas:
status: Incomplete → New
status: New → Incomplete
Alberto Donato (ack)
Changed in maas:
assignee: nobody → Alberto Donato (ack)
Alberto Donato (ack)
Changed in maas:
milestone: none → 3.4.0
Changed in maas:
status: Incomplete → Fix Committed
Alberto Donato (ack)
Changed in maas:
status: Fix Committed → In Progress
importance: Undecided → Medium
Changed in maas:
status: In Progress → Fix Committed
Alberto Donato (ack)
Changed in maas:
milestone: 3.4.0 → 3.4.0-beta2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.