| 2021-02-16 14:20:32 |
Frode Nordahl |
bug |
|
|
added bug |
| 2021-02-16 14:20:39 |
Frode Nordahl |
openvswitch (Ubuntu): assignee |
|
Frode Nordahl (fnordahl) |
|
| 2021-02-16 14:20:44 |
Frode Nordahl |
openvswitch (Ubuntu): status |
New |
Triaged |
|
| 2021-02-16 14:20:48 |
Frode Nordahl |
openvswitch (Ubuntu): status |
Triaged |
In Progress |
|
| 2021-02-16 14:20:56 |
Frode Nordahl |
openvswitch (Ubuntu): importance |
Undecided |
High |
|
| 2021-02-16 16:22:04 |
Frode Nordahl |
description |
The Open vSwitch init script `ovs-ctl` determines the system hostname and records it in the `external-ids:hostname` field of the `Open-vSwitch` table in the local OVSDB.
This value may be consumed by downstream software and having it unset or set to a incorrect value could lead to erratic behavior of a system.
In recent Ubuntu development we have also made it possible to configure Open vSwitch with netplan.io, which allows for a Open vSwitch controlled data path to be the only external network connection on a system.
As such the current startup sequence of Open vSwitch is insufficient to allow for reliable recording of FQDN / hostname at system boot-up time.
A possible solution to this would be to extend the upstream `ovs-ctl` script to allow controlling when the hostname is recorded and adding a new Systemd service file to the package that calls the `record-hostname` function at a more appropriate time, i.e. after or as part of the `network-online.target`. |
The Open vSwitch init script `ovs-ctl` determines the system hostname and records it in the `external-ids:hostname` field of the `Open-vSwitch` table in the local OVSDB.
This value may be consumed by downstream software and having it unset or set to a incorrect value could lead to erratic behavior of a system.
In recent Ubuntu development we have also made it possible to configure Open vSwitch with netplan.io, which allows for a Open vSwitch controlled data path to be the only external network connection on a system.
As such the current startup sequence of Open vSwitch is insufficient to allow for reliable recording of FQDN / hostname at system boot-up time.
A possible solution to this would be to extend the upstream `ovs-ctl` script to allow controlling when the hostname is recorded and adding a new Systemd service file to the package that calls the `record-hostname` function at a more appropriate time, i.e. after or as part of the `network-online.target`.
An example of downstream issues can be viewed in bug 1896630. |
|
| 2021-02-16 21:47:54 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~fnordahl/ubuntu/+source/openvswitch/+git/openvswitch/+merge/398164 |
|
| 2021-02-17 02:42:40 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~fnordahl/ubuntu/+source/openvswitch/+git/openvswitch/+merge/398174 |
|
| 2021-02-19 08:36:09 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
| 2021-03-05 16:33:56 |
Frode Nordahl |
openvswitch (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2021-03-05 16:34:15 |
Frode Nordahl |
nominated for series |
|
Ubuntu Focal |
|
| 2021-03-05 16:34:15 |
Frode Nordahl |
bug task added |
|
openvswitch (Ubuntu Focal) |
|
| 2021-03-05 16:34:15 |
Frode Nordahl |
nominated for series |
|
Ubuntu Groovy |
|
| 2021-03-05 16:34:15 |
Frode Nordahl |
bug task added |
|
openvswitch (Ubuntu Groovy) |
|
| 2021-03-05 16:34:15 |
Frode Nordahl |
nominated for series |
|
Ubuntu Hirsute |
|
| 2021-03-05 16:34:15 |
Frode Nordahl |
bug task added |
|
openvswitch (Ubuntu Hirsute) |
|
| 2021-03-05 16:34:53 |
Frode Nordahl |
openvswitch (Ubuntu Groovy): importance |
Undecided |
High |
|
| 2021-03-05 16:34:55 |
Frode Nordahl |
openvswitch (Ubuntu Focal): importance |
Undecided |
High |
|
| 2021-03-05 16:34:58 |
Frode Nordahl |
openvswitch (Ubuntu Groovy): status |
New |
Triaged |
|
| 2021-03-05 16:35:02 |
Frode Nordahl |
openvswitch (Ubuntu Focal): status |
New |
Triaged |
|
| 2021-03-05 16:35:06 |
Frode Nordahl |
openvswitch (Ubuntu Groovy): assignee |
|
Frode Nordahl (fnordahl) |
|
| 2021-03-05 16:35:08 |
Frode Nordahl |
openvswitch (Ubuntu Focal): assignee |
|
Frode Nordahl (fnordahl) |
|
| 2021-03-06 14:57:31 |
Launchpad Janitor |
openvswitch (Ubuntu Hirsute): status |
Fix Committed |
Fix Released |
|
| 2021-03-17 06:59:20 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~fnordahl/ubuntu/+source/openvswitch/+git/openvswitch/+merge/399763 |
|
| 2021-03-17 06:59:45 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~fnordahl/ubuntu/+source/openvswitch/+git/openvswitch/+merge/399764 |
|
| 2021-03-17 07:20:54 |
Frode Nordahl |
description |
The Open vSwitch init script `ovs-ctl` determines the system hostname and records it in the `external-ids:hostname` field of the `Open-vSwitch` table in the local OVSDB.
This value may be consumed by downstream software and having it unset or set to a incorrect value could lead to erratic behavior of a system.
In recent Ubuntu development we have also made it possible to configure Open vSwitch with netplan.io, which allows for a Open vSwitch controlled data path to be the only external network connection on a system.
As such the current startup sequence of Open vSwitch is insufficient to allow for reliable recording of FQDN / hostname at system boot-up time.
A possible solution to this would be to extend the upstream `ovs-ctl` script to allow controlling when the hostname is recorded and adding a new Systemd service file to the package that calls the `record-hostname` function at a more appropriate time, i.e. after or as part of the `network-online.target`.
An example of downstream issues can be viewed in bug 1896630. |
[ Impact ]
The Open vSwitch init script `ovs-ctl` determines the system hostname and records it in the `external-ids:hostname` field of the `Open-vSwitch` table in the local OVSDB.
This value may be consumed by downstream software and having it unset or set to a incorrect value could lead to erratic behavior of a system.
In recent Ubuntu development we have also made it possible to configure Open vSwitch with netplan.io, which allows for a Open vSwitch controlled data path to be the only external network connection on a system.
As such the current startup sequence of Open vSwitch is insufficient to allow for reliable recording of FQDN / hostname at system boot-up time.
Examples of downstream issues can be viewed in bug 1896630 and bug 1912844 comment #26.
[ Test Case ]
1) Use MAAS 2.9, configure a machine with Open vSwitch bridge for networking and deploy.
2) Confirm that without the change the hostname recorded in Open vSwitch is `ubuntu`.
3) Add a PPA with the updated Open vSwitch package to MAAS.
4) Re-deploy and confirm that the hostname recorded in Open vSwitch matches the FQDN as provided by MAAS.
[ Regression potential ]
Minimal, the update uses the exact same methods to accomplish the end result of recording the hostname as before, we have only re-ordered when the events occur to ensure successful operation.
[ Other Info ]
A possible solution to this would be to extend the upstream `ovs-ctl` script to allow controlling when the hostname is recorded and adding a new Systemd service file to the package that calls the `record-hostname` function at a more appropriate time, i.e. after or as part of the `network-online.target`.
An example of downstream issues can be viewed in bug 1896630. |
|
| 2021-03-17 07:52:35 |
James Page |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-03-17 07:52:51 |
James Page |
bug task added |
|
cloud-archive |
|
| 2021-03-17 07:53:00 |
James Page |
nominated for series |
|
cloud-archive/ussuri |
|
| 2021-03-17 07:53:00 |
James Page |
bug task added |
|
cloud-archive/ussuri |
|
| 2021-03-17 07:53:00 |
James Page |
nominated for series |
|
cloud-archive/wallaby |
|
| 2021-03-17 07:53:00 |
James Page |
bug task added |
|
cloud-archive/wallaby |
|
| 2021-03-17 07:53:00 |
James Page |
nominated for series |
|
cloud-archive/victoria |
|
| 2021-03-17 07:53:00 |
James Page |
bug task added |
|
cloud-archive/victoria |
|
| 2021-03-17 07:53:07 |
James Page |
cloud-archive/wallaby: status |
New |
Triaged |
|
| 2021-03-17 07:53:09 |
James Page |
cloud-archive/victoria: status |
New |
Triaged |
|
| 2021-03-17 07:53:11 |
James Page |
cloud-archive/ussuri: status |
New |
Triaged |
|
| 2021-03-17 07:53:14 |
James Page |
cloud-archive/wallaby: status |
Triaged |
Fix Released |
|
| 2021-03-17 07:53:16 |
James Page |
cloud-archive/victoria: importance |
Undecided |
High |
|
| 2021-03-17 07:53:17 |
James Page |
cloud-archive/ussuri: importance |
Undecided |
High |
|
| 2021-03-17 07:53:19 |
James Page |
cloud-archive/wallaby: importance |
Undecided |
High |
|
| 2021-04-05 11:26:19 |
Dmitrii Shcherbakov |
openvswitch (Ubuntu Focal): status |
Triaged |
Fix Committed |
|
| 2021-04-05 11:26:21 |
Dmitrii Shcherbakov |
openvswitch (Ubuntu Groovy): status |
Triaged |
Fix Committed |
|
| 2021-04-07 10:27:42 |
James Page |
openvswitch (Ubuntu Focal): status |
Fix Committed |
In Progress |
|
| 2021-04-07 10:27:43 |
James Page |
openvswitch (Ubuntu Groovy): status |
Fix Committed |
In Progress |
|
| 2021-04-09 13:58:51 |
Robie Basak |
description |
[ Impact ]
The Open vSwitch init script `ovs-ctl` determines the system hostname and records it in the `external-ids:hostname` field of the `Open-vSwitch` table in the local OVSDB.
This value may be consumed by downstream software and having it unset or set to a incorrect value could lead to erratic behavior of a system.
In recent Ubuntu development we have also made it possible to configure Open vSwitch with netplan.io, which allows for a Open vSwitch controlled data path to be the only external network connection on a system.
As such the current startup sequence of Open vSwitch is insufficient to allow for reliable recording of FQDN / hostname at system boot-up time.
Examples of downstream issues can be viewed in bug 1896630 and bug 1912844 comment #26.
[ Test Case ]
1) Use MAAS 2.9, configure a machine with Open vSwitch bridge for networking and deploy.
2) Confirm that without the change the hostname recorded in Open vSwitch is `ubuntu`.
3) Add a PPA with the updated Open vSwitch package to MAAS.
4) Re-deploy and confirm that the hostname recorded in Open vSwitch matches the FQDN as provided by MAAS.
[ Regression potential ]
Minimal, the update uses the exact same methods to accomplish the end result of recording the hostname as before, we have only re-ordered when the events occur to ensure successful operation.
[ Other Info ]
A possible solution to this would be to extend the upstream `ovs-ctl` script to allow controlling when the hostname is recorded and adding a new Systemd service file to the package that calls the `record-hostname` function at a more appropriate time, i.e. after or as part of the `network-online.target`.
An example of downstream issues can be viewed in bug 1896630. |
[ Impact ]
The Open vSwitch init script `ovs-ctl` determines the system hostname and records it in the `external-ids:hostname` field of the `Open-vSwitch` table in the local OVSDB.
This value may be consumed by downstream software and having it unset or set to a incorrect value could lead to erratic behavior of a system.
In recent Ubuntu development we have also made it possible to configure Open vSwitch with netplan.io, which allows for a Open vSwitch controlled data path to be the only external network connection on a system.
As such the current startup sequence of Open vSwitch is insufficient to allow for reliable recording of FQDN / hostname at system boot-up time.
Examples of downstream issues can be viewed in bug 1896630 and bug 1912844 comment #26.
[ Test Case ]
1) Use MAAS 2.9, configure a machine with Open vSwitch bridge for networking and deploy.
2) Confirm that without the change the hostname recorded in Open vSwitch is `ubuntu`.
3) Add a PPA with the updated Open vSwitch package to MAAS.
4) Re-deploy and confirm that the hostname recorded in Open vSwitch matches the FQDN as provided by MAAS.
[ Regression potential ]
Minimal, the update uses the exact same methods to accomplish the end result of recording the hostname as before, we have only re-ordered when the events occur to ensure successful operation.
[racb] A new service is added in packaging. Users who have overridden existing services to change behaviour (eg. "disable all OVS-related services") may have that configuration not have the same effect after this update (eg. "I thought I disabled all OVS-related services but what's this ovs-record-hostname thing now?")
[ Other Info ]
A possible solution to this would be to extend the upstream `ovs-ctl` script to allow controlling when the hostname is recorded and adding a new Systemd service file to the package that calls the `record-hostname` function at a more appropriate time, i.e. after or as part of the `network-online.target`.
An example of downstream issues can be viewed in bug 1896630. |
|
| 2021-04-13 12:43:40 |
Robie Basak |
openvswitch (Ubuntu Groovy): status |
In Progress |
Fix Committed |
|
| 2021-04-13 12:43:42 |
Robie Basak |
bug |
|
|
added subscriber SRU Verification |
| 2021-04-13 12:43:44 |
Robie Basak |
tags |
|
verification-needed verification-needed-groovy |
|
| 2021-04-13 12:45:01 |
Robie Basak |
openvswitch (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2021-04-13 12:45:08 |
Robie Basak |
tags |
verification-needed verification-needed-groovy |
verification-needed verification-needed-focal verification-needed-groovy |
|
| 2021-04-14 09:34:12 |
James Page |
cloud-archive/ussuri: status |
Triaged |
Fix Committed |
|
| 2021-04-14 09:34:14 |
James Page |
tags |
verification-needed verification-needed-focal verification-needed-groovy |
verification-needed verification-needed-focal verification-needed-groovy verification-ussuri-needed |
|
| 2021-05-11 13:45:40 |
Frode Nordahl |
description |
[ Impact ]
The Open vSwitch init script `ovs-ctl` determines the system hostname and records it in the `external-ids:hostname` field of the `Open-vSwitch` table in the local OVSDB.
This value may be consumed by downstream software and having it unset or set to a incorrect value could lead to erratic behavior of a system.
In recent Ubuntu development we have also made it possible to configure Open vSwitch with netplan.io, which allows for a Open vSwitch controlled data path to be the only external network connection on a system.
As such the current startup sequence of Open vSwitch is insufficient to allow for reliable recording of FQDN / hostname at system boot-up time.
Examples of downstream issues can be viewed in bug 1896630 and bug 1912844 comment #26.
[ Test Case ]
1) Use MAAS 2.9, configure a machine with Open vSwitch bridge for networking and deploy.
2) Confirm that without the change the hostname recorded in Open vSwitch is `ubuntu`.
3) Add a PPA with the updated Open vSwitch package to MAAS.
4) Re-deploy and confirm that the hostname recorded in Open vSwitch matches the FQDN as provided by MAAS.
[ Regression potential ]
Minimal, the update uses the exact same methods to accomplish the end result of recording the hostname as before, we have only re-ordered when the events occur to ensure successful operation.
[racb] A new service is added in packaging. Users who have overridden existing services to change behaviour (eg. "disable all OVS-related services") may have that configuration not have the same effect after this update (eg. "I thought I disabled all OVS-related services but what's this ovs-record-hostname thing now?")
[ Other Info ]
A possible solution to this would be to extend the upstream `ovs-ctl` script to allow controlling when the hostname is recorded and adding a new Systemd service file to the package that calls the `record-hostname` function at a more appropriate time, i.e. after or as part of the `network-online.target`.
An example of downstream issues can be viewed in bug 1896630. |
[ Impact ]
The Open vSwitch init script `ovs-ctl` determines the system hostname and records it in the `external-ids:hostname` field of the `Open-vSwitch` table in the local OVSDB.
This value may be consumed by downstream software and having it unset or set to a incorrect value could lead to erratic behavior of a system.
In recent Ubuntu development we have also made it possible to configure Open vSwitch with netplan.io, which allows for a Open vSwitch controlled data path to be the only external network connection on a system.
As such the current startup sequence of Open vSwitch is insufficient to allow for reliable recording of FQDN / hostname at system boot-up time.
Examples of downstream issues can be viewed in bug 1896630 and bug 1912844 comment #26.
[ Test Case ]
1) Deploy bundle on metal:
series: focal
machines:
'0':
constraints: cores=48
relations:
- - octavia:ovsdb-subordinate
- ovn-chassis:ovsdb-subordinate
applications:
ovn-chassis:
charm: cs:ovn-chassis
bindings:
"": public-space
octavia:
charm: cs:octavia
options:
openstack-origin: distro
num_units: 1
to:
- 'lxd:0'
bindings:
"": public-space
2) juju run --unit ovn-chassis/0 'ovs-vsctl remove open-vswitch . external-ids hostname'
3) juju run --unit ovn-chassis/0 'sudo shutdown -r now'
4) Observe external-ids:hostname being recorded as a shortname
5) Add proposed and install openvswitch packages, repeat step 2-3
6) Observe external-ids:hostname being recorded as a FQDN
[ Regression potential ]
Minimal, the update uses the exact same methods to accomplish the end result of recording the hostname as before, we have only re-ordered when the events occur to ensure successful operation.
[racb] A new service is added in packaging. Users who have overridden existing services to change behaviour (eg. "disable all OVS-related services") may have that configuration not have the same effect after this update (eg. "I thought I disabled all OVS-related services but what's this ovs-record-hostname thing now?")
[ Other Info ]
A possible solution to this would be to extend the upstream `ovs-ctl` script to allow controlling when the hostname is recorded and adding a new Systemd service file to the package that calls the `record-hostname` function at a more appropriate time, i.e. after or as part of the `network-online.target`.
An example of downstream issues can be viewed in bug 1896630. |
|
| 2021-05-11 13:49:48 |
Frode Nordahl |
tags |
verification-needed verification-needed-focal verification-needed-groovy verification-ussuri-needed |
verification-done-focal verification-needed verification-needed-groovy verification-ussuri-needed |
|
| 2021-05-13 12:53:23 |
James Page |
tags |
verification-done-focal verification-needed verification-needed-groovy verification-ussuri-needed |
verification-done-focal verification-done-groovy verification-needed verification-ussuri-needed |
|
| 2021-05-13 12:54:00 |
James Page |
cloud-archive/victoria: status |
Triaged |
Invalid |
|
| 2021-05-17 23:14:24 |
Launchpad Janitor |
openvswitch (Ubuntu Groovy): status |
Fix Committed |
Fix Released |
|
| 2021-05-17 23:14:24 |
Launchpad Janitor |
cve linked |
|
2015-8011 |
|
| 2021-05-17 23:14:24 |
Launchpad Janitor |
cve linked |
|
2020-27827 |
|
| 2021-05-17 23:14:24 |
Launchpad Janitor |
cve linked |
|
2020-35498 |
|
| 2021-05-17 23:14:42 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2021-05-17 23:15:58 |
Launchpad Janitor |
openvswitch (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-05-25 07:44:21 |
Frode Nordahl |
tags |
verification-done-focal verification-done-groovy verification-needed verification-ussuri-needed |
verification-done verification-done-focal verification-done-groovy verification-ussuri-done |
|
| 2021-06-03 15:15:07 |
Chris MacNaughton |
cloud-archive/ussuri: status |
Fix Committed |
Fix Released |
|
