[Bug 1877643] [NEW] netplan.io 0.98 introduced more strict parsing of bonding mode, causing failures at boot for existing systems

[Steve Langasek]

Public bug reported:

As noted in
https://github.com/CanonicalLtd/netplan/pull/97#issuecomment-625868233 ,
netplan.io 0.98 has introduced stricter validation rules for netplan
yaml compared to previous versions.  This causes previously accepted
netplan yaml to fail to validate and therefore fail to apply, regressing
users' networks after SRU upgrade.

It may be appropriate from an upstream POV to make the validation of
input more strict over time, but it is never acceptable for an SRU to
regress the interpretation of user config in this manner and cause
config to fail to apply.  This PR either needs to be reverted for
bionic, or it needs to be modified to treat unknown modes as a warning
instead of a failure.

** Affects: netplan.io (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: netplan.io (Ubuntu Bionic)
     Importance: High
         Status: Triaged


** Tags: regression-update

** Also affects: netplan.io (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Changed in: netplan.io (Ubuntu Bionic)
       Status: New => Triaged

** Changed in: netplan.io (Ubuntu Bionic)
   Importance: Undecided => High

** Tags added: regression-update

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1877643

Title:
  netplan.io 0.98 introduced more strict parsing of bonding mode,
  causing failures at boot for existing systems

Status in netplan.io package in Ubuntu:
  New
Status in netplan.io source package in Bionic:
  Triaged

Bug description:
  As noted in
  https://github.com/CanonicalLtd/netplan/pull/97#issuecomment-625868233
  , netplan.io 0.98 has introduced stricter validation rules for netplan
  yaml compared to previous versions.  This causes previously accepted
  netplan yaml to fail to validate and therefore fail to apply,
  regressing users' networks after SRU upgrade.

  It may be appropriate from an upstream POV to make the validation of
  input more strict over time, but it is never acceptable for an SRU to
  regress the interpretation of user config in this manner and cause
  config to fail to apply.  This PR either needs to be reverted for
  bionic, or it needs to be modified to treat unknown modes as a warning
  instead of a failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1877643/+subscriptions