[Yahoo-eng-team] [Bug 2043873] Re: Unexpected API Error
[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/2043873 Title: Unexpected API Error Status in OpenStack Compute (nova): Expired Bug description: The following error was mainstay when trying to create/start an instance with the openstack server create command and logged as a Nova API bug to raise a report. (HTTP 500) (Request-ID: req-0b7361e3-bb66-4e61-b6bc-782861a80b3a) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/2043873/+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 2045111] Re: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
[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/2045111 Title: 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-0971807f-dc3f-4882-8a1f-c7c24b86aa0e) Status in OpenStack Compute (nova): Expired Bug description: we are running openstack on 22.04 qemu .Cant create an instance on the self-service network (we have created flavor,attached network list, security group,keypair,rule, but instanace is not creating )[command used "openstack server create --flavor m1.nano --image cirros --nic net-id=1fbb66da-7362-4ba9-851b-f9251b3e12e2 --security-group 424fd166-6252-4118-97d6-7062aad3c9eb--key-name mykey inbinternet"]. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/2045111/+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 2046510] Re: neutron-servers have high memory usage
[Expired for neutron because there has been no activity for 60 days.] ** Changed in: neutron Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2046510 Title: neutron-servers have high memory usage Status in neutron: Expired Bug description: USERPID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND neutron 11686 6.8 7.3 29205516 28869568 ? SNov30 1438:32 /usr/bin/python2 /usr/bin/neutron-server --config-file /usr/share/neutron/neutron-dist.conf --config-dir /usr/share/neutron/server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini --config-dir /etc/neutron/conf.d/common --config-dir /etc/neutron/conf.d/neutron-server --log-file /var/log/neutron/server.log neutron 11678 5.3 5.9 23972284 23636560 ? SNov30 1117:52 /usr/bin/python2 /usr/bin/neutron-server --config-file /usr/share/neutron/neutron-dist.conf --config-dir /usr/share/neutron/server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini --config-dir /etc/neutron/conf.d/common --config-dir /etc/neutron/conf.d/neutron-server --log-file /var/log/neutron/server.log neutron 11677 23.3 5.9 23925788 23590656 ? SNov30 4882:29 /usr/bin/python2 /usr/bin/neutron-server --config-file /usr/share/neutron/neutron-dist.conf --config-dir /usr/share/neutron/server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini --config-dir /etc/neutron/conf.d/common --config-dir /etc/neutron/conf.d/neutron-server --log-file /var/log/neutron/server.log neutron 11694 21.7 5.9 23909852 23574128 ? SNov30 4550:55 /usr/bin/python2 /usr/bin/neutron-server --config-file /usr/share/neutron/neutron-dist.conf --config-dir /usr/share/neutron/server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini --config-dir /etc/neutron/conf.d/common --config-dir /etc/neutron/conf.d/neutron-server --log-file /var/log/neutron/server.log neutron 11693 16.4 5.9 23624384 23288660 ? SNov30 3431:10 /usr/bin/python2 /usr/bin/neutron-server --config-file /usr/share/neutron/neutron-dist.conf --config-dir /usr/share/neutron/server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini --config-dir /etc/neutron/conf.d/common --config-dir /etc/neutron/conf.d/neutron-server --log-file /var/log/neutron/server.log neutron 11696 4.2 5.5 22357296 22021572 ? SNov30 878:51 /usr/bin/python2 /usr/bin/neutron-server --config-file /usr/share/neutron/neutron-dist.conf --config-dir /usr/share/neutron/server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini --config-dir /etc/neutron/conf.d/common --config-dir /etc/neutron/conf.d/neutron-server --log-file /var/log/neutron/server.log You may see the RSS reachs 28869568KB, it's about 20G+ memory. Openstack version: stable/rocky To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2046510/+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 2054203] [NEW] Default flag change in netaddr breaks (at least) unit tests
Public bug reported:
netaddr 1.0.0 changed the default parsing mode from INET_ATON to
INET_PTON[1]. This was initially added to netaddr.IPAddress and then
later was applied to netaddr.IPNetwork in 1.1.0 [2]
While we attempted to bump netaddr to 1.0.1, we noticed this change
broke some of the unit tests in neutron.
https://zuul.opendev.org/t/openstack/build/8cfad48dcfb84be893fe78a1f965c5e6
(example)
```
neutron.tests.unit.agent.l3.extensions.test_ndp_proxy.NDPProxyExtensionDVRTestCase.test__get_snat_idx_ipv4
--
Captured traceback:
~~~
Traceback (most recent call last):
File
"/home/zuul/src/opendev.org/openstack/neutron/.tox/py311/lib/python3.11/site-packages/netaddr/ip/__init__.py",
line 346, in __init__
self._value = self._module.str_to_int(addr, flags)
File
"/home/zuul/src/opendev.org/openstack/neutron/.tox/py311/lib/python3.11/site-packages/netaddr/strategy/ipv4.py",
line 120, in str_to_int
raise error
netaddr.core.AddrFormatError: '101.12.13.00' is not a valid IPv4 address
string!
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/home/zuul/src/opendev.org/openstack/neutron/.tox/py311/lib/python3.11/site-packages/netaddr/ip/__init__.py",
line 1019, in __init__
value, prefixlen = parse_ip_network(module, addr, flags)
^
File
"/home/zuul/src/opendev.org/openstack/neutron/.tox/py311/lib/python3.11/site-packages/netaddr/ip/__init__.py",
line 899, in parse_ip_network
ip = IPAddress(val1, module.version, flags=INET_PTON)
File
"/home/zuul/src/opendev.org/openstack/neutron/.tox/py311/lib/python3.11/site-packages/netaddr/ip/__init__.py",
line 348, in __init__
raise AddrFormatError(
netaddr.core.AddrFormatError: base address '101.12.13.00' is not IPv4
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/home/zuul/src/opendev.org/openstack/neutron/neutron/tests/base.py", line 178,
in func
return f(self, *args, **kwargs)
File
"/home/zuul/src/opendev.org/openstack/neutron/neutron/tests/base.py", line 178,
in func
return f(self, *args, **kwargs)
File
"/home/zuul/src/opendev.org/openstack/neutron/neutron/tests/unit/agent/l3/test_dvr_local_router.py",
line 549, in test__get_snat_idx_ipv4
snat_idx = ri._get_snat_idx(ip_cidr)
^
File
"/home/zuul/src/opendev.org/openstack/neutron/neutron/agent/l3/dvr_local_router.py",
line 412, in _get_snat_idx
net = netaddr.IPNetwork(ip_cidr)
^^
File
"/home/zuul/src/opendev.org/openstack/neutron/.tox/py311/lib/python3.11/site-packages/netaddr/ip/__init__.py",
line 1028, in __init__
raise AddrFormatError('invalid IPNetwork %s' % (addr,))
netaddr.core.AddrFormatError: invalid IPNetwork 101.12.13.00/24
```
An "easy" fix is adding flags=INET_ATON to all places. (note that
INET_ATON was added in netaddr 0.10.0) but I'd like to ask someone from
the neutron team to look into this and check whether we really have to
use INET_ATON or fix unit test side to apply the more strict rule.
[1] https://netaddr.readthedocs.io/en/latest/changes.html#release-1-0-0
[2] https://netaddr.readthedocs.io/en/latest/changes.html#release-1-1-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/2054203
Title:
Default flag change in netaddr breaks (at least) unit tests
Status in neutron:
New
Bug description:
netaddr 1.0.0 changed the default parsing mode from INET_ATON to
INET_PTON[1]. This was initially added to netaddr.IPAddress and then
later was applied to netaddr.IPNetwork in 1.1.0 [2]
While we attempted to bump netaddr to 1.0.1, we noticed this change
broke some of the unit tests in neutron.
https://zuul.opendev.org/t/openstack/build/8cfad48dcfb84be893fe78a1f965c5e6
(example)
```
neutron.tests.unit.agent.l3.extensions.test_ndp_proxy.NDPProxyExtensionDVRTestCase.test__get_snat_idx_ipv4
--
Captured traceback:
~~~
Traceback (most recent call last):
File
"/home/zuul/src/opendev.org/openstack/neutron/.tox/py311/lib/python3.11/site-packages/netaddr/ip/__init__.py",
line 346, in __init__
self._value = self._module.str_to_int(addr, flags)
