[Yahoo-eng-team] [Bug 1600226] [NEW] neutron-lib/api-ref: Create network missing the Request parameters

user can specify another tenant UUID, which is the tenant who owns the network, in the request body. Error response codes:201,401,400, Request --- <<<<<< Danny Choi (dannchoi) ** Changed in: neutron Status: New => In Progress -- You received this bug not

[Yahoo-eng-team] [Bug 1483853] [NEW] [Juno]: Cannot set the VXLAN UDP destination port to 4789 using Linux Bridge

Public bug reported: I'm running stable/Juno with VXLAN and Linux Bridge. Linux default VxLAN UDP port is 8472. IANA assigned port is 4789. I tried to add the following in /etc/neutron/plugins/ml2/ml2_conf.ini file, but it still use port 8472 afterwards. [agent] vxlan_udp_port=4789

[Yahoo-eng-team] [Bug 1472347] Re: With multiple Neutron api/rpc workers enabled, intermittent failure deleting dhcp_port

I was running a private RPM for cisco-networking neutron. I could not reproduce the problem with stable/juno nor stable/kilo. ** Changed in: neutron Status: Incomplete = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is

[Yahoo-eng-team] [Bug 1472347] [NEW] With multiple Neutron api/rpc workers enabled, intermittent failure deleting dhcp_port

Public bug reported: Neutron multiple workers are enabled as follows in neutron.conf: - api_workers=3 - rpc_workers=3 The following were configured: - 20 tenants - Each tenant had 5 tenant networks - For each network, one VM at each Compute nodes (2) for a total of 10 VMs -

[Yahoo-eng-team] [Bug 1432373] [NEW] Horizon: port create missing options

Public bug reported: nova-manage version: 2015.1 In Horizon, port create is missing options compared to CLI: --tenant-id --mac-address --fixed-ip --security-group --no-security-groups --extra-dhcp-opt

[Yahoo-eng-team] [Bug 1432393] [NEW] Neutron: port-create missing help info for the option: --binding

Public bug reported: nova-manage version: 2015.1 Issue: Neutron port-create missing help info for the option: --binding:vnic-type Valid inputs are 'normal', 'direct' and 'macvtap'. ubuntu@trusty1:~/devstack$ neutron port-create --name sriov-mactap --binding:vnic-type=mactap private Invalid

[Yahoo-eng-team] [Bug 1425294] [NEW] security-group is not applied correctly when port-id is used for the --nic option in nova boot

Public bug reported: When port-id is used for the --nic option in nove boot command, the user defined security-group is not applied. E.g. user defined security-group is my-secgroup. It is specified with the --security-groups option in nova boot. However, if port-id is used for the --nic

[Yahoo-eng-team] [Bug 1423747] [NEW] neutron port-create error message is not helpful

