[Yahoo-eng-team] [Bug 1607395] Re: Traceback in dynamic metadata driver: unexpected keyword argument 'extra_md'
The vendordata_driver option was already removed. So we may not "fix" this problem really. ** Changed in: nova Status: Incomplete => Invalid -- 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/1607395 Title: Traceback in dynamic metadata driver: unexpected keyword argument 'extra_md' Status in OpenStack Compute (nova): Invalid Bug description: Using new dynamic metadata driver fails with a traceback: ERROR nova.api.metadata.handler [req-d4df1623-dc4a-4e9c-b129-1e5dd76c59ac None None] Failed to get metadata for IP 10.0.0.3 TRACE nova.api.metadata.handler Traceback (most recent call last): TRACE nova.api.metadata.handler File "/home/stack/openstack/nova/nova/api/metadata/handler.py", line 134, in _handle_remote_ip_request TRACE nova.api.metadata.handler meta_data = self.get_metadata_by_remote_address(remote_address) TRACE nova.api.metadata.handler File "/home/stack/openstack/nova/nova/api/metadata/handler.py", line 61, in get_metadata_by_remote_address TRACE nova.api.metadata.handler data = base.get_metadata_by_address(address) TRACE nova.api.metadata.handler File "/home/stack/openstack/nova/nova/api/metadata/base.py", line 660, in get_metadata_by_address TRACE nova.api.metadata.handler ctxt) TRACE nova.api.metadata.handler File "/home/stack/openstack/nova/nova/api/metadata/base.py", line 670, in get_metadata_by_instance_id TRACE nova.api.metadata.handler return InstanceMetadata(instance, address) TRACE nova.api.metadata.handler File "/home/stack/openstack/nova/nova/api/metadata/base.py", line 195, in __init__ TRACE nova.api.metadata.handler extra_md=extra_md, network_info=network_info) TRACE nova.api.metadata.handler TypeError: __init__() got an unexpected keyword argument 'extra_md' This is the configuration: vendordata_providers = StaticJSON, DynamicJSON vendordata_dynamic_targets = 'join@http://127.0.0.1:/v1/' vendordata_driver = nova.api.metadata.vendordata_dynamic.DynamicVendorData vendordata_dynamic_connect_timeout = 5 vendordata_dynamic_read_timeout = 30 vendordata_jsonfile_path = /etc/nova/cloud-config.json To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1607395/+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 1259760] Re: Spice console isn't working when ssl_only=True is set
** Changed in: nova Status: Incomplete => Invalid -- 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/1259760 Title: Spice console isn't working when ssl_only=True is set Status in OpenStack Nova Cloud Controller Charm: Invalid Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive queens series: Fix Released Status in OpenStack Compute (nova): Invalid Status in spice-html5 package in Ubuntu: Fix Released Bug description: OpenStack instalation: 2013.2 OS: Ubuntu 13.10 Repo: standart Ubuntu repozitory When using ssl_only in nova.conf, browser gets error: [Exception... "The operation is insecure." code: "18" nsresult: "0x80530012 (SecurityError)" location: "https://api.region.domain.tld:6082/spiceconn.js Line: 34"] Problem: trying to reach using ws:// schema, not wss://. Temporary fixed changing /usr/share/spice-html5/spice_auto.html scheme = "wss://" at 82th line. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1259760/+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 2051066] [NEW] Traceback is dumped when nova-api is run by apache + mod_wsgi
Public bug reported: Description === We noticed that the following traceback is dumped to error log in httpd when nova-api is run by httpd + mod_wsgi. This is because nova-api WSGI application attempts to register signal handers for GMR but this is blocked y httpd. This does not cause any functional problem, but is annoying for operators, and we should consider the way to surpress these warnings. [Mon Jan 22 06:29:49.889120 2024] [wsgi:warn] [pid 82455:tid 82557] mod_wsgi (pid=82455): Callback registration for signal 12 ignored. [Mon Jan 22 06:29:49.889918 2024] [wsgi:warn] [pid 82455:tid 82557] File "/var/www/cgi-bin/nova/nova-api", line 52, in [Mon Jan 22 06:29:49.889937 2024] [wsgi:warn] [pid 82455:tid 82557] application = init_application() [Mon Jan 22 06:29:49.889955 2024] [wsgi:warn] [pid 82455:tid 82557] File "/usr/lib/python3.9/site-packages/nova/api/openstack/compute/wsgi.py", line 20, in init_application [Mon Jan 22 06:29:49.889967 2024] [wsgi:warn] [pid 82455:tid 82557] return wsgi_app.init_application(NAME) [Mon Jan 22 06:29:49.889983 2024] [wsgi:warn] [pid 82455:tid 82557] File "/usr/lib/python3.9/site-packages/nova/api/openstack/wsgi_app.py", line 128, in init_application [Mon Jan 22 06:29:49.889994 2024] [wsgi:warn] [pid 82455:tid 82557] init_global_data(conf_files, name) [Mon Jan 22 06:29:49.890027 2024] [wsgi:warn] [pid 82455:tid 82557] File "/usr/lib/python3.9/site-packages/nova/utils.py", line 1133, in wrapper [Mon Jan 22 06:29:49.890039 2024] [wsgi:warn] [pid 82455:tid 82557] return func(*args, **kwargs) [Mon Jan 22 06:29:49.890054 2024] [wsgi:warn] [pid 82455:tid 82557] File "/usr/lib/python3.9/site-packages/nova/api/openstack/wsgi_app.py", line 105, in init_global_data [Mon Jan 22 06:29:49.890065 2024] [wsgi:warn] [pid 82455:tid 82557] gmr.TextGuruMeditation.setup_autorun( [Mon Jan 22 06:29:49.890080 2024] [wsgi:warn] [pid 82455:tid 82557] File "/usr/lib/python3.9/site-packages/oslo_reports/guru_meditation_report.py", line 155, in setup_autorun [Mon Jan 22 06:29:49.890091 2024] [wsgi:warn] [pid 82455:tid 82557] cls._setup_signal(signal.SIGUSR2, [Mon Jan 22 06:29:49.890106 2024] [wsgi:warn] [pid 82455:tid 82557] File "/usr/lib/python3.9/site-packages/oslo_reports/guru_meditation_report.py", line 188, in _setup_signal [Mon Jan 22 06:29:49.890117 2024] [wsgi:warn] [pid 82455:tid 82557] signal.signal(signum, Steps to reproduce == * Install httpd * Add vhost to run nova-api * Start httpd Expected result === No traceback appears in error.log Actual result = Traceback appears in error.log Environment === This issue wsa initially found in CentOS Stream 9 + RDO master. httpd-2.4.57-6.el9.x86_64 openstack-nova-api-28.1.0-0.20240111050756.fed1230.el9.noarch openstack-nova-common-28.1.0-0.20240111050756.fed1230.el9.noarch openstack-nova-compute-28.1.0-0.20240111050756.fed1230.el9.noarch openstack-nova-conductor-28.1.0-0.20240111050756.fed1230.el9.noarch openstack-nova-novncproxy-28.1.0-0.20240111050756.fed1230.el9.noarch openstack-nova-scheduler-28.1.0-0.20240111050756.fed1230.el9.noarch Logs & Configs == Example log: https://cab2ad659632c7fadcca-8cee698db2ecce5ea7fdb78c34542529.ssl.cf1.rackcdn.com/906237/1/check/puppet-openstack-integration-7-scenario001-tempest-centos-9-stream/29e7836/logs/apache/nova_api_wsgi_error_ssl.txt ** Affects: nova Importance: Undecided Assignee: Takashi Kajinami (kajinamit) Status: In Progress ** Changed in: nova Assignee: (unassigned) => Takashi Kajinami (kajinamit) -- 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/2051066 Title: Traceback is dumped when nova-api is run by apache + mod_wsgi Status in OpenStack Compute (nova): In Progress Bug description: Description === We noticed that the following traceback is dumped to error log in httpd when nova-api is run by httpd + mod_wsgi. This is because nova-api WSGI application attempts to register signal handers for GMR but this is blocked y httpd. This does not cause any functional problem, but is annoying for operators, and we should consider the way to surpress these warnings. [Mon Jan 22 06:29:49.889120 2024] [wsgi:warn] [pid 82455:tid 82557] mod_wsgi (pid=82455): Callback registration for signal 12 ignored. [Mon Jan 22 06:29:49.889918 2024] [wsgi:warn] [pid 82455:tid 82557] File "/var/www/cgi-bin/nova/nova-api", line 52, in [Mon Jan 22 06:29:49.889937 2024] [wsgi:warn] [pid 82455:tid 82557] application = init_application() [Mon Jan 22 06:29:49.889955 2024] [wsgi:warn] [pid 82455:tid 82557] File "/usr/lib/python3.9/site-packages/nova/api/openstack/compute/wsgi.py", line 20, in init_application [Mon Jan 22 06:29:49.889967 2024] [wsgi:warn] [pid 82455:tid 82557]
[Yahoo-eng-team] [Bug 2049211] Re: neutron_tempest_plugin.api sorted() Function Issue
Reviewed:
https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/905853
Committed:
https://opendev.org/openstack/neutron-tempest-plugin/commit/71a73245083f0135aea2fb063fd3dd7332ff08e1
Submitter: "Zuul (22348)"
Branch:master
commit 71a73245083f0135aea2fb063fd3dd7332ff08e1
Author: Martin Kopec
Date: Wed Jan 17 12:02:24 2024 +0100
Fix network sorting in API tests
There is a mismatch in some tests because sorted() sorts in ASCII
order - digits are followed by uppercase characters and then
lowercase characters. That doesn't work if a network's name starts
with a capital letter.
Closes-Bug: #2049211
Change-Id: I8328d7d8ca7b49b99feb24d77525abdc064aae80
** 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/2049211
Title:
neutron_tempest_plugin.api sorted() Function Issue
Status in neutron:
Fix Released
Bug description:
Hi,
We got mismatch error in some tests as below. I debugged it and the
test passes if we change sorted() function. Because sorted() function
sorts by ascii character. When sorted in ASCII order, digits are
followed by uppercase characters and then lowercase characters. If I
have a network name starting with a capital letter, it gives an error.
If we change the sorted() function as follows, the test passed.
expected = sorted(retrieved_names, key=lambda x: (x.isdigit(), x.upper(),
x.lower()))
Example tests:
neutron_tempest_plugin.api.test_networks.NetworksSearchCriteriaTest.test_list_sorts_asc
neutron_tempest_plugin.api.test_networks.NetworksSearchCriteriaTest.test_list_sorts_desc
neutron_tempest_plugin.api.test_subnets.SubnetsSearchCriteriaTest.test_list_sorts_asc
neutron_tempest_plugin.api.test_subnets.SubnetsSearchCriteriaTest.test_list_sorts_desc
neutron_tempest_plugin.api.test_security_groups.SecGroupSearchCriteriaTest.test_list_sorts_by_name_asc
neutron_tempest_plugin.api.test_security_groups.SecGroupSearchCriteriaTest.test_list_sorts_by_name_desc
File: /etc/tempest/neutron-tempest-plugin/neutron_tempest_plugin/api/base.py
```
...
def _test_list_sorts(self, direction):
sort_args = {
'sort_dir': direction,
'sort_key': self.field
}
body = self.list_method(**sort_args)
resources = self._extract_resources(body)
self.assertNotEmpty(
resources, "%s list returned is empty" % self.resource)
retrieved_names = [res[self.field] for res in resources]
expected = sorted(retrieved_names)
if direction == constants.SORT_DIRECTION_DESC:
expected = list(reversed(expected))
self.assertEqual(expected, retrieved_names)
...
```
Debug:
retrieved_names
['', '', '', '123test', 'abc1', 'admin-x-x-net-01',
'admin-x-x-net-01', 'x--net', 'HA network tenant
2b09e7b2e1244fd4be2dc4092e39d17b', 'lb--net', 'm-temp--net',
'mxxx-xxx-xxx-net', 'mxxx---net', 'port-search-test-net',
'subnet-search-test-net', 'subnet-search-test-net', 'subnet-search-test-net',
'tempest-bgp-net', 'tempest-internal-dns-test-network-1876397349',
'tempest-internal-dns-test-network-332103665',
'tempest-MetadataTest-2030842204', 'tempest-test-network--1146463009',
'tempest-test-network--1164657513', 'tempest-test-network--1229813769',
'tempest-test-network--1233298883', 'tempest-test-network--1331054017',
'tempest-test-network--1415812209', 'tempest-test-network--1420967741',
'tempest-test-network--1424837927', 'tempest-test-network--1522800460',
'tempest-test-network--1542595587', 'tempest-test-network--1602874451',
'tempest-test-network--1651416667', 'tempest-test-network--1756609168',
'tempest-test-network--2053127518', '
tempest-test-network--2065848286', 'tempest-test-network--2086276043',
'tempest-test-network--234088028', 'tempest-test-network--303087501',
'tempest-test-network--377750320', 'tempest-test-network--433648246',
'tempest-test-network--488800423', 'tempest-test-network--52430',
'tempest-test-network--586734631', 'tempest-test-network--602944876',
'tempest-test-network--653992987', 'tempest-test-network-884004988', 'test1',
'test1', 'test10', 'testproject-other-net']
(Pdb) print(sorted(retrieved_names))
print(sorted(retrieved_names))
['', '', '', '123test', 'HA network tenant 2b09e7b2e1244fd4be2dc4092e39d17b',
'abc1', 'admin-x-x-net-01', 'admin-vprotect-provider-net-01',
'devxxx-xxx-net', 'lxxx-xxx-net', 'mxxx--x-net', 'mxxx--x-net',
'mxxx-xxx--net', 'port-search-test-net', 'subnet-search-test-net',
'subnet-search-test-net', 'subnet-search-test-net',
'tempest-MetadataTest-2030842204', 'tempest-bgp-net',
'tempest-internal-dns-test-network-1876397349',
[Yahoo-eng-team] [Bug 2026345] Re: Sphinx raises 'ImageDraw' object has no attribute 'textsize' error
Reviewed: https://review.opendev.org/c/openstack/nova/+/906309 Committed: https://opendev.org/openstack/nova/commit/cc25813b6d07e00dbdfb52f5b1c8bedfc25c74ff Submitter: "Zuul (22348)" Branch:master commit cc25813b6d07e00dbdfb52f5b1c8bedfc25c74ff Author: Sylvain Bauza Date: Mon Jan 22 15:55:47 2024 +0100 doc: drop blockdiag usage Since blockdiag seems a bit unmaintenained, let's just statically generate the SVGs but let's keep the source files in tree so we can modify the diagrams whenever we want, provided blockdiag exists in a foreseenable future :-) Closes-Bug: #2026345 Change-Id: I1cc078554ab149a9849c895e08c878180b7510b0 ** 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/2026345 Title: Sphinx raises 'ImageDraw' object has no attribute 'textsize' error Status in Designate: Fix Released Status in Ironic: Confirmed Status in OpenStack Identity (keystone): New Status in OpenStack Compute (nova): Fix Released Status in octavia: In Progress Status in tacker: Fix Released Bug description: Pillow version 10.0 or higher sphinx raises error. ''' 'ImageDraw' object has no attribute 'textsize' ''' Tacker specs use sphinx and pillow to build some diagrams in .rst file. Pillow remove ImageDraw.textsize() form version 10.0[1], but sphinx use ImageDraw.textsize(). [1] https://pillow.readthedocs.io/en/stable/releasenotes/10.0.0.html#font- size-and-offset-methods To manage notifications about this bug go to: https://bugs.launchpad.net/designate/+bug/2026345/+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
