[Yahoo-eng-team] [Bug 1794706] Re: The instance left stuck when oslo.messaging raised MessageDeliveryFailure exception
[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.] ** Changed in: nova Status: Incomplete => Expired -- 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/1794706 Title: The instance left stuck when oslo.messaging raised MessageDeliveryFailure exception Status in OpenStack Compute (nova): Expired Bug description: Description === Currently, nova use message queue such as rabbitmq to communicate between services. When booting an instance, nova api send creating message to nova conductor, unfortunately the rabbitmq is unnormal and raised MessageDeliveryFailure exception, the process is aborted and instance left stuck. so we should catch this exception and delete this instance. Steps to reproduce == 1. Rabbitmq is unnormal 2. Boot an instance. Expected result === The instance boot failed and the instance is deleted. Actual result = The instance is stunk in scheduling state. Environment === 1. Nova Pike [root@cdpm01 ~]# nova --version 9.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1794706/+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 1839028] Re: Port forwarding API test fails because "description" was added to the PF resource
It failed like that only on patch https://review.opendev.org/#/c/670930/ which in fact is trying to add this field to the port forwarding. So there is no bug at all \o/ ** Changed in: neutron Status: Confirmed => 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/1839028 Title: Port forwarding API test fails because "description" was added to the PF resource Status in neutron: Invalid Bug description: Tempest API test for port_forwarding failed because port_forwarding returned from neutron server had got "description" attribute. Problem is that according to API definition it shouldn't have description: https://github.com/openstack/neutron-lib/blob/master/neutron_lib/api/definitions/floating_ip_port_forwarding.py#L74 Details on: http://logs.openstack.org/30/670930/3/check/neutron-tempest-plugin-api/5a731da/testr_results.html.gz To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1839028/+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 1839028] [NEW] Port forwarding API test fails because "description" was added to the PF resource
Public bug reported: Tempest API test for port_forwarding failed because port_forwarding returned from neutron server had got "description" attribute. Problem is that according to API definition it shouldn't have description: https://github.com/openstack/neutron-lib/blob/master/neutron_lib/api/definitions/floating_ip_port_forwarding.py#L74 Details on: http://logs.openstack.org/30/670930/3/check/neutron-tempest-plugin-api/5a731da/testr_results.html.gz ** Affects: neutron Importance: Medium Assignee: Slawek Kaplonski (slaweq) Status: Confirmed ** Tags: api gate-failure -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1839028 Title: Port forwarding API test fails because "description" was added to the PF resource Status in neutron: Confirmed Bug description: Tempest API test for port_forwarding failed because port_forwarding returned from neutron server had got "description" attribute. Problem is that according to API definition it shouldn't have description: https://github.com/openstack/neutron-lib/blob/master/neutron_lib/api/definitions/floating_ip_port_forwarding.py#L74 Details on: http://logs.openstack.org/30/670930/3/check/neutron-tempest-plugin-api/5a731da/testr_results.html.gz To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1839028/+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 1834875] Re: cloud-init growpart race with udev
Oh, good observation, Dan. Yes, it was happening on Cosmic and later. But I cannot say when it started. Now in a moment of despair I tried something very unorthodox: I copied udevadm from Bionic to the Eoan image and ran the tests again. Look and behold, all pass. ** No longer affects: linux-azure (Ubuntu) ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev Status in cloud-init: In Progress Status in systemd package in Ubuntu: New Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1839009] [NEW] os-server-external-events does not behave correctly for failed single events
Public bug reported: The "os-server-external-events" API does not behave correctly when the request body contains a list of one event and if that event ends up in a non-200 state, i.e if the event ends up in either 400 or 404 or 422 states, the function executes all the way to L147 (https://github.com/openstack/nova/blob/433b1662e48db57aaa42e11756fa4a6d8722b386/nova/api/openstack/compute/server_external_events.py#L147) and overall returns a 404 HTTP response without any body. This is wrong since as per the documentation it should return the respective codes (422/404/400) to the client. Infact correctly speaking, if out of the list of provided events, if at least one of them doesn't get into the "accepted_events" list, rest of them are discarded without returning the correct response against each event. ** Affects: nova Importance: Undecided Status: New ** Tags: api -- 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/1839009 Title: os-server-external-events does not behave correctly for failed single events Status in OpenStack Compute (nova): New Bug description: The "os-server-external-events" API does not behave correctly when the request body contains a list of one event and if that event ends up in a non-200 state, i.e if the event ends up in either 400 or 404 or 422 states, the function executes all the way to L147 (https://github.com/openstack/nova/blob/433b1662e48db57aaa42e11756fa4a6d8722b386/nova/api/openstack/compute/server_external_events.py#L147) and overall returns a 404 HTTP response without any body. This is wrong since as per the documentation it should return the respective codes (422/404/400) to the client. Infact correctly speaking, if out of the list of provided events, if at least one of them doesn't get into the "accepted_events" list, rest of them are discarded without returning the correct response against each event. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1839009/+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 1771116] Re: network configuration fails on CentoS 7.5: using dhcp instead of static address
Excellent, ok leaving this bug as INVALID then. If the problem is still exhibited on latest cloud-init please re-open and provide the failing cloud-init version. If your image doesn't contain cloud-init version 19.2 or later, Latest cloud-init for centos is here available here https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/ ** Changed in: cloud-init Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1771116 Title: network configuration fails on CentoS 7.5: using dhcp instead of static address Status in cloud-init: Invalid Status in cloud-init package in CentOS: Confirmed Bug description: Cloud-Provider: NoCloud via Proxmox and qm set I have centostemplate CentOS 7.5 VM on Proxmox and with: [root@centostemplate ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 TYPE=Ethernet BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no NAME=eth0 UUID=9c[…] DEVICE=eth0 ONBOOT=yes DNS1=10.0.0.4 DOMAIN=qs.de IPADDR=10.0.88.101 PREFIX=8 GATEWAY=10.0.0.4 IPV6_PRIVACY=no PROXY_METHOD=none BROWSER_ONLY=no I have a script that on Proxmox does: - qm clone 2100 2101 --name centos1 - qm set 2101 --ipconfig0 ip=10.0.88.151/8,gw=10.0.0.4 --cores 2 --memory 4096 - qm start 2101 I get [root@centos1 ~]# cat /mnt/zeit/network-config version: 1 config: - type: physical name: eth0 mac_address: F2:15:C8:E1:0A:49 subnets: - type: static address: 10.0.88.151/8 gateway: 10.0.0.4 - type: nameserver address: - 10.0.0.4 search: - somedomain.de [root@centos1 ~]# ip -4 addr show eth0 2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 inet 10.0.0.161/16 brd 10.0.255.255 scope global noprefixroute dynamic eth0 valid_lft 171536sec preferred_lft 171536sec and: [root@centos1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 # Created by cloud-init on instance boot automatically, do not edit. # BOOTPROTO=none DEFROUTE=yes DEVICE=eth0 GATEWAY=10.0.0.4 HWADDR=F2:15:C8:E1:0A:49 IPADDR=10.0.88.151/8 ONBOOT=yes TYPE=Ethernet USERCTL=no [root@centos1 ~]# ip link show eth0 2: eth0: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether f2:15:c8:e1:0a:49 brd ff:ff:ff:ff:ff:ff Yet while this works it is wrong on RedHat. It has to be: IPADDR=10.0.88.151 PREFIX=8 Otherwise I get this: [root@centos1 ~]# LANG=C ifup eth0 ipcalc: both netmask and prefix specified Usage: ipcalc [OPTION...] -c, --check Validate IP address for specified address family -4, --ipv4 IPv4 address family (default) -6, --ipv6 IPv6 address family -b, --broadcast Display calculated broadcast address -h, --hostname Show hostname determined via DNS -m, --netmask Display default netmask for IP (class A, B, or C) -n, --network Display network address -p, --prefixDisplay network prefix -s, --silentDon't ever display error messages Help options: -?, --help Show this help message --usage Display brief usage message ipcalc: both netmask and prefix specified Usage: ipcalc [OPTION...] -c, --check Validate IP address for specified address family -4, --ipv4 IPv4 address family (default) -6, --ipv6 IPv6 address family -b, --broadcast Display calculated broadcast address -h, --hostname Show hostname determined via DNS -m, --netmask Display default netmask for IP (class A, B, or C) -n, --network Display network address -p, --prefixDisplay network prefix -s, --silentDon't ever display error messages Help options: -?, --help Show this help message --usage Display brief usage message ipcalc: both netmask and prefix specified Usage: ipcalc [OPTION...] -c, --check Validate IP address for specified address family -4, --ipv4 IPv4 address family (default) -6, --ipv6 IPv6 address family -b, --broadcast Display calculated broadcast address -h, --hostname Show hostname determined via DNS -m, --netmask Display default netmask for IP (class A, B, or C) -n, --network Display network address -p, --prefixDisplay network prefix -s, --silentDon't ever display error messages Help options: -?, --help Show this help message --usage Display brief usage message arping: 10.0.88.151/8: Name or service not known Error: any valid prefix is expected rather than "10.0.88.151/8/". ERROR : [/etc/sysconfig
[Yahoo-eng-team] [Bug 1839004] [NEW] Rocky DVR-SNAT seems missing entries for conntrack marking
Public bug reported:
Hello,
I've been playing with Rocky on CentOS 7 with DVR / DVR-SNAT / BGP. Our
provider network uses private IP-space for scalability. Our tenants run
in public IP-space.
Steps:
openstack network create --share --provider-network-type vlan --external
--provider-physical-network EXTERNAL NET-EXT-VLAN625-UPLINK --provider-segment
625
openstack subnet create --network NET-EXT-VLAN625-UPLINK --subnet-range
192.0.2.0/24 SUBNET-EXT-VLAN625-UPLINK
openstack bgp speaker add network BGP-REFLECTOR-SHARED NET-EXT-VLAN625-UPLINK
openstack address scope create --share --ip-version 4 SCOPE-SHARED-VFOUR
openstack subnet pool create --pool-prefix 93.115.169.128/25 --address-scope
SCOPE-SHARED-VFOUR POOL-SHARED-EXTERNAL
openstack subnet pool set --default-prefix-length 28 --min-prefix-length 26
POOL-SHARED-EXTERNAL
openstack network create --share NET-INT-PUBLIC-SHARED
openstack subnet create --network NET-INT-PUBLIC-SHARED --subnet-pool
POOL-SHARED-EXTERNAL --prefix-length 28 SUBNET-INT-PUBLIC-SHARED
openstack bgp speaker add network BGP-REFLECTOR-SHARED NET-INT-PUBLIC-SHARED
openstack router create ROUTER-SHARED
openstack router set ROUTER-SHARED --disable-snat --external-gateway
NET-EXT-VLAN625-UPLINK
openstack router add subnet ROUTER-SHARED SUBNET-INT-PUBLIC-SHARED
openstack bgp speaker list advertised routes BGP-REFLECTOR-SHARED
Result:
+---+---+
| Destination | Nexthop |
+---+---+
| 93.115.169.128/28 | 192.0.2.6 |
+---+---+
Where 192.0.2.6 is the IP in the SNAT instance on the DVR-SNAT network
node. So far things seem good however it seems my egress traffic is
blocked. I'm not 100% sure it's not caused by misconfiguration but I
found the two lines to get traffic flowing in my config:
https://github.com/openstack/neutron/blob/stable/rocky/neutron/agent/l3/router_info.py#L1093
was rewritten to "dont_block_external = (ip_version ==
lib_constants.IP_VERSION_4 and external_port)"
-> This would allow traffic to go egress into the provider network
https://github.com/openstack/neutron/blob/stable/rocky/neutron/agent/l3/router_info.py#L1122
if-return statement was commented out.
-> I need that connmark/mark restore rule to have ingress replies match
the existing connections.
Validate:
ip netns exec $(ip netns | grep snat | awk '{ print $1}') iptables -t mangle -L
neutron-l3-agent-POSTROUTING -nv
Chain neutron-l3-agent-POSTROUTING (1 references)
pkts bytes target prot opt in out source destination
508 27174 CONNMARK all -- * qg-b075d908-66 0.0.0.0/0 0.0.0.0/0 connmark match
0x0/0x CONNMARK save mask 0x
1 entry
ip netns exec $(ip netns | grep snat | awk '{ print $1}') iptables -t filter -L
neutron-l3-agent-scope -nv
Chain neutron-l3-agent-scope (1 references)
pkts bytes target prot opt in out source destination
6588 350K DROP all -- * sg-c46c9df8-06 0.0.0.0/0 0.0.0.0/0 mark match !
0x401/0x
1 entry (instead of two before)
** 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/1839004
Title:
Rocky DVR-SNAT seems missing entries for conntrack marking
Status in neutron:
New
Bug description:
Hello,
I've been playing with Rocky on CentOS 7 with DVR / DVR-SNAT / BGP.
Our provider network uses private IP-space for scalability. Our
tenants run in public IP-space.
Steps:
openstack network create --share --provider-network-type vlan --external
--provider-physical-network EXTERNAL NET-EXT-VLAN625-UPLINK --provider-segment
625
openstack subnet create --network NET-EXT-VLAN625-UPLINK --subnet-range
192.0.2.0/24 SUBNET-EXT-VLAN625-UPLINK
openstack bgp speaker add network BGP-REFLECTOR-SHARED NET-EXT-VLAN625-UPLINK
openstack address scope create --share --ip-version 4 SCOPE-SHARED-VFOUR
openstack subnet pool create --pool-prefix 93.115.169.128/25 --address-scope
SCOPE-SHARED-VFOUR POOL-SHARED-EXTERNAL
openstack subnet pool set --default-prefix-length 28 --min-prefix-length 26
POOL-SHARED-EXTERNAL
openstack network create --share NET-INT-PUBLIC-SHARED
openstack subnet create --network NET-INT-PUBLIC-SHARED --subnet-pool
POOL-SHARED-EXTERNAL --prefix-length 28 SUBNET-INT-PUBLIC-SHARED
openstack bgp speaker add network BGP-REFLECTOR-SHARED NET-INT-PUBLIC-SHARED
openstack router create ROUTER-SHARED
openstack router set ROUTER-SHARED --disable-snat --external-gateway
NET-EXT-VLAN625-UPLINK
openstack router add subnet ROUTER-SHARED SUBNET-INT-PUBLIC-SHARED
openstack bgp speaker list advertised routes BGP-REFLECTOR-SHARED
Result:
+---+---+
| Destination | Nexthop |
+---+---+
| 93.115.169.128/28 | 192.0.2.6 |
+---+---+
Where 192.0.2.6 is the IP in the SNAT instance on
[Yahoo-eng-team] [Bug 1838811] Re: /opt/stack/devstack/tools/outfilter.py failing in neutron functional jobs since 8/2
** No longer affects: devstack ** Changed in: neutron Importance: Undecided => Critical -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1838811 Title: /opt/stack/devstack/tools/outfilter.py failing in neutron functional jobs since 8/2 Status in neutron: Fix Released Bug description: Seen here: https://logs.opendev.org/86/673486/4/gate/neutron-functional- python27/c3fe4df/ara-report/result/28d8d223-313a-49ba-b8aa- 8af15fdda973/ ++ ./stack.sh:main:500 : /opt/stack/devstack/tools/outfilter.py -v --no-timestamp -o /opt/stack/logs/devstacklog.txt.2019-08-02-160322 Traceback (most recent call last): File "/opt/stack/devstack/tools/outfilter.py", line 104, in sys.exit(main()) File "/opt/stack/devstack/tools/outfilter.py", line 61, in main outfile = open(opts.outfile, 'ab', 0) IOError: [Errno 13] Permission denied: '/opt/stack/logs/devstacklog.txt.2019-08-02-160322' Looks like it's a result of: https://review.opendev.org/#/c/203698/ Based on logstash data of that failure: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22IOError%3A%20%5BErrno%2013%5D%20Permission%20denied%3A%20'%2Fopt%2Fstack%2Flogs%2Fdevstacklog.txt%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1838811/+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 1832210] Re: fwaas netfilter_log: incorrect decode of log prefix under python 3
This bug was fixed in the package neutron-fwaas - 1:14.0.0-0ubuntu1.1~cloud0
---
neutron-fwaas (1:14.0.0-0ubuntu1.1~cloud0) bionic-stein; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
neutron-fwaas (1:14.0.0-0ubuntu1.1) disco; urgency=medium
.
[ Corey Bryant ]
* d/gbp.conf: Create stable/stein branch.
.
[ James Page ]
* d/p/netfilter_log-Correct-decode-binary-types.patch: Cherry pick fix
to resolve decoding of netfilter log prefix information under Python
3 (LP: #1832210).
** Changed in: cloud-archive/stein
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/1832210
Title:
fwaas netfilter_log: incorrect decode of log prefix under python 3
Status in Ubuntu Cloud Archive:
Fix Released
Status in Ubuntu Cloud Archive rocky series:
Fix Committed
Status in Ubuntu Cloud Archive stein series:
Fix Released
Status in Ubuntu Cloud Archive train series:
Fix Released
Status in neutron:
Fix Released
Status in neutron-fwaas package in Ubuntu:
Fix Released
Status in neutron-fwaas source package in Cosmic:
Won't Fix
Status in neutron-fwaas source package in Disco:
Fix Released
Status in neutron-fwaas source package in Eoan:
Fix Released
Bug description:
Under Python 3, the prefix of a firewall log message is not correctly
decoded "b'10612530182266949194'":
2019-06-10 09:14:34 Unknown cookie packet_in
pkt=ethernet(dst='fa:16:3e:c6:58:5e',ethertype=2048,src='fa:16:3e:e0:2c:be')ipv4(csum=51290,dst='10.5.0.10',flags=2,header_length=5,identification=37612,offset=0,option=None,proto=6,src='192.168.21.182',tos=16,total_length=52,ttl=63,version=4)tcp(ack=3151291228,bits=17,csum=23092,dst_port=57776,offset=8,option=[TCPOptionNoOperation(kind=1,length=1),
TCPOptionNoOperation(kind=1,length=1),
TCPOptionTimestamps(kind=8,length=10,ts_ecr=1574746440,ts_val=482688)],seq=2769917228,src_port=22,urgent=0,window_size=3120)
2019-06-10 09:14:34 {'prefix': "b'10612530182266949194'", 'msg':
"ethernet(dst='fa:16:3e:c6:58:5e',ethertype=2048,src='fa:16:3e:e0:2c:be')ipv4(csum=51290,dst='10.5.0.10',flags=2,header_length=5,identification=37612,offset=0,option=None,proto=6,src='192.168.21.182',tos=16,total_length=52,ttl=63,version=4)tcp(ack=3151291228,bits=17,csum=23092,dst_port=57776,offset=8,option=[TCPOptionNoOperation(kind=1,length=1),
TCPOptionNoOperation(kind=1,length=1),
TCPOptionTimestamps(kind=8,length=10,ts_ecr=1574746440,ts_val=482688)],seq=2769917228,src_port=22,urgent=0,window_size=3120)"}
2019-06-10 09:14:34 {'0bf81ded-bf94-437d-ad49-063bba9be9bb':
[,
]}
This results in the firewall log driver not being able to map the
message to the associated port and log resources in neutron resulting
in the 'unknown cookie packet_in' warning message.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1832210/+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 1832210] Re: fwaas netfilter_log: incorrect decode of log prefix under python 3
# apt-cache policy python3-neutron-fwaas
python3-neutron-fwaas:
Installed: 1:14.0.0-0ubuntu1.1~cloud0
Candidate: 1:14.0.0-0ubuntu1.1~cloud0
Version table:
*** 1:14.0.0-0ubuntu1.1~cloud0 500
500 http://ubuntu-cloud.archive.canonical.com/ubuntu
bionic-proposed/stein/main amd64 Packages
100 /var/lib/dpkg/status
Sample log messages:
Aug 5 09:17:33 juju-ccc3cd-bionic-stein-19 neutron-l3-agent: action=DROP,
project_id=8d69996595bf43568a66f6e4edb551b7,
log_resource_ids=['719c90e1-e6a4-49cb-a105-74cc86cff67f'],
port=79704b31-91a4-42ae-b66f-e356b2811df0,
pkt=ethernet(dst='fa:16:3e:97:b3:4f',ethertype=2048,src='fa:16:3e:41:6f:cc')ipv4(csum=20223,dst='192.168.21.92',flags=2,header_length=5,identification=3223,offset=0,option=None,proto=1,src='10.5.0.10',tos=0,total_length=84,ttl=63,version=4)icmp(code=0,csum=63684,data=echo(data=b'#\xf4G]\x00\x00\x00\x00\xc8\xc7\x03\x00\x00\x00\x00\x00\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\x1a\x1b\x1c\x1d\x1e\x1f
!"#$%&\'()*+,-./01234567',id=2227,seq=156),type=8)
Aug 5 09:17:34 juju-ccc3cd-bionic-stein-19 neutron-l3-agent: action=DROP,
project_id=8d69996595bf43568a66f6e4edb551b7,
log_resource_ids=['719c90e1-e6a4-49cb-a105-74cc86cff67f'],
port=79704b31-91a4-42ae-b66f-e356b2811df0,
pkt=ethernet(dst='fa:16:3e:97:b3:4f',ethertype=2048,src='fa:16:3e:41:6f:cc')ipv4(csum=20066,dst='192.168.21.92',flags=2,header_length=5,identification=3380,offset=0,option=None,proto=1,src='10.5.0.10',tos=0,total_length=84,ttl=63,version=4)icmp(code=0,csum=8550,data=echo(data=b'$\xf4G]\x00\x00\x00\x00\x9e%\x04\x00\x00\x00\x00\x00\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\x1a\x1b\x1c\x1d\x1e\x1f
!"#$%&\'()*+,-./01234567',id=2227,seq=157),type=8)
Aug 5 09:17:35 juju-ccc3cd-bionic-stein-19 neutron-l3-agent: action=ACCEPT,
project_id=8d69996595bf43568a66f6e4edb551b7,
log_resource_ids=['719c90e1-e6a4-49cb-a105-74cc86cff67f'],
port=79704b31-91a4-42ae-b66f-e356b2811df0,
pkt=ethernet(dst='fa:16:3e:97:b3:4f',ethertype=2048,src='fa:16:3e:41:6f:cc')ipv4(csum=2473,dst='192.168.21.92',flags=2,header_length=5,identification=20992,offset=0,option=None,proto=6,src='10.5.0.10',tos=0,total_length=60,ttl=63,version=4)tcp(ack=0,bits=2,csum=7323,dst_port=22,offset=10,option=[TCPOptionMaximumSegmentSize(kind=2,length=4,max_seg_size=8918),
TCPOptionSACKPermitted(kind=4,length=2),
TCPOptionTimestamps(kind=8,length=10,ts_ecr=0,ts_val=3542096121),
TCPOptionNoOperation(kind=1,length=1),
TCPOptionWindowScale(kind=3,length=3,shift_cnt=7)],seq=1338233633,src_port=46744,urgent=0,window_size=26754)
** Tags removed: verification-stein-needed
** Tags added: verification-stein-done
** Changed in: neutron-fwaas (Ubuntu Cosmic)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1832210
Title:
fwaas netfilter_log: incorrect decode of log prefix under python 3
Status in Ubuntu Cloud Archive:
Fix Released
Status in Ubuntu Cloud Archive rocky series:
Fix Committed
Status in Ubuntu Cloud Archive stein series:
Fix Released
Status in Ubuntu Cloud Archive train series:
Fix Released
Status in neutron:
Fix Released
Status in neutron-fwaas package in Ubuntu:
Fix Released
Status in neutron-fwaas source package in Cosmic:
Won't Fix
Status in neutron-fwaas source package in Disco:
Fix Released
Status in neutron-fwaas source package in Eoan:
Fix Released
Bug description:
Under Python 3, the prefix of a firewall log message is not correctly
decoded "b'10612530182266949194'":
2019-06-10 09:14:34 Unknown cookie packet_in
pkt=ethernet(dst='fa:16:3e:c6:58:5e',ethertype=2048,src='fa:16:3e:e0:2c:be')ipv4(csum=51290,dst='10.5.0.10',flags=2,header_length=5,identification=37612,offset=0,option=None,proto=6,src='192.168.21.182',tos=16,total_length=52,ttl=63,version=4)tcp(ack=3151291228,bits=17,csum=23092,dst_port=57776,offset=8,option=[TCPOptionNoOperation(kind=1,length=1),
TCPOptionNoOperation(kind=1,length=1),
TCPOptionTimestamps(kind=8,length=10,ts_ecr=1574746440,ts_val=482688)],seq=2769917228,src_port=22,urgent=0,window_size=3120)
2019-06-10 09:14:34 {'prefix': "b'10612530182266949194'", 'msg':
"ethernet(dst='fa:16:3e:c6:58:5e',ethertype=2048,src='fa:16:3e:e0:2c:be')ipv4(csum=51290,dst='10.5.0.10',flags=2,header_length=5,identification=37612,offset=0,option=None,proto=6,src='192.168.21.182',tos=16,total_length=52,ttl=63,version=4)tcp(ack=3151291228,bits=17,csum=23092,dst_port=57776,offset=8,option=[TCPOptionNoOperation(kind=1,length=1),
TCPOptionNoOperation(kind=1,length=1),
TCPOptionTimestamps(kind=8,length=10,ts_ecr=1574746440,ts_val=482688)],seq=2769917228,src_port=22,urgent=0,window_size=3120)"}
2019-06-10 09:14:34 {'0bf81ded-bf94-437d-ad49-063bba9be9bb':
[,
]}
This results in the firewall log driver not being able to map the
message to the associated port and log resources in neutron resulting
in the 'unknown cookie pa
[Yahoo-eng-team] [Bug 1838952] [NEW] security_group_rule is not correctly processed with legacy neutron
Public bug reported: If neutron does not support quota_details, currently horizon is broken emitting KeyError below. [Mon Aug 05 18:14:59.218082 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] File "/var/lib/kolla/venv/lib/python3.6/site-packages/horizon/tables/views.py", line 226, in get [Mon Aug 05 18:14:59.218086 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] context = self.get_context_data(**kwargs) [Mon Aug 05 18:14:59.218090 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] File "/var/lib/kolla/venv/lib/python3.6/site-packages/openstack_dashboard/usage/views.py", line 201, in get_context_data [Mon Aug 05 18:14:59.218097 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] context['charts'] = self._get_charts_data() [Mon Aug 05 18:14:59.218101 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] File "/var/lib/kolla/venv/lib/python3.6/site-packages/openstack_dashboard/usage/views.py", line 154, in _get_charts_data [Mon Aug 05 18:14:59.218105 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] chart_data = self._process_chart_section(section['charts']) [Mon Aug 05 18:14:59.218109 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] File "/var/lib/kolla/venv/lib/python3.6/site-packages/openstack_dashboard/usage/views.py", line 170, in _process_chart_section [Mon Aug 05 18:14:59.218113 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] used = self.usage.limits[key]['used'] [Mon Aug 05 18:14:59.218119 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] KeyError: 'used' [Mon Aug 05 18:14:59.218127 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] It's due to the function _get_neutron_quota_data() in that the function add the key 'security_group_rules' but _get_tenant_network_usages_legacy() does not 'tally' the key 'security_group_rules'. usages['security_group_rules'] now only have 'quota' key without 'used'. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1838952 Title: security_group_rule is not correctly processed with legacy neutron Status in OpenStack Dashboard (Horizon): New Bug description: If neutron does not support quota_details, currently horizon is broken emitting KeyError below. [Mon Aug 05 18:14:59.218082 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] File "/var/lib/kolla/venv/lib/python3.6/site-packages/horizon/tables/views.py", line 226, in get [Mon Aug 05 18:14:59.218086 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] context = self.get_context_data(**kwargs) [Mon Aug 05 18:14:59.218090 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] File "/var/lib/kolla/venv/lib/python3.6/site-packages/openstack_dashboard/usage/views.py", line 201, in get_context_data [Mon Aug 05 18:14:59.218097 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] context['charts'] = self._get_charts_data() [Mon Aug 05 18:14:59.218101 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] File "/var/lib/kolla/venv/lib/python3.6/site-packages/openstack_dashboard/usage/views.py", line 154, in _get_charts_data [Mon Aug 05 18:14:59.218105 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] chart_data = self._process_chart_section(section['charts']) [Mon Aug 05 18:14:59.218109 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] File "/var/lib/kolla/venv/lib/python3.6/site-packages/openstack_dashboard/usage/views.py", line 170, in _process_chart_section [Mon Aug 05 18:14:59.218113 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] used = self.usage.limits[key]['used'] [Mon Aug 05 18:14:59.218119 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] KeyError: 'used' [Mon Aug 05 18:14:59.218127 2019] [wsgi:error] [pid 34:tid 140353969415936] [remote 172.26.100.219:53513] It's due to the function _get_neutron_quota_data() in that the function add the key 'security_group_rules' but _get_tenant_network_usages_legacy() does not 'tally' the key 'security_group_rules'. usages['security_group_rules'] now only have 'quota' key without 'used'. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1838952/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-e
[Yahoo-eng-team] [Bug 1838950] Re: "Domain" panel under Identity is missing
** Changed in: horizon Status: New => Invalid -- 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/1838950 Title: "Domain" panel under Identity is missing Status in OpenStack Dashboard (Horizon): Invalid Bug description: I am following this document for the Horizon development environment. When I run 'tox -e runserver' everything works fine but 'Domain' panel is missing under identity panel however, it is visible in my devstack setup. Steps to Reproduce: 1. Deploy OpenStack using devstack. 2. clone horizon repo https://opendev.org/openstack/horizon 3. Enter your devstack keystone url in 'OPENSTACK_KEYSTONE_URL' variable in openstack_dashboard/local/local_settings.py file. 4. Run tox -e runserver 5. Go to identity Panel. 6. Domain panel under Identity is missing. I don,t know whether I have to enable some setting in my local_settings.py file? To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1838950/+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 1838950] [NEW] "Domain" panel under Identity is missing
Public bug reported: I am following this document for the Horizon development environment. When I run 'tox -e runserver' everything works fine but 'Domain' panel is missing under identity panel however, it is visible in my devstack setup. Steps to Reproduce: 1. Deploy OpenStack using devstack. 2. clone horizon repo https://opendev.org/openstack/horizon 3. Enter your devstack keystone url in 'OPENSTACK_KEYSTONE_URL' variable in openstack_dashboard/local/local_settings.py file. 4. Run tox -e runserver 5. Go to identity Panel. 6. Domain panel under Identity is missing. I don,t know whether I have to enable some setting in my local_settings.py file? ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1838950 Title: "Domain" panel under Identity is missing Status in OpenStack Dashboard (Horizon): New Bug description: I am following this document for the Horizon development environment. When I run 'tox -e runserver' everything works fine but 'Domain' panel is missing under identity panel however, it is visible in my devstack setup. Steps to Reproduce: 1. Deploy OpenStack using devstack. 2. clone horizon repo https://opendev.org/openstack/horizon 3. Enter your devstack keystone url in 'OPENSTACK_KEYSTONE_URL' variable in openstack_dashboard/local/local_settings.py file. 4. Run tox -e runserver 5. Go to identity Panel. 6. Domain panel under Identity is missing. I don,t know whether I have to enable some setting in my local_settings.py file? To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1838950/+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
