[Yahoo-eng-team] [Bug 1978543] [NEW] default not accepted as destination in routes: in the network-config
Public bug reported:
I have this network-config file (which is valid as per netplan
version: 2
ethernets:
enp0s3:
dhcp4: false
addresses: [10.0.4.10/24]
nameservers:
addresses: [10.0.4.1]
routes:
- to: default
via: 10.0.4.1
metric: 100
And cloud-config bumps on the 'default':
022-06-14 10:30:10,662 - util.py[WARNING]: failed stage init-local
failed run of stage init-local
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 738, in
status_wrapper
ret = functor(name, args)
File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 410, in
main_init
...
File "/usr/lib/python3/dist-packages/cloudinit/net/network_state.py", line 953
, in _normalize_net_keys
raise ValueError(f"Address {addr} is not a valid ip address")
ValueError: Address default is not a valid ip address
student@osm11:~$ uname -a
Linux osm11 5.4.0-117-generic #132-Ubuntu SMP Thu Jun 2 00:39:06 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux
student@osm11:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.4 LTS"
With the cloud-enabled OVA from
https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.ova
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1978543
Title:
default not accepted as destination in routes: in the network-config
Status in cloud-init:
New
Bug description:
I have this network-config file (which is valid as per netplan
version: 2
ethernets:
enp0s3:
dhcp4: false
addresses: [10.0.4.10/24]
nameservers:
addresses: [10.0.4.1]
routes:
- to: default
via: 10.0.4.1
metric: 100
And cloud-config bumps on the 'default':
022-06-14 10:30:10,662 - util.py[WARNING]: failed stage init-local
failed run of stage init-local
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 738, in
status_wrapper
ret = functor(name, args)
File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 410, in
main_init
...
File "/usr/lib/python3/dist-packages/cloudinit/net/network_state.py", line
953
, in _normalize_net_keys
raise ValueError(f"Address {addr} is not a valid ip address")
ValueError: Address default is not a valid ip address
student@osm11:~$ uname -a
Linux osm11 5.4.0-117-generic #132-Ubuntu SMP Thu Jun 2 00:39:06 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux
student@osm11:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.4 LTS"
With the cloud-enabled OVA from
https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.ova
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1978543/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1978549] [NEW] Placement resource_providers table has dangling column "can_host"
Public bug reported: With bug https://bugs.launchpad.net/nova/+bug/1648197 or rather change https://review.opendev.org/c/openstack/nova/+/461494 the can_host column was removed from the resource_provider table in the placement db. 1) Apparently there is no migration task to also drop this column should it exist already (due to an installation being older than this change), see https://opendev.org/openstack/placement/src/branch/master/placement/db/sqlalchemy/alembic/versions See my comment https://bugs.launchpad.net/nova/+bug/1648197/comments/9 on how I ran into this while changing from PostgreSQL -> MariaDB on an Ussuri installation. 2) I just might be confused here ... but it seems the column is still used in Nova? https://github.com/openstack/nova/blob/master/nova/db/main/migrations/versions/8f2f1571d55b_initial_version.py ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1978549 Title: Placement resource_providers table has dangling column "can_host" Status in OpenStack Compute (nova): New Bug description: With bug https://bugs.launchpad.net/nova/+bug/1648197 or rather change https://review.opendev.org/c/openstack/nova/+/461494 the can_host column was removed from the resource_provider table in the placement db. 1) Apparently there is no migration task to also drop this column should it exist already (due to an installation being older than this change), see https://opendev.org/openstack/placement/src/branch/master/placement/db/sqlalchemy/alembic/versions See my comment https://bugs.launchpad.net/nova/+bug/1648197/comments/9 on how I ran into this while changing from PostgreSQL -> MariaDB on an Ussuri installation. 2) I just might be confused here ... but it seems the column is still used in Nova? https://github.com/openstack/nova/blob/master/nova/db/main/migrations/versions/8f2f1571d55b_initial_version.py To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1978549/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1978549] Re: Placement resource_providers table has dangling column "can_host"
I documented that can_host can be manually removed from the DB in https://review.opendev.org/c/openstack/placement/+/845730 I set this bug to Won't Fix as I don't think we want to go back to stein and add a DB migration or change the initial DB schema of Placement. Feel free to set it back to New if you disagree ** Changed in: nova Status: New => Won't Fix ** Tags added: db placement -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1978549 Title: Placement resource_providers table has dangling column "can_host" Status in OpenStack Compute (nova): Won't Fix Bug description: With bug https://bugs.launchpad.net/nova/+bug/1648197 or rather change https://review.opendev.org/c/openstack/nova/+/461494 the can_host column was removed from the resource_provider table in the placement db. 1) Apparently there is no migration task to also drop this column should it exist already (due to an installation being older than this change), see https://opendev.org/openstack/placement/src/branch/master/placement/db/sqlalchemy/alembic/versions See my comment https://bugs.launchpad.net/nova/+bug/1648197/comments/9 on how I ran into this while changing from PostgreSQL -> MariaDB on an Ussuri installation. 2) I just might be confused here ... but it seems the column is still used in Nova? https://github.com/openstack/nova/blob/master/nova/db/main/migrations/versions/8f2f1571d55b_initial_version.py To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1978549/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1978564] [NEW] Unit tests fail with latest pyroute2 releases
Public bug reported: With the latest pyroute2 releases, import handling has changed again, causing some unit tests to fail. https://zuul.opendev.org/t/openstack/build/c217d83a69664925aad47be4398f5b9a 2022-06-14 03:53:43.007328 | ubuntu-focal | == 2022-06-14 03:53:43.007340 | ubuntu-focal | Failed 3 tests - output below: 2022-06-14 03:53:43.007351 | ubuntu-focal | == 2022-06-14 03:53:43.007363 | ubuntu-focal | 2022-06-14 03:53:43.007374 | ubuntu-focal | neutron.tests.unit.agent.linux.test_tc_lib.TcTestCase.test_list_tc_qdiscs_tbf 2022-06-14 03:53:43.007409 | ubuntu-focal | - 2022-06-14 03:53:43.007420 | ubuntu-focal | 2022-06-14 03:53:43.007431 | ubuntu-focal | Captured traceback: 2022-06-14 03:53:43.007445 | ubuntu-focal | ~~~ 2022-06-14 03:53:43.007456 | ubuntu-focal | Traceback (most recent call last): 2022-06-14 03:53:43.007475 | ubuntu-focal | 2022-06-14 03:53:43.007486 | ubuntu-focal | File "/usr/lib/python3.8/unittest/mock.py", line 1215, in _dot_lookup 2022-06-14 03:53:43.007496 | ubuntu-focal | return getattr(thing, comp) 2022-06-14 03:53:43.007507 | ubuntu-focal | 2022-06-14 03:53:43.007517 | ubuntu-focal | AttributeError: module 'pyroute2' has no attribute 'netlink' 2022-06-14 03:53:43.007532 | ubuntu-focal | 2022-06-14 03:53:43.007544 | ubuntu-focal | 2022-06-14 03:53:43.007555 | ubuntu-focal | During handling of the above exception, another exception occurred: 2022-06-14 03:53:43.007566 | ubuntu-focal | 2022-06-14 03:53:43.007576 | ubuntu-focal | 2022-06-14 03:53:43.007586 | ubuntu-focal | Traceback (most recent call last): 2022-06-14 03:53:43.007597 | ubuntu-focal | 2022-06-14 03:53:43.007607 | ubuntu-focal | File "/home/zuul/src/opendev.org/openstack/neutron/neutron/tests/base.py", line 182, in func 2022-06-14 03:53:43.007618 | ubuntu-focal | return f(self, *args, **kwargs) 2022-06-14 03:53:43.007628 | ubuntu-focal | 2022-06-14 03:53:43.007639 | ubuntu-focal | File "/usr/lib/python3.8/unittest/mock.py", line 1322, in patched 2022-06-14 03:53:43.007649 | ubuntu-focal | with self.decoration_helper(patched, 2022-06-14 03:53:43.007660 | ubuntu-focal | 2022-06-14 03:53:43.007670 | ubuntu-focal | File "/usr/lib/python3.8/contextlib.py", line 113, in __enter__ 2022-06-14 03:53:43.007681 | ubuntu-focal | return next(self.gen) 2022-06-14 03:53:43.007698 | ubuntu-focal | 2022-06-14 03:53:43.007708 | ubuntu-focal | File "/usr/lib/python3.8/unittest/mock.py", line 1304, in decoration_helper 2022-06-14 03:53:43.007719 | ubuntu-focal | arg = exit_stack.enter_context(patching) 2022-06-14 03:53:43.007729 | ubuntu-focal | 2022-06-14 03:53:43.007740 | ubuntu-focal | File "/usr/lib/python3.8/contextlib.py", line 425, in enter_context 2022-06-14 03:53:43.007750 | ubuntu-focal | result = _cm_type.__enter__(cm) 2022-06-14 03:53:43.007778 | ubuntu-focal | 2022-06-14 03:53:43.007790 | ubuntu-focal | File "/usr/lib/python3.8/unittest/mock.py", line 1377, in __enter__ 2022-06-14 03:53:43.007800 | ubuntu-focal | self.target = self.getter() 2022-06-14 03:53:43.007810 | ubuntu-focal | 2022-06-14 03:53:43.007820 | ubuntu-focal | File "/usr/lib/python3.8/unittest/mock.py", line 1552, in 2022-06-14 03:53:43.007830 | ubuntu-focal | getter = lambda: _importer(target) 2022-06-14 03:53:43.007840 | ubuntu-focal | 2022-06-14 03:53:43.007849 | ubuntu-focal | File "/usr/lib/python3.8/unittest/mock.py", line 1228, in _importer 2022-06-14 03:53:43.007859 | ubuntu-focal | thing = _dot_lookup(thing, comp, import_path) 2022-06-14 03:53:43.007869 | ubuntu-focal | 2022-06-14 03:53:43.007878 | ubuntu-focal | File "/usr/lib/python3.8/unittest/mock.py", line 1218, in _dot_lookup 2022-06-14 03:53:43.007888 | ubuntu-focal | return getattr(thing, comp) 2022-06-14 03:53:43.007898 | ubuntu-focal | 2022-06-14 03:53:43.007908 | ubuntu-focal | AttributeError: module 'pyroute2' has no attribute 'netlink' 2022-06-14 03:53:43.007918 | ubuntu-focal | 2022-06-14 03:53:43.007928 | ubuntu-focal | 2022-06-14 03:53:43.007937 | ubuntu-focal | neutron.tests.unit.agent.linux.test_tc_lib.TcPolicyClassTestCase.test_list_tc_policy_classes 2022-06-14 03:53:43.007947 | ubuntu-focal | 2022-06-14 03:53:43.007957 | ubuntu-focal | 2022-06-14 03:53:43.007974 | ubuntu-focal | Captured traceback: 2022-06-14 03:53:43.007985 | ubuntu-focal | ~~~ 2022-06-14 03:53:43.007995 | ubuntu-focal | Traceback (most recent call last): 2022-06-14 03:53:43.008004 | ubuntu-focal | 2022-06-14 03:53:43.008014 | ubuntu-focal | File "/usr/lib/python3.8/unittest/mock.py", line 1215, in _dot_lookup 2022-06-14 03:53:43.008024 | ubuntu-focal | return getattr(thing, comp) 2022-06-14 03:53:
[Yahoo-eng-team] [Bug 1893121] Re: nova does not balance vm across numa node or prefer numa node with pci device when one is requested
this was fixed by https://github.com/openstack/nova/commit/d13412648d011994a146dac1e7214ead3b82b31b ** Changed in: nova Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1893121 Title: nova does not balance vm across numa node or prefer numa node with pci device when one is requested Status in OpenStack Compute (nova): Fix Released Bug description: the current implementation of numa has evolved over the years to support pci affinity policyes and numa affinity for other deivces like pmem. when numa was first intoduced the recomenation was to match the virtual numa toplogy of a guest to the numa toplogy of the host for best performance. in such a configuration the guest cpus and memory are evenly distubuted across the host numa nodes meanin that the memroy contoler and phsyicall cpus are consumed evenly. i.e. all vms do not use the cores form oh host numa node. if you create a vm with only hw:numa_nodes set and no other numa requests however due to how we currently iterage over host numa cells in a deterministic order the all vms will be placeed on numa node 0. if other vms also request numa resource like pinned cpus hw:cpu_policy=dedicated or explict pages size hw:mem_page_size then the consumption of those resource will eventually cause those vms to loadblance onto the other numa nodes. as a reuslt the current behavior is to fill the first numa node before ever using resouces form the rest for numa vms using cpu pinnign or hugepages but numa vms that only request hw:numa_nodes wont be loadblanced. in both case this is suboptimal as it resulting in lower utilisation of the host hardware as the second and subsequent numa nodes will not be used untill the first numa node is full when using pinning and huge pages and will never be used for numa instance that dont request other numa resources. in a similar vain https://specs.openstack.org/openstack/nova-specs/specs/pike/implemented/reserve-numa-with-pci.html partly implemented a preferential sorting of host with pci devices. if the vm did not request a pci device we weighter host with pcidevice lowere vs host without them. https://github.com/openstack/nova/blob/20459e3e88cb8382d450c7fdb042e2016d5560c5/nova/virt/hardware.py#L2268-L2275 a full implemation would have on the selected host prefer putting the vms on numa nodes that had a pci device. as a result if a host has 2 numa nodes and the vm request a pci deice and 1 numa node. if the vm will fit on the first numa node (node0) and has the prefered police for pci affintiy we wont check or use the second numa node (node1). the fix for this is triviail add an else clause # If PCI device(s) are not required, prefer host cells that don't have # devices attached. Presence of a given numa_node in a PCI pool is # indicative of a PCI device being associated with that node if not pci_requests and pci_stats: # TODO(stephenfin): pci_stats can't be None here but mypy can't figure # that out for some reason host_cells = sorted(host_cells, key=lambda cell: cell.id in [ pool['numa_node'] for pool in pci_stats.pools]) # type: ignore becomes # If PCI device(s) are not required, prefer host cells that don't have # devices attached. Presence of a given numa_node in a PCI pool is # indicative of a PCI device being associated with that node if not pci_requests and pci_stats: # TODO(stephenfin): pci_stats can't be None here but mypy can't figure # that out for some reason host_cells = sorted(host_cells, key=lambda cell: cell.id in [ pool['numa_node'] for pool in pci_stats.pools]) # type: ignore else: host_cells = sorted(host_cells, key=lambda cell: cell.id in [ pool['numa_node'] for pool in pci_stats.pools], reverse=True) # type: ignore or more compactly # If PCI device(s) are not required, prefer host cells that don't have # devices attached. Presence of a given numa_node in a PCI pool is # indicative of a PCI device being associated with that node reverse = pci_requests and pci_stats: # TODO(stephenfin): pci_stats can't be None here but mypy can't figure # that out for some reason host_cells = sorted(host_cells, key=lambda cell: cell.id in [ pool['numa_node'] for pool in pci_stats.pools], reverse=reverse) # type: ignore since python support stable sort orders complex sort can be achcive by multiple stables sorts https://docs.python.org/3/howto/sorting.html#sort-stability-and- complex-sorts so we can also adress the numa blanceing issue by first sorting by instance per numa node then sorting by free memory per num
[Yahoo-eng-team] [Bug 1978571] [NEW] VPNaaS: creating ipsec site connection fails (in master)
Public bug reported: With the current master branch of neutron and neutron-vpnaas requests to create VPN ipsec site connections fail with a 500 Internal Server Error. I noticed that in a devstack with vpnaas enabled. The automated tests (neutron-tempest-plugin-vpnaas) also started to fail. See https://zuul.opendev.org/t/openstack/build/7f680cca45544cec9e3418bda7399324 In the neutron-server log there is an exception (see below). This seems to be related to neutron commit 6b529ea3c559ed1a016e2aa2c30769429192d528 "[sqlalchemy-20] Use session.transaction information to decide if active" https://review.opendev.org/c/openstack/neutron/+/843256 Probably the neutron-vpnaas code needs to be adapted to avoid the error of remove_reservation inside a transaction. Exception log: Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource [None req-6d1d249c-3dba-4be4-996d-fa6b5f1fa718 tempest-VPNaaSTestJSON-706399164 tempest-VPNaaSTestJSON-706399164-project] create failed: No details.: RuntimeError: Method cannot be called within a transaction. Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource Traceback (most recent call last): Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource File "/opt/stack/neutron/neutron/api/v2/resource.py", line 98, in resource Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource result = method(request=request, **args) Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource File "/opt/stack/neutron/neutron/api/v2/base.py", line 438, in create Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource return self._create(request, body, **kwargs) Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource File "/usr/local/lib/python3.8/dist-packages/neutron_lib/db/api.py", line 142, in wrapped Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource setattr(e, '_RETRY_EXCEEDED', True) Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource File "/usr/local/lib/python3.8/dist-packages/oslo_utils/excutils.py", line 227, in __exit__ Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource self.force_reraise() Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource File "/usr/local/lib/python3.8/dist-packages/oslo_utils/excutils.py", line 200, in force_reraise Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource raise self.value Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource File "/usr/local/lib/python3.8/dist-packages/neutron_lib/db/api.py", line 138, in wrapped Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource return f(*args, **kwargs) Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource File "/usr/local/lib/python3.8/dist-packages/oslo_db/api.py", line 154, in wrapper Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource ectxt.value = e.inner_exc Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource File "/usr/local/lib/python3.8/dist-packages/oslo_utils/excutils.py", line 227, in __exit__ Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource self.force_reraise() Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource File "/usr/local/lib/python3.8/dist-packages/oslo_utils/excutils.py", line 200, in force_reraise Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource raise self.value Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource File "/usr/local/lib/python3.8/dist-packages/oslo_db/api.py", line 142, in wrapper Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource return f(*args, **kwargs) Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource File "/usr/local/lib/python3.8/dist-packages/neutron_lib/db/api.py", line 190, in wrapped Jun 12 08:46:58.908642 ubuntu-focal-ovh-gra1-0029982028 neutron-server[74088]: ERROR neutron.api.v2.resource contex
[Yahoo-eng-team] [Bug 1978573] [NEW] Unshelve with az update the requestSpec.availability_zone this can be inconsistent if schedule fails
Public bug reported: Description === Unshelving a shelved offloaded server will go through the scheduler to pick a new host, so we update the RequestSpec.availability_zone here. Note that if scheduling fails the RequestSpec will remain updated, which is not great. https://review.opendev.org/c/openstack/nova/+/831507/comment/12fd28cd_42160512/ Steps to reproduce == NA Expected result === If schedule fails, restore the original az. Actual result = RequestSpec inconsistent if schedule fails. Environment === This was introduced in Train (Aug 28, 2019) with the following note: If we want to change that we need to defer updating the RequestSpec until conductor which probably means RPC changes to pass the new_az variable to conductor. This is likely low priority since the RequestSpec.availability_zone on a shelved offloaded server does not mean much anyway and clearly the user is trying to put the server in the target AZ. Logs & Configs == NA ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1978573 Title: Unshelve with az update the requestSpec.availability_zone this can be inconsistent if schedule fails Status in OpenStack Compute (nova): New Bug description: Description === Unshelving a shelved offloaded server will go through the scheduler to pick a new host, so we update the RequestSpec.availability_zone here. Note that if scheduling fails the RequestSpec will remain updated, which is not great. https://review.opendev.org/c/openstack/nova/+/831507/comment/12fd28cd_42160512/ Steps to reproduce == NA Expected result === If schedule fails, restore the original az. Actual result = RequestSpec inconsistent if schedule fails. Environment === This was introduced in Train (Aug 28, 2019) with the following note: If we want to change that we need to defer updating the RequestSpec until conductor which probably means RPC changes to pass the new_az variable to conductor. This is likely low priority since the RequestSpec.availability_zone on a shelved offloaded server does not mean much anyway and clearly the user is trying to put the server in the target AZ. Logs & Configs == NA To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1978573/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1978519] Re: Create auto allocated topology encounter error when enable ndp_proxy service plugin
Reviewed: https://review.opendev.org/c/openstack/neutron/+/845662 Committed: https://opendev.org/openstack/neutron/commit/81a330113b5ae3d9b163eb2a92bfa0a628a31dd1 Submitter: "Zuul (22348)" Branch:master commit 81a330113b5ae3d9b163eb2a92bfa0a628a31dd1 Author: yangjianfeng Date: Tue Jun 14 11:15:02 2022 +0800 Return default value when get router's enable_ndp_proxy from `request_body` In some cases, the creation of router was called by `l3 plugin` directly, didn't call API. In this way, the router's request_body of the `ndp_proxy` service plugin received has no `enable_ndp_proxy`, this will result in `ndp_proxy` service plugin raise error. Closes-Bug: #1978519 Related-Bug: #1877301 Change-Id: I413c33970002532d11de5bc2afb145704a8488a9 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1978519 Title: Create auto allocated topology encounter error when enable ndp_proxy service plugin Status in neutron: Fix Released Bug description: In master branch, when `auto_allocate` and `ndp_proxy` service plugin were enabled simultaneously. Then, execute the below command to create a `auto allocated topology create`, the neutron server log will report ERROR [1]. openstack network auto allocated topology create --or-show [1] https://paste.opendev.org/show/bYdBYap1NcOnTjIK7inP/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1978519/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1978564] Re: Unit tests fail with latest pyroute2 releases
Reviewed: https://review.opendev.org/c/openstack/neutron/+/845715 Committed: https://opendev.org/openstack/neutron/commit/d01700034ac80631893215e742de44cb903ba2a3 Submitter: "Zuul (22348)" Branch:master commit d01700034ac80631893215e742de44cb903ba2a3 Author: Dr. Jens Harbott Date: Tue Jun 14 11:21:10 2022 +0200 Fix tests involving pyroute2.netlink module pyroute2 0.6.11 did some further refactoring of their module imports, so using pyroute2.netlink.some_func() doesn't work anymore. Since we do "from pyroute2 import netlink" anyway, use the imported module everywhere. Also, mock.patch()ing pyroute2.netlink.rtnl.tcmsg.common.tick_in_usec doesn't work anymore, but also doesn't seem to be necessary for the tests to succeed, so just drop it. Closes-Bug: 1978564 Change-Id: Ie06b987f7efbff8057293893e42bee7b682b9ba1 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1978564 Title: Unit tests fail with latest pyroute2 releases Status in neutron: Fix Released Bug description: With the latest pyroute2 releases, import handling has changed again, causing some unit tests to fail. https://zuul.opendev.org/t/openstack/build/c217d83a69664925aad47be4398f5b9a 2022-06-14 03:53:43.007328 | ubuntu-focal | == 2022-06-14 03:53:43.007340 | ubuntu-focal | Failed 3 tests - output below: 2022-06-14 03:53:43.007351 | ubuntu-focal | == 2022-06-14 03:53:43.007363 | ubuntu-focal | 2022-06-14 03:53:43.007374 | ubuntu-focal | neutron.tests.unit.agent.linux.test_tc_lib.TcTestCase.test_list_tc_qdiscs_tbf 2022-06-14 03:53:43.007409 | ubuntu-focal | - 2022-06-14 03:53:43.007420 | ubuntu-focal | 2022-06-14 03:53:43.007431 | ubuntu-focal | Captured traceback: 2022-06-14 03:53:43.007445 | ubuntu-focal | ~~~ 2022-06-14 03:53:43.007456 | ubuntu-focal | Traceback (most recent call last): 2022-06-14 03:53:43.007475 | ubuntu-focal | 2022-06-14 03:53:43.007486 | ubuntu-focal | File "/usr/lib/python3.8/unittest/mock.py", line 1215, in _dot_lookup 2022-06-14 03:53:43.007496 | ubuntu-focal | return getattr(thing, comp) 2022-06-14 03:53:43.007507 | ubuntu-focal | 2022-06-14 03:53:43.007517 | ubuntu-focal | AttributeError: module 'pyroute2' has no attribute 'netlink' 2022-06-14 03:53:43.007532 | ubuntu-focal | 2022-06-14 03:53:43.007544 | ubuntu-focal | 2022-06-14 03:53:43.007555 | ubuntu-focal | During handling of the above exception, another exception occurred: 2022-06-14 03:53:43.007566 | ubuntu-focal | 2022-06-14 03:53:43.007576 | ubuntu-focal | 2022-06-14 03:53:43.007586 | ubuntu-focal | Traceback (most recent call last): 2022-06-14 03:53:43.007597 | ubuntu-focal | 2022-06-14 03:53:43.007607 | ubuntu-focal | File "/home/zuul/src/opendev.org/openstack/neutron/neutron/tests/base.py", line 182, in func 2022-06-14 03:53:43.007618 | ubuntu-focal | return f(self, *args, **kwargs) 2022-06-14 03:53:43.007628 | ubuntu-focal | 2022-06-14 03:53:43.007639 | ubuntu-focal | File "/usr/lib/python3.8/unittest/mock.py", line 1322, in patched 2022-06-14 03:53:43.007649 | ubuntu-focal | with self.decoration_helper(patched, 2022-06-14 03:53:43.007660 | ubuntu-focal | 2022-06-14 03:53:43.007670 | ubuntu-focal | File "/usr/lib/python3.8/contextlib.py", line 113, in __enter__ 2022-06-14 03:53:43.007681 | ubuntu-focal | return next(self.gen) 2022-06-14 03:53:43.007698 | ubuntu-focal | 2022-06-14 03:53:43.007708 | ubuntu-focal | File "/usr/lib/python3.8/unittest/mock.py", line 1304, in decoration_helper 2022-06-14 03:53:43.007719 | ubuntu-focal | arg = exit_stack.enter_context(patching) 2022-06-14 03:53:43.007729 | ubuntu-focal | 2022-06-14 03:53:43.007740 | ubuntu-focal | File "/usr/lib/python3.8/contextlib.py", line 425, in enter_context 2022-06-14 03:53:43.007750 | ubuntu-focal | result = _cm_type.__enter__(cm) 2022-06-14 03:53:43.007778 | ubuntu-focal | 2022-06-14 03:53:43.007790 | ubuntu-focal | File "/usr/lib/python3.8/unittest/mock.py", line 1377, in __enter__ 2022-06-14 03:53:43.007800 | ubuntu-focal | self.target = self.getter() 2022-06-14 03:53:43.007810 | ubuntu-focal | 2022-06-14 03:53:43.007820 | ubuntu-focal | File "/usr/lib/python3.8/unittest/mock.py", line 1552, in 2022-06-14 03:53:43.007830 | ubuntu-focal | getter = lambda: _importer(target) 2022-06-14 03:53:43.007840 | ubuntu-focal | 2022-06-14 03:53:43.007849 | ubuntu-focal | File "/usr/lib/python3.8/unittest/mock.py", line 1228, in _importer 2022-06-14 03:53:43.007859 | ubuntu-focal | thing = _dot_loo
[Yahoo-eng-team] [Bug 1977952] Re: In 22.2 cloud-init fails when phone-home module does not have "tries" parameter
This bug was fixed in the package cloud-init - 22.2-0ubuntu1~22.04.2
---
cloud-init (22.2-0ubuntu1~22.04.2) jammy; urgency=medium
* cherry-pick a2e62738: Fix cc_phone_home requiring 'tries' (#1500)
(LP: #1977952)
-- James Falcon Thu, 09 Jun 2022 16:25:29
-0500
** Changed in: cloud-init (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1977952
Title:
In 22.2 cloud-init fails when phone-home module does not have "tries"
parameter
Status in cloud-init:
Fix Committed
Status in cloud-init package in Ubuntu:
Fix Committed
Status in cloud-init source package in Bionic:
Fix Released
Status in cloud-init source package in Focal:
Fix Released
Status in cloud-init source package in Impish:
Fix Released
Status in cloud-init source package in Jammy:
Fix Released
Bug description:
=== Begin SRU Template ===
[Impact]
The cloud-init "phone home" module contains an optional "tries" parameter. In
release 22.2, this was accidentally changed to become mandatory. Any previously
working cloud-config that didn't contain the "tries" parameter will now cause
the module exit with exception. This happened because an overly broad exception
handler for converting the 'tries' string to an int was changed to only raise
on ValueError. However, if None (or any other non-string) is passed, a
TypeError is raised, and this needs to be caught as well.
[Test Case]
1. Launch an Ubuntu instance on any cloud-init supported platform with the
following userdata:
#cloud-config
phone_home:
url: http://192.168.1.1
post: all
2. By inspecting /var/log/cloud-init.log, ensure the phone home module
attempts to make a web request, with the following log:
url_helper.py[DEBUG]: [0/10] open 'http://192.168.1.1' with {'url':
'http://192.168.1.1', 'allow_redirects': True, 'method': 'POST', 'headers':
{'User-Agent': 'Cloud-Init/22.2'}} configuration
[Regression Potential]
The parsing exceptions being caught should now be broad enough to handle any
configuration we receive, but if not, we would still exit the module with
exception.
[Other Info]
Github PR: https://github.com/canonical/cloud-init/pull/1500
=== End SRU Template ===
Initial bug:
Hi!
We have some user-data files where we use the phone-home module of cloud-init.
So far we did not use it's "tries" parameter and everything worked.
However now in version 22.2 there was a change which causes cloud-init to
fail.
https://github.com/canonical/cloud-init/compare/22.1...22.2#diff-a4aa83fbb946ba1ea7cf6c8dd5965cd62631dc9cb48d4baa50adddbfef06b82cL108
In our case this change in the exception handling throws a TypeError,
instead of the ValueError that is excepted:
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_phone_home.py", line
132, in handle
tries = int(tries) # type: ignore
TypeError: int() argument must be a string, a bytes-like object or a number,
not 'NoneType'
While we can add the "tries" parameter (and after that everything works just
like before),
this exception should be handled properly.
Also according to guidelines:
1. Tell us your cloud provider
None
2. Any appropriate cloud-init configuration you can provide us
phone-home module
3. Perform the following on the system and attach it to this bug:
no logs are necessary
Best regards:
Zsolt
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1977952/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1977952] Re: In 22.2 cloud-init fails when phone-home module does not have "tries" parameter
This bug was fixed in the package cloud-init - 22.2-0ubuntu1~20.04.2
---
cloud-init (22.2-0ubuntu1~20.04.2) focal; urgency=medium
* cherry-pick a2e62738: Fix cc_phone_home requiring 'tries' (#1500)
(LP: #1977952)
-- James Falcon Thu, 09 Jun 2022 16:53:07
-0500
** Changed in: cloud-init (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1977952
Title:
In 22.2 cloud-init fails when phone-home module does not have "tries"
parameter
Status in cloud-init:
Fix Committed
Status in cloud-init package in Ubuntu:
Fix Committed
Status in cloud-init source package in Bionic:
Fix Released
Status in cloud-init source package in Focal:
Fix Released
Status in cloud-init source package in Impish:
Fix Released
Status in cloud-init source package in Jammy:
Fix Released
Bug description:
=== Begin SRU Template ===
[Impact]
The cloud-init "phone home" module contains an optional "tries" parameter. In
release 22.2, this was accidentally changed to become mandatory. Any previously
working cloud-config that didn't contain the "tries" parameter will now cause
the module exit with exception. This happened because an overly broad exception
handler for converting the 'tries' string to an int was changed to only raise
on ValueError. However, if None (or any other non-string) is passed, a
TypeError is raised, and this needs to be caught as well.
[Test Case]
1. Launch an Ubuntu instance on any cloud-init supported platform with the
following userdata:
#cloud-config
phone_home:
url: http://192.168.1.1
post: all
2. By inspecting /var/log/cloud-init.log, ensure the phone home module
attempts to make a web request, with the following log:
url_helper.py[DEBUG]: [0/10] open 'http://192.168.1.1' with {'url':
'http://192.168.1.1', 'allow_redirects': True, 'method': 'POST', 'headers':
{'User-Agent': 'Cloud-Init/22.2'}} configuration
[Regression Potential]
The parsing exceptions being caught should now be broad enough to handle any
configuration we receive, but if not, we would still exit the module with
exception.
[Other Info]
Github PR: https://github.com/canonical/cloud-init/pull/1500
=== End SRU Template ===
Initial bug:
Hi!
We have some user-data files where we use the phone-home module of cloud-init.
So far we did not use it's "tries" parameter and everything worked.
However now in version 22.2 there was a change which causes cloud-init to
fail.
https://github.com/canonical/cloud-init/compare/22.1...22.2#diff-a4aa83fbb946ba1ea7cf6c8dd5965cd62631dc9cb48d4baa50adddbfef06b82cL108
In our case this change in the exception handling throws a TypeError,
instead of the ValueError that is excepted:
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_phone_home.py", line
132, in handle
tries = int(tries) # type: ignore
TypeError: int() argument must be a string, a bytes-like object or a number,
not 'NoneType'
While we can add the "tries" parameter (and after that everything works just
like before),
this exception should be handled properly.
Also according to guidelines:
1. Tell us your cloud provider
None
2. Any appropriate cloud-init configuration you can provide us
phone-home module
3. Perform the following on the system and attach it to this bug:
no logs are necessary
Best regards:
Zsolt
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1977952/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1977952] Re: In 22.2 cloud-init fails when phone-home module does not have "tries" parameter
This bug was fixed in the package cloud-init - 22.2-0ubuntu1~21.10.2
---
cloud-init (22.2-0ubuntu1~21.10.2) impish; urgency=medium
* cherry-pick a2e62738: Fix cc_phone_home requiring 'tries' (#1500)
(LP: #1977952)
-- James Falcon Thu, 09 Jun 2022 16:48:01
-0500
** Changed in: cloud-init (Ubuntu Impish)
Status: Fix Committed => Fix Released
** Changed in: cloud-init (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1977952
Title:
In 22.2 cloud-init fails when phone-home module does not have "tries"
parameter
Status in cloud-init:
Fix Committed
Status in cloud-init package in Ubuntu:
Fix Committed
Status in cloud-init source package in Bionic:
Fix Released
Status in cloud-init source package in Focal:
Fix Released
Status in cloud-init source package in Impish:
Fix Released
Status in cloud-init source package in Jammy:
Fix Released
Bug description:
=== Begin SRU Template ===
[Impact]
The cloud-init "phone home" module contains an optional "tries" parameter. In
release 22.2, this was accidentally changed to become mandatory. Any previously
working cloud-config that didn't contain the "tries" parameter will now cause
the module exit with exception. This happened because an overly broad exception
handler for converting the 'tries' string to an int was changed to only raise
on ValueError. However, if None (or any other non-string) is passed, a
TypeError is raised, and this needs to be caught as well.
[Test Case]
1. Launch an Ubuntu instance on any cloud-init supported platform with the
following userdata:
#cloud-config
phone_home:
url: http://192.168.1.1
post: all
2. By inspecting /var/log/cloud-init.log, ensure the phone home module
attempts to make a web request, with the following log:
url_helper.py[DEBUG]: [0/10] open 'http://192.168.1.1' with {'url':
'http://192.168.1.1', 'allow_redirects': True, 'method': 'POST', 'headers':
{'User-Agent': 'Cloud-Init/22.2'}} configuration
[Regression Potential]
The parsing exceptions being caught should now be broad enough to handle any
configuration we receive, but if not, we would still exit the module with
exception.
[Other Info]
Github PR: https://github.com/canonical/cloud-init/pull/1500
=== End SRU Template ===
Initial bug:
Hi!
We have some user-data files where we use the phone-home module of cloud-init.
So far we did not use it's "tries" parameter and everything worked.
However now in version 22.2 there was a change which causes cloud-init to
fail.
https://github.com/canonical/cloud-init/compare/22.1...22.2#diff-a4aa83fbb946ba1ea7cf6c8dd5965cd62631dc9cb48d4baa50adddbfef06b82cL108
In our case this change in the exception handling throws a TypeError,
instead of the ValueError that is excepted:
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_phone_home.py", line
132, in handle
tries = int(tries) # type: ignore
TypeError: int() argument must be a string, a bytes-like object or a number,
not 'NoneType'
While we can add the "tries" parameter (and after that everything works just
like before),
this exception should be handled properly.
Also according to guidelines:
1. Tell us your cloud provider
None
2. Any appropriate cloud-init configuration you can provide us
phone-home module
3. Perform the following on the system and attach it to this bug:
no logs are necessary
Best regards:
Zsolt
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1977952/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1940450] Re: XSS The data-template attribute of the tooltip and popover plugins lacks input sanitization and may allow attacker to execute arbitrary JavaScript.
** Changed in: horizon (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1940450 Title: XSS The data-template attribute of the tooltip and popover plugins lacks input sanitization and may allow attacker to execute arbitrary JavaScript. Status in Ubuntu Cloud Archive: New Status in OpenStack Dashboard (Horizon): Invalid Status in OpenStack Security Advisory: Invalid Status in horizon package in Ubuntu: Won't Fix Status in python-xstatic-bootstrap-scss package in Ubuntu: Won't Fix Bug description: The data-template attribute of the tooltip and popover plugins lacks input sanitization and may allow attacker to execute arbitrary JavaScript. github source: https://github.com/twbs/bootstrap/pull/28236 github upstream MR: https://github.com/twbs/bootstrap/pull/28236/commits/5efa9b531d25927b907e3fa24b818608bc38a2f0 ubuntu-cve https://ubuntu.com/security/CVE-2019-8331 openstack-dashboard,from xenial UCA, python-django-horizon version 13.0.2-0ubuntu3~cloud0 `pull-uca-source python-django-horizon 3:13.0.2-0ubuntu3~cloud0` To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1940450/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1978722] [NEW] docs: update sharing discussion for removal of owner_is_tenant
Public bug reported: The section "How do you identify a producer or consumer?" can be simplified because it is no longer possible for an operator to configure whether images are owned by projects or by individual users. That config option was removed by Change I8edc957ad50ec28 in wallaby. --- Release: 0.0.1.dev436 on 2017-01-29 16:15:44 SHA: 3a02b069a42d9741cd0df39b161310de4bceac2b Source: https://opendev.org/openstack/glance-specs/src/doc/source/specs/api/v2/sharing-image-api-v2.rst URL: https://specs.openstack.org/openstack/glance-specs/specs/api/v2/sharing-image-api-v2.html ** Affects: glance Importance: Low Status: Triaged ** Tags: documentation -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1978722 Title: docs: update sharing discussion for removal of owner_is_tenant Status in Glance: Triaged Bug description: The section "How do you identify a producer or consumer?" can be simplified because it is no longer possible for an operator to configure whether images are owned by projects or by individual users. That config option was removed by Change I8edc957ad50ec28 in wallaby. --- Release: 0.0.1.dev436 on 2017-01-29 16:15:44 SHA: 3a02b069a42d9741cd0df39b161310de4bceac2b Source: https://opendev.org/openstack/glance-specs/src/doc/source/specs/api/v2/sharing-image-api-v2.rst URL: https://specs.openstack.org/openstack/glance-specs/specs/api/v2/sharing-image-api-v2.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1978722/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1978723] [NEW] docs: policies page in the admin guide needs an update
Public bug reported: The page still refers to the v1 API, so those things can go. Additionally, some of the descriptions are misleading, for example, publicize_image - Create or update public images That permission really only has to do with the image visibility, I'm pretty sure the image owner can always update the "reglar" properties on a public image. It would also be nice to say something about the policy filename, where it should go, etc., something like cinder has at the top of this page: https://docs.openstack.org/cinder/latest/configuration/block- storage/samples/policy.yaml.html --- Release: 25.0.0.dev67 on 2020-11-24 16:30:47 SHA: 39b44ce1cca0cb3cdb95248b589e0f55fd421856 Source: https://opendev.org/openstack/glance/src/doc/source/admin/policies.rst URL: https://docs.openstack.org/glance/latest/admin/policies.html ** Affects: glance Importance: Low Status: Triaged ** Tags: documentation -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1978723 Title: docs: policies page in the admin guide needs an update Status in Glance: Triaged Bug description: The page still refers to the v1 API, so those things can go. Additionally, some of the descriptions are misleading, for example, publicize_image - Create or update public images That permission really only has to do with the image visibility, I'm pretty sure the image owner can always update the "reglar" properties on a public image. It would also be nice to say something about the policy filename, where it should go, etc., something like cinder has at the top of this page: https://docs.openstack.org/cinder/latest/configuration/block- storage/samples/policy.yaml.html --- Release: 25.0.0.dev67 on 2020-11-24 16:30:47 SHA: 39b44ce1cca0cb3cdb95248b589e0f55fd421856 Source: https://opendev.org/openstack/glance/src/doc/source/admin/policies.rst URL: https://docs.openstack.org/glance/latest/admin/policies.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1978723/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1978775] [NEW] ovn: ovs-system: deferred action limit reached, drop recirc action
Public bug reported: OpenStack release - Wallaby OVN version 21.06 OVS version 2.16 CentOS Stream 8, various kernel versions Seeing a lot of ovs-system: deferred action limit reached, drop recirc action on the active gateway chassis. Also the dropped packets counter for breth2-ovs (which is the external bridge) is increasing over time. [ 3435.828519] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3436.820595] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3436.964035] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3437.620312] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3437.706389] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3438.153331] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3438.346396] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3440.328273] net_ratelimit: 2 callbacks suppressed [ 3440.333636] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3462.687204] openvswitch: ovs-system: deferred action limit reached, drop recirc action Found https://www.mail-archive.com/ovs-dev@openvswitch.org/msg53195.html and https://mail.openvswitch.org/pipermail/ovs-discuss/2021-August/051340.html which might be related. I'm not sure if that's Neutron bug or OVN bug. It's not a blocker, or a huge problem - everything works properly. ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1978775 Title: ovn: ovs-system: deferred action limit reached, drop recirc action Status in neutron: New Bug description: OpenStack release - Wallaby OVN version 21.06 OVS version 2.16 CentOS Stream 8, various kernel versions Seeing a lot of ovs-system: deferred action limit reached, drop recirc action on the active gateway chassis. Also the dropped packets counter for breth2-ovs (which is the external bridge) is increasing over time. [ 3435.828519] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3436.820595] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3436.964035] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3437.620312] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3437.706389] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3438.153331] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3438.346396] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3440.328273] net_ratelimit: 2 callbacks suppressed [ 3440.333636] openvswitch: ovs-system: deferred action limit reached, drop recirc action [ 3462.687204] openvswitch: ovs-system: deferred action limit reached, drop recirc action Found https://www.mail-archive.com/ovs-dev@openvswitch.org/msg53195.html and https://mail.openvswitch.org/pipermail/ovs-discuss/2021-August/051340.html which might be related. I'm not sure if that's Neutron bug or OVN bug. It's not a blocker, or a huge problem - everything works properly. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1978775/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1940243] Re: Neutron-tempest-plugin scenario tests - oom-killer is killing mysql process
Reopening the bz as seeing few failures(5 failures in last 15 days as per https://opensearch.logs.openstack.org) in linuxbridge and openvswitch scenario jobs:- https://1b33868f301e2201a22c-a64bb815b8796eabf8a53948331bd878.ssl.cf5.rackcdn.com/845366/2/check/neutron-tempest-plugin-openvswitch/aa3106c/controller/logs/syslog.txt https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_82d/843649/2/gate/neutron-tempest-plugin-openvswitch-iptables_hybrid/82d4dbe/controller/logs/syslog.txt https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_052/842135/1/check/neutron-tempest-plugin-linuxbridge/0528022/controller/logs/syslog.txt https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_f11/844680/1/check/neutron-tempest-plugin-linuxbridge/f111e3f/controller/logs/syslog.txt https://bd6c3da3b1723c5f3502-97cb3b32849366f5bed744685e46b266.ssl.cf1.rackcdn.com/844860/3/check/neutron-tempest-plugin-linuxbridge/35e5065/controller/logs/syslog.txt In all the above failures, SwapFree: 0 kB and many vms were active(using 256 mb/128 mb each) and mysql utilizing approx 10% of total memory. Also multiple(around 10) neutron-keepalived-state-change processes utilizing approx 12-14% of memory. Considering only seen in master jobs and with timings seems this triggered after https://review.opendev.org/c/openstack/neutron-tempest- plugin/+/836912 as more api tests running along with scenario tests now. The swap used in these jobs is 1 gb, so it can be increased to some extent like 3-4 gb to avoid these issues due to memory shortage. ** Changed in: neutron Status: Fix Released => Triaged -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1940243 Title: Neutron-tempest-plugin scenario tests - oom-killer is killing mysql process Status in neutron: Triaged Bug description: It happens pretty often recently that during our scenario tests we are running out of memory and oom-killer is killing mysql process as it is number 1 in memory consumption. That is causing job's failures. It seems for me that it happens when there are running tests which uses vms with advanced image (ubuntu). Maybe we should extract those tests and run them as second stage with "--concurency 1"? Examples of failures: https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_85a/803462/2/check/neutron- tempest-plugin-scenario-openvswitch- iptables_hybrid/85afc13/testr_results.html https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_944/803936/1/gate/neutron- tempest-plugin-scenario-openvswitch- iptables_hybrid/9445e5f/testr_results.html https://09e003a6a650f320c43d-e30f275ad83ed88289c7399adb6c5ee6.ssl.cf1.rackcdn.com/804236/5/check/neutron- tempest-plugin-scenario-linuxbridge/770722a/testr_results.html https://bd90009aa1732b7b8d4a-e998c5625939f617052baaae6f827bb8.ssl.cf5.rackcdn.com/797221/1/check/neutron- tempest-plugin-scenario-openvswitch/2a7ab79/testr_results.html https://27020bbcd4882754b192-88656c065c39ed46f44b21a92a1cea67.ssl.cf5.rackcdn.com/800445/7/check/neutron- tempest-plugin-scenario-openvswitch- iptables_hybrid/5e597ae/testr_results.html https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_e7d/800446/9/check/neutron- tempest-plugin-scenario-openvswitch/e7d72c9/testr_results.html https://637b02491f0435a9a86b-ccec73fd7dde7a9826f6a9aeb49ab878.ssl.cf5.rackcdn.com/804397/1/gate/neutron- tempest-plugin-scenario-linuxbridge/64bae23/testr_results.html https://d1b1a7bc5606074c0db2-9f552c22a38891cd59267376a7a41496.ssl.cf5.rackcdn.com/802596/12/check/neutron- tempest-plugin-scenario-openvswitch- iptables_hybrid/de03f1f/testr_results.html https://b395fe859a68f8d08e03-e48e76b6f53fcff59de7a7c1c3da6c62.ssl.cf1.rackcdn.com/804394/3/check/neutron- tempest-plugin-scenario-openvswitch- iptables_hybrid/98bfff3/testr_results.html https://6ee071d84f4801a650d3-2635c9269ad2bde2592553cd282ad960.ssl.cf2.rackcdn.com/804394/3/check/neutron- tempest-plugin-scenario-linuxbridge/a9282d0/testr_results.html Logstash query: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Details%3A%20Unexpected%20API%20Error.%20Please%20report%20this%20at%20http%3A%2F%2Fbugs.launchpad.net%2Fnova%2F%20and%20attach%20the%20Nova%20API%20log%20if%20possible.%5C%22 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1940243/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
