[Yahoo-eng-team] [Bug 1732624] [NEW] VM lost connecting when manually reboot using XenAPI driver and neutron pooling mode
Public bug reported: Precondition: 1. XenAPI driver in nova with XenServer 7.1 2. minimize_polling = True in neutron-openvswitch-agent running for dom0 (q-domua in devstack) 3. Booting a VM via OpenStack CLI and all works 4. Reboot the VM manually, not from OpenStack CLI Result: Cannot ping VM anymore ** Affects: nova Importance: Undecided Assignee: huan (huan-xie) Status: In Progress ** Changed in: nova Assignee: (unassigned) => huan (huan-xie) -- 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/1732624 Title: VM lost connecting when manually reboot using XenAPI driver and neutron pooling mode Status in OpenStack Compute (nova): In Progress Bug description: Precondition: 1. XenAPI driver in nova with XenServer 7.1 2. minimize_polling = True in neutron-openvswitch-agent running for dom0 (q-domua in devstack) 3. Booting a VM via OpenStack CLI and all works 4. Reboot the VM manually, not from OpenStack CLI Result: Cannot ping VM anymore To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1732624/+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 1732655] [NEW] Install and configure (Ubuntu) in glance - Missing Create DB part
Public bug reported: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: __ - [ ] This is a doc addition request. - [X] I have a fix to the document that I can paste below including example: Start of glance install instructions (Pike on Ubuntu) say: "mysql" but doesnt create DB or add grants (Missing steps) before running the ostack client commands to add glance service, user, role and tie them up I think you are missing the following lines/should be: "mysql -u root -p" "create database glance;" "grant all privileges on glance.* to 'glance'@'localhost' identified by 'GLANCE_DBPASS';" "grant all privileges on glance.* to 'glance'@'%' identified by 'GLANCE_DBPASS';" If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: 15.0.1.dev1 on 'Mon Aug 7 01:28:54 2017, commit 9091d26' SHA: 9091d262afb120fd077bae003d52463f833a4fde Source: https://git.openstack.org/cgit/openstack/glance/tree/doc/source/install/install-ubuntu.rst URL: https://docs.openstack.org/glance/pike/install/install-ubuntu.html ** Affects: glance Importance: Undecided Status: New ** Tags: glance install -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1732655 Title: Install and configure (Ubuntu) in glance - Missing Create DB part Status in Glance: New Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: __ - [ ] This is a doc addition request. - [X] I have a fix to the document that I can paste below including example: Start of glance install instructions (Pike on Ubuntu) say: "mysql" but doesnt create DB or add grants (Missing steps) before running the ostack client commands to add glance service, user, role and tie them up I think you are missing the following lines/should be: "mysql -u root -p" "create database glance;" "grant all privileges on glance.* to 'glance'@'localhost' identified by 'GLANCE_DBPASS';" "grant all privileges on glance.* to 'glance'@'%' identified by 'GLANCE_DBPASS';" If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: 15.0.1.dev1 on 'Mon Aug 7 01:28:54 2017, commit 9091d26' SHA: 9091d262afb120fd077bae003d52463f833a4fde Source: https://git.openstack.org/cgit/openstack/glance/tree/doc/source/install/install-ubuntu.rst URL: https://docs.openstack.org/glance/pike/install/install-ubuntu.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1732655/+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 1732024] Re: docs: unit tests doc links to hacking repo docs which isn't particularly helpful
Reviewed: https://review.openstack.org/519482 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=85235d229be7ee77640a68ffd8619518478d0805 Submitter: Zuul Branch:master commit 85235d229be7ee77640a68ffd8619518478d0805 Author: Matt Riedemann Date: Mon Nov 13 17:13:18 2017 -0500 doc: fix link to creating unit tests in contributor guide The testing strategy doc was linking to the hacking repo docs on creating unit tests, which are very specific to creating unit tests for hacking rules. This changes the link to the 'creating unit tests' section in the HACKING.rst file, which has more information on testing within nova. Along with that change, the HACKING.rst testing section is updated a bit to point out that we use stestr now instead of testr and adds a proper link to the development environment quickstart docs. The nova/tests/unit/README.rst actually needs a lot of work, but that's left for another day. Change-Id: Ie5106d87d632286162b31ce132e947c306d21abd Closes-Bug: #1732024 ** Changed in: nova Status: In Progress => 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/1732024 Title: docs: unit tests doc links to hacking repo docs which isn't particularly helpful Status in OpenStack Compute (nova): Fix Released Bug description: This page: https://docs.openstack.org/nova/latest/contributor/testing.html#unit- tests Links to: https://docs.openstack.org/hacking/latest/user/hacking.html#creating- unit-tests Which is specific to writing unit tests for the hacking repo, not nova. The nova docs should probably point at the nova hacking docs instead: https://github.com/openstack/nova/blob/master/HACKING.rst#creating- unit-tests To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1732024/+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 1731439] Re: stack topology doesn't show dependency when convergence is disabled
** Also affects: heat-dashboard 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/1731439 Title: stack topology doesn't show dependency when convergence is disabled Status in heat-dashboard: New Status in OpenStack Dashboard (Horizon): New Bug description: When convergence engine is disabled in heat.conf Stack topology doesn't show dependency lines between the resources To manage notifications about this bug go to: https://bugs.launchpad.net/heat-dashboard/+bug/1731439/+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 1732669] [NEW] Install and configure controller node in neutron - need to install nova compute and api first
Public bug reported: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [X] This doc is inaccurate in this way: In order to edit and configure compute to use neutron, nova needs to be installed (so executing the Compute Service Instructions should be pre-req for Neutron installation) - imho. - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: 11.0.2.dev64 on 2017-11-14 20:38 SHA: eb2be51d847f8e8b79488b0c956d0d2aa6122ea7 Source: https://git.openstack.org/cgit/openstack/neutron/tree/doc/source/install/controller-install-ubuntu.rst URL: https://docs.openstack.org/neutron/pike/install/controller-install-ubuntu.html ** Affects: neutron Importance: Undecided Status: New ** Tags: doc -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1732669 Title: Install and configure controller node in neutron - need to install nova compute and api first Status in neutron: New Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [X] This doc is inaccurate in this way: In order to edit and configure compute to use neutron, nova needs to be installed (so executing the Compute Service Instructions should be pre-req for Neutron installation) - imho. - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: 11.0.2.dev64 on 2017-11-14 20:38 SHA: eb2be51d847f8e8b79488b0c956d0d2aa6122ea7 Source: https://git.openstack.org/cgit/openstack/neutron/tree/doc/source/install/controller-install-ubuntu.rst URL: https://docs.openstack.org/neutron/pike/install/controller-install-ubuntu.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1732669/+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 1732685] [NEW] instance.snapshot notification samples are assigned to two different Notification classes
Public bug reported: Here attached to the wrong class: https://github.com/openstack/nova/blob/b28924b8e4115f436d46812877066d5d03ad272a/nova/notifications/objects/instance.py#L414-L415 Here attached to the correct class: https://github.com/openstack/nova/blob/b28924b8e4115f436d46812877066d5d03ad272a/nova/notifications/objects/instance.py#L522-L523 This causes that the sample will appear twice in the table of versioned notifications in the devref: https://docs.openstack.org/nova/latest/reference/notifications.html #existing-versioned-notifications It also makes both occurrences shown by default instead of hidden as the rest of the sample by default. The bug only effects the master branch as the patch https://review.openstack.org/#/c/453077/ that caused this was merged after Pike. ** Affects: nova Importance: Undecided Assignee: Balazs Gibizer (balazs-gibizer) Status: In Progress ** Tags: doc docs notifications ** Description changed: Here attached to the wrong class: https://github.com/openstack/nova/blob/b28924b8e4115f436d46812877066d5d03ad272a/nova/notifications/objects/instance.py#L414-L415 Here attached to the correct class: https://github.com/openstack/nova/blob/b28924b8e4115f436d46812877066d5d03ad272a/nova/notifications/objects/instance.py#L522-L523 This causes that the sample will appear twice in the table of versioned notifications in the devref: https://docs.openstack.org/nova/latest/reference/notifications.html #existing-versioned-notifications It also makes both occurrences shown by default instead of hidden as the rest of the sample by default. + + The bug only effects the master branch as the patch + https://review.openstack.org/#/c/453077/ that caused this was merged + after Pike. ** Tags added: notifications ** Tags added: doc ** Tags added: docs ** Changed in: nova Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer) -- 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/1732685 Title: instance.snapshot notification samples are assigned to two different Notification classes Status in OpenStack Compute (nova): In Progress Bug description: Here attached to the wrong class: https://github.com/openstack/nova/blob/b28924b8e4115f436d46812877066d5d03ad272a/nova/notifications/objects/instance.py#L414-L415 Here attached to the correct class: https://github.com/openstack/nova/blob/b28924b8e4115f436d46812877066d5d03ad272a/nova/notifications/objects/instance.py#L522-L523 This causes that the sample will appear twice in the table of versioned notifications in the devref: https://docs.openstack.org/nova/latest/reference/notifications.html #existing-versioned-notifications It also makes both occurrences shown by default instead of hidden as the rest of the sample by default. The bug only effects the master branch as the patch https://review.openstack.org/#/c/453077/ that caused this was merged after Pike. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1732685/+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 1732707] [NEW] AllocationCandidates.get_by_filters returns candidates containing non connected RPs
Public bug reported: Consider the following setup in placement: CN1 (VCPU) CN2 (VCPU) / agg3 \ agg1 / agg1 \ agg2 SS3 (IPV4) SS1 (DISK_GB) SS2 (IPV4) Then VCPU, DISK_GB nd IPV4 resources are requested. However besides the expected candidates we get invalid candidates mixing CN1 with SS2 and CN2 with SS3 which are clearly invalid. Here is a functional test reproducing the issue: https://review.openstack.org/#/c/519617 ** Affects: nova Importance: Undecided Status: New ** Tags: placement ** Tags added: 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/1732707 Title: AllocationCandidates.get_by_filters returns candidates containing non connected RPs Status in OpenStack Compute (nova): New Bug description: Consider the following setup in placement: CN1 (VCPU) CN2 (VCPU) / agg3 \ agg1 / agg1 \ agg2 SS3 (IPV4) SS1 (DISK_GB) SS2 (IPV4) Then VCPU, DISK_GB nd IPV4 resources are requested. However besides the expected candidates we get invalid candidates mixing CN1 with SS2 and CN2 with SS3 which are clearly invalid. Here is a functional test reproducing the issue: https://review.openstack.org/#/c/519617 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1732707/+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 1533083] Re: useless HTTP info in the error info for creating existing flavor
This is arguably not a bug, so marked as opinion. ** No longer affects: nova ** Changed in: python-novaclient Status: In Progress => Opinion -- 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/1533083 Title: useless HTTP info in the error info for creating existing flavor Status in python-novaclient: Opinion Bug description: [Summary] useless HTTP info in the error info for creating existing flavor [Topo] devstack all-in-one node [Description and expect result] no useless HTTP info in the error info for creating existing flavor [Reproduceable or not] reproduceable [Recreate Steps] 1) create an existing flavor: root@45-59:/opt/stack/devstack# nova flavor-create --is-public false f1 13 1024 1 1 ERROR (Conflict): Flavor with name f1 already exists. (HTTP 409) (Request-ID: req-3769491c-5f82-4064-8b45-ef1a3442957d) root@45-59:/opt/stack/devstack# ISSUE: For a cli user, the info "ERROR (Conflict): Flavor with name f1 already exists." is enough, it let user know what happened. But the info "HTTP 409" is useless 2) same issue when remove a non-existing flavor-access: root@45-59:/opt/stack/devstack# nova flavor-access-remove 13 adminm ERROR (NotFound): Flavor access not found for 13 / adminm combination. (HTTP 404) (Request-ID: req-2eeb9656-72a9-45d8-bbe0-48536c8e0b5d) root@45-59:/opt/stack/devstack# 3)Below is the error info when remove a non-existing flavor for reference: root@45-59:/opt/stack/devstack# nova flavor-delete aa ERROR (CommandError): No flavor with a name or ID of 'aa' exists. root@45-59:/opt/stack/devstack# [Configration] reproduceable bug, no need [logs] reproduceable bug, no need [Root cause anlyze or debug inf] reproduceable bug [Attachment] None To manage notifications about this bug go to: https://bugs.launchpad.net/python-novaclient/+bug/1533083/+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 1715691] Re: install docs for controller missing db commands
** 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/1715691 Title: install docs for controller missing db commands Status in neutron: Fix Released Bug description: The page https://docs.openstack.org/neutron/pike/install/controller- install-rdo.html just mentioned the login database, but there are other operations after login to the database. The document should also have the steps to create the database and add access. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1715691/+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 1732731] [NEW] AllocationCandidates.get_by_filters does not handle indirectly connected sharing RPs
Public bug reported: Consider the following resource setup: CN1 (VCPU, MEMORY_MB) / \ /agg1\agg2 / \ SS1 ( SS2 ( DISK_GB) IPV4_ADDRESS SRIOV_NET_VF) Then we only request resources provided by SS1 and SS2 but not CN1. This case results in no allocation candidates returned. I expect that in this case we get allocation candidates that contains SS1 and SS2. See the reproduction test case in https://review.openstack.org/#/c/519601/ ** Affects: nova Importance: Undecided Status: New ** Tags: placement ** Tags added: 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/1732731 Title: AllocationCandidates.get_by_filters does not handle indirectly connected sharing RPs Status in OpenStack Compute (nova): New Bug description: Consider the following resource setup: CN1 (VCPU, MEMORY_MB) / \ /agg1\agg2 / \ SS1 ( SS2 ( DISK_GB) IPV4_ADDRESS SRIOV_NET_VF) Then we only request resources provided by SS1 and SS2 but not CN1. This case results in no allocation candidates returned. I expect that in this case we get allocation candidates that contains SS1 and SS2. See the reproduction test case in https://review.openstack.org/#/c/519601/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1732731/+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 1732741] [NEW] Image Create Sets Property architecture=''
Public bug reported: When creating an image, if the user fills in the architecture field, then deletes the entered value, when the image is registered, it will have the architecture property set to a value of '' (empty string). This prevents the image from being used, as it is not a valid architecture. If the user completely avoids the architecture field, then the image will not have this empty architecture property set. I'm guessing that the data model for the image gets built up as the user is filling out the information about the image, and once something is typed into the architecture field, it creates the property and corresponding value, but when the value is cleared, the property is left with a value of an empty string, instead of removing the property entirely. ** 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/1732741 Title: Image Create Sets Property architecture='' Status in OpenStack Dashboard (Horizon): New Bug description: When creating an image, if the user fills in the architecture field, then deletes the entered value, when the image is registered, it will have the architecture property set to a value of '' (empty string). This prevents the image from being used, as it is not a valid architecture. If the user completely avoids the architecture field, then the image will not have this empty architecture property set. I'm guessing that the data model for the image gets built up as the user is filling out the information about the image, and once something is typed into the architecture field, it creates the property and corresponding value, but when the value is cleared, the property is left with a value of an empty string, instead of removing the property entirely. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1732741/+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 1705755] Re: [RFE] Plugin support for API resource attribute extensions
** Changed in: python-openstacksdk
Status: New => Won't Fix
** No longer affects: python-openstacksdk
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1705755
Title:
[RFE] Plugin support for API resource attribute extensions
Status in neutron:
Triaged
Status in python-openstackclient:
New
Bug description:
FORWARD
---
The purpose of this bug is to facilitate a discussion. While I'm willing to
do all the work to implement the feature request herein, I'd first like some
agreement that:
- We want to solve this problem.
- Core(s) on the respective projects (python-openstackclient and
python-openstacksdk) are willing to provide some guidance on the best
high-level approach.
BACKGROUND
--
Some OpenStack REST APIs such as neutron and nova support API extensions.
While the implementation details for API extensions may differ from project
to project, the basic extension support across all projects includes the
ability for pluggable extensions to augment the REST API in the following ways:
(a) Introducing new RESTful resources (APIs). These may be new top-level
resources (e.g. /v1/theapi/{extension_resource}) or sub-resources (e.g.
/v1/theapi/existing_resource/{extension_subresource}).
(b) Adding new attributes (fields) to existing RESTful resources. For example
neutron's net-mtu extension adds a 'mtu' attribute to networks [1] and nova's
extended status adds attributes to servers [2].
While some API extensions may exist in-tree (e.g. right in neutron or
nova), they can also live in out-of-tree projects that implement
plugins/drivers/etc..
Hopefully we can all agree that a CLI should encompass the means to
support both #a and #b above in some form or another in order to
obtain the pluggability our consumers expect with OpenStack.
PROBLEM DESCRIPTION
For sake of argument lets consider #a and #b as use cases from an OpenStack
CLI (python-openstackclient and python-openstacksdk) perspective. Albeit we are
talking from a contributor perspective here; but the ability to contribute
drive features users can consume.
(a) This case should already be supported via the existing OSC plugin
model. For example [3].
(b) This case is covered for stadium projects; they can add logic
right into python-openstackclient[sdk] as needed. However for non-
stadium projects, this case is not covered; today there's no easy way
to extend existing OSC resources/actions/options/etc. in a reusable
manner. For example, suppose a non-stadium neutron (plugin) project
implements the network API, extends the network resource with
additional attribute(s) and wants to provide CLI support for these
attributes. Ideally they should be able to reuse the existing neutron
network OSC logic in a pluggable manner such that they need not
reimplement the OSC "actions" and associated logic.
From a technical perspective, case #b roughly requires the ability for
non-stadium projects (with such attribute extensions) to:
(1) Add attributes to python-openstacksdk resource(s). This allows the
extension attributes to be "collected" from an API response body.
(2) Extend existing python-openstackclient commands by;
a) Adding parser options if needed to support the attribute extension(s).
b) Adding custom "take action" logic enabling the extension to process
attribute extension options if needed.
c) Displaying the attribute extension(s).
In neutron alone, the following out-of-tree projects implement extensions
falling under case #b:
- vmware-nsx
- gbpservice
- quark
- networking-cisco
- networking-bigswitch
- networking-h3c
This support was provided in an ad-hoc fashion with the classic python
clients (e.g. python-neutronclient) via it's ability to
pass/handle/display arbitrary key/values. For example an API extension
that adds a 'meta' boolean attribute to networks can be handled with
the neutron client without any changes. The sample output snippets
below show GET and POST (notice the 'meta' attribute that's added by
the sample extension).
-->
stack@bvm2:~/devstack$ neutron --debug net-show my-meta-net
...
RESP BODY:
{"network":{"provider:physical_network":null,"ipv6_address_scope":null,"meta":true,
...
+---+--+
| Field | Value|
+---+--+
| admin_state_up| True |
| availability_zone_hints | |
| availability_zones| nova |
| created_at| 2017-07-21T17:31:23Z |
| description |
[Yahoo-eng-team] [Bug 1732593] Re: TypeError: archive_deleted_rows got multiple values for keyword arguments 'max_rows'
** Also affects: nova/ocata Importance: Undecided Status: New ** Also affects: nova/pike 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/1732593 Title: TypeError: archive_deleted_rows got multiple values for keyword arguments 'max_rows' Status in OpenStack Compute (nova): In Progress Status in OpenStack Compute (nova) ocata series: New Status in OpenStack Compute (nova) pike series: New Bug description: If you run archive_deleted_rows subcommand with following parameters, it raises TypeError exception. $nova-manage db archive_deleted_rows 1000 1000 Output An error has occurred: Traceback (most recent call last): File "/opt/stack/nova/nova/cmd/manage.py", line 1924, in main ret = fn(*fn_args, **fn_kwargs) TypeError: archive_deleted_rows() got multiple values for argument 'max_rows' Environment details: : commit 91f62818c3ab5f7f7cee11df7a7b7d3ce290ecb8 Merge: a6280e5 c09eaf8 Author: Jenkins Date: Sun Sep 10 18:31:13 2017 + Merge "Update OS_AUTH_URL in Configuration.rst" nova: commit b7f53a33faf6187ad0b16e45cb14ece07892f7bc Merge: e48db05 a9d9255 Author: Zuul Date: Wed Nov 8 07:16:14 2017 + Merge "Fix return type in FilterScheduler._legacy_find_hosts" Reason: In fn_kwargs for max_rows parameter it is assigning default value of max_rows which is 1000, and not the value which we are passing through command. So it is giving above mentioned TypeError. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1732593/+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 1732581] Re: nova-specs: py27 fails "Line limited to a maximum of 79 characters."
Reviewed: https://review.openstack.org/520281 Committed: https://git.openstack.org/cgit/openstack/nova-specs/commit/?id=43981801396455e832199a47b48a68c2fe88acb3 Submitter: Zuul Branch:master commit 43981801396455e832199a47b48a68c2fe88acb3 Author: Takashi NATSUME Date: Thu Nov 16 12:38:41 2017 +0900 Fix "Line limited to a maximum of 79 characters" The py27 job was not executed when Id7ed89a24ff6e2fd7ab4eee5b117cb6b6c763c44 was merged. So fix the maximum length of the line. Change-Id: I9953a8576942d394b91152a5fe221683d1057fb9 Closes-Bug: #1732581 ** Changed in: nova Status: In Progress => 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/1732581 Title: nova-specs: py27 fails "Line limited to a maximum of 79 characters." Status in OpenStack Compute (nova): Fix Released Bug description: http://logs.openstack.org/23/517223/2/check/openstack-tox-py27/9de4411 /job-output.txt.gz 2017-11-16 00:34:56.141804 | ubuntu-xenial | Traceback (most recent call last): 2017-11-16 00:34:56.141837 | ubuntu-xenial | File "tests/test_titles.py", line 137, in test_template 2017-11-16 00:34:56.141866 | ubuntu-xenial | self._check_lines_wrapping(filename, data) 2017-11-16 00:34:56.141900 | ubuntu-xenial | File "tests/test_titles.py", line 95, in _check_lines_wrapping 2017-11-16 00:34:56.141924 | ubuntu-xenial | (tpl, i + 1)) 2017-11-16 00:34:56.141983 | ubuntu-xenial | File "/home/zuul/src/git.openstack.org/openstack/nova-specs/.tox/py27/local/lib/python2.7/site-packages/unittest2/case.py", line 702, in assertTrue 2017-11-16 00:34:56.142012 | ubuntu-xenial | raise self.failureException(msg) 2017-11-16 00:34:56.142066 | ubuntu-xenial | AssertionError: False is not true : specs/queens/approved/symmetric-allocations.rst:61: Line limited to a maximum of 79 characters. The py27 job was not executed when https://review.openstack.org/#/c/508164/ was merged. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1732581/+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 1727602] Re: nova-specs: tests.test_titles.TestTitles.test_template fails
Reviewed: https://review.openstack.org/517223
Committed:
https://git.openstack.org/cgit/openstack/nova-specs/commit/?id=44334e7114f16b329438b4145217be6fd751c66c
Submitter: Zuul
Branch:master
commit 44334e7114f16b329438b4145217be6fd751c66c
Author: Takashi NATSUME
Date: Thu Nov 2 18:09:16 2017 +0900
Set the 'Upgrade impact' subsection as optional
The 'Upgrade impact' subsection has been added in the spec template
in I1798f2bdb246af9b9b12dbe9276d0a68a82e4c88.
But 'py27' test fails since it is merged
because the 'Upgrade impact' subsection is required
in existing queens and backlog specs.
So set the 'Upgrade impact' subsection as optional
in queens and backlog specs.
Change-Id: I8c69369a421454f30675a9ad9da8b9c51a2e7baa
Closes-Bug: #1727602
** Changed in: nova
Status: In Progress => 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/1727602
Title:
nova-specs: tests.test_titles.TestTitles.test_template fails
Status in OpenStack Compute (nova):
Fix Released
Bug description:
In nova-specs, tests.test_titles.TestTitles.test_template fails when
'tox -e py27' is executed.
stack@devstack-master:/tmp/nova-specs$ tox -e py27
py27 develop-inst-nodeps: /tmp/nova-specs
py27 installed:
alabaster==0.7.10,Babel==2.5.1,certifi==2017.7.27.1,chardet==3.0.4,cssselect==1.0.1,docutils==0.14,extras==1.0.0,fixtures==3.0.0,idna==2.6,imagesize==0.7.1,Jinja2==2.9.6,linecache2==1.0.0,lxml==4.1.0,MarkupSafe==1.0,-e
git+https://git.openstack.org/openstack/nova-specs.git@a081ad1f0a6028d0fcb9f1a383fc96217f5c3ddf#egg=nova_specs,oslosphinx==4.17.0,pbr==3.1.1,pkg-resources==0.0.0,Pygments==2.2.0,pyquery==1.3.0,python-mimeparse==1.6.0,python-subunit==1.2.0,pytz==2017.2,requests==2.18.4,six==1.11.0,snowballstemmer==1.2.1,Sphinx==1.6.5,sphinxcontrib-websupport==1.0.1,testrepository==0.0.20,testtools==2.3.0,traceback2==1.4.0,typing==3.6.2,unittest2==1.1.0,urllib3==1.22,yasfb==0.6.1
py27 runtests: PYTHONHASHSEED='2547028128'
py27 runtests: commands[0] | find . -type f -name *.pyc -delete
py27 runtests: commands[1] | python setup.py testr --slowest --testr-args=
running testr
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_TEST_TIMEOUT=60
${PYTHON:-python} -m subunit.run discover -t ./ . --list
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_TEST_TIMEOUT=60
${PYTHON:-python} -m subunit.run discover -t ./ . --load-list /tmp/tmp5_llTX
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_TEST_TIMEOUT=60
${PYTHON:-python} -m subunit.run discover -t ./ . --load-list /tmp/tmpW704PS
==
FAIL: tests.test_titles.TestTitles.test_template
tags: worker-0
--
Traceback (most recent call last):
File "tests/test_titles.py", line 131, in test_template
self._check_titles(filename, template_titles, titles)
File "tests/test_titles.py", line 69, in _check_titles
% (filename, "\n ".join(msgs)))
File
"/tmp/nova-specs/.tox/py27/local/lib/python2.7/site-packages/unittest2/case.py",
line 690, in fail
raise self.failureException(msg)
AssertionError: While checking 'specs/backlog/approved/instance-tasks.rst':
Section 'Proposed change' is missing subsections: [u'Upgrade impact']
Ran 2 tests in 0.101s (-0.022s)
FAILED (id=1, failures=1)
error: testr failed (1)
ERROR: InvocationError: '/tmp/nova-specs/.tox/py27/bin/python setup.py testr
--slowest --testr-args='
summary
ERROR: py27: commands failed
stack@devstack-master:/tmp/nova-specs$ git log -1
commit a081ad1f0a6028d0fcb9f1a383fc96217f5c3ddf
Merge: 65dabe0 7af4f1f
Author: Zuul
Date: Wed Oct 25 23:23:50 2017 +
Merge "Spec for API extensions policy removal"
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1727602/+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 1732077] Re: Unreachable line need to be removed from stage() method of V2
Reviewed: https://review.openstack.org/519544 Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=db4a83f8bcc786dba9b1eb4e69af45c46b0a333c Submitter: Zuul Branch:master commit db4a83f8bcc786dba9b1eb4e69af45c46b0a333c Author: Pranali Deore Date: Tue Nov 14 11:31:02 2017 +0530 Removing unreachable line from stage() method In stage() method of v2 api, _restore() is called after raising HTTPConflict exception, which won't be reachable in any case after the exception is raised. _restore() changes the image_status from 'uploading' to 'queued' and data staging would start from the beginning after new stage call with same image-id even though staging data has already been loaded to store. Hence it seems there is no point in keeping that _restore() incase of Duplicate exception is raised. Change-Id: I317587bc1ba6544b722a11ae217a5d1212c96ce2 Closes-Bug: 1732077 ** Changed in: glance Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1732077 Title: Unreachable line need to be removed from stage() method of V2 Status in Glance: Fix Released Bug description: In stage() method of v2 api, _restore() is called after the raising Duplicate exception [1] which won't be reachable in any case after the exception is raised. _restore() changes the image_status from 'uploading' to 'queued' and data staging would start from the beginning after new stage call with same image-id even though staging data has already been loaded to store. Hence it seems there is no point in keeping that _restore() incase of Duplicate exception is raised. [1]: https://github.com/openstack/glance/blob/5d2ce20a9e31808d9e91dc5da4a124823f23ad09/glance/api/v2/image_data.py#L306 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1732077/+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 1732824] [NEW] Cannot run dsvm-functional in local centos 7 VM
Public bug reported: Steps to reproduce: 1. create centos 7 vm with CentOS-7-x86_64-DVD-1708.iso 2. do the neutron test docs [1] steps: - git clone https://git.openstack.org/openstack-dev/devstack ../devstack - ./tools/configure_for_func_testing.sh ../devstack -i - tox -e dsvm-functional 3. test failed 3.1 a lot of errors: "ImportError: No module named agent.linux.ip_lib" for instance: http://paste.openstack.org/show/626568/ 3.2 ovsdbapp: Connection refused for instance: http://paste.openstack.org/show/626569/ [1] https://docs.openstack.org/neutron/latest/contributor/testing/testing.html ** Affects: neutron Importance: Undecided Status: New ** Tags: functional-tests ** Tags added: functional-tests -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1732824 Title: Cannot run dsvm-functional in local centos 7 VM Status in neutron: New Bug description: Steps to reproduce: 1. create centos 7 vm with CentOS-7-x86_64-DVD-1708.iso 2. do the neutron test docs [1] steps: - git clone https://git.openstack.org/openstack-dev/devstack ../devstack - ./tools/configure_for_func_testing.sh ../devstack -i - tox -e dsvm-functional 3. test failed 3.1 a lot of errors: "ImportError: No module named agent.linux.ip_lib" for instance: http://paste.openstack.org/show/626568/ 3.2 ovsdbapp: Connection refused for instance: http://paste.openstack.org/show/626569/ [1] https://docs.openstack.org/neutron/latest/contributor/testing/testing.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1732824/+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 1732830] [NEW] Unreachable 'ImageSizeLimitExceeded' exception block in stage call
Public bug reported: ImageSizeLimitExceeded exception block [1] is unreachable in stage because we are using sotre_backend.add (filesystem.add in this case) and it will raise 'exceptions.StorageFull()' [2] if image file is too large (errno.EFBIG). [1] https://github.com/openstack/glance/blob/master/glance/api/v2/image_data.py#L323 [2] https://github.com/openstack/glance_store/blob/master/glance_store/_drivers/filesystem.py#L691 ** Affects: glance Importance: Undecided Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: glance Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1732830 Title: Unreachable 'ImageSizeLimitExceeded' exception block in stage call Status in Glance: New Bug description: ImageSizeLimitExceeded exception block [1] is unreachable in stage because we are using sotre_backend.add (filesystem.add in this case) and it will raise 'exceptions.StorageFull()' [2] if image file is too large (errno.EFBIG). [1] https://github.com/openstack/glance/blob/master/glance/api/v2/image_data.py#L323 [2] https://github.com/openstack/glance_store/blob/master/glance_store/_drivers/filesystem.py#L691 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1732830/+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 1727176] Re: HPE 3PAR : With single path FC configuration, multiple vluns were created, after volume attached
** Project changed: nova => cinder ** Changed in: cinder Assignee: (unassigned) => Vivek Soni (viveksoni) ** Changed in: cinder Status: New => 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/1727176 Title: HPE 3PAR : With single path FC configuration, multiple vluns were created, after volume attached Status in Cinder: Fix Released Status in os-brick: New Bug description: Description === HPE 3PAR : With single path FC configuration, multiple vluns were created, after volume attached Steps to reproduce == 1) use 3parfc backend and create volume 2) make sure nova.conf DO NOT have 'volume_use_multipath=True' in libvirt section (i.e. we should have single path configuration) 3) attach that volume to an instance Actual result = multiple vluns were created in 3par Expected === since its a single path configuration. only one vlun must be created. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1727176/+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 1732835] [NEW] Stage call fails with TypeError
Public bug reported: If store_backend denies writing to store then glance_store will raise 'StorageWriteDenied' error. After catching this exception at glance side, unstage call [1] will fail with TypeError as it requires 3 arguments and only two were provided. Actual call: self._unstage(image_repo, image) Expected call: self._unstage(image_repo, image, staging_store) [1] https://github.com/openstack/glance/blob/master/glance/api/v2/image_data.py#L335 ** Affects: glance Importance: Undecided Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: glance Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1732835 Title: Stage call fails with TypeError Status in Glance: New Bug description: If store_backend denies writing to store then glance_store will raise 'StorageWriteDenied' error. After catching this exception at glance side, unstage call [1] will fail with TypeError as it requires 3 arguments and only two were provided. Actual call: self._unstage(image_repo, image) Expected call: self._unstage(image_repo, image, staging_store) [1] https://github.com/openstack/glance/blob/master/glance/api/v2/image_data.py#L335 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1732835/+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 1732837] [NEW] weather applet crashes on logout
You have been subscribed to a public bug: weather applet crashes on logout ** Affects: glance Importance: Undecided Status: New -- weather applet crashes on logout https://bugs.launchpad.net/bugs/1732837 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. -- 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 1732837] [NEW] weather applet crashes on logout
Public bug reported: weather applet crashes on logout ** Affects: glance Importance: Undecided Status: New ** Project changed: fuel-plugin-contrail => glance -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1732837 Title: weather applet crashes on logout Status in Glance: New Bug description: weather applet crashes on logout To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1732837/+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 1732841] [NEW] The name of a deleted image should not be shown as a link
Public bug reported: Steps to reproduce with the master branch: 1. Create an image 2. Click the create volume action of this image 3. Delete the image 3. Go to the volume details panel of this newly created volume The image field in the volume source section is shown as a link. If the user clicks on the link, he will get a 404 error. This image name should be shown as plain text, not a link. ** Affects: horizon Importance: Low Status: New ** Tags: low-hanging-fruit ** Changed in: horizon Importance: Undecided => Low ** Tags added: low-hanging-fruit ** Changed in: horizon Milestone: None => next -- 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/1732841 Title: The name of a deleted image should not be shown as a link Status in OpenStack Dashboard (Horizon): New Bug description: Steps to reproduce with the master branch: 1. Create an image 2. Click the create volume action of this image 3. Delete the image 3. Go to the volume details panel of this newly created volume The image field in the volume source section is shown as a link. If the user clicks on the link, he will get a 404 error. This image name should be shown as plain text, not a link. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1732841/+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 1732852] [NEW] neutron don't support Router gateway rate limit
Public bug reported: Refer to this patch(Apply QoS policy on network:router_gateway :https://review.openstack.org/#/c/425218/),I apply qos policy to router gateway port. Execution command： ovs-vsctl list interface qg- I find that the ingress rate limit of qg port has been configured successfully,but I found this rate limit didn't work by using iperf test.By view the openvswitch log,i find error: --- 2017-11-16T01:22:55.598Z|00115|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on qg-d0c7278b-d2 device failed: No such device 2017-11-16T01:22:55.604Z|00116|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on qg-d0c7278b-d2 device failed: No such device 2017-11-16T01:22:55.604Z|00117|netdev_linux|WARN|qg-d0c7278b-d2: removing policing failed: No such device -- I think openvswitch don't support police rate of namespace qg port, so neutron don't support Router gateway rate limit. ** 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/1732852 Title: neutron don't support Router gateway rate limit Status in neutron: New Bug description: Refer to this patch(Apply QoS policy on network:router_gateway :https://review.openstack.org/#/c/425218/),I apply qos policy to router gateway port. Execution command： ovs-vsctl list interface qg- I find that the ingress rate limit of qg port has been configured successfully,but I found this rate limit didn't work by using iperf test.By view the openvswitch log,i find error: --- 2017-11-16T01:22:55.598Z|00115|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on qg-d0c7278b-d2 device failed: No such device 2017-11-16T01:22:55.604Z|00116|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on qg-d0c7278b-d2 device failed: No such device 2017-11-16T01:22:55.604Z|00117|netdev_linux|WARN|qg-d0c7278b-d2: removing policing failed: No such device -- I think openvswitch don't support police rate of namespace qg port, so neutron don't support Router gateway rate limit. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1732852/+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 1732603] Re: neutron-dynamic-routing CI failure
Reviewed: https://review.openstack.org/520355 Committed: https://git.openstack.org/cgit/openstack/neutron-dynamic-routing/commit/?id=39699184d83962f17bb1935aecd68bb0711c15e4 Submitter: Zuul Branch:master commit 39699184d83962f17bb1935aecd68bb0711c15e4 Author: Nguyen Phuong An Date: Thu Nov 16 16:31:23 2017 +0700 Use agent OVO for bgp_dragent_scheduler Neutron agent scheduler has been switched to use Agent OVO[1]. So this patch uses agent OVO for bgp_dragent_scheduler. [1] https://review.openstack.org/#/c/495810 Change-Id: I7e5da95ab3c28c00f3be9eca2c92a772492cfa69 Closes-Bug: #1732603 ** 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/1732603 Title: neutron-dynamic-routing CI failure Status in neutron: Fix Released Bug description: http://logs.openstack.org/23/519123/17/check/legacy-neutron-dynamic- routing-dsvm-tempest-scenario- ipv4/1b02d4a/logs/screen-q-svc.txt.gz#_Nov_15_18_59_37_488143 Nov 15 18:59:37.488143 ubuntu-xenial-ovh-gra1-897328 neutron- server[20475]: ERROR neutron_lib.callbacks.manager [None req- cb907c11-9482-400e-86a5-32305cca147c tempest- BgpSpeakerIpv4Test-1058299739 tempest-BgpSpeakerIpv4Test-1058299739] Error during notification for neutron_dynamic_routing.services.bgp.scheduler.bgp_dragent_scheduler.ChanceScheduler.schedule_bgp_speaker_callback --9223372036854723935 bgp_speaker, after_create: TypeError: update() takes exactly 2 arguments (1 given) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1732603/+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
