[Yahoo-eng-team] [Bug 1665548] [NEW] nova fail to evacuate as wrong onSharedStorarge parameter

Public bug reported: Nova API removed onSharedStorage parameter after v2.14, but we still have many users use API under v2.14. And we found that nova 100% fail to evacuate a server via novaclient, the error log as follows: 2017-02-16 20:22:48.106 6144 ERROR oslo_messaging.rpc.dispatcher

[Yahoo-eng-team] [Bug 1665539] [NEW] Jasmine unit tests view broken by profiler

Public bug reported: The new profiler dashboard defines an angular constant in the _scripts.html page; this is not reflected in the jasmine.html page, which causes injection to fail during testing when run through the /jasmine URL. ** Affects: horizon Importance: High Status:

[Yahoo-eng-team] [Bug 1658877] Re: live migration failed with XenServer as hypervisor

** Also affects: nova/ocata Importance: Undecided Status: New ** Changed in: nova/ocata Status: New => Fix Released ** Changed in: nova/ocata Importance: Undecided => High ** Changed in: nova/ocata Assignee: (unassigned) => Matt Riedemann (mriedem) ** Tags removed:

[Yahoo-eng-team] [Bug 1662626] Re: live-migrate left in migrating as domain not found

** Also affects: nova/ocata Importance: Undecided Status: New ** Tags removed: ocata-rc-potential ** Tags added: ocata-backport-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova).

[Yahoo-eng-team] [Bug 1567181] Re: Request release for networking-fujitsu for stable/mitaka

** Changed in: networking-fujitsu Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1567181 Title: Request release for networking-fujitsu for stable/mitaka