Public bug reported: nova-manage version: 2015.1 Issue: Error message for neutron port-create failure is not helpful. ubuntu@trusty1:~/devstack$ neutron help port-create usage: neutron port-create [-h] [-f {html,json,shell,table,value,yaml}] [-c COLUMN] [--max-width

[Yahoo-eng-team] [Bug 1414450] [NEW] nova reset-state server does not work using server name.

Public bug reported: According to the help description, either the name or ID of the server can be used in nova reset-state server. Using the server name actually fails. localadmin@qa4:~/devstack$ nova help reset-state usage: nova reset-state [--active] server [server ...] Reset the state of a

[Yahoo-eng-team] [Bug 1414164] [NEW] Horizon: incorrect error message when VM deletion failed

Public bug reported: nova-manage version: 2014.2.2 Issue: incorrect error message when VM delete failed. It should be delete, not launch. e.g. ERROR: Failed to launch instance XYZ. Please try again later. [Error: delete_port_precommit failed.]. ** Affects: horizon Importance: Undecided

[Yahoo-eng-team] [Bug 1406656] [NEW] Horizon: Edit Network option disappeared when shared=true

Public bug reported: nova-manage version: 2014.2.2 Issue: Edit Network option disappeared after setting shared=true via CLI. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is

[Yahoo-eng-team] [Bug 1406657] [NEW] Horizon: Edit Network missing options

Public bug reported: nova-manage version: 2014.2.2 Issue: Horizon Edit Network missing the following options --router:external --shared --tenant_id ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo!

[Yahoo-eng-team] [Bug 1381568] Re: Cannot start the VM console when VM is launched at Compute node

Missing config settings in localrc at the Compute node. Able to start the VM VNC console after adding the following lines in localrc: NOVA_VNC_ENABLED=True NOVNCPROXY_URL=http://172.29.172.161:6080/vnc_auto.html; # 172.29.172.161 is the Controller IP address VNCSERVER_LISTEN=$HOST_IP

[Yahoo-eng-team] [Bug 1399454] Re: Nexus VXLAN gateway: 4K VLANs limitation

This bug is able using Cisco Nexus switch VXLAN functionality to extend the VLAN limits beyond 4K. ** Changed in: neutron Status: Invalid = New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron.

[Yahoo-eng-team] [Bug 1399998] [NEW] Cisco Nexus VXLAN: incomplete switch configuration when launch multiple VMs simultaneously.

Public bug reported: Cisco Nexus VXLAN setup: Compute-1 and Compute-2 connect to N9K-1, Compute-3 and Controller+Network node connect to N9K-2. Issue: when launch multiple VMs simultaneously, the Nexus switch is not configured properly. Sometimes missing the VLAN, or the VNI mapping. It

[Yahoo-eng-team] [Bug 1399453] [NEW] Nexus VXLAN gateway: VM with 2 interfaces to the same subnet delete issues

Public bug reported: With Nexus VXLAN gateway, there are delete issues with the last VM that has 2 interfaces to the same subnet. 1. When one interface is deleted, all the VLAN/VNI mapping configurations are deleted at the Nexus switch. 2. When the last interface or the VM is deleted, traceback

[Yahoo-eng-team] [Bug 1399454] [NEW] Nexus VXLAN gateway: 4K VLANs limitation

Public bug reported: With the Nexus VXLAN gateway, each Compute host still has the 4K VLANs limitation. ** 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.

[Yahoo-eng-team] [Bug 1395207] [NEW] glance create-image returned error message contains html keys.

Public bug reported: OpenStack version: Juno localadmin@qa4:~/devstack$ nova-manage version 2014.2.1 Issue: when glance create-image operation fails, the returned error message contains html keys. localadmin@qa4:~/devstack$ glance image-create --name stcva_4.46 --is-public true --disk-format

[Yahoo-eng-team] [Bug 1381568] [NEW] Cannot start the VM console when VM is launched at Compute node

Public bug reported: OpenStack version: Juno localadmin@qa4:/etc/nova$ nova-manage version 2015.1 I used devstack to deploy multi-node OpenStack, with Controller + nova-compute + Network on one physical node (qa4), and Compute on a separate physical node (qa5). When I launch a VM which spun

[Yahoo-eng-team] [Bug 1381285] [NEW] Nexus driver keeps trying to configure VLAN at the switch

Public bug reported: OpenStack version: Juno Issue: Nexus driver keeps trying to configure VLAN at the switch after update_port_postcommit failed due to ssh connection issue Description: I used devstack to deploy Multi-Node OpenStack with Cisco Nexus ML2 plugin for VLAN network type. There’s

[Yahoo-eng-team] [Bug 1377687] [NEW] Typo in CLI error message: seting

Public bug reported: OpenStack version: Juno localadmin@qa4:~/devstack$ nova-manage version 2015.1 Issue: typo in CLI error message; setting should be setting localadmin@qa4:~/devstack$ ip netns exec qrouter-7b422c9d-c5f9-4bb5-b1b3-159954c72323 ip addr list seting TYPO the network

[Yahoo-eng-team] [Bug 1368789] [NEW] Fail to resize VM; No valid host was found

Public bug reported: OpenStack version: Icehouse Issue: fail to resize VM Setup: 3 nodes, namely Controller, Compute and Network; with nova- compute running solely on Compute node. Steps to reproduce: 1. Create an instance using image cirrus 0.3.2. 2. Verify instance is running: nova list

[Yahoo-eng-team] [Bug 1368378] [NEW] Cannot run nova shelve-offload command

Public bug reported: OpenStack version: Icehouse Setup: 3-node, namely Controller, Compute and Network Issue: cannot run nova shelve-offload server command Steps to reproduce: 1. Create an instance. 2. Verify instance is running/active: nova list 3. Run command: nova shelve server 4. Verify

[Yahoo-eng-team] [Bug 1367845] [NEW] Traceback is logged when delete an instance.

Public bug reported: OpenStack version: Icehouse Issue: traceback is logged in nova-compute.log when delete an instance. Setup: 3 nodes, namely Controller, Compute and Network; with nova- compute running solely on Compute node. Steps to reproduce: 1. Create an instance using image cirrus

[Yahoo-eng-team] [Bug 1366059] [NEW] Missing some entries in Default Quotas display compared to CLI output

Public bug reported: OpenStack version: Icehouse Issue: Missing some entries in Default Quotas display compared to CLI output, namely: floating_ips, fixed_ips, security_groups and security_group_rules Steps to reproduce: 1. Log in Horizon Dashboard as admin. 2. Navigate Admin - System Panel -

[Yahoo-eng-team] [Bug 1366145] [NEW] nova quota-show --tenant tenant-id | --user user-id does not check valid id

Public bug reported: OpenStack version: icehouse Issue: nova quota-show --tenant tenant-id | --user user-id does not check for valid id. User can enter a bogus value and the show command still successfully executed. Steps to reproduce: 1. Run the command with a bogus id for tenant-id or

[Yahoo-eng-team] [Bug 1364588] [NEW] Server in ERROR state after running nova resize-revert command.

Public bug reported: OpenStack version: Icehouse root@all-in-one:~# dpkg -l | grep nova-common ii nova-common 10:2014.1-43-cisco1 all OpenStack Compute - common files Issue: server in ERROR state after running the nova resize-revert command.