[Yahoo-eng-team] [Bug 1585859] [NEW] SRIOV port cann't get the IP which is allocated by dhcp agent on the same node

Public bug reported: I create a VM with a sriov port. Nova services and neutron services are on the same physical node. I find that the nic in VM can't auto get IP address. The neutron dhcp-agent service is active and I can see the network namespace which the siov port belongs to by command "ip

[Yahoo-eng-team] [Bug 1585860] [NEW] SRIOV port cann't get the IP which is allocated by dhcp agent on the same node

Public bug reported: I create a VM with a sriov port. Nova services and neutron services are on the same physical node. I find that the nic in VM can't auto get IP address. The neutron dhcp-agent service is active and I can see the network namespace which the sriov port belongs to by command "ip

[Yahoo-eng-team] [Bug 1584737] Re: Incorrect objects comparison in unit test

Reviewed: https://review.openstack.org/320220 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b1973fc300b2cb2d476cd9b63184368e44a8fba9 Submitter: Jenkins Branch:master commit b1973fc300b2cb2d476cd9b63184368e44a8fba9 Author: Takashi NATSUME

[Yahoo-eng-team] [Bug 1585831] [NEW] Horizon dashboard leaks internal information through cookies

Public bug reported: When horizon is configured where: 1) internalURL and publicURL are on different networks 2) horizon uses the internalURL endpoint for authentication The cookie "login_region" will be set to the value configured as OPENSTACK_KEYSTONE_URL. This URL contains the IP address of

[Yahoo-eng-team] [Bug 1585826] [NEW] nova hypervisor-show/stats reports incorrect values

Public bug reported: When looking at hypervisor resources through either nova hypervisor- stats or nova hypervisor-show with compute nodes of differing sizes, I am getting incorrect/inconsistent values back for one of the hypervisors. For example, in an environment with one 32 GB compute node

[Yahoo-eng-team] [Bug 1585816] [NEW] qos-bandwidth-limit-rule-create failed with internal server error

Public bug reported: When using following command to create a bandwidth rule: # neutron qos-bandwidth-limit-rule-create --max-kbps 1000 --max-burst-kbps 100 test-policy error returned: Request Failed: internal server error while processing your request. in /var/log/neutron/server.log, error

[Yahoo-eng-team] [Bug 1580440] Re: neutron purge - executing command on non existing tenant print wrong command

@John - Done. Thank you! ** Also affects: openstack-manuals Importance: Undecided Status: New ** Changed in: openstack-manuals Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron.

[Yahoo-eng-team] [Bug 1576000] Re: Deprecate advertise_mtu option

Reviewed: https://review.openstack.org/310448 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4955746bbff317d5976a1130d695b928561afc00 Submitter: Jenkins Branch:master commit 4955746bbff317d5976a1130d695b928561afc00 Author: Ihar Hrachyshka Date:

[Yahoo-eng-team] [Bug 1585789] [NEW] Deprecate advertise_mtu option

Public bug reported: https://review.openstack.org/310448 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option

[Yahoo-eng-team] [Bug 1585770] [NEW] [RFE] DVR-aware fixed IP announcements for with BGP

Public bug reported: Enable BGP to announce the next-hop for fixed IP host route when using DVR. The next-hop when using DVR is the IP address of the FIP agent gateway. This would allow an operator to toggle whether to enable announcement of host routes for each fixed IP or just rely on the

[Yahoo-eng-team] [Bug 1585761] [NEW] failed to boot instance from image without cinder volume

Public bug reported: using master horizon it is currently not possible to boot and instance form a glance image without allocating a cinder volume. this prevent horizon from booting an instance if cinder is not deployed. to reproduce on the launch instance screen go to the source tab and select

[Yahoo-eng-team] [Bug 1585738] [NEW] ML2 doesn't return fixed_ips on a port update with binding

Public bug reported: I found this yesterday while working on deferred IP allocation for routed networks. However, it isn't unique to deferred port binding. With my deferred IP allocation patch [2], I need to be able to make a port create call [1] without binding information that doesn't allocate

[Yahoo-eng-team] [Bug 1585706] [NEW] neutron-lbaas test failure webob.exc.HTTPClientError: Unexpected error code: 400

