[Yahoo-eng-team] [Bug 1663570] Re: Remove usage of config option verbose
** Changed in: cinder 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/1663570 Title: Remove usage of config option verbose Status in Cinder: Fix Released Status in OpenStack Compute (nova): Fix Released Bug description: oslo.log deprecate config option verbose since aug 1, 2015 in review: in https://review.openstack.org/#/c/206437/ That was a long time ago so it should be possible to remove it now. This was already merged once but had to be reverted because some projects were still relying on it. so we need clean up usage of it before removing it. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1663570/+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 1789844] [NEW] vxlan not work
Public bug reported:
openstack Q
[root@compute ~]# cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)
[root@compute ~]# uname -r
4.18.5-1.el7.elrepo.x86_64
[root@compute ~]# ovs-vswitchd -V
ovs-vswitchd (Open vSwitch) 2.9.0
DPDK 17.11.0
1、Flat network is normal
2、Vxlan port is not created？Is it related to the kernel version?
[root@compute ~]# ovs-appctl dpif/show
system@ovs-system: hit:182292 missed:2077
br-int:
br-int 65534/1: (internal)
int-br-provider 1/none: (patch: peer=phy-br-provider)
patch-tun 2/none: (patch: peer=patch-int)
qvobcafce85-89 4/3: (system)
br-provider:
br-provider 65534/5: (internal)
ens224 2/4: (system)
phy-br-provider 1/none: (patch: peer=int-br-provider)
br-tun:
br-tun 65534/2: (internal)
patch-int 1/none: (patch: peer=patch-tun)
[root@compute ~]# ovs-vsctl show
9c3e2d45-cd47-4718-8adc-b899828c28f5
Manager "ptcp:6640:127.0.0.1"
is_connected: true
Bridge br-tun
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port br-tun
Interface br-tun
type: internal
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Bridge br-provider
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port br-provider
Interface br-provider
type: internal
Port "ens224"
Interface "ens224"
Port phy-br-provider
Interface phy-br-provider
type: patch
options: {peer=int-br-provider}
Bridge br-int
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port "qvobcafce85-89"
tag: 2
Interface "qvobcafce85-89"
Port br-int
Interface br-int
type: internal
Port int-br-provider
Interface int-br-provider
type: patch
options: {peer=phy-br-provider}
ovs_version: "2.9.0"
** 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/1789844
Title:
vxlan not work
Status in neutron:
New
Bug description:
openstack Q
[root@compute ~]# cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)
[root@compute ~]# uname -r
4.18.5-1.el7.elrepo.x86_64
[root@compute ~]# ovs-vswitchd -V
ovs-vswitchd (Open vSwitch) 2.9.0
DPDK 17.11.0
1、Flat network is normal
2、Vxlan port is not created？Is it related to the kernel version?
[root@compute ~]# ovs-appctl dpif/show
system@ovs-system: hit:182292 missed:2077
br-int:
br-int 65534/1: (internal)
int-br-provider 1/none: (patch: peer=phy-br-provider)
patch-tun 2/none: (patch: peer=patch-int)
qvobcafce85-89 4/3: (system)
br-provider:
br-provider 65534/5: (internal)
ens224 2/4: (system)
phy-br-provider 1/none: (patch: peer=int-br-provider)
br-tun:
br-tun 65534/2: (internal)
patch-int 1/none: (patch: peer=patch-tun)
[root@compute ~]# ovs-vsctl show
9c3e2d45-cd47-4718-8adc-b899828c28f5
Manager "ptcp:6640:127.0.0.1"
is_connected: true
Bridge br-tun
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port br-tun
Interface br-tun
type: internal
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Bridge br-provider
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port br-provider
Interface br-provider
type: internal
Port "ens224"
Interface "ens224"
Port phy-br-provider
Interface phy-br-provider
type: patch
options: {peer=int-br-provider}
Bridge br-int
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port "qvobcafce85-89"
tag: 2
Interface "qvobcafce85-89"
Port br-int
Interface br-int
[Yahoo-eng-team] [Bug 1789846] [NEW] l2_pop flows missing when spawning VMs at a high rate
Public bug reported: version: Pike, DVR enabled, 28 compute nodes scenario: spawn 140 VMs concurrently, with pre-created neutron ports issue: on some compute nodes VMs cannot get IP address, no reply on dhcp broadcasts. All new VMs spawned on the same compute node in the same network have this problem. it appears that flood table on compute nodes with issue is missing outputs to dhcp nodes: cookie=0x679aebcfbb8dc9a2, duration=296.991s, table=22, n_packets=2, n_bytes=220, priority=1,dl_vlan=4 actions=strip_vlan,load:0x14->NXM_NX_TUN_ID[],output:"vxlan- ac1ef47a",output:"vxlan-ac1ef480",output:"vxlan-ac1ef46d",output:"vxlan- ac1ef477",... ** Affects: neutron Importance: High Assignee: Oleg Bondarev (obondarev) Status: Confirmed ** Tags: l2-pop l3-dvr-backlog -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1789846 Title: l2_pop flows missing when spawning VMs at a high rate Status in neutron: Confirmed Bug description: version: Pike, DVR enabled, 28 compute nodes scenario: spawn 140 VMs concurrently, with pre-created neutron ports issue: on some compute nodes VMs cannot get IP address, no reply on dhcp broadcasts. All new VMs spawned on the same compute node in the same network have this problem. it appears that flood table on compute nodes with issue is missing outputs to dhcp nodes: cookie=0x679aebcfbb8dc9a2, duration=296.991s, table=22, n_packets=2, n_bytes=220, priority=1,dl_vlan=4 actions=strip_vlan,load:0x14->NXM_NX_TUN_ID[],output:"vxlan- ac1ef47a",output:"vxlan-ac1ef480",output:"vxlan-ac1ef46d",output :"vxlan-ac1ef477",... To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1789846/+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 1789849] [NEW] Install and configure in keystone, pike: incorrect variable names
Public bug reported: Install and configure in keystone, pike: incorrect variable names 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: Two variable names in the shell code sample at https://git.openstack.org/cgit/openstack/keystone/tree/doc/source/install/keystone-install-ubuntu.rst?h=stable%2Fpike#n159 seem to be incorrect. Strictly applying the code sample, the commands on the next page (https://docs.openstack.org/keystone/pike/install/keystone-users-ubuntu.html) do not work. ``` openstack project create --domain default \ --description "Service Project" service ``` yields ``` The request you have made requires authentication. (HTTP 401) (Request-ID: req-384b7024-193f-49f9-babd-5b92567418ee) ``` - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. ``` diff --git a/doc/source/install/keystone-install-ubuntu.rst b/doc/source/install/keystone-install-ubuntu.rst index 7d6635bbf..94d6886f4 100644 --- a/doc/source/install/keystone-install-ubuntu.rst +++ b/doc/source/install/keystone-install-ubuntu.rst @@ -163,6 +163,8 @@ Finalize the installation $ export OS_PROJECT_NAME=admin $ export OS_USER_DOMAIN_NAME=Default $ export OS_PROJECT_DOMAIN_NAME=Default + $ export OS_USER_DOMAIN_ID=default + $ export OS_PROJECT_DOMAIN_ID=default $ export OS_AUTH_URL=http://controller:35357/v3 $ export OS_IDENTITY_API_VERSION=3 ``` I am not sure if this was changed in further releases or not --- Release: 12.0.1.dev19 on 2018-07-26 21:51 SHA: ce46cc25dc4d967c062587ab21b2b38cab045e00 Source: https://git.openstack.org/cgit/openstack/keystone/tree/doc/source/install/keystone-install-ubuntu.rst?h=stable%2Fpike URL: https://docs.openstack.org/keystone/pike/install/keystone-install-ubuntu.html ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1789849 Title: Install and configure in keystone, pike: incorrect variable names Status in OpenStack Identity (keystone): New Bug description: Install and configure in keystone, pike: incorrect variable names 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: Two variable names in the shell code sample at https://git.openstack.org/cgit/openstack/keystone/tree/doc/source/install/keystone-install-ubuntu.rst?h=stable%2Fpike#n159 seem to be incorrect. Strictly applying the code sample, the commands on the next page (https://docs.openstack.org/keystone/pike/install/keystone-users-ubuntu.html) do not work. ``` openstack project create --domain default \ --description "Service Project" service ``` yields ``` The request you have made requires authentication. (HTTP 401) (Request-ID: req-384b7024-193f-49f9-babd-5b92567418ee) ``` - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. ``` diff --git a/doc/source/install/keystone-install-ubuntu.rst b/doc/source/install/keystone-install-ubuntu.rst index 7d6635bbf..94d6886f4 100644 --- a/doc/source/install/keystone-install-ubuntu.rst +++ b/doc/source/install/keystone-install-ubuntu.rst @@ -163,6 +163,8 @@ Finalize the installation $ export OS_PROJECT_NAME=admin $ export OS_USER_DOMAIN_NAME=Default $ export OS_PROJECT_DOMAIN_NAME=Default + $ export OS_USER_DOMAIN_ID=default + $ export OS_PROJECT_DOMAIN_ID=default $ export OS_AUTH_URL=http://controller:35357/v3 $ export OS_IDENTITY_API_VERSION=3 ``` I am not sure if this was changed in further releases or not --- Release: 12.0.1.dev19 on 2018-07-26 21:51 SHA: ce46cc25dc4d967c062587ab21b2b38cab045e00 Source: https://git.openstack.org/cgit/openstack/keystone/tree/doc/source/install/keystone-install-ubuntu.rst?h=stable%2Fpike URL: https://docs.openstack.org/keystone/pike/install/keystone-install-ubuntu.html To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1789849/+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 1789870] [NEW] Cannot change provider network type
Public bug reported: After creating a network using "openstack network create --provider- network-type vlan testNetwork", Cannot change provider network type by using "openstack network set --provider-network-type vxlan testNetwork". And with "BadRequestException: Unknown error" The OpenStack version is Queens, and installed in a lxc container with the OS Ubuntu16.04 and in a All In One Manner. The neutron-server.log is" 2018-08-30 17:05:54.761 8389 INFO neutron.wsgi [-] 192.168.122.175 "GET / HTTP/1.1" status: 200 len: 257 time: 0.0010800 2018-08-30 17:05:54.826 8389 INFO neutron.pecan_wsgi.hooks.translation [req-604b9bdb-2f0f-430c-a5e5-995fdd5d196c 14d584b0c41547e394d7f793bd8cd0f2 a4d6cb4de22746458041f74e77987832 - default default] GET failed (client error): The resource could not be found. 2018-08-30 17:05:54.827 8389 INFO neutron.wsgi [req-604b9bdb-2f0f-430c-a5e5-995fdd5d196c 14d584b0c41547e394d7f793bd8cd0f2 a4d6cb4de22746458041f74e77987832 - default default] 192.168.122.175 "GET /v2.0/networks/testNetwork HTTP/1.1" status: 404 len: 319 time: 0.0637438 2018-08-30 17:05:55.048 8389 INFO neutron.wsgi [req-97d5b076-47e1-4466-8f18-b9668397e222 14d584b0c41547e394d7f793bd8cd0f2 a4d6cb4de22746458041f74e77987832 - default default] 192.168.122.175 "GET /v2.0/networks HTTP/1.1" status: 200 len: 1485 time: 0.2166309 2018-08-30 17:05:55.137 8389 INFO neutron.pecan_wsgi.hooks.translation [req-69ddcf3a-3982-4a9b-a6ff-8d5bd4fbf7bc 14d584b0c41547e394d7f793bd8cd0f2 a4d6cb4de22746458041f74e77987832 - default default] PUT failed (client error): The server could not comply with the request since it is either malformed or otherwise incorrect. 2018-08-30 17:05:55.138 8389 INFO neutron.wsgi [req-69ddcf3a-3982-4a9b-a6ff-8d5bd4fbf7bc 14d584b0c41547e394d7f793bd8cd0f2 a4d6cb4de22746458041f74e77987832 - default default] 192.168.122.175 "PUT /v2.0/networks/48a90199-bf4e-42d1-9b0e-8c38fe84b834 HTTP/1.1" status: 400 len: 361 time: 0.0822990 " Thanks ** 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/1789870 Title: Cannot change provider network type Status in neutron: New Bug description: After creating a network using "openstack network create --provider- network-type vlan testNetwork", Cannot change provider network type by using "openstack network set --provider-network-type vxlan testNetwork". And with "BadRequestException: Unknown error" The OpenStack version is Queens, and installed in a lxc container with the OS Ubuntu16.04 and in a All In One Manner. The neutron-server.log is" 2018-08-30 17:05:54.761 8389 INFO neutron.wsgi [-] 192.168.122.175 "GET / HTTP/1.1" status: 200 len: 257 time: 0.0010800 2018-08-30 17:05:54.826 8389 INFO neutron.pecan_wsgi.hooks.translation [req-604b9bdb-2f0f-430c-a5e5-995fdd5d196c 14d584b0c41547e394d7f793bd8cd0f2 a4d6cb4de22746458041f74e77987832 - default default] GET failed (client error): The resource could not be found. 2018-08-30 17:05:54.827 8389 INFO neutron.wsgi [req-604b9bdb-2f0f-430c-a5e5-995fdd5d196c 14d584b0c41547e394d7f793bd8cd0f2 a4d6cb4de22746458041f74e77987832 - default default] 192.168.122.175 "GET /v2.0/networks/testNetwork HTTP/1.1" status: 404 len: 319 time: 0.0637438 2018-08-30 17:05:55.048 8389 INFO neutron.wsgi [req-97d5b076-47e1-4466-8f18-b9668397e222 14d584b0c41547e394d7f793bd8cd0f2 a4d6cb4de22746458041f74e77987832 - default default] 192.168.122.175 "GET /v2.0/networks HTTP/1.1" status: 200 len: 1485 time: 0.2166309 2018-08-30 17:05:55.137 8389 INFO neutron.pecan_wsgi.hooks.translation [req-69ddcf3a-3982-4a9b-a6ff-8d5bd4fbf7bc 14d584b0c41547e394d7f793bd8cd0f2 a4d6cb4de22746458041f74e77987832 - default default] PUT failed (client error): The server could not comply with the request since it is either malformed or otherwise incorrect. 2018-08-30 17:05:55.138 8389 INFO neutron.wsgi [req-69ddcf3a-3982-4a9b-a6ff-8d5bd4fbf7bc 14d584b0c41547e394d7f793bd8cd0f2 a4d6cb4de22746458041f74e77987832 - default default] 192.168.122.175 "PUT /v2.0/networks/48a90199-bf4e-42d1-9b0e-8c38fe84b834 HTTP/1.1" status: 400 len: 361 time: 0.0822990 " Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1789870/+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 1789868] [NEW] RFE: Add a virtio-rng device to Nova instances by default
Public bug reported: What do we want: Entropy! When do we want it: By default! Nova don't add a RNG to the guests by default; this seems a serious problem - the guests should get a good entropy source to ensure that everything during boot gets randomised, and also you sometimes get hangs where guests are starved of entropy (there are some newer guest kernels that seem more prone to this, but still it's a more general problem). Old arguments for why we didn't have a virtio-rng by default: a) We were using hosts /dev/random and it could block - we moved to urandom and that problem doesn't exist any more b) We didn't have windows drivers? We do now (IMHO this is fairly important - we really should have the RNG) ** Affects: nova Importance: Medium Assignee: Kashyap Chamarthy (kashyapc) Status: Triaged ** Tags: libvirt -- 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/1789868 Title: RFE: Add a virtio-rng device to Nova instances by default Status in OpenStack Compute (nova): Triaged Bug description: What do we want: Entropy! When do we want it: By default! Nova don't add a RNG to the guests by default; this seems a serious problem - the guests should get a good entropy source to ensure that everything during boot gets randomised, and also you sometimes get hangs where guests are starved of entropy (there are some newer guest kernels that seem more prone to this, but still it's a more general problem). Old arguments for why we didn't have a virtio-rng by default: a) We were using hosts /dev/random and it could block - we moved to urandom and that problem doesn't exist any more b) We didn't have windows drivers? We do now (IMHO this is fairly important - we really should have the RNG) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1789868/+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 1789873] [NEW] Filter server list result by multiple vm state assgingments not working
Public bug reported: Description API call "GET servers/detail?vm_state=ACTIVE&vm_state=STOPPED" only returns servers with STOPPED vm_state instead of those with either vm_state. Environment === $ nova --version 10.1.0 ** Affects: nova Importance: Undecided Assignee: Chen (chenn2) Status: New ** Changed in: nova Assignee: (unassigned) => Chen (chenn2) -- 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/1789873 Title: Filter server list result by multiple vm state assgingments not working Status in OpenStack Compute (nova): New Bug description: Description API call "GET servers/detail?vm_state=ACTIVE&vm_state=STOPPED" only returns servers with STOPPED vm_state instead of those with either vm_state. Environment === $ nova --version 10.1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1789873/+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 1789824] Re: One single ip is allocated for a port in the network with multiple subnets
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1789824
Title:
One single ip is allocated for a port in the network with multiple
subnets
Status in neutron:
Invalid
Bug description:
Steps:
1.Create a network with multiple subnets.
2.Create a port with the network above.
3.Port is created, but only one ip is allocated for the port.
The problem is as follows in [1]:
def _allocate_ips_for_port(self, context, port):
..
..
..
.
else:
ips = []
version_subnets = [v4, v6_stateful]
for subnets in version_subnets:
if subnets:
ips.append([{'subnet_id': s['id']}#"extend"should be used
instead of "append"
for s in subnets])
[1]https://github.com/openstack/neutron/blob/master/neutron/db/ipam_pluggable_backend.py#L223
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1789824/+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 1789878] [NEW] bgpvpn router fallback broken by change in neutron openvswitch firewall
Public bug reported: This issue impacts current master, stable/rocky and stable/queens. The first symptom is that we have seen failures of many tests from legacy-tempest-dsvm-networking-bgpvpn-bagpipe since the merge of [1] in neutron code (August 14th). Background: networking-bagpipe code for BGPVPN has a "router fallback" mechanism: in cases where a network is at the same time connected to a Router and associated to a BGPVPN, the traffic sent by a VM to its gateway is redirected to br-mpls to attempt BGPVPN route matching, before eventually being sent, as a fallback, to the neutron netns router if it did no VPN route was matched in br-mpls. For this mechanism to work, a rule is in place in table 91 to override the NORMAL action (which would result in flood/learn) for the traffic destinated to the gateway MAC address, with a higher priority rule that sends the traffic to br-tun instead (br-tun is where the redirection to br-mpls takes place): cookie=0x8b0cf47ac991c941, duration=5371.870s, table=91, n_packets=217, n_bytes=21266, priority=2,reg6=0x18,dl_dst=fa:16:3e:c5:89:72 actions=mod_vlan_vid:24,output:"patch-tun" cookie=0x89f8a81c314f2696, duration=71265.896s, table=91, n_packets=338, n_bytes=27094, priority=1 actions=NORMAL (above, fa:16:3e:c5:89:72 is the gateway MAC address for the network with vlan_id 24) Analysis of the issue: Change [1] replaced some rule that were resubmiting to table 91, with a NORMAL action, resulting in only the first packets (from a conntrack standpoint) to reach table 91. This prevents the redirection of traffic to br-tun,br-mpls. The tricky thing is that the issue does not always occurs: when there is no entry in the MAC leaning table (ovs-appctl fdb/show br-int) for the gateway MAC, the traffic is flooded and eventually reaches br-tun,br-mpls . This explains why some tests, but not all tests, fail. (not also that the tests where no Router is used in the destination network do not seem to fail.) [1] https://review.openstack.org/#/q/Ib6ced838a7ec6d5c459a8475318556001c31bdf ** Affects: networking-bagpipe Importance: High Status: Confirmed ** Affects: neutron Importance: Undecided Status: New ** Also 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/1789878 Title: bgpvpn router fallback broken by change in neutron openvswitch firewall Status in BaGPipe: Confirmed Status in neutron: New Bug description: This issue impacts current master, stable/rocky and stable/queens. The first symptom is that we have seen failures of many tests from legacy-tempest-dsvm-networking-bgpvpn-bagpipe since the merge of [1] in neutron code (August 14th). Background: networking-bagpipe code for BGPVPN has a "router fallback" mechanism: in cases where a network is at the same time connected to a Router and associated to a BGPVPN, the traffic sent by a VM to its gateway is redirected to br-mpls to attempt BGPVPN route matching, before eventually being sent, as a fallback, to the neutron netns router if it did no VPN route was matched in br-mpls. For this mechanism to work, a rule is in place in table 91 to override the NORMAL action (which would result in flood/learn) for the traffic destinated to the gateway MAC address, with a higher priority rule that sends the traffic to br-tun instead (br-tun is where the redirection to br-mpls takes place): cookie=0x8b0cf47ac991c941, duration=5371.870s, table=91, n_packets=217, n_bytes=21266, priority=2,reg6=0x18,dl_dst=fa:16:3e:c5:89:72 actions=mod_vlan_vid:24,output:"patch-tun" cookie=0x89f8a81c314f2696, duration=71265.896s, table=91, n_packets=338, n_bytes=27094, priority=1 actions=NORMAL (above, fa:16:3e:c5:89:72 is the gateway MAC address for the network with vlan_id 24) Analysis of the issue: Change [1] replaced some rule that were resubmiting to table 91, with a NORMAL action, resulting in only the first packets (from a conntrack standpoint) to reach table 91. This prevents the redirection of traffic to br-tun,br-mpls. The tricky thing is that the issue does not always occurs: when there is no entry in the MAC leaning table (ovs-appctl fdb/show br-int) for the gateway MAC, the traffic is flooded and eventually reaches br-tun,br-mpls . This explains why some tests, but not all tests, fail. (not also that the tests where no Router is used in the destination network do not seem to fail.) [1] https://review.openstack.org/#/q/Ib6ced838a7ec6d5c459a8475318556001c31bdf To manage notifications about this bug go to: https://bugs.launchpad.net/networking-bagpipe/+bug/1789878/+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 hel
[Yahoo-eng-team] [Bug 1712480] Re: Soft-deleting vm fails after "nova resize" the vm
Reviewed: https://review.openstack.org/546920 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=018522f4d0566bf9f22fe0264eaedffa12f245e9 Submitter: Zuul Branch:master commit 018522f4d0566bf9f22fe0264eaedffa12f245e9 Author: Neha Alhat Date: Mon Sep 18 17:57:44 2017 +0530 Fix soft deleting vm fails after "nova resize" vm Problem description: When trying to soft-delete an instance that is just resized but the resize action is not yet confirmed, the soft-delete call will first attempt to confirm_resize the instance, then an error will occur since confirm_resize method does not expect a SOFT_DELETING task_state currently. https://github.com/openstack/nova/blob/8e052c7/nova/compute/manager.py#L3911 Fix steps: 1 Add SOFT_DELETING to the expected_task_state of confirm_resize method. 2 Since confirm_resize method sets instance.task_state to None, set instance.task_state to back to SOFT_DELETING after confirm_resize is executed, so the rest workflow should finish as normal situations. Co-Authored-By: Chen Change-Id: Ia4592adc93960625148ffa6e9f7d1cfa0c6046aa Closes-Bug: #1712480 ** 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/1712480 Title: Soft-deleting vm fails after "nova resize" the vm Status in OpenStack Compute (nova): Fix Released Bug description: Description === I use "nova resize" command to resize the vm ,but I don't call "nova resize-confirm" ,then I use "nova delete" command to soft-delete the vm ,it reports ERROR as this: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-2ee1cacd-78d8-4a9d-b975-dec7d31c8033) ERROR (CommandError): Unable to delete the specified server(s). Steps to reproduce == 1)I config nova.conf, make reclaim_instance_interval equal to 60 to enable "soft-delete", then restart openstack-nova-api service, restart openstack-nova-compute service. 1)resize vm1 by "nova resize" command line 2)delete vm1 by "nova delete" command line Environment === The branch of OpenStack that I use is "mitaka" Expected result === The vm is deleted Actual result = The vm is not deleted ,and report ERROR. Logs & Configs == nova.conf: reclaim_instance_interval = 60 nova-api.log: 2017-08-23 10:45:38.233 1458420 ERROR nova.api.openstack.extensions [req-2ee1cacd-78d8-4a9d-b975-dec7d31c8033 fbc7acf5e66e4a2289f419d257ffba84 95579f6a417e41ca8e8a74fdd8b23b14 - - -] Unexpected exception in API method 2017-08-23 10:45:38.233 1458420 ERROR nova.api.openstack.extensions Traceback (most recent call last): 2017-08-23 10:45:38.233 1458420 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 478, in wrapped 2017-08-23 10:45:38.233 1458420 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/servers.py", line 959, in delete 2017-08-23 10:45:38.233 1458420 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/servers.py", line 809, in _delete 2017-08-23 10:45:38.233 1458420 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 170, in wrapped 2017-08-23 10:45:38.233 1458420 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 159, in inner 2017-08-23 10:45:38.233 1458420 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 187, in _wrapped 2017-08-23 10:45:38.233 1458420 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 140, in inner 2017-08-23 10:45:38.233 1458420 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 1928, in soft_delete 2017-08-23 10:45:38.233 1458420 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 1708, in _delete 2017-08-23 10:45:38.233 1458420 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2017-08-23 10:45:38.233 1458420 ERROR nova.api.openstack.extensions self.force_reraise() 2017-08-23 10:45:38.233 1458420 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2017-08-23 10:45:38.233 1458420 ERROR nova.api.openstack.extensions six.reraise(self.type_, self.value, self.tb) 2017-08-2
[Yahoo-eng-team] [Bug 1750892] Re: Image remains in queued status after location set via PATCH
** Also affects: glance/queens
Importance: Undecided
Status: New
** Changed in: glance/queens
Milestone: None => queens-stable-2
** Changed in: glance/queens
Assignee: (unassigned) => iain MacDonnell (imacdonn)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1750892
Title:
Image remains in queued status after location set via PATCH
Status in Glance:
Fix Released
Status in Glance queens series:
New
Status in Glance rocky series:
In Progress
Bug description:
Pike release, with show_image_direct_url and show_multiple_locations
enabled.
Attempting to create an image using the HTTP backend with the glance
v2 API. I create a new/blank image (goes into "queued" status), then
set the location with:
curl -g -i -X PATCH -H 'Accept-Encoding: gzip, deflate' -H 'Accept:
*/*' -H 'User-Agent: imacdonn-getting-dangerous' -H 'X-Auth-Token:
xxx' -H 'Content-Type: application/openstack-images-v2.1-json-patch'
-d '[{"op":"replace", "path": "/locations", "value": [{"url":
"http://my_http_server/cirros.img";, "metadata": {}}]}]'
http://my_glance_api_endpoint:9292/v2/images/e5581f14-2d05-4ae7-8d78-9da42731a37e
This results in the direct_url getting set correctly, and the size of
the image is correctly determined, but the image remains in "queued"
status. It should become "active".
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1750892/+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 1789074] Re: failed to boot guest with vnic_type direct when rx_queue_size and tx_queue_size are set
Okay, on IRC today, stephenfin reminded me that upstream, the configurable RX/TX Queue Size code is new in Rocky, but that OSP backported it all the way back to Newton. That's why Moshe is seeing the feature code in OSP10-OSP13. So, indeed upstream this bug is a regression in Rocky, and will have to be backported to stable/rocky. ** Changed in: nova Importance: Undecided => High ** Also affects: nova/rocky Importance: Undecided Status: New ** Changed in: nova/rocky Importance: Undecided => High -- 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/1789074 Title: failed to boot guest with vnic_type direct when rx_queue_size and tx_queue_size are set Status in OpenStack Compute (nova): In Progress Status in OpenStack Compute (nova) rocky series: New Bug description: Description of problem: Nova compute forces the virtio RX/TX Queue Size also on SRIOV devices. This makes VM spawn to fail. The configurable RX/TX Queue Size code is similar all the way from OSP10 to OSP13, so it's possible the issue is present also on other releases. Version-Release number of selected component (if applicable): OSP13 z3 How reproducible: (quick and dirty way) Change nova config file # crudini --set /var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.conf libvirt rx_queue_size 1024 # crudini --set /var/lib/config-data/puppet-generated/nova_libvirt/etc/nova/nova.conf libvirt tx_queue_size 1024 # restart nova_compute container docker restart nova_compute # boot a VM with an SRIOV (PF or VF) interface Actual results: Nova add on the sriov port section rx_queue_size Expected results: Additional info: To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1789074/+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 1787119] Re: [Logging] firewall_group log resource and security_group log resource could not co-exist correctly
Reviewed: https://review.openstack.org/591978 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=310bfa326fb9c016d02f9a505ae309ae0e15e7d4 Submitter: Zuul Branch:master commit 310bfa326fb9c016d02f9a505ae309ae0e15e7d4 Author: Kim Bao Long Date: Wed Aug 15 15:52:28 2018 +0700 Fix incorrect log resources querying This patch aims to fix a co-existence problem between security_group and firewall_group log resources due to incorrect log querying from database. Change-Id: Ic60ad436e0fbb23cdae0e63eaeb73130ebf02089 Closes-Bug: #1787119 ** 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/1787119 Title: [Logging] firewall_group log resource and security_group log resource could not co-exist correctly Status in neutron: Fix Released Bug description: I would like to report a bug that relates to co-existence between security_group log resource and firewall_group log resource in stable/rocky [1]. Please follow a given procedure to reproduce this bug. Environment --- - Devstack stable/rocky - Install devstack with local.conf: http://paste.openstack.org/show/727916/ - Make sure that 'log' is added into '[agent] extensions' in '/etc/neutron/plugins/ml2/ml2_conf.ini' - Topology: Set up topolocy with the following script http://paste.openstack.org/show/728095/ Testcase - Create firewall_group log resource: openstack network log create --resource-type firewall_group fwg_log +-+--+ | Field | Value| +-+--+ | Description | | | Enabled | True | | Event | ALL | | ID | ebe7a495-027e-4982-bd64-fe269617dd6d | | Name| fwg_log | | Project | 61c7600120ac44178c8064250d971b76 | | Resource| None | | Target | None | | Type| firewall_group | | created_at | 2018-08-15T07:55:37Z | | revision_number | 0| | tenant_id | 61c7600120ac44178c8064250d971b76 | | updated_at | 2018-08-15T07:55:37Z | +-+--+ - Ping from VM0 to router0 -> Cannot ping - Check ovs flow with: sudo ovs-ofctl dump-flows br-int Results: http://paste.openstack.org/show/728098/ - Check log in /var/log/syslog with: tailf /var/log/syslog | grep -e ACCEPT Results: http://paste.openstack.org/show/728097/ This log came from security_group log, but log_resource_ids=[u'ebe7a495-027e-4982-bd64-fe269617dd6d'] that include the ID of fwg_log Each of log message contains a list of log objects that capture itself in log_resource_ids. This log message come from security_group logging, but it contains the ID of firewall_group log resource. Please note that, I only created firewall_group log with ID is 'ebe7a495-027e-4982-bd64-fe269617dd6d', and there is no security_group at this moment => Bug References: [1] https://docs.openstack.org/neutron/latest/admin/config-logging.html#service-workflow-for-operator To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1787119/+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 1789991] [NEW] nova-compute error after enrolling ironic baremetal nodes
Public bug reported:
Description
===
After enrolling some ironic baremetal nodes, I noticed the following in
nova-compute.log (longer trace below):
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager [req-73ba9d4b-b51d-
4ab7-88c8-5fc3f27fd89e - - - - -] Error updating resources for node
0e5705cc-e872-49aa-aff4-1a91278b5cb3.: NotImplementedError: Cannot load
'id' in the base class
Steps to reproduce
==
* Enroll ironic baremetal nodes (openstack baremetal node provide)
* Wait
* Error repeatedly appears in nova-compute.log
Expected result
===
No errors in log
Actual result
=
Errors in log
Environment
===
openstack-nova-compute-18.0.0-0.20180829095234.45fc232.el7.noarch
puppet-nova-13.3.1-0.20180825165256.5d1889b.el7.noarch
python-nova-18.0.0-0.20180829095234.45fc232.el7.noarch
python-novajoin-1.0.19-0.20180828183900.3d58511.el7.noarch
openstack-nova-common-18.0.0-0.20180829095234.45fc232.el7.noarch
python2-novaclient-11.0.0-0.20180807085257.f1005ce.el7.noarch
Logs & Configs
=
2018-08-30 17:00:51.142 7 DEBUG oslo_concurrency.lockutils
[req-73ba9d4b-b51d-4ab7-88c8-5fc3f27fd89e - - - - -] Lock "compute_resources"
release\
d by "nova.compute.resource_tracker._update_available_resource" :: held 0.001s
inner /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils\
.py:285
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager
[req-73ba9d4b-b51d-4ab7-88c8-5fc3f27fd89e - - - - -] Error updating resources
for node 0e57\
05cc-e872-49aa-aff4-1a91278b5cb3.: NotImplementedError: Cannot load 'id' in the
base class
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager Traceback (most recent
call last):
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager File
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 7729, in
_update_av\
ailable_resource_for_node
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager
rt.update_available_resource(context, nodename)
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager File
"/usr/lib/python2.7/site-packages/nova/compute/resource_tracker.py", line 700,
in up\
date_available_resource
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager
self._update_available_resource(context, resources)
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager File
"/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", line 274, in
inner
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager return f(*args,
**kwargs)
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager File
"/usr/lib/python2.7/site-packages/nova/compute/resource_tracker.py", line 723,
in _u\
pdate_available_resource
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager
self._init_compute_node(context, resources)
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager File
"/usr/lib/python2.7/site-packages/nova/compute/resource_tracker.py", line 563,
in _i\
nit_compute_node
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager
self._setup_pci_tracker(context, cn, resources)
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager File
"/usr/lib/python2.7/site-packages/nova/compute/resource_tracker.py", line 594,
in _s\
etup_pci_tracker
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager n_id = compute_node.id
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager File
"/usr/lib/python2.7/site-packages/oslo_versionedobjects/base.py", line 67, in
getter
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager
self.obj_load_attr(name)
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager File
"/usr/lib/python2.7/site-packages/oslo_versionedobjects/base.py", line 603, in
obj_l\
oad_attr
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager _("Cannot load '%s' in
the base class") % attrname)
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager NotImplementedError:
Cannot load 'id' in the base class
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager
** 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/1789991
Title:
nova-compute error after enrolling ironic baremetal nodes
Status in OpenStack Compute (nova):
New
Bug description:
Description
===
After enrolling some ironic baremetal nodes, I noticed the following in
nova-compute.log (longer trace below):
2018-08-30 17:00:51.142 7 ERROR nova.compute.manager [req-73ba9d4b-
b51d-4ab7-88c8-5fc3f27fd89e - - - - -] Error updating resources for
node 0e5705cc-e872-49aa-aff4-1a91278b5cb3.: NotImplementedError:
Cannot load 'id' in the base class
Steps to reproduce
==
* Enroll ironic baremetal nodes (openstack baremetal node provide)
* Wait
* Error repeatedly appears in nova-compute.log
Expected result
===
No errors in log
Actual result
=
Errors in log
Environment
[Yahoo-eng-team] [Bug 1789998] [NEW] ResourceProviderAllocationRetrievalFailed ERROR log message on fresh n-cpu startup
Public bug reported:
As a result of this recent change in stein:
https://review.openstack.org/#/c/584598/21/nova/compute/resource_tracker.py@1281
We now get this error in the n-cpu logs on a fresh startup after the
compute node record is created in the database but before the resource
provider is created in placement:
http://logs.openstack.org/98/584598/21/check/tempest-
full/85acbda/controller/logs/screen-n-cpu.txt.gz?level=TRACE#_Aug_29_21_43_10_675029
Aug 29 21:43:10.675029 ubuntu-xenial-rax-iad-0001643010 nova-
compute[16853]: ERROR nova.compute.resource_tracker [None req-
5ee3cf40-9136-42b6-b370-89f6b17ac61a None None] Skipping removal of
allocations for deleted instances: Failed to retrieve allocations for
resource provider 6b03ae3f-495d-472a-804b-6cac034f5661: {"errors":
[{"status": 404, "request_id": "req-
6ff222c2-be32-471a-8764-d7168e6de73f", "detail": "The resource could not
be found.\n\n Resource provider '6b03ae3f-495d-472a-804b-6cac034f5661'
not found: No resource provider with uuid 6b03ae3f-495d-472a-804b-
6cac034f5661 found ", "title": "Not Found"}]}:
ResourceProviderAllocationRetrievalFailed: Failed to retrieve
allocations for resource provider 6b03ae3f-495d-472a-804b-6cac034f5661:
{"errors": [{"status": 404, "request_id": "req-
6ff222c2-be32-471a-8764-d7168e6de73f", "detail": "The resource could not
be found.\n\n Resource provider '6b03ae3f-495d-472a-804b-6cac034f5661'
not found: No resource provider with uuid 6b03ae3f-495d-472a-804b-
6cac034f5661 found ", "title": "Not Found"}]}
We could probably pass a flag down to indicate if the compute node is
newly created and if so, and we hit that exception, to just ignore it.
** Affects: nova
Importance: Low
Status: Triaged
** Tags: compute placement resource-tracker
--
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/1789998
Title:
ResourceProviderAllocationRetrievalFailed ERROR log message on fresh
n-cpu startup
Status in OpenStack Compute (nova):
Triaged
Bug description:
As a result of this recent change in stein:
https://review.openstack.org/#/c/584598/21/nova/compute/resource_tracker.py@1281
We now get this error in the n-cpu logs on a fresh startup after the
compute node record is created in the database but before the resource
provider is created in placement:
http://logs.openstack.org/98/584598/21/check/tempest-
full/85acbda/controller/logs/screen-n-cpu.txt.gz?level=TRACE#_Aug_29_21_43_10_675029
Aug 29 21:43:10.675029 ubuntu-xenial-rax-iad-0001643010 nova-
compute[16853]: ERROR nova.compute.resource_tracker [None req-
5ee3cf40-9136-42b6-b370-89f6b17ac61a None None] Skipping removal of
allocations for deleted instances: Failed to retrieve allocations for
resource provider 6b03ae3f-495d-472a-804b-6cac034f5661: {"errors":
[{"status": 404, "request_id": "req-
6ff222c2-be32-471a-8764-d7168e6de73f", "detail": "The resource could
not be found.\n\n Resource provider '6b03ae3f-495d-472a-804b-
6cac034f5661' not found: No resource provider with uuid 6b03ae3f-495d-
472a-804b-6cac034f5661 found ", "title": "Not Found"}]}:
ResourceProviderAllocationRetrievalFailed: Failed to retrieve
allocations for resource provider 6b03ae3f-495d-472a-804b-
6cac034f5661: {"errors": [{"status": 404, "request_id": "req-
6ff222c2-be32-471a-8764-d7168e6de73f", "detail": "The resource could
not be found.\n\n Resource provider '6b03ae3f-495d-472a-804b-
6cac034f5661' not found: No resource provider with uuid 6b03ae3f-495d-
472a-804b-6cac034f5661 found ", "title": "Not Found"}]}
We could probably pass a flag down to indicate if the compute node is
newly created and if so, and we hit that exception, to just ignore it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1789998/+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 1790023] [NEW] ERROR networking_hyperv.neutron.agent.layer2
Public bug reported:
When i create new instance on Hyper-V 2016 with Hyper-v Nova Driver(Queens
release) its start without interface and i see this error all the time:
2018-08-31 04:12:57.009 4268 INFO networking_hyperv.neutron.agent.layer2
[req-33b89cee-bc36-4e3b-a984-d5ee42636cbe - - - - -] Adding port
4cd2c214-5a9b-4680-a0e7-36bf2d85728c
2018-08-31 04:12:57.022 4268 INFO networking_hyperv.neutron.agent.layer2
[req-33b89cee-bc36-4e3b-a984-d5ee42636cbe - - - - -] Port
4cd2c214-5a9b-4680-a0e7-36bf2d85728c updated. Details: {u'profile': {},
u'network_qos_policy_id': None, u'qos_policy_id': None,
u'allowed_address_pairs': [], u'admin_state_up': True, u'network_id':
u'2f004645-de11-4b04-a3f9-1c2abfb78899', u'segmentation_id': 1001, u'mtu':
1500, u'device_owner': u'compute:test', u'physical_network': u'provider',
u'mac_address': u'fa:16:3e:5d:58:7e', u'device':
u'4cd2c214-5a9b-4680-a0e7-36bf2d85728c', u'port_security_enabled': True,
u'port_id': u'4cd2c214-5a9b-4680-a0e7-36bf2d85728c', u'fixed_ips':
[{u'subnet_id': u'2b15aa6c-d9ce-4247-9bc4-4b6896fcf625', u'ip_address':
u'172.18.200.5'}], u'network_type': u'vlan'}
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2 [-]
Exception encountered while processing port
4cd2c214-5a9b-4680-a0e7-36bf2d85728c. Exception: 'ascii' codec can't encode
characters in position 31-38: ordinal not in range(128): UnicodeEncodeError:
'ascii' codec can't encode characters in position 31-38: ordinal not in
range(128)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
Traceback (most recent call last):
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\agent\layer2.py",
line 314, in process_added_port
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
self._process_added_port(device_details)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\agent\hyperv_neutron_agent.py",
line 252, in _process_added_port
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
device_details)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\agent\layer2.py",
line 302, in _process_added_port
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
set_port_sriov=set_port_sriov)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\_common_utils.py",
line 36, in wrapper
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
return inner()
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\oslo_concurrency\lockutils.py",
line 274, in inner
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
return f(*args, **kwargs)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\_common_utils.py",
line 35, in inner
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
return f(*args, **kwargs)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\agent\layer2.py",
line 479, in _treat_vif_port
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
port_security_enabled, set_port_sriov)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\agent\hyperv_neutron_agent.py",
line 197, in _port_bound
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
self._vlan_driver.bind_vlan_port(port_id, segmentation_id)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\trunk_driver.py",
line 88, in bind_vlan_port
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
trunk = self._fetch_trunk(port_id)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\trunk_driver.py",
line 109, in _fetch_trunk
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
if 'CallbackNotFound' not in str(ex):
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
Uni
[Yahoo-eng-team] [Bug 1790023] Re: ERROR networking_hyperv.neutron.agent.layer2
** Description changed:
- When i create new instance on Hyper-V 2016 with Hyper-v Nova Driver its start
without interface and i see this error all the time:
+ When i create new instance on Hyper-V 2016 with Hyper-v Nova Driver(Queens
release) its start without interface and i see this error all the time:
2018-08-31 04:12:57.009 4268 INFO networking_hyperv.neutron.agent.layer2
[req-33b89cee-bc36-4e3b-a984-d5ee42636cbe - - - - -] Adding port
4cd2c214-5a9b-4680-a0e7-36bf2d85728c
2018-08-31 04:12:57.022 4268 INFO networking_hyperv.neutron.agent.layer2
[req-33b89cee-bc36-4e3b-a984-d5ee42636cbe - - - - -] Port
4cd2c214-5a9b-4680-a0e7-36bf2d85728c updated. Details: {u'profile': {},
u'network_qos_policy_id': None, u'qos_policy_id': None,
u'allowed_address_pairs': [], u'admin_state_up': True, u'network_id':
u'2f004645-de11-4b04-a3f9-1c2abfb78899', u'segmentation_id': 1001, u'mtu':
1500, u'device_owner': u'compute:test', u'physical_network': u'provider',
u'mac_address': u'fa:16:3e:5d:58:7e', u'device':
u'4cd2c214-5a9b-4680-a0e7-36bf2d85728c', u'port_security_enabled': True,
u'port_id': u'4cd2c214-5a9b-4680-a0e7-36bf2d85728c', u'fixed_ips':
[{u'subnet_id': u'2b15aa6c-d9ce-4247-9bc4-4b6896fcf625', u'ip_address':
u'172.18.200.5'}], u'network_type': u'vlan'}
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2 [-]
Exception encountered while processing port
4cd2c214-5a9b-4680-a0e7-36bf2d85728c. Exception: 'ascii' codec can't encode
characters in position 31-38: ordinal not in range(128): UnicodeEncodeError:
'ascii' codec can't encode characters in position 31-38: ordinal not in
range(128)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
Traceback (most recent call last):
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\agent\layer2.py",
line 314, in process_added_port
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
self._process_added_port(device_details)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\agent\hyperv_neutron_agent.py",
line 252, in _process_added_port
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
device_details)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\agent\layer2.py",
line 302, in _process_added_port
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
set_port_sriov=set_port_sriov)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\_common_utils.py",
line 36, in wrapper
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
return inner()
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\oslo_concurrency\lockutils.py",
line 274, in inner
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
return f(*args, **kwargs)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\_common_utils.py",
line 35, in inner
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
return f(*args, **kwargs)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\agent\layer2.py",
line 479, in _treat_vif_port
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
port_security_enabled, set_port_sriov)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\agent\hyperv_neutron_agent.py",
line 197, in _port_bound
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
self._vlan_driver.bind_vlan_port(port_id, segmentation_id)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\trunk_driver.py",
line 88, in bind_vlan_port
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
trunk = self._fetch_trunk(port_id)
2018-08-31 04:12:57.042 4268 ERROR networking_hyperv.neutron.agent.layer2
File
"C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\networking_hyperv\neutron\trunk_driver.py",
line 109, in _fetch_trunk
2018-08-
[Yahoo-eng-team] [Bug 1790027] [NEW] Error retrieving instances list
Public bug reported: Queens release (After restart works ok) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi [req-73c5fdb2-822a-416b-b91c-b7e6fa36fb67 a700160233594eddb2621493b1a1d8d2 08847efa215b4fa6bbe6d1437e38194b - default default] Unexpected exception in API method: OperationalError: (pymysql.err.OperationalError) (1040, u'Too many connections') (Background on this error at: http://sqlalche.me/e/e3q8) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi Traceback (most recent call last): 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py", line 788, in wrapped 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi return f(*args, **kwargs) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/servers.py", line 439, in show 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi instance = self._get_server(context, req, id, is_detail=True) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/servers.py", line 344, in _get_server 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi expected_attrs=expected_attrs) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/api/openstack/common.py", line 479, in get_instance 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi expected_attrs=expected_attrs) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 2348, in get 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi expected_attrs) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 2308, in _get_instance 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi context, instance_uuid, expected_attrs=expected_attrs) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/oslo_versionedobjects/base.py", line 184, in wrapper 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi result = fn(cls, context, *args, **kwargs) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/objects/instance.py", line 475, in get_by_uuid 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi use_slave=use_slave) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 225, in wrapper 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi return f(*args, **kwargs) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/objects/instance.py", line 467, in _db_instance_get_by_uuid 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi columns_to_join=columns_to_join) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/db/api.py", line 764, in instance_get_by_uuid 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi return IMPL.instance_get_by_uuid(context, uuid, columns_to_join) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 169, in wrapper 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi return f(*args, **kwargs) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 270, in wrapped 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi return f(context, *args, **kwargs) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 1872, in instance_get_by_uuid 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi columns_to_join=columns_to_join) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 1877, in _instance_get_by_uuid 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi filter_by(uuid=uuid).\ 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/query.py", line 2778, in first 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi ret = list(self[0:1]) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/query.py", line 2570, in __getitem__ 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi return list(res) 2018-08-31 04:04:11.328 58009 ERROR nova.api.openstack.wsgi File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/query.py", line 2878,
[Yahoo-eng-team] [Bug 1790032] [NEW] revision documentation Install and configure controller node for Ubuntu in nova (queens)
Public bug reported: maybe you should change # su -s /bin/sh -c "nova-manage cell_v2 create_cell --name=cell1 --verbose" nova 109e1d4b-536a-40d0-83c6-5f121b82b650 to # su -s /bin/sh -c "nova-manage cell_v2 create_cell --name=cell1 --verbose" nova thanks for your attention ridho.adilla 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: 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: 17.0.6.dev87 on 2018-08-23 20:28 SHA: fdc3d22ea77a21d525c5ae3eafd9618723bb5df2 Source: https://git.openstack.org/cgit/openstack/nova/tree/doc/source/install/controller-install-ubuntu.rst URL: https://docs.openstack.org/nova/queens/install/controller-install-ubuntu.html ** 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/1790032 Title: revision documentation Install and configure controller node for Ubuntu in nova (queens) Status in OpenStack Compute (nova): New Bug description: maybe you should change # su -s /bin/sh -c "nova-manage cell_v2 create_cell --name=cell1 --verbose" nova 109e1d4b-536a-40d0-83c6-5f121b82b650 to # su -s /bin/sh -c "nova-manage cell_v2 create_cell --name=cell1 --verbose" nova thanks for your attention ridho.adilla 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: 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: 17.0.6.dev87 on 2018-08-23 20:28 SHA: fdc3d22ea77a21d525c5ae3eafd9618723bb5df2 Source: https://git.openstack.org/cgit/openstack/nova/tree/doc/source/install/controller-install-ubuntu.rst URL: https://docs.openstack.org/nova/queens/install/controller-install-ubuntu.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1790032/+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 1790038] [NEW] Network's subnets with different subnet pools
Public bug reported: I created two subnet pools all belong to the same address scope. +---+--+ | Field | Value| +---+--+ | address_scope_id | a86423de-dee6-41b3-a7bf-f7dfef27919d | | created_at| 2018-08-31T09:55:16Z | | default_prefixlen | 28 | | default_quota | None | | description | | | id| f3123096-c566-4962-9760-37e0ad118b76 | | ip_version| 4| | is_default| False| | max_prefixlen | 32 | | min_prefixlen | 8| | name | subnet-pool-ip4-2| | prefixes | 192.168.100.0/24 | | project_id| a4d6cb4de22746458041f74e77987832 | | revision_number | 0| | shared| True | | tags | | | updated_at| 2018-08-31T09:55:16Z | +---+--+ +---+--+ | Field | Value| +---+--+ | address_scope_id | a86423de-dee6-41b3-a7bf-f7dfef27919d | | created_at| 2018-08-30T15:42:06Z | | default_prefixlen | 26 | | default_quota | None | | description | | | id| d977634a-fb6d-42db-8c8e-e3f8248c24ec | | ip_version| 4| | is_default| False| | max_prefixlen | 32 | | min_prefixlen | 8| | name | subnet-pool-ip4 | | prefixes | 203.0.112.0/21 | | project_id| a4d6cb4de22746458041f74e77987832 | | revision_number | 0| | shared| True | | tags | | | updated_at| 2018-08-30T15:42:06Z | +---+--+ Then I create a network, "openstack network create --provider-network-type vlan network" Then I want to create two subnets, with different subnet pools. The first one is successfully created, but the second on fails with "BadRequestException: Unknown error" THe OpenStack version is queens. And it is installed in a Ubuntu 16.04 server. Thanks ** 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/1790038 Title: Network's subnets with different subnet pools Status in neutron: New Bug description: I created two subnet pools all belong to the same address scope. +---+--+ | Field | Value| +---+--+ | address_scope_id | a86423de-dee6-41b3-a7bf-f7dfef27919d | | created_at| 2018-08-31T09:55:16Z | | default_prefixlen | 28 | | default_quota | None | | description | | | id| f3123096-c566-4962-9760-37e0ad118b76 | | ip_version| 4| | is_default| False| | max_prefixlen | 32 | | min_prefixlen | 8| | name | subnet-pool-ip4-2| | prefixes | 192.168.100.0/24 | | project_id| a4d6cb4de22746458041f74e77987832 | | revision_number | 0| | shared| True | | tags | | | updated_at| 2018-08-31T09:55:16Z | +---+--+ +---+--+ | Field | Value| +---+--+ | address_scope_id | a86423de-dee6-41b3-a7bf-f7dfef27919d | | created_at|
