** Tags added: fr-2349
** Tags removed: rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745648
Title:
netplan renders bond lacp-rate as a timevalue should be "fast" or
"slow"
To
** Tags removed: rls-jj-incoming
** Tags added: rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745648
Title:
netplan renders bond lacp-rate as a timevalue should be "fast" or
The input validation for "lacp-rate" is still missing and should be
checked for "slow" or "fast" in src/parse.c.
Re-assigning to the netplan.io project as "nplan" is deprecated.
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: netplan
Ok, this is a bug in tests/generate.py, and a missing step to sanitize
the string (check for the correct values of 'slow' or 'fast') in
parse.c.
** Changed in: nplan (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
You're right. It looks like the unittest passes because it switched to a
string which is passed through.
But the value of 10 in the tests/generate.py for lacp-rate isn't right and
looks like parse is not validating
the string value.
On Fri, Jan 26, 2018 at 11:42 AM, Mathieu Trudel-Lapierre <
If it's the case, then this would be a critical bug. However, it looks
to me like LACP rate is being properly handled, values are 'slow' or
'fast', and an integration test exists to validate that.
** Changed in: nplan (Ubuntu)
Status: New => Triaged
** Changed in: nplan (Ubuntu)