[Yahoo-eng-team] [Bug 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR

Reviewed: https://review.openstack.org/385881 Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=155f6c9456d4a0c878bc1209cf91fadc3899a211 Submitter: Jenkins Branch:master commit 155f6c9456d4a0c878bc1209cf91fadc3899a211 Author: pawnesh.kumar

[Yahoo-eng-team] [Bug 1617282] Re: functional gate failed with git clone timeout on fetching ovs from github

The ovs fix we need for functional job stability: https://mail.openvswitch.org/pipermail/ovs-git/2016-March/017804.html ** Also affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team,

[Yahoo-eng-team] [Bug 1665487] Re: Live migration tests sometimes timeout waiting for instance to be ACTIVE: "KVM: entry failed, hardware error 0x0"

The fix is here: https://review.openstack.org/#/c/435154/ ** Also affects: openstack-gate Importance: Undecided Status: New ** Changed in: openstack-gate Status: New => In Progress ** Changed in: openstack-gate Assignee: (unassigned) => Matt Riedemann (mriedem) ** Changed

[Yahoo-eng-team] [Bug 1665487] [NEW] Live migration tests sometimes timeout waiting for instance to be ACTIVE: "KVM: entry failed, hardware error 0x0"

Public bug reported: I've seen this a few times, but start tracking from here: http://logs.openstack.org/50/435050/1/check/gate-tempest-dsvm-multinode- live-migration-ubuntu- xenial/49adcde/console.html#_2017-02-16_22_25_43_645525 2017-02-16 22:25:43.645525 | 2017-02-16 22:25:43.645 |

[Yahoo-eng-team] [Bug 1663163] Re: Improper prompt when update existed resource class

Reviewed: https://review.openstack.org/431392 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ff1133c8ba649d6bfe2af6abc68bf42ebb68831e Submitter: Jenkins Branch:master commit ff1133c8ba649d6bfe2af6abc68bf42ebb68831e Author: ericxiett Date: Thu Feb

[Yahoo-eng-team] [Bug 1664509] Re: api-ref: POST /servers does not note that bdm:device_name is ignored by libvirt driver

Reviewed: https://review.openstack.org/433575 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=748639822093ef71090a3e3c277c60f3d770ded7 Submitter: Jenkins Branch:master commit 748639822093ef71090a3e3c277c60f3d770ded7 Author: Balazs Gibizer

[Yahoo-eng-team] [Bug 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR

** Also affects: glance Importance: Undecided Status: New ** Changed in: glance Importance: Undecided => Low ** Changed in: glance Status: New => In Progress ** Changed in: glance Milestone: None => pike-1 -- You received this bug notification because you are a member

[Yahoo-eng-team] [Bug 1229445] Re: db type could not be determined

** Also affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1229445 Title: db type could not be determined Status

[Yahoo-eng-team] [Bug 1665441] [NEW] cloudinit/net/sysconfig.py does not parse network_data.json correctly

Public bug reported: In cloudinit/net/sysconfig.py, we see: elif len(iface_subnets) > 1: for i, iface_subnet in enumerate(iface_subnets, start=len(iface.children)): iface_sub_cfg = iface_cfg.copy()

[Yahoo-eng-team] [Bug 1658877] Re: live migration failed with XenServer as hypervisor

Reviewed: https://review.openstack.org/424428 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4cd32645fb26d39a900433c4c1dfecaac1767522 Submitter: Jenkins Branch:master commit 4cd32645fb26d39a900433c4c1dfecaac1767522 Author: Huan Xie Date: Sun Jan

[Yahoo-eng-team] [Bug 1665145] Re: enable defaults for 'nova-manage cell_v2 update-cell'

** Also affects: nova/ocata Importance: Undecided Status: New ** Changed in: nova/ocata Status: New => In Progress ** Changed in: nova/ocata Assignee: (unassigned) => Matt Riedemann (mriedem) ** Changed in: nova/ocata Importance: Undecided => High ** Changed in: nova

[Yahoo-eng-team] [Bug 1664913] Re: cell_v2 update_cell command don't allow default value

*** This bug is a duplicate of bug 1665145 *** https://bugs.launchpad.net/bugs/1665145 ** This bug has been marked a duplicate of bug 1665145 enable defaults for 'nova-manage cell_v2 update-cell' -- You received this bug notification because you are a member of Yahoo! Engineering Team,

[Yahoo-eng-team] [Bug 1665145] Re: enable defaults for 'nova-manage cell_v2 update-cell'

Reviewed: https://review.openstack.org/434533 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b276e8410c91c32b6ccb229104dd87b8167d Submitter: Jenkins Branch:master commit b276e8410c91c32b6ccb229104dd87b8167d Author: Corey Bryant Date:

[Yahoo-eng-team] [Bug 1661360] Re: tempest test fails with "Instance not found" error

** Changed in: tripleo Status: Fix Committed => 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/1661360 Title: tempest test fails with "Instance not

[Yahoo-eng-team] [Bug 1653517] Re: Move ovsdb nested transaction from trunk code to ovs_lib

Reviewed: https://review.openstack.org/416647 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=acfbd2d490700d616d8050f4ea6a4565bc72fc52 Submitter: Jenkins Branch:master commit acfbd2d490700d616d8050f4ea6a4565bc72fc52 Author: Jakub Libosvar Date:

[Yahoo-eng-team] [Bug 1665263] Re: instance.delete notification is missing for unscheduled instance

** Changed in: nova Status: New => Confirmed ** Changed in: nova Importance: Undecided => High ** Also affects: nova/ocata Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to

[Yahoo-eng-team] [Bug 1665370] [NEW] api db_sync fails on upgrade due to duplicate migration files

Public bug reported: I'm testing upgrades on TripleO, and hit this problem, discussion with owalsh indicates it may be a nova bug related to backport migration numbering: 14:44 < owalsh> shardy: it's a nova bug, 028 needs to be renamed to 021_build_requests_instance_mediumtext.py in ocata &

[Yahoo-eng-team] [Bug 1665366] [NEW] [RFE] Add --key-name option to 'nova rebuild'

Public bug reported: Currently there is no way to change key-name associated with instance. This has some justification as key may be downloaded only at build time and later changes will be ignored by instance. But this is not a case for rebuild command. If tenant want to rebuild instance, he

[Yahoo-eng-team] [Bug 1082248] Re: Use uuidutils instead of uuid.uuid4()

I don't see value in this for networking-calico. ** No longer affects: networking-calico -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1082248 Title: Use uuidutils instead of

[Yahoo-eng-team] [Bug 1662109] Re: tempest scenario test_qos fails intermittently

It seems we still suffer from this issue: http://logs.openstack.org/47/416647/5/check/gate-tempest-dsvm-neutron- dvr-multinode-scenario-ubuntu-xenial- nv/330522c/logs/testr_results.html.gz ** Changed in: neutron Status: Fix Released => Confirmed -- You received this bug notification

[Yahoo-eng-team] [Bug 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR

Reviewed: https://review.openstack.org/386513 Committed: https://git.openstack.org/cgit/openstack/swauth/commit/?id=6573269e379d65bbd68326124d193eca4e690b5e Submitter: Jenkins Branch:master commit 6573269e379d65bbd68326124d193eca4e690b5e Author: nizam

[Yahoo-eng-team] [Bug 1665330] [NEW] Fwaas(reduce the associated floatingip count to zero):the firewall rules which in the qrouter namespace will not be cleaned, after delete the firewall.

Public bug reported: environment: Mitaka In the DVR mode: 1.create the router, network, vm, firewall 2.bind the firewall to the router, after associate the floatingip to the wm 3.disassociate the floatingip 4.delete the firewall The firewall rules still in the qrouter namespace. ** Affects:

[Yahoo-eng-team] [Bug 1665326] [NEW] Fwaas:it will execute firewall rules twice for a router, when update the firewall.

Public bug reported: environment: Mitaka It will execute firewall rules twice for a router, when update the firewall. The code is in the agent update_firewall(): ... router_ids = self._get_router_ids_for_fw(context, firewall) if router_ids or firewall['router_ids']: router_info_list =

[Yahoo-eng-team] [Bug 1665323] [NEW] Fwaas:When update the firewall name, the neutron-l3-agent will be called to reload the firewall rules.

Public bug reported: environment: Mitaka Update the firewall name, the neutron-l3-agent will be called to reload the firewall rules. When update the firewall name, it should be only updated the DB. ** Affects: neutron Importance: Undecided Assignee: wujun (wujun) Status: New

[Yahoo-eng-team] [Bug 1665318] [NEW] Fwaas(bind a firewall to a legacy router that without qrouter namespace):iptables rules do not tabke effect after the qrouter namespace created.

Public bug reported: environment: Mitaka 1.create a legacy router (do not add interface and set gateway), so there is no qrouter namespace 2.bind a firewall to the router 3.add interface or set gateway for the router, qrouter namespace is created now The problem is there no firewall rule in

[Yahoo-eng-team] [Bug 1665300] [NEW] [FWaaS v2] Unused attribut 'firewall_policy_id' on rule resource

Public bug reported: In the FWaaS v2 API extension, an attribut named 'firewall_policy_id' was declared on the 'rule' resource [1] but it not set or used anywhere in the code. Probably a copy/paste from v1 API. [1] https://github.com/openstack/neutron-

[Yahoo-eng-team] [Bug 1665282] [NEW] To prioritize port QoS policies over network QoS policies

Public bug reported: Two type of QoS policies can apply to a port: - Port QoS policies: set directly on the port. - Network QoS policies: those ones applied on the port's network. If both are applied, port QoS policy must prevail over the network QoS policy (if both are different) [1]. To know

[Yahoo-eng-team] [Bug 1665263] [NEW] instance.delete notification is missing for unscheduled instance

Public bug reported: Description === It seems that the Move instance creation to conductor commit [1] changed when and how the instance.delete notification is emitted for an unscheduled instance. Unfortunately the legacy notification doesn't have test coverage and the versioned