Public bug reported: I have several tests failing similar to the following ever since commit b0b6a0aa8566bae552f6a7607cf254ee0cbc76ae. If I revert that commit (e.g. s/n_constants.ATTR_NOT_SPECIFIED/attributes.ATTR_NOT_SPECIFIED) then this error goes away.

[Yahoo-eng-team] [Bug 1585699] [NEW] Neutron Metadata Agent Configuration - nova_metadata_ip

Public bug reported: I am not sure if this constitutes the tag 'bug'. However it has lead us to some confusion and I feel it should be updated. This option in neutron metadata configuration (and install docs) is misleading. {{{ # IP address used by Nova metadata server. (string value)

[Yahoo-eng-team] [Bug 1190149] Re: Token auth fails when token is larger than 8k

** No longer affects: heat/havana -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1190149 Title: Token auth fails when token is larger than 8k Status in Cinder: Fix Released Status in

[Yahoo-eng-team] [Bug 1340596] Re: Tests fail due to novaclient 2.18 update

** No longer affects: heat/havana -- 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/1340596 Title: Tests fail due to novaclient 2.18 update Status in heat: Invalid

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

** No longer affects: cloud-init ** Changed in: maas Status: Triaged => In Progress ** Changed in: maas Importance: High => Critical ** Changed in: maas Assignee: (unassigned) => Blake Rouse (blake-rouse) ** Changed in: maas Milestone: None => 2.0.0 -- You received this

[Yahoo-eng-team] [Bug 1339273] Re: Sphinx documentation build failed in stable/havana: source_dir is not a directory

** Changed in: heat/havana Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1339273 Title: Sphinx documentation build failed in stable/havana: source_dir is

[Yahoo-eng-team] [Bug 1503501] Re: oslo.db no longer requires testresources and testscenarios packages

** Changed in: heat/liberty 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/1503501 Title: oslo.db no longer requires testresources and

[Yahoo-eng-team] [Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

It was recommended by smoser to add this to MAAS: http://paste.ubuntu.com/16683033/ But then it was discovered that will not handle all cases. A kernel parameter would be needed to force only one datasource. ** Also affects: cloud-init Importance: Undecided Status: New ** Changed in:

[Yahoo-eng-team] [Bug 1585682] [NEW] Horizon gating on dsvm-integration job is broken due to recent changes in devstack/keystone

Public bug reported: More importantly, Horizon in devstack is broken too due to the inability to get list of projects / switch the current project for a user, see DEBUG:keystoneauth.session:Request returned failure status: 404 Unable to retrieve project list. Traceback (most recent call last):

[Yahoo-eng-team] [Bug 1568197] Re: Problems with neutron.common.constants import break HA and DVRHA functionality

** 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/1568197 Title: Problems with neutron.common.constants import break HA

[Yahoo-eng-team] [Bug 1585680] [NEW] neutron-lbaas doesn't have tempest plugin

Public bug reported: Puppet OpenStack CI is interested to run neutron-lbaas Tempest tests but it's currently not working because neutron-lbaas is missing a Tempest plugin and its entry-point, so discovery of tests does not work. Right now, to run tempest we need to go in the neutron-lbaas

[Yahoo-eng-team] [Bug 1580440] Re: neutron purge - executing command on non existing tenant print wrong command

I've posted a patch to improve the documentation here: https://review.openstack.org/#/c/321012 Please review and let me know if those changes help to clarify the expected behavior. @Assaf Could you expand on your thoughts about shared resources? Perhaps on the doc review. Thanks ** Changed in:

[Yahoo-eng-team] [Bug 1585652] [NEW] EmptyCatalog not treated during cinderclient creation

Public bug reported: Steps to reproduce == 1 - Get a keystone v3 token using the ?nocatalog param. Example: export TOKEN=`curl -i -k -v -H "Content-type: application/json" -d '{"auth": {"identity": {"methods": ["password"], "password": {"user": {"domain": {"name": "Default"},

[Yahoo-eng-team] [Bug 1585632] [NEW] test_revoke_by_audit_chain_id_chained_token() fails

Public bug reported: This test started failing in Ubuntu package builds as of commit 79952ffbd4c1ffd2dab32c04581b3a7f71a05e28. == Failed 1 tests - output below: ==

[Yahoo-eng-team] [Bug 1585623] [NEW] A vm's port is in down state after compute node reboot

Public bug reported: After compute node reboot some ports may end up in DOWN state and corresponding VMs lose net access. ** Affects: neutron Importance: High Assignee: Oleg Bondarev (obondarev) Status: Confirmed ** Tags: mitaka-backport-potential ovs -- You received this

[Yahoo-eng-team] [Bug 1585494] Re: instances recovered

** Project changed: devstack => nova -- 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/1585494 Title: instances recovered Status in OpenStack Compute (nova): In

[Yahoo-eng-team] [Bug 1585608] [NEW] theme switcher broken

Public bug reported: while adding a new theme via local_settings.d, all themes from theme switcher get removed. ** Affects: horizon 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 1585494] [NEW] instances recovered

You have been subscribed to a public bug: Nova currently does not rebuild instances if they were removed from the disk. The instances should be recovered (after we restart the OpenStack) if the compute host is replaced or the disk is erased so that a board replacement can be performed in case

[Yahoo-eng-team] [Bug 1585606] [NEW] theming via local_settings.d broken

Public bug reported: while adding a theme via settings.py works, the same theme does NOT work, when added via local_settings.d Compressing... CommandError: An error occurred during rendering /home/mrunge/work/jeff-theme/horizon/openstack_dashboard/templates/_stylesheets.html: Couldn't find

[Yahoo-eng-team] [Bug 1585601] [NEW] Deleting a live-migrated instance causes its fixed IP to remain reserved

Public bug reported: When using nova-network, an attempt to boot an instance with the fixed IP of an instance that has been live-migrated and then deleted will fail with 'Fixed IP address is already in use on instance.' To reproduce: 1. Boot an instance 2. Live-migrate it 3. Delete it 4. Boot a

[Yahoo-eng-team] [Bug 1585515] Re: Paramiko doesn't work with Nova

Paramiko 2.0 got released 26 days ago with [1]. Nova put a workaround in place to work with paramiko 2.x 21 days ago [2]. After that, we bumped the version in the global requirements to 2.0 [3]. I tested it locally with commit 9d99081 (Newton master) and it works for me. I also didn't find the

[Yahoo-eng-team] [Bug 1585584] [NEW] [Glare] Glare v0.1 is unable to create a public artifact draft

Public bug reported: Due to some reason the visibility field gets excluded from the valid input when creating an artifact draft. Thus it is impossible to create a public artifact in a single call: a PATCH call should follow instead. ** Affects: glance Importance: Undecided Status:

[Yahoo-eng-team] [Bug 1558683] Re: Versions endpoint does not support X-Forwarded-Proto

Reviewed: https://review.openstack.org/305152 Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=d7e7e7bdf0f112c8315ae38f04b4849338173d51 Submitter: Jenkins Branch:master commit d7e7e7bdf0f112c8315ae38f04b4849338173d51 Author: yuriy_n Date: Mon

[Yahoo-eng-team] [Bug 1585524] Re: neutron server Error: TooManyExternalNetworks

According to [1], this should be invalid. I have verified that config as [1], no error will report. [1] https://github.com/openstack/neutron/blob/f60291820599804e8bfdaafa0cd0565549daa193/neutron/agent/l3/config.py#L64-L66 ** Changed in: neutron Assignee: (unassigned) => Hong Hui Xiao

[Yahoo-eng-team] [Bug 1585250] Re: Statuses not shown for non-"loadbalancer" LBaaS objects on CLI

** Project changed: python-neutronclient => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1585250 Title: Statuses not shown for non-"loadbalancer" LBaaS objects on CLI Status

[Yahoo-eng-team] [Bug 1585250] [NEW] Statuses not shown for non-"loadbalancer" LBaaS objects on CLI

You have been subscribed to a public bug: There is no indication on the CLI when creating an LBaaSv2 object (other than a "loadbalancer") has failed... stack@openstack:~$ neutron lbaas-listener-create --name MyListener1 --loadbalancer MyLB1 --protocol HTTP --protocol-port 80 Created a new

[Yahoo-eng-team] [Bug 1585538] [NEW] Creating LBaaS pool related to LB (not listener) does not reflect the new pool to provider's driver

Public bug reported: 1. Create LB 2. Create pool related to that LB (with --loadbalancer argument). 3. The LB object passed as an argument to the provider's driver handling does not include the new pool in LB'a pools parameter. The problem occurs because the context is not refreshed for the

[Yahoo-eng-team] [Bug 1585537] [NEW] Healthmonitor is not deleted from DB when its pool is deleted

Public bug reported: When LBaaS pool having a health monitor is deleted, its health monitor remains in DB. Recreate: 1. Create LB, Listener, Pool with HM. 2. Delete Pool 3. See HM is still in lbaas_healthmonitors table in DB ** Affects: neutron Importance: Undecided Assignee: Evgeny

[Yahoo-eng-team] [Bug 1585524] [NEW] neutron server Error: TooManyExternalNetworks

Public bug reported: Main steps: 1 create 2 external networks each with a different subnet with neutron CLI commands, there is no error info from CLI. e.g. neutron net-create --router:external=True --provider:physical_network provider100 --provider:network_type flat provider100 2 create 2

[Yahoo-eng-team] [Bug 1183523] Re: db-archiving fails to clear some deleted rows from instances table

As we use the "direct-release" model in Nova we don't use the "Fix Comitted" status for merged bug fixes anymore. I'm setting this manually to "Fix Released" to be consistent. [1] "[openstack-dev] [release][all] bugs will now close automatically when patches merge"; Doug Hellmann; 2015-12-07;

[Yahoo-eng-team] [Bug 1582278] Re: [SR-IOV][CPU Pinning] nova compute can try to boot VM with CPUs from one NUMA node and PCI device from another NUMA node.

As we use the "direct-release" model in Nova we don't use the "Fix Comitted" status for merged bug fixes anymore. I'm setting this manually to "Fix Released" to be consistent. [1] "[openstack-dev] [release][all] bugs will now close automatically when patches merge"; Doug Hellmann; 2015-12-07;

[Yahoo-eng-team] [Bug 1575335] Re: Out-of-tree compute drivers no longer loading

As we use the "direct-release" model in Nova we don't use the "Fix Comitted" status for merged bug fixes anymore. I'm setting this manually to "Fix Released" to be consistent. [1] "[openstack-dev] [release][all] bugs will now close automatically when patches merge"; Doug Hellmann; 2015-12-07;

[Yahoo-eng-team] [Bug 1585520] [NEW] Only some specific router or ovs ports which SRI-OV port need to reach but now can not on the same compute

Public bug reported: In some cases, we need to implement that the SRI-OV ports can reach some specific ovs ports but not all the ovs ports on the same compute node or the SRI-OV ports can reach the specific router internal ports, don't need to add all the router ports mac into fdb tables on the

[Yahoo-eng-team] [Bug 1585515] [NEW] Paramiko doesn't work with Nova

Public bug reported: It looks like Paramiko 2.0.0 again breaks nova which currently has a requirement for 'paramiko>=1.16.0 # LGPL'. nova.tests.unit.api.openstack.compute.test_keypairs.KeypairsTestV210.test_keypair_create_duplicate

[Yahoo-eng-team] [Bug 1585510] [NEW] [RFE] openvswitch-agent support rootwrap daemon when hypervisor is XenServer

Public bug reported: As titled, when XenServer is hypervisor we want to implement rootwrap daemon mode in neutron-openvswitch-agent which runs in compute node. neutron-openvswitch-agent which runs in compute node(DomU) cannot support rootwrap daemon mode. This is because XenServer has the

[Yahoo-eng-team] [Bug 1584333] Re: BGP code still exist in neutron repo

Reviewed: https://review.openstack.org/319562 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=12200922a923befe47e7edcbdd1683c3486a8b92 Submitter: Jenkins Branch:master commit 12200922a923befe47e7edcbdd1683c3486a8b92 Author: Na Date: Sat May 21