[Yahoo-eng-team] [Bug 1806053] Re: APITestCase still needs to be patched utils.patch_middleware_get_user()
** Changed in: neutron-fwaas-dashboard (Ubuntu Bionic) Status: New => Invalid ** Changed in: neutron-fwaas-dashboard (Ubuntu Disco) Importance: Undecided => High ** Changed in: neutron-fwaas-dashboard (Ubuntu Disco) Status: New => Triaged ** Changed in: neutron-fwaas-dashboard (Ubuntu Eoan) Importance: Undecided => High ** Changed in: neutron-fwaas-dashboard (Ubuntu Eoan) Status: New => Triaged -- 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/1806053 Title: APITestCase still needs to be patched utils.patch_middleware_get_user() Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive queens series: Invalid Status in Ubuntu Cloud Archive rocky series: Triaged Status in Ubuntu Cloud Archive stein series: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in horizon package in Ubuntu: Fix Released Status in neutron-fwaas-dashboard package in Ubuntu: Triaged Status in horizon source package in Bionic: Invalid Status in neutron-fwaas-dashboard source package in Bionic: Invalid Status in horizon source package in Cosmic: Triaged Status in neutron-fwaas-dashboard source package in Cosmic: Triaged Status in horizon source package in Disco: Fix Released Status in neutron-fwaas-dashboard source package in Disco: Triaged Status in horizon source package in Eoan: Fix Released Status in neutron-fwaas-dashboard source package in Eoan: Triaged Bug description: After merging commit 0d163613265e036818fe567793a4fc88fe140d4a, we see some UT breakage in horizon plugins. bgpvpn-dashboard https://bugs.launchpad.net/bgpvpn/+bug/1805240 neutron-fwaas-dashboard https://review.openstack.org/621155 neutron-vpnaas-dashboard https://review.openstack.org/621152 Previously APITestCase called patch_middleware_get_user explicitly, but the commit above dropped it. This seems to trigger the above UT failures. - SRU Details for Ubuntu -- [Impact] See above. Also, building a horizon dashboard package, such as neutron-fwaas- dashboard, will result in several unit test failures such due to "AttributeError: 'AnonymousUser' object has no attribute 'token'". [Test Case] Build the horizon and neutron-fwaas-dashboard packages. [Regression Potential] Very minimal as the changes update test code only. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1806053/+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 1828494] [NEW] [RFE][L3] l3-agent should have its capacity
Public bug reported: Recently we meet some scale issue about L3-agent. According to what I'm informed, most cloud service provider does not charge for the neutron virtual router. This can become a headach for the operators. Every tenant may create free routers for doing nothing. But neutron will create many resource for it, especially the HA scenario, there will be namespaces, keepalived processes, and monitor processes. It will absolutely increase the failure risk, especially for agent restart. So this RFE is aimming to add a scheduling mechanism, and for l3-agent, it will collect and report some resource usage, for instance available bandiwidth. So during the router scheduler process, if there is no more available, the number of routers can be under a controlled range. ** 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/1828494 Title: [RFE][L3] l3-agent should have its capacity Status in neutron: New Bug description: Recently we meet some scale issue about L3-agent. According to what I'm informed, most cloud service provider does not charge for the neutron virtual router. This can become a headach for the operators. Every tenant may create free routers for doing nothing. But neutron will create many resource for it, especially the HA scenario, there will be namespaces, keepalived processes, and monitor processes. It will absolutely increase the failure risk, especially for agent restart. So this RFE is aimming to add a scheduling mechanism, and for l3-agent, it will collect and report some resource usage, for instance available bandiwidth. So during the router scheduler process, if there is no more available, the number of routers can be under a controlled range. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1828494/+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 1822884] Re: live migration fails due to port binding duplicate key entry in post_live_migrate
** Changed in: nova
Importance: Undecided => High
** Also affects: nova/stein
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Changed in: nova
Importance: High => Medium
** Changed in: nova/rocky
Status: New => Triaged
** Changed in: nova/stein
Status: New => Triaged
** Changed in: nova/rocky
Importance: Undecided => Medium
** Changed in: nova/stein
Importance: Undecided => Medium
--
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/1822884
Title:
live migration fails due to port binding duplicate key entry in
post_live_migrate
Status in OpenStack Compute (nova):
In Progress
Status in OpenStack Compute (nova) rocky series:
Triaged
Status in OpenStack Compute (nova) stein series:
Triaged
Bug description:
We are converting a site from RDO to OSA; At this stage all control
nodes and net nodes are running OSA (Rocky), some compute are running
RDO (Queens), some are RDO (Rocky) and the remaining are OSA (Rocky).
We are attempting to Live Migrate VMs from the RDO (Rocky) nodes to
OSA (Rocky) before reinstalling the RDO nodes as OSA (Rocky).
When Live Migrating between RDO nodes we see no issues similarly when
migrating between OSA nodes, we see no issue, however Live Migrating
RDO -> OSA fails with the below error on the target.
2019-01-24 13:33:11.701 85926 INFO nova.network.neutronv2.api
[req-3c4ceac0-7c12-428d-9f63-7c1d6879be4e a3bee416cf67420995855d602d2bccd3
a564613210ee43708b8a7fc6274ebd63 - default default] [instance:
8ecbfc14-2699-4276-a577-18ed6a662232] Updating port
419c18e1-05c0-44c3-9a97-8334d0c15cc1 with attributes {'binding:profile': {},
'binding:host_id': 'cc-compute24-kna1'}
2019-01-24 13:33:59.357 85926 ERROR nova.network.neutronv2.api
[req-3c4ceac0-7c12-428d-9f63-7c1d6879be4e a3bee416cf67420995855d602d2bccd3
a564613210ee43708b8a7fc6274ebd63 - default default] [instance:
8ecbfc14-2699-4276-a577-18ed6a662232] Unable to update binding details for port
419c18e1-05c0-44c3-9a97-8334d0c15cc1: InternalServerError: Request Failed:
internal server error while processing your request.
Digging further into the logs, reveals an issue with duplicate keys:
2019-02-01 09:48:10.268 11854 ERROR oslo_db.api
[req-152bce20-8895-4238-910c-b26fde44913d e7bbce5e15994104bdf5e3af68a55b31
a894e8109af3430aa7ae03e0c49a0aa0 - default default] DB exceeded retry limit.:
DBDuplicateEntry: (pymysql.err.IntegrityError) (1062, u"Duplicate entry
'5bedceef-1b65-4b19-a6d4-da3595adaf61-cc-com
pute24-kna1' for key 'PRIMARY'") [SQL: u'UPDATE ml2_port_bindings SET
host=%(host)s, profile=%(profile)s, vif_type=%(vif_type)s,
vif_details=%(vif_details)s WHERE ml2_port_bindings.port_id =
%(ml2_port_bindings_port_id)s AND ml2_port_bindings.host =
%(ml2_port_bindings_host)s'] [parameters: {'profile': '{}', 'vif_ty
pe': 'unbound', 'ml2_port_bindings_host': u'cc-compute06-kna1',
'vif_details': '', 'ml2_port_bindings_port_id':
u'5bedceef-1b65-4b19-a6d4-da3595adaf61', 'host': u'cc-compute24-kna1'}]
(Background on this error at: http://sqlalche.me/e/gkpj)
this is confirmed when reviewing the ml2_port_bindings table:
MariaDB [neutron]> select * from ml2_port_bindings where port_id =
'5bedceef-1b65-4b19-a6d4-da3595adaf61';
+--+---+--+---+---+---+--+
| port_id | host | vif_type |
vnic_type | vif_details
| profile | status |
+--+---+--+---+---+---+--+
| 5bedceef-1b65-4b19-a6d4-da3595adaf61 | cc-compute06-kna1 | ovs |
normal| {"port_filter": true, "datapath_type": "system", "ovs_hybrid_plug":
true} | {"migrating_to": "cc-compute24-kna1"} | ACTIVE |
| 5bedceef-1b65-4b19-a6d4-da3595adaf61 | cc-compute24-kna1 | ovs |
normal| {"port_filter": true, "datapath_type": "system", "ovs_hybrid_plug":
true} | | INACTIVE |
+--+---+--+---+---+---+--+
The exception is not caught and handled, the VM is stuck in migrating.
According to OpenStack, the VM is still on the source compute node,
whilst libvirt/virsh believes it to be on the target. Forcing the VM
state to active, keeps the VM available, however rebooting
[Yahoo-eng-team] [Bug 1828479] [NEW] Release 19.1
Public bug reported: This bug tracks cloud-init upstream release of version 19.1. == Release Notes == Hello All, Cloud-init release 19.1 is now available The 19.1 release: * spanned just under 5 months in length * had 24 contributors from 20 domains * fixed 30 launchpad issues Highlights: - Azure datasource telemetry, network configuration and ssh key hardening - new config module for interacting with third party drivers on Ubuntu - EC2 Classic instance support for network config changes across reboot - Add support for the com.vmware.guestInfo OVF transport. - Scaleway: Support ssh keys provided inside an instance tag. - Better NoCloud support for case-insensitive fs labels. == Changelog == - tests: add Eoan release [Paride Legovini] - cc_mounts: check if mount -a on no-change fstab path [Jason Zions (MSFT)] (LP: #1825596) - replace remaining occurrences of LOG.warn [Daniel Watkins] - DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo] - Azure: Changes to the Hyper-V KVP Reporter [Anh Vo] - git tests: no longer show warning about safe yaml. - tools/read-version: handle errors [Chad Miller] - net/sysconfig: only indicate available on known sysconfig distros (LP: #1819994) - packages: update rpm specs for new bash completion path [Daniel Watkins] (LP: #1825444) - test_azure: mock util.SeLinuxGuard where needed [Jason Zions (MSFT)] (LP: #1825253) - setup.py: install bash completion script in new location [Daniel Watkins] - mount_cb: do not pass sync and rw options to mount [Gonéri Le Bouder] (LP: #1645824) - cc_apt_configure: fix typo in apt documentation [Dominic Schlegel] - Revert "DataSource: move update_events from a class to an instance..." [Daniel Watkins] - Change DataSourceNoCloud to ignore file system label's case. [Risto Oikarinen] - cmd:main.py: Fix missing 'modules-init' key in modes dict [Antonio Romito] (LP: #1815109) - ubuntu_advantage: rewrite cloud-config module - Azure: Treat _unset network configuration as if it were absent [Jason Zions (MSFT)] (LP: #1823084) - DatasourceAzure: add additional logging for azure datasource [Anh Vo] - cloud_tests: fix apt_pipelining test-cases - Azure: Ensure platform random_seed is always serializable as JSON. [Jason Zions (MSFT)] - net/sysconfig: write out SUSE-compatible IPv6 config [Robert Schweikert] - tox: Update testenv for openSUSE Leap to 15.0 [Thomas Bechtold] - net: Fix ipv6 static routes when using eni renderer [Raphael Glon] (LP: #1818669) - Add ubuntu_drivers config module [Daniel Watkins] - doc: Refresh Azure walinuxagent docs [Daniel Watkins] - tox: bump pylint version to latest (2.3.1) [Daniel Watkins] - DataSource: move update_events from a class to an instance attribute [Daniel Watkins] (LP: #1819913) - net/sysconfig: Handle default route setup for dhcp configured NICs [Robert Schweikert] (LP: #1812117) - DataSourceEc2: update RELEASE_BLOCKER to be more accurate [Daniel Watkins] - cloud-init-per: POSIX sh does not support string subst, use sed (LP: #1819222) - Support locking user with usermod if passwd is not available. - Example for Microsoft Azure data disk added. [Anton Olifir] - clean: correctly determine the path for excluding seed directory [Daniel Watkins] (LP: #1818571) - helpers/openstack: Treat unknown link types as physical [Daniel Watkins] (LP: #1639263) - drop Python 2.6 support and our NIH version detection [Daniel Watkins] - tip-pylint: Fix assignment-from-return-none errors - net: append type:dhcp[46] only if dhcp[46] is True in v2 netconfig [Kurt Stieger] (LP: #1818032) - cc_apt_pipelining: stop disabling pipelining by default [Daniel Watkins] (LP: #1794982) - tests: fix some slow tests and some leaking state [Daniel Watkins] - util: don't determine string_types ourselves [Daniel Watkins] - cc_rsyslog: Escape possible nested set [Daniel Watkins] (LP: #1816967) - Enable encrypted_data_bag_secret support for Chef [Eric Williams] (LP: #1817082) - azure: Filter list of ssh keys pulled from fabric [Jason Zions (MSFT)] - doc: update merging doc with fixes and some additional details/examples - tests: integration test failure summary to use traceback if empty error - This is to fix https://bugs.launchpad.net/cloud-init/+bug/1812676 [Vitaly Kuznetsov] - EC2: Rewrite network config on AWS Classic instances every boot [Guilherme G. Piccoli] (LP: #1802073) - netinfo: Adjust ifconfig output parsing for FreeBSD ipv6 entries (LP: #1779672) - netplan: Don't render yaml aliases when dumping netplan (LP: #1815051) - add PyCharm IDE .idea/ path to .gitignore [Dominic Schlegel] - correct grammar issue in instance metadata documentation [Dominic Schlegel] (LP: #1802188) - clean: cloud-init clean should not trace when run from within cloud_dir (LP: #1795508) - Resolve flake8 comparison and pycodestyle over-ident
[Yahoo-eng-team] [Bug 1828473] [NEW] Dnsmasq spawned by neutron-dhcp-agent should use bind-dynamic option instead of bind-interfaces
Public bug reported: According to warning log from dnsmasq: May 09 23:08:59 devstack-ubuntu-ovs dnsmasq[27287]: LOUD WARNING: use --bind-dynamic rather than --bind-interfaces to avoid DNS amplification attacks via these interface(s) Option bind-interfaces is available since dnsmasq 2.63 (https://github.com/liquidm/dnsmasq/blob/master/FAQ#L239) and we are already requiring 2.67 at least so we should change this option in calling dnsmasq process. ** Affects: neutron Importance: Low Assignee: Slawek Kaplonski (slaweq) Status: Confirmed ** Tags: l3-ipam-dhcp -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1828473 Title: Dnsmasq spawned by neutron-dhcp-agent should use bind-dynamic option instead of bind-interfaces Status in neutron: Confirmed Bug description: According to warning log from dnsmasq: May 09 23:08:59 devstack-ubuntu-ovs dnsmasq[27287]: LOUD WARNING: use --bind-dynamic rather than --bind-interfaces to avoid DNS amplification attacks via these interface(s) Option bind-interfaces is available since dnsmasq 2.63 (https://github.com/liquidm/dnsmasq/blob/master/FAQ#L239) and we are already requiring 2.67 at least so we should change this option in calling dnsmasq process. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1828473/+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 1806053] Re: APITestCase still needs to be patched utils.patch_middleware_get_user()
** Also affects: neutron-fwaas-dashboard (Ubuntu) Importance: Undecided Status: New ** Changed in: neutron-fwaas-dashboard (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: neutron-fwaas-dashboard (Ubuntu Cosmic) Status: New => Triaged -- 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/1806053 Title: APITestCase still needs to be patched utils.patch_middleware_get_user() Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive queens series: Invalid Status in Ubuntu Cloud Archive rocky series: Triaged Status in Ubuntu Cloud Archive stein series: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in horizon package in Ubuntu: Fix Released Status in neutron-fwaas-dashboard package in Ubuntu: New Status in horizon source package in Bionic: Invalid Status in neutron-fwaas-dashboard source package in Bionic: New Status in horizon source package in Cosmic: Triaged Status in neutron-fwaas-dashboard source package in Cosmic: Triaged Status in horizon source package in Disco: Fix Released Status in neutron-fwaas-dashboard source package in Disco: New Status in horizon source package in Eoan: Fix Released Status in neutron-fwaas-dashboard source package in Eoan: New Bug description: After merging commit 0d163613265e036818fe567793a4fc88fe140d4a, we see some UT breakage in horizon plugins. bgpvpn-dashboard https://bugs.launchpad.net/bgpvpn/+bug/1805240 neutron-fwaas-dashboard https://review.openstack.org/621155 neutron-vpnaas-dashboard https://review.openstack.org/621152 Previously APITestCase called patch_middleware_get_user explicitly, but the commit above dropped it. This seems to trigger the above UT failures. - SRU Details for Ubuntu -- [Impact] See above. Also, building a horizon dashboard package, such as neutron-fwaas- dashboard, will result in several unit test failures such due to "AttributeError: 'AnonymousUser' object has no attribute 'token'". [Test Case] Build the horizon and neutron-fwaas-dashboard packages. [Regression Potential] Very minimal as the changes update test code only. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1806053/+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 1806053] Re: APITestCase still needs to be patched utils.patch_middleware_get_user()
It appears this is not needed for the Ubuntu Queens package as 0d163613265e036818fe567793a4fc88fe140d4a had not yet landed as of 13.0.1. ** Changed in: horizon (Ubuntu Bionic) Importance: High => Undecided ** Changed in: horizon (Ubuntu Bionic) Status: Triaged => Invalid ** Changed in: cloud-archive/queens Importance: High => Undecided ** Changed in: cloud-archive/queens Status: Triaged => Invalid -- 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/1806053 Title: APITestCase still needs to be patched utils.patch_middleware_get_user() Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive queens series: Invalid Status in Ubuntu Cloud Archive rocky series: Triaged Status in Ubuntu Cloud Archive stein series: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in horizon package in Ubuntu: Fix Released Status in horizon source package in Bionic: Invalid Status in horizon source package in Cosmic: Triaged Status in horizon source package in Disco: Fix Released Status in horizon source package in Eoan: Fix Released Bug description: After merging commit 0d163613265e036818fe567793a4fc88fe140d4a, we see some UT breakage in horizon plugins. bgpvpn-dashboard https://bugs.launchpad.net/bgpvpn/+bug/1805240 neutron-fwaas-dashboard https://review.openstack.org/621155 neutron-vpnaas-dashboard https://review.openstack.org/621152 Previously APITestCase called patch_middleware_get_user explicitly, but the commit above dropped it. This seems to trigger the above UT failures. - SRU Details for Ubuntu -- [Impact] See above. Also, building a horizon dashboard package, such as neutron-fwaas- dashboard, will result in several unit test failures such due to "AttributeError: 'AnonymousUser' object has no attribute 'token'". [Test Case] Build the horizon and neutron-fwaas-dashboard packages. [Regression Potential] Very minimal as the changes update test code only. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1806053/+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 1806053] Re: APITestCase still needs to be patched utils.patch_middleware_get_user()
We'll need to cherry pick this for Ubuntu since it's not included in a stable release. ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/queens Importance: Undecided Status: New ** Also affects: cloud-archive/stein Importance: Undecided Status: New ** Also affects: cloud-archive/rocky Importance: Undecided Status: New ** Changed in: cloud-archive/stein Importance: Undecided => High ** Changed in: cloud-archive/stein Status: New => Fix Released ** Changed in: cloud-archive/rocky Importance: Undecided => High ** Changed in: cloud-archive/rocky Status: New => Triaged ** Changed in: cloud-archive/queens Importance: Undecided => High ** Changed in: cloud-archive/queens Status: New => Triaged -- 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/1806053 Title: APITestCase still needs to be patched utils.patch_middleware_get_user() Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive queens series: Triaged Status in Ubuntu Cloud Archive rocky series: Triaged Status in Ubuntu Cloud Archive stein series: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in horizon package in Ubuntu: Fix Released Status in horizon source package in Bionic: Triaged Status in horizon source package in Cosmic: Triaged Status in horizon source package in Disco: Fix Released Status in horizon source package in Eoan: Fix Released Bug description: After merging commit 0d163613265e036818fe567793a4fc88fe140d4a, we see some UT breakage in horizon plugins. bgpvpn-dashboard https://bugs.launchpad.net/bgpvpn/+bug/1805240 neutron-fwaas-dashboard https://review.openstack.org/621155 neutron-vpnaas-dashboard https://review.openstack.org/621152 Previously APITestCase called patch_middleware_get_user explicitly, but the commit above dropped it. This seems to trigger the above UT failures. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1806053/+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 1826259] Re: Create Volume dialog opens (from image panel in Horizon) but getting error default volume type can not be found
** Also affects: horizon Importance: Undecided Status: New -- 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/1826259 Title: Create Volume dialog opens (from image panel in Horizon) but getting error default volume type can not be found Status in OpenStack Dashboard (Horizon): New Status in StarlingX: Triaged Bug description: Brief Description - Create Volume dialog opens (from image panel in Horizon) but getting error default volume type can not be found Severity standard Steps to Reproduce -- 1. As tenant user, navigate to the Images panel 2. Select "Create Volume" to opent the dialog 3. Confirm the volume "Type" setting Expected Behavior -- Create Volume dialog should open and a default "Type" should be set (so that errors are not popping up) +Note: Create Volume dialog from the Volumes panel has default Volume Type setting "No volume type" Actual Behavior Creating Volume dialog (from image panel) opens without a default Volume Type resulting in error Error: Unable to retrieve the default volume type. Reproducibility --- yes System Configuration any Branch/Pull Time/Commit --- BUILD_ID="20190421T233001Z" Timestamp/Logs -- "Default volume type can not be found. (HTTP 404) (Request-ID: req-e9858d29-31c8-4d37-a05e-54710d029332)" To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1826259/+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 1828437] [NEW] Remove unneeded compatibility conversions
Public bug reported: In order to remove complexity and cleanup the code, those compatibility conversions present for more than two releases can be removed now. ** Affects: neutron Importance: Undecided Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez) Status: New ** Changed in: neutron Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1828437 Title: Remove unneeded compatibility conversions Status in neutron: New Bug description: In order to remove complexity and cleanup the code, those compatibility conversions present for more than two releases can be removed now. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1828437/+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 1806053] Re: APITestCase still needs to be patched utils.patch_middleware_get_user()
** Also affects: horizon (Ubuntu) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: horizon (Ubuntu Bionic) Status: New => Triaged ** Changed in: horizon (Ubuntu Cosmic) Status: New => Triaged ** Changed in: horizon (Ubuntu Disco) Status: New => Fix Released ** Changed in: horizon (Ubuntu Eoan) Status: New => Fix Released ** Changed in: horizon (Ubuntu Bionic) Importance: Undecided => High ** Changed in: horizon (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: horizon (Ubuntu Disco) Importance: Undecided => High ** Changed in: horizon (Ubuntu Eoan) Importance: Undecided => High -- 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/1806053 Title: APITestCase still needs to be patched utils.patch_middleware_get_user() Status in OpenStack Dashboard (Horizon): Fix Released Status in horizon package in Ubuntu: Fix Released Status in horizon source package in Bionic: Triaged Status in horizon source package in Cosmic: Triaged Status in horizon source package in Disco: Fix Released Status in horizon source package in Eoan: Fix Released Bug description: After merging commit 0d163613265e036818fe567793a4fc88fe140d4a, we see some UT breakage in horizon plugins. bgpvpn-dashboard https://bugs.launchpad.net/bgpvpn/+bug/1805240 neutron-fwaas-dashboard https://review.openstack.org/621155 neutron-vpnaas-dashboard https://review.openstack.org/621152 Previously APITestCase called patch_middleware_get_user explicitly, but the commit above dropped it. This seems to trigger the above UT failures. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1806053/+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 1827628] Re: Cannot model affinity (and/or anti) with placement "limits" parameter
This is closer to bug 1777591 than bug 1805984. ** Also affects: nova/queens Importance: Undecided Status: New ** Also affects: nova/stein Importance: Undecided Status: New ** Also affects: nova/rocky Importance: Undecided Status: New ** Changed in: nova/queens Status: New => Confirmed ** Changed in: nova/rocky Status: New => Confirmed ** Changed in: nova/rocky Importance: Undecided => Medium ** Changed in: nova/stein Importance: Undecided => Medium ** Changed in: nova/stein Status: New => Confirmed -- 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/1827628 Title: Cannot model affinity (and/or anti) with placement "limits" parameter Status in OpenStack Compute (nova): In Progress Status in OpenStack Compute (nova) queens series: Confirmed Status in OpenStack Compute (nova) rocky series: Confirmed Status in OpenStack Compute (nova) stein series: Confirmed Bug description: It is currently not possible to use affinity/anti-affinity with the placement "limits" parameter since if you want your instance to land on a node where another instance lives you cannot rely on what placement GET/allocation_candidates would return and this could result in a no valid host. Current workaround is to unset the limits parameter. We already have the same-ish problem for disabled computes (https://bugs.launchpad.net/nova/+bug/1805984). We could just do a more generic solution that fits both these cases. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1827628/+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 1828423] [NEW] Very often in DHCP agent we have ""Duplicate IP addresses found, DHCP cache is out of sync"
Public bug reported: As described in comment https://bugs.launchpad.net/neutron/+bug/1760047/comments/24 it looks that after patch https://review.opendev.org/#/c/626830/ we have a lot of messages like "Duplicate IP addresses found, DHCP cache is out of sync" in neutron dhcp agent's logs. To reproduce this it is enough to create new network, subnet and port in this network. It will then be allocated to dhcp agent and in logs there will be such warning. ** Affects: neutron Importance: Undecided Assignee: Slawek Kaplonski (slaweq) Status: Confirmed ** Tags: l3-ipam-dhcp -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1828423 Title: Very often in DHCP agent we have ""Duplicate IP addresses found, DHCP cache is out of sync" Status in neutron: Confirmed Bug description: As described in comment https://bugs.launchpad.net/neutron/+bug/1760047/comments/24 it looks that after patch https://review.opendev.org/#/c/626830/ we have a lot of messages like "Duplicate IP addresses found, DHCP cache is out of sync" in neutron dhcp agent's logs. To reproduce this it is enough to create new network, subnet and port in this network. It will then be allocated to dhcp agent and in logs there will be such warning. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1828423/+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 1828406] [NEW] neutron-dynamic-routing bgp ryu hold timer expired but never tried to recover
Public bug reported:
Lost connection to the peer and the hold timer expired but it never
tried to recover.
2019-05-09 13:26:24.921 2461284 INFO bgpspeaker.speaker [-] Negotiated hold
time 40 expired.
2019-05-09 13:26:24.922 2461284 INFO bgpspeaker.peer [-] Connection to peer
lost, reason: failed to write to socket Resetting retry
connect loop: False
2019-05-09 13:26:24.922 2461284 ERROR ryu.lib.hub [-] hub: uncaught exception:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/ryu/lib/hub.py", line 80, in _launch
return func(*args, **kwargs)
File
"/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/utils/evtlet.py",
line 63, in __call__
self._funct(*self._args, **self._kwargs)
File
"/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/speaker.py", line
542, in _expired
self.send_notification(code, subcode)
File
"/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/speaker.py", line
374, in send_notification
self._send_with_lock(notification)
File
"/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/speaker.py", line
386, in _send_with_lock
self.connection_lost('failed to write to socket')
File
"/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/speaker.py", line
596, in connection_lost
self._peer.connection_lost(reason)
File "/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/peer.py",
line 2323, in connection_lost
self._protocol.stop()
File
"/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/speaker.py", line
405, in stop
Activity.stop(self)
File "/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/base.py",
line 314, in stop
raise ActivityException(desc='Cannot call stop when activity is '
ActivityException: 100.1 - Cannot call stop when activity is not started or has
been stopped already.
: ActivityException: 100.1 - Cannot call stop when activity is not started or
has been stopped already.
** 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/1828406
Title:
neutron-dynamic-routing bgp ryu hold timer expired but never tried to
recover
Status in neutron:
New
Bug description:
Lost connection to the peer and the hold timer expired but it never
tried to recover.
2019-05-09 13:26:24.921 2461284 INFO bgpspeaker.speaker [-] Negotiated hold
time 40 expired.
2019-05-09 13:26:24.922 2461284 INFO bgpspeaker.peer [-] Connection to peer
lost, reason: failed to write to socket Resetting retry
connect loop: False
2019-05-09 13:26:24.922 2461284 ERROR ryu.lib.hub [-] hub: uncaught
exception: Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/ryu/lib/hub.py", line 80, in _launch
return func(*args, **kwargs)
File
"/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/utils/evtlet.py",
line 63, in __call__
self._funct(*self._args, **self._kwargs)
File
"/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/speaker.py", line
542, in _expired
self.send_notification(code, subcode)
File
"/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/speaker.py", line
374, in send_notification
self._send_with_lock(notification)
File
"/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/speaker.py", line
386, in _send_with_lock
self.connection_lost('failed to write to socket')
File
"/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/speaker.py", line
596, in connection_lost
self._peer.connection_lost(reason)
File "/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/peer.py",
line 2323, in connection_lost
self._protocol.stop()
File
"/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/speaker.py", line
405, in stop
Activity.stop(self)
File "/usr/lib/python2.7/site-packages/ryu/services/protocols/bgp/base.py",
line 314, in stop
raise ActivityException(desc='Cannot call stop when activity is '
ActivityException: 100.1 - Cannot call stop when activity is not started or
has been stopped already.
: ActivityException: 100.1 - Cannot call stop when activity is not started or
has been stopped already.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1828406/+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 1761197] Re: Not defined keypairs in instance_extra cellsV1 DBs
** Also affects: nova/ocata Importance: Undecided Status: New ** Changed in: nova/ocata Assignee: (unassigned) => Surya Seetharaman (tssurya) ** Changed in: nova/ocata Importance: Undecided => High ** Changed in: nova/ocata Status: New => Confirmed -- 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/1761197 Title: Not defined keypairs in instance_extra cellsV1 DBs Status in OpenStack Compute (nova): Confirmed Status in OpenStack Compute (nova) ocata series: In Progress Bug description: In newton there was the data migration to fill the "keypair" in instance_extra table. The migration checks if an instance has a keypair and then adds the keypair entry in the instance_extra table. This works if the keypair still exists in the keypair table. However, when running with cellsV1 the keypairs only exist in top DB and the migration only works in the instance_extra table of that DB. This means that in all cells DBs the instance_extra has the keypair not defined. This is important when migrating to cellsV2 because we will rely in the cells DBs. We should have a migration that gets the keypairs from nova_api DB to fill the keypair in instance_extra of the different cells DBs. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1761197/+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 1828382] [NEW] Missing field "Rbac policy" in Edit quota table under Identity Panel
Public bug reported: "Rbac policy" filed is missing in Edit Quota table. Steps to Reproduce: Go to Identity>Projects>Select any Project>Select Modify Quota Action>Go to "Network" tab in Edit Quota table. Here 'Rbac policy' filed is missing form table. ** Affects: horizon Importance: Undecided Status: New -- 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/1828382 Title: Missing field "Rbac policy" in Edit quota table under Identity Panel Status in OpenStack Dashboard (Horizon): New Bug description: "Rbac policy" filed is missing in Edit Quota table. Steps to Reproduce: Go to Identity>Projects>Select any Project>Select Modify Quota Action>Go to "Network" tab in Edit Quota table. Here 'Rbac policy' filed is missing form table. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1828382/+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 1818614] Re: [SRU] Various L3HA functional tests fails often
This bug was fixed in the package neutron - 2:12.0.5-0ubuntu4
---
neutron (2:12.0.5-0ubuntu4) bionic; urgency=medium
* d/p/bug1823038.patch: Cherry pick fix to ensure that None is not
passed as an argument when spawning the neutron-keepalived-state-change
agent (LP: #1823038).
neutron (2:12.0.5-0ubuntu3) bionic; urgency=medium
* d/p/fix-KeyError-in-OVS-firewall.patch: Cherry-picked from upstream
to prevent neutron ovs agent from crashing due to creation of two
security groups that both use the same remote security group, where
the first group's port range is a subset of the second (LP: #1813007).
* d/p/set-initial-ha-router-state-in-neutron-keepalived-st.patch:
Cherry-picked from upstream stable/rocky branch to ensure proper
detection of MASTER HA router by neutron-keepalived-state-change
(LP: #1818614).
-- James Page Tue, 09 Apr 2019 10:59:22 +0100
** Changed in: neutron (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 neutron.
https://bugs.launchpad.net/bugs/1818614
Title:
[SRU] Various L3HA functional tests fails often
Status in Ubuntu Cloud Archive:
Fix Released
Status in Ubuntu Cloud Archive pike series:
Fix Committed
Status in Ubuntu Cloud Archive queens series:
Fix Committed
Status in Ubuntu Cloud Archive rocky series:
Fix Committed
Status in Ubuntu Cloud Archive stein series:
Fix Released
Status in neutron:
Fix Released
Status in neutron package in Ubuntu:
Fix Released
Status in neutron source package in Bionic:
Fix Released
Status in neutron source package in Cosmic:
Fix Released
Status in neutron source package in Disco:
Fix Released
Bug description:
[Impact]
Need to get this added to the Ubuntu packages in order to safeguard against
missed VRRP transitions due to ip -o monitor not running at the time the
transition occurs. We have seen many cases in the fields where neutron routers
end up as active on multiple l3 agents (via neutron api) which leads to a
number of problems.
[Test Case]
* deploy Openstack (any version that supports l3ha)
* create HA router with max-l3-agents=2
* check neutron l3-agent-list-hosting-router for master location
* on both hosts that are running the l3-agent do
pid=`pgrep -f "/usr/bin/neutron-keepalived-state-change
--router_id=$ROUTER_UUID"`
ps -f --ppid $pid
pkill -f "/var/lib/neutron/ha_confs/$ROUTER_UUID/keepalived.conf"
pkill -f "/usr/bin/neutron-keepalived-state-change --router_id=$ROUTER_UUID"
ps -f --ppid $pid # <<< this should return nothing now
* without this patch you should now see both agents reporting the router as
"active"
* with the patch this should not happen (once neutron-keepalived-state-change
has been restarted by neutron-l3-agent)
[Regression Potential]
These patches have already landed in corresponding upstream branches and
therefore have undergone reviews + unit and functional testing upstream,
therefore regression potential is expected to be low.
Recently many L3 HA related functional tests are failing.
The common thing in all those errors is fact that it fails when waiting for
l3 ha router to become master.
Example stack trace:
ft2.12:
neutron.tests.functional.agent.l3.test_ha_router.LinuxBridgeL3HATestCase.test_ha_router_lifecycle_StringException:
Traceback (most recent call last):
File "neutron/tests/base.py", line 174, in func
return f(self, *args, **kwargs)
File "neutron/tests/base.py", line 174, in func
return f(self, *args, **kwargs)
File "neutron/tests/functional/agent/l3/test_ha_router.py", line 81, in
test_ha_router_lifecycle
self._router_lifecycle(enable_ha=True, router_info=router_info)
File "neutron/tests/functional/agent/l3/framework.py", line 274, in
_router_lifecycle
common_utils.wait_until_true(lambda: router.ha_state == 'master')
File "neutron/common/utils.py", line 690, in wait_until_true
raise WaitTimeout(_("Timed out after %d seconds") % timeout)
neutron.common.utils.WaitTimeout: Timed out after 60 seconds
Example failure: http://logs.openstack.org/79/633979/21/check/neutron-
functional-python27/ce7ef07/logs/testr_results.html.gz
Logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22ha_state%20%3D%3D%20'master')%5C%22
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1818614/+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 1823038] Re: Neutron-keepalived-state-change fails to check initial router state
This bug was fixed in the package neutron - 2:12.0.5-0ubuntu4 --- neutron (2:12.0.5-0ubuntu4) bionic; urgency=medium * d/p/bug1823038.patch: Cherry pick fix to ensure that None is not passed as an argument when spawning the neutron-keepalived-state-change agent (LP: #1823038). neutron (2:12.0.5-0ubuntu3) bionic; urgency=medium * d/p/fix-KeyError-in-OVS-firewall.patch: Cherry-picked from upstream to prevent neutron ovs agent from crashing due to creation of two security groups that both use the same remote security group, where the first group's port range is a subset of the second (LP: #1813007). * d/p/set-initial-ha-router-state-in-neutron-keepalived-st.patch: Cherry-picked from upstream stable/rocky branch to ensure proper detection of MASTER HA router by neutron-keepalived-state-change (LP: #1818614). -- James Page Tue, 09 Apr 2019 10:59:22 +0100 ** Changed in: neutron (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 neutron. https://bugs.launchpad.net/bugs/1823038 Title: Neutron-keepalived-state-change fails to check initial router state Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive pike series: Fix Committed Status in Ubuntu Cloud Archive queens series: Fix Committed Status in Ubuntu Cloud Archive rocky series: Fix Released Status in Ubuntu Cloud Archive stein series: Fix Released Status in neutron: Confirmed Status in neutron package in Ubuntu: Fix Released Status in neutron source package in Bionic: Fix Released Status in neutron source package in Cosmic: Fix Released Status in neutron source package in Disco: Fix Released Bug description: [Impact] Fix for bug 1818614 in *-proposed includes a regression is the deployment is not using the rootwrap-daemon. [Test Case] See bug 1818614 [Regression Potential] Low - this is a minor fix to resolve a regression due to the SRU bug 1818614. [Original Description] As fix for bug https://bugs.launchpad.net/neutron/+bug/1818614 we added to neutron-keepalived-state-change monitor possibility to check initial status of router (master or slave). Unfortunately for some reason I see now in journal log of functional job that this check is failing with error like: Apr 03 09:19:09 ubuntu-bionic-ovh-gra1-0004666718 neutron-keepalived-state-change[1553]: 2019-04-03 09:19:09.778 1553 ERROR neutron.agent.l3.keepalived_state_change [-] Failed to get initial status of router cd300e6b-8222-4100-8f6a-3b5c4d5fe37b: FailedToDropPrivileges: privsep helper command exited non-zero (96) 2019-04-03 09:19:09.778 1553 ERROR neutron.agent.l3.keepalived_state_change Traceback (most recent call last): 2019-04-03 09:19:09.778 1553 ERROR neutron.agent.l3.keepalived_state_change File "/home/zuul/src/git.openstack.org/openstack/neutron/neutron/agent/l3/keepalived_state_change.py", line 98, in handle_initial_state 2019-04-03 09:19:09.778 1553 ERROR neutron.agent.l3.keepalived_state_change for address in ip.addr.list(): 2019-04-03 09:19:09.778 1553 ERROR neutron.agent.l3.keepalived_state_change File "/home/zuul/src/git.openstack.org/openstack/neutron/neutron/agent/linux/ip_lib.py", line 540, in list 2019-04-03 09:19:09.778 1553 ERROR neutron.agent.l3.keepalived_state_change **kwargs) 2019-04-03 09:19:09.778 1553 ERROR neutron.agent.l3.keepalived_state_change File "/home/zuul/src/git.openstack.org/openstack/neutron/neutron/agent/linux/ip_lib.py", line 1412, in get_devices_with_ip 2019-04-03 09:19:09.778 1553 ERROR neutron.agent.l3.keepalived_state_change devices = privileged.get_link_devices(namespace, **link_args) 2019-04-03 09:19:09.778 1553 ERROR neutron.agent.l3.keepalived_state_change File "/home/zuul/src/git.openstack.org/openstack/neutron/.tox/dsvm-functional-python27/local/lib/python2.7/site-packages/oslo_privsep/priv_context.py", line 240, in _wrap 2019-04-03 09:19:09.778 1553 ERROR neutron.agent.l3.keepalived_state_change self.start()
[Yahoo-eng-team] [Bug 1813007] Re: [SRU] [OSSA-2019-002] Unable to install new flows on compute nodes when having broken security group rules (CVE-2019-10876)
This bug was fixed in the package neutron - 2:12.0.5-0ubuntu4 --- neutron (2:12.0.5-0ubuntu4) bionic; urgency=medium * d/p/bug1823038.patch: Cherry pick fix to ensure that None is not passed as an argument when spawning the neutron-keepalived-state-change agent (LP: #1823038). neutron (2:12.0.5-0ubuntu3) bionic; urgency=medium * d/p/fix-KeyError-in-OVS-firewall.patch: Cherry-picked from upstream to prevent neutron ovs agent from crashing due to creation of two security groups that both use the same remote security group, where the first group's port range is a subset of the second (LP: #1813007). * d/p/set-initial-ha-router-state-in-neutron-keepalived-st.patch: Cherry-picked from upstream stable/rocky branch to ensure proper detection of MASTER HA router by neutron-keepalived-state-change (LP: #1818614). -- James Page Tue, 09 Apr 2019 10:59:22 +0100 ** Changed in: neutron (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 neutron. https://bugs.launchpad.net/bugs/1813007 Title: [SRU] [OSSA-2019-002] Unable to install new flows on compute nodes when having broken security group rules (CVE-2019-10876) Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive pike series: Fix Committed Status in Ubuntu Cloud Archive queens series: Fix Committed Status in Ubuntu Cloud Archive rocky series: Fix Committed Status in Ubuntu Cloud Archive stein series: Fix Released Status in neutron: Fix Released Status in OpenStack Security Advisory: Fix Released Status in neutron package in Ubuntu: Fix Released Status in neutron source package in Bionic: Fix Released Status in neutron source package in Cosmic: Fix Released Status in neutron source package in Disco: Fix Released Bug description: It appears that we have found that neutron-openvswitch-agent appears to have a bug where two security group rules that have two different port ranges that overlap tied to the same parent security group will cause neutron to not be able to configure networks on the compute nodes where those security groups are present. Those are the broken security rules: https://pastebin.canonical.com/p/wSy8RSXt85/ Here is the log when we discovered the issue: https://pastebin.canonical.com/p/wvFKjNWydr/ Ubuntu SRU Details -- [Impact] Neutron openvswitch agent crashes due to creation of two security groups that both use the same remote security group, where the first group doesn't define a port range and the second one does (one is a subset of the other; specifying no port range is the same as a full port range). [Test case] See comment #18 below. [Regression Potential] The fix is fairly minimal and has landed upstream in master branch. It has therefore passed all unit and function tests that get run in the upstream gate and has been reviewed by upstream neutron core reviewers. This all helps to minimize the regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1813007/+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 1828375] [NEW] Bulk creation of subports fails with StaleDataError
Public bug reported: ENV: Neutron Ocata (10.0.4) Kola Ansible Rhel 7.4 One compute node (openvswitch) with 3 virtual machine kubernetes minions with Nested Kuryr. REPRODUCTION: Creation of multiple containers in very short time (in fact creation of many subports in very short time) Some OpenStack ports(trunk subports) will never transition to Active status. EXCEPTION: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 155, in _process_incoming res = self.dispatcher.dispatch(message) File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 222, in dispatch return self._do_dispatch(endpoint, method, ctxt, args) File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 192, in _do_dispatch result = func(ctxt, **new_args) File "/usr/lib/python2.7/site-packages/neutron/services/trunk/rpc/server.py", line 110, in update_trunk_status trunk.update(status=status) File "/usr/lib/python2.7/site-packages/neutron/objects/base.py", line 203, in decorator res = func(self, *args, **kwargs) File "/usr/lib/python2.7/site-packages/neutron/objects/trunk.py", line 127, in update super(Trunk, self).update() File "/usr/lib/python2.7/site-packages/neutron/objects/base.py", line 618, in update self._get_composite_keys())) File "/usr/lib/python2.7/site-packages/neutron/objects/db/api.py", line 80, in update_object db_obj.save(session=context.session) File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/models.py", line 50, in save session.flush() File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/session.py", line 2027, in flush self._flush(objects) File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/session.py", line 2145, in _flush transaction.rollback(_capture_exception=True) File "/usr/lib64/python2.7/site-packages/sqlalchemy/util/langhelpers.py", line 60, in __exit__ compat.reraise(exc_type, exc_value, exc_tb) File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/session.py", line 2109, in _flush flush_context.execute() File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/unitofwork.py", line 373, in execute rec.execute(self) File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/unitofwork.py", line 532, in execute uow File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/persistence.py", line 170, in save_obj mapper, table, update) File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/persistence.py", line 728, in _emit_update_statements (table.description, len(records), rows)) StaleDataError: UPDATE statement on table 'standardattributes' expected to update 1 row(s); 0 were matched. ADDITIONAL INVESTIGATION: Actually there are multiple concurrent update calls to database for trunk ports revision_number. Trunks in database: MariaDB [neutron]> select * from trunks; ++--+--+--+--+--+--+ | admin_state_up | project_id | id | name | port_id | status | standard_attr_id | ++--+--+--+--+--+--+ | 1 | 9e8f068a23914209a839be451fe7533a | ce3c9271-70e9-4e4a-bdaf-bcb1a8d3901f | owc4-trunk-1 | e4392b5f-ecc7-4b94-bfe3-a2a8bc001057 | ACTIVE | 56 | | 1 | 9e8f068a23914209a839be451fe7533a | d9242ed7-4274-4537-962e-5e40b6540cc5 | owc4-trunk-2 | fe0c1041-4ccd-4fd7-b2b9-0c78c6b8c5fa | ACTIVE | 58 | | 1 | 9e8f068a23914209a839be451fe7533a | f50f1f1e-539b-4915-b410-d4b349c70d4b | owc4-trunk-0 | e4ff627d-37ca-447e-85cc-23347a9ba871 | ACTIVE | 49 | ++--+--+--+--+--+--+ 3 rows in set (0.00 sec) standardattributes for trunks: MariaDB [neutron]> select * from standardattributes where resource_type='trunks'; ++---+-+-+-+-+ | id | resource_type | created_at | updated_at | description | revision_number | ++---+-+-+-+-+ | 49 | trunks| 2019-04-16 08:14:10 | 2019-04-25 08:37:32 | | 710 | | 56 | trunks| 2019-04-16 08:14:45 | 2019-04-25 08:37:32 | | 739 | | 58 | trunks| 2019-04-16 08:15:09 | 2019-04-25 08:37:56 | | 654 |
[Yahoo-eng-team] [Bug 1828367] [NEW] Ironic notifier - Notify Ironic on port status changes
Public bug reported: More details in: https://storyboard.openstack.org/#!/story/1304673 Similar to how Nova can be notified (neutron/notifiers/nova.py) Ironic should also be notified on relevant port status changes. ** 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/1828367 Title: Ironic notifier - Notify Ironic on port status changes Status in neutron: New Bug description: More details in: https://storyboard.openstack.org/#!/story/1304673 Similar to how Nova can be notified (neutron/notifiers/nova.py) Ironic should also be notified on relevant port status changes. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1828367/+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 1828364] [NEW] DVR: Fip namespaces are created in all the controllers and computes with vm only when an external interface to the router is added
Public bug reported: Even if there is no any floating IP created in external network, "fip" namespace is created on all compute and network nodes for dvr router with external gateway set. In case when user don't want to use floating IPs but only SNAT, it is "waste" of (possible) many external IPs used for "network:floatingip_agent_gateway" devices. Also fip namespace should be (probably) created only on compute nodes as on network nodes it isn't necessary probably. ** Affects: neutron Importance: Undecided Assignee: Slawek Kaplonski (slaweq) Status: New ** Tags: l3-dvr-backlog -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1828364 Title: DVR: Fip namespaces are created in all the controllers and computes with vm only when an external interface to the router is added Status in neutron: New Bug description: Even if there is no any floating IP created in external network, "fip" namespace is created on all compute and network nodes for dvr router with external gateway set. In case when user don't want to use floating IPs but only SNAT, it is "waste" of (possible) many external IPs used for "network:floatingip_agent_gateway" devices. Also fip namespace should be (probably) created only on compute nodes as on network nodes it isn't necessary probably. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1828364/+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 1828363] [NEW] FdbInterfaceTestCase interface names should be randomly generated
Public bug reported: "FdbInterfaceTestCase" interface names, in "no_namespace" case, should be generated randomly to avoid interference between test cases. ** Affects: neutron Importance: Undecided Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez) Status: New ** Changed in: neutron Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1828363 Title: FdbInterfaceTestCase interface names should be randomly generated Status in neutron: New Bug description: "FdbInterfaceTestCase" interface names, in "no_namespace" case, should be generated randomly to avoid interference between test cases. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1828363/+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 1828333] Re: changing path of filesystem_store_datadir does not reflect
Flagging this to Devstack as Glance parses the config files as designed. ** Also affects: devstack Importance: Undecided Status: New ** Changed in: glance Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1828333 Title: changing path of filesystem_store_datadir does not reflect Status in devstack: New Status in Glance: Invalid Bug description: If you change the 'filesystem_store_datadir' under glance_store section in glance-api.conf file and restart the glance-api service then it still points towards earlier/default path. DevStack Version: train Change: 0cb721b790baa8f2929f716dc8945f4bfd25f08f Merge "Fix is_neutron_legacy_enabled function" 2019-05-04 22:38:45 + How to reproduce: 1. Modify glance-api.conf file [glance_store] #filesystem_store_datadir = /opt/stack/data/glance/images/ (old path) filesystem_store_datadir = /opt/stack/data/glance/images_1/ #(new path) 2. Restart glance-api service $ sudo systemctl restart devstack@g-api.service Expected result: After restart images_1 directory should be created in /opt/stack/data/glance directory Actual result: images_1 directory is not created. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1828333/+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
