[Yahoo-eng-team] [Bug 1853223] [NEW] [VPNaaS]: Python3 RuntimeError: dictionary changed size during iteration
Public bug reported: PY3 runtime error in driver report status: Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall [-] Fixed interval looping call 'neutron_vpnaas.services.vpn.device_drivers.strongswan_ipsec.IPsecDriver.report_status' failed: RuntimeError: dictionary changed size during iteration Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall Traceback (most recent call last): Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall File "/usr/local/lib/python3.6/dist-packages/oslo_service/loopingcall.py", line 150, in _run_loop Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall result = func(*self.args, **self.kw) Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall File "/usr/local/lib/python3.6/dist-packages/oslo_log/helpers.py", line 67, in wrapper Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall return method(*args, **kwargs) Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall File "/opt/stack/neutron-vpnaas/neutron_vpnaas/services/vpn/device_drivers/ipsec.py", line 1067, in report_status Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall for process_id, process in self.processes.items(): Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall RuntimeError: dictionary changed size during iteration Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall Please search RuntimeError in log[1][2] [1] https://f68629e21ed230feb603-193839948e82df3f7b6031d1afea5d13.ssl.cf5.rackcdn.com/659063/8/check /neutron-vpnaas-tempest/4e5241b/controller/logs/screen-q-l3.txt.gz [2] https://c808c0465a7aa7421965-eb83075bad77f107ed9b57803fd20c1f.ssl.cf2.rackcdn.com/693965/1/check /neutron-vpnaas-tempest/3dde8e5/controller/logs/screen-q-l3.txt.gz ** Affects: neutron Importance: Undecided Assignee: Dongcan Ye (hellochosen) Status: New ** Tags: vpnaas ** Changed in: neutron Assignee: (unassigned) => Dongcan Ye (hellochosen) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1853223 Title: [VPNaaS]: Python3 RuntimeError: dictionary changed size during iteration Status in neutron: New Bug description: PY3 runtime error in driver report status: Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall [-] Fixed interval looping call 'neutron_vpnaas.services.vpn.device_drivers.strongswan_ipsec.IPsecDriver.report_status' failed: RuntimeError: dictionary changed size during iteration Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall Traceback (most recent call last): Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall File "/usr/local/lib/python3.6/dist-packages/oslo_service/loopingcall.py", line 150, in _run_loop Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall result = func(*self.args, **self.kw) Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall File "/usr/local/lib/python3.6/dist-packages/oslo_log/helpers.py", line 67, in wrapper Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall return method(*args, **kwargs) Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall File "/opt/stack/neutron-vpnaas/neutron_vpnaas/services/vpn/device_drivers/ipsec.py", line 1067, in report_status Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall for process_id, process in self.processes.items(): Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall RuntimeError: dictionary changed size during iteration Nov 13 03:13:11.221694 ubuntu-bionic-rax-iad-0012769742 neutron-l3-agent[20209]: ERROR oslo.service.loopingcall Please search RuntimeError in log[1][2] [1] https://f68629e21ed230feb603-193839948e82df3f7b6031d1afea5d13.ssl.cf5.rackcdn.com/659063/8/check /neutron-vpnaas-tempest/4e5241b/controller/logs/screen-q-l3.txt.gz [2] https://c808c0465a7aa7421965-eb83075bad77f107ed9b57803
[Yahoo-eng-team] [Bug 1853089] Re: openstack env in Stein, CLI or Dashboard response slowly
Hi, Same comments as in #1 and #2 above from Neutron. To treat this as a bug, we need more specific data. Marking it invalid until more is reported ** Changed in: neutron Status: New => 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/1853089 Title: openstack env in Stein, CLI or Dashboard response slowly Status in neutron: Invalid Status in OpenStack Compute (nova): Invalid Bug description: Installed Stein OpenStack via Kolla, OpenStack node info as below: 3 * Controller node which running in Virtualbox --- each machine memory: 32G and Disk:300G 2 * Compute node which is physical rack server after operating in some days, the OpenStack response become very slow, the dashboard response is more slower. for example: run "openstack port list --timing" in CLI, it would spent about 13s when got 60 port data, and dashboard would spent more than 20s. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1853089/+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 1744670] Re: In pike ssl deployment horizon cnt retrieve volumes/snapshots and service data via cinderclient
Reviewed: https://review.opendev.org/675894
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=285c51f7e1b27a786fa9684abdc489998285b4e2
Submitter: Zuul
Branch:master
commit 285c51f7e1b27a786fa9684abdc489998285b4e2
Author: Ivan Kolodyazhny
Date: Mon Aug 12 16:19:44 2019 +0300
Add custom SSL CA Cert support for api.cinder.get_microversion
api.cinder.get_microversion function now supports OPENSTACK_SSL_NO_VERIFY
and OPENSTACK_SSL_CACERT config options.
This depends on commit 4a3a2c3c9a89ccff4e64d3da96de5b0af4303840 in
python-cinderclient, so the minimum version of python-cinderclient
is bumped to 5.0.0.
NOTE(amotoki): The stretegy of backporting to stable branches needs
a discussion with the requirements team as we cannot bump the
minimum version (at least the major version bump is surprising).
Change-Id: I22c6c60e10d8e9328f7f1e0c24d6c74496ec1a71
Closes-Bug: 1744670
** Changed in: horizon
Status: In Progress => Fix Released
--
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/1744670
Title:
In pike ssl deployment horizon cnt retrieve volumes/snapshots and
service data via cinderclient
Status in OpenStack Dashboard (Horizon):
Fix Released
Status in keystoneauth:
Incomplete
Status in python-cinderclient:
Confirmed
Bug description:
Ops packages versions:
openstack-cinder.noarch 11.0.1-1.el7
openstack-dashboard.noarch 12.0.1-1.el7
openstack-glance.noarch 15.0.0-2.el7
openstack-keystone.noarch 12.0.0-1.el7
openstack-neutron.noarch11.0.2-2.el7
openstack-neutron-common.noarch 11.0.2-2.el7
openstack-neutron-ml2.noarch11.0.2-2.el7
openstack-nova-api.noarch 16.0.3-2.el7
openstack-nova-common.noarch16.0.3-2.el7
openstack-nova-conductor.noarch 16.0.3-2.el7
openstack-nova-console.noarch 16.0.3-2.el7
openstack-nova-novncproxy.noarch16.0.3-2.el7
openstack-nova-placement-api.noarch 16.0.3-2.el7
openstack-nova-scheduler.noarch 16.0.3-2.el7
python2-cinderclient.noarch 3.1.0-1.el7
Only after applying hard-coded links to certificate in cinder-client
and keystone, the dashboard starts working:
/cinderclient/client.py
if self.timeout:
kwargs.setdefault('timeout', self.timeout)
self.http_log_req((url, method,), kwargs)
resp = requests.request(
method,
url,
+ cert = ("/etc/keystone/ssl/certs/signing_cert.pem",
"/etc/keystone/ssl/private/signing_key.pem"),
verify=self.verify_cert,
**kwargs)
self.http_log_resp(resp)
/keystoneauth1/session.py
def __init__(self, auth=None, session=None, original_ip=None, verify=True,
cert=None, timeout=None, user_agent=None,
redirect=_DEFAULT_REDIRECT_LIMIT, additional_headers=None,
app_name=None, app_version=None, additional_user_agent=None,
discovery_cache=None):
self.auth = auth
self.session = _construct_session(session)
self.original_ip = original_ip
self.verify = verify
- self.cert = cert
+ self.cert = ("/etc/keystone/ssl/certs/signing_cert.pem",
"/etc/keystone/ssl/private/signing_key.pem")
self.timeout = None
self.redirect = redirect
self.additional_headers = additional_headers or {}
self.app_name = app_name
self.app_version = app_version
self.additional_user_agent = additional_user_agent or []
self._determined_user_agent = None
if discovery_cache is None:
discovery_cache = {}
self._discovery_cache = discovery_cache
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1744670/+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 1850602] Re: remove firewall_v1 in neutron-lib
Reviewed: https://review.opendev.org/692094 Committed: https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=330e233a40b7d10436c8a8f74528a601747c98ec Submitter: Zuul Branch:master commit 330e233a40b7d10436c8a8f74528a601747c98ec Author: zhanghao Date: Mon Nov 4 07:54:39 2019 -0500 Remove fwaas_v1 extensions There are still related extensions of fwaas_v1 in neutron-fwaas, it is necessary to remove them because the fwaas_v1 code has been removed in the Stein cycle[1]. [1] https://review.opendev.org/#/c/616410/ Needed-By: https://review.opendev.org/#/c/692068/ Change-Id: I26d23c74123302ef167bd621acdafd9e0e02c6a0 Closes-bug: #1850602 ** 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/1850602 Title: remove firewall_v1 in neutron-lib Status in neutron: Fix Released Bug description: The fwaas_v1 code was removed in stein[1], so the related exceptions and api definitions can also be removed. [1]https://review.opendev.org/#/c/616410/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1850602/+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 1853166] Re: nova not installable on py2 environments which breaks the gate
** 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/1853166 Title: nova not installable on py2 environments which breaks the gate Status in OpenStack Compute (nova): Fix Released Bug description: As noted in the revert https://review.opendev.org/#/c/694891/ change https://review.opendev.org/#/c/687954/ made nova not installable on environments running python < 3.6: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22nova%20requires%20Python%20'%3E%3D3.6'%20but%20the%20running%20Python%20is%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d Since devstack isn't by default using py3 lots of downstream jobs broke in other projects. This bug is to track the fix: https://review.opendev.org/#/c/695007/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1853166/+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 1853171] [NEW] Deprecate and remove any "ofctl" code in Neutron and related projects
Public bug reported: This bug should track all changes related to deprecate and remove all "ofctl" CLI application code in Neutron and related projects (e.g.: networking-sfc). Base function that should be removed: https://github.com/openstack/neutron/blob/0fa7e74ebb386b178d36ae684ff04f03bdd6cb0d/neutron/agent/common/ovs_lib.py#L343 Any Open Flow call should use the native implementation, using os-ken library. ** 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/1853171 Title: Deprecate and remove any "ofctl" code in Neutron and related projects Status in neutron: New Bug description: This bug should track all changes related to deprecate and remove all "ofctl" CLI application code in Neutron and related projects (e.g.: networking-sfc). Base function that should be removed: https://github.com/openstack/neutron/blob/0fa7e74ebb386b178d36ae684ff04f03bdd6cb0d/neutron/agent/common/ovs_lib.py#L343 Any Open Flow call should use the native implementation, using os-ken library. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1853171/+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 1853166] [NEW] nova not installable on py2 environments which breaks the gate
Public bug reported: As noted in the revert https://review.opendev.org/#/c/694891/ change https://review.opendev.org/#/c/687954/ made nova not installable on environments running python < 3.6: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22nova%20requires%20Python%20'%3E%3D3.6'%20but%20the%20running%20Python%20is%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d Since devstack isn't by default using py3 lots of downstream jobs broke in other projects. This bug is to track the fix: https://review.opendev.org/#/c/695007/ ** Affects: nova Importance: Critical Assignee: Luigi Toscano (ltoscano) Status: In Progress ** Tags: gate-failure -- 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/1853166 Title: nova not installable on py2 environments which breaks the gate Status in OpenStack Compute (nova): In Progress Bug description: As noted in the revert https://review.opendev.org/#/c/694891/ change https://review.opendev.org/#/c/687954/ made nova not installable on environments running python < 3.6: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22nova%20requires%20Python%20'%3E%3D3.6'%20but%20the%20running%20Python%20is%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d Since devstack isn't by default using py3 lots of downstream jobs broke in other projects. This bug is to track the fix: https://review.opendev.org/#/c/695007/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1853166/+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 1852993] Re: Don't delete compute node when deleting service other than nova-compute
Deleting a nova-consoleauth service shouldn't have anything to do with deleting compute_nodes records, only deleting nova-compute services, but I guess this doesn't filter on the service binary being nova-compute: https://github.com/openstack/nova/blob/a054d03adef692db22e2466084e50cbf50112bb0/nova/db/sqlalchemy/api.py#L415 However, a nova-consoleauth service id shouldn't be mapped to a compute node record, but that's probably where the OR is breaking things - the service_id is likely NULL and the host is the same. ** Changed in: nova Importance: Undecided => Medium ** Tags added: db ** Also affects: nova/train Importance: Undecided Status: New ** Also affects: nova/rocky Importance: Undecided Status: New ** Also affects: nova/stein Importance: Undecided Status: New ** Changed in: nova/rocky Status: New => Confirmed ** Changed in: nova/stein Status: New => Confirmed ** Changed in: nova/stein Importance: Undecided => Medium ** Changed in: nova/train Importance: Undecided => Medium ** Changed in: nova/rocky Importance: Undecided => Medium ** Changed in: nova/train Status: New => Confirmed -- 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/1852993 Title: Don't delete compute node when deleting service other than nova- compute Status in OpenStack Compute (nova): In Progress Status in OpenStack Compute (nova) rocky series: Confirmed Status in OpenStack Compute (nova) stein series: Confirmed Status in OpenStack Compute (nova) train series: Confirmed Bug description: When upgrading to Stein, nova-consoleauth service is deprecated and should be removed. However if nova-consoleauth service is located on the same host with nova-compute, matching row in compute_nodes table is soft-deleted as well, making nova-compute service report in log, that stale resource provider exists in placement: 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager [req-f0255008-c398-406c-bca0-12cdc34fc0b4 - - - - -] Error updating resources for node vzstor1.vstoragedomain.: ResourceProviderCreationFailed: Failed to create resource provider vzstor1.vstoragedomain 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager Traceback (most recent call last): 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 7399, in update_available_resource_for_node 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager rt.update_available_resource(context, nodename) 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/compute/resource_tracker.py", line 689, in update_available_resource 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager self._update_available_resource(context, resources) 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", line 274, in inner 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager return f(*args, **kwargs) 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/compute/resource_tracker.py", line 713, in _update_available_resource 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager self._init_compute_node(context, resources) 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/compute/resource_tracker.py", line 562, in _init_compute_node 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager self._update(context, cn) 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/compute/resource_tracker.py", line 887, in _update 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager inv_data, 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/scheduler/client/__init__.py", line 68, in set_inventory_for_provider 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager parent_provider_uuid=parent_provider_uuid, 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/scheduler/client/__init__.py", line 37, in __run_method 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager return getattr(self.instance, __name)(*args, **kwargs) 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/scheduler/client/report.py", line 1106, in set_inventory_for_provider 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager parent_provider_uuid=parent_provider_uuid) 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/scheduler/client/report.py", line 667, in _ensure_resource_provider 2019-11-18 16:03:20.069 7 ERROR nova.compute.manager parent_
[Yahoo-eng-team] [Bug 1853160] [NEW] uptime code does not work on FreeBSD
Public bug reported:
The uptime code in cloudinit/util.py does not work for FreeBSD (any
more)
https://github.com/canonical/cloud-
init/blob/3baabe76a70b28abeee2da77826a35e27cf9019a/cloudinit/util.py#L1806-L1825
(link to the code in question at the time of reporting)
root@container-host-02:~ # python3.6
Python 3.6.9 (default, Oct 24 2019, 01:18:01)
[GCC 4.2.1 Compatible FreeBSD Clang 6.0.1 (tags/RELEASE_601/final 335540)] on
freebsd12
Type "help", "copyright", "credits" or "license" for more information.
>>> import ctypes
>>> libc = ctypes.CDLL('/lib/libc.so.7')
>>> import time
>>> size = ctypes.c_size_t()
>>> buf = ctypes.c_int()
>>> size.value = ctypes.sizeof(buf)
>>> libc.sysctlbyname("kern.boottime", ctypes.byref(buf), ctypes.byref(size),
>>> None, 0)
-1
>>>
root@container-host-02:~ #
and here's what happens when we ask for kern.boottime via sysctl(8):
root@container-host-02:~ # sysctl kern.boottime
kern.boottime: { sec = 1573656128, usec = 384300 } Wed Nov 13 14:42:08 2019
root@container-host-02:~ #
** Affects: cloud-init
Importance: Undecided
Status: New
** Tags: freebsd
** Tags added: freebsd
--
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/1853160
Title:
uptime code does not work on FreeBSD
Status in cloud-init:
New
Bug description:
The uptime code in cloudinit/util.py does not work for FreeBSD (any
more)
https://github.com/canonical/cloud-
init/blob/3baabe76a70b28abeee2da77826a35e27cf9019a/cloudinit/util.py#L1806-L1825
(link to the code in question at the time of reporting)
root@container-host-02:~ # python3.6
Python 3.6.9 (default, Oct 24 2019, 01:18:01)
[GCC 4.2.1 Compatible FreeBSD Clang 6.0.1 (tags/RELEASE_601/final 335540)] on
freebsd12
Type "help", "copyright", "credits" or "license" for more information.
>>> import ctypes
>>> libc = ctypes.CDLL('/lib/libc.so.7')
>>> import time
>>> size = ctypes.c_size_t()
>>> buf = ctypes.c_int()
>>> size.value = ctypes.sizeof(buf)
>>> libc.sysctlbyname("kern.boottime", ctypes.byref(buf), ctypes.byref(size),
None, 0)
-1
>>>
root@container-host-02:~ #
and here's what happens when we ask for kern.boottime via sysctl(8):
root@container-host-02:~ # sysctl kern.boottime
kern.boottime: { sec = 1573656128, usec = 384300 } Wed Nov 13 14:42:08 2019
root@container-host-02:~ #
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1853160/+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 1853159] [NEW] Compute node soft undelete raises inactive session error
Public bug reported: In the fix for bug 1839560, soft-deleted compute nodes may be restored, to ensure we can reuse ironic node UUIDs as compute node UUIDs. While this seems to largely work, it results in some nasty errors being generated. Steps to reproduce == Same as bug 1839560. Expected results Compute node is restored in an orderly fashion. Actual results == Example error: http://paste.openstack.org/show/786350/ Despite the error, all my testing shows that the node is actually restored. However, the exception raised breaks the execution of the resource tracker update, which no doubt has some unintended consequences. Environment === Seen on Rocky 18.2.0, and master (in functional testing). ** Affects: nova Importance: Undecided Assignee: Mark Goddard (mgoddard) Status: In Progress ** Changed in: nova Assignee: (unassigned) => Mark Goddard (mgoddard) ** Changed in: nova Status: New => In Progress -- 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/1853159 Title: Compute node soft undelete raises inactive session error Status in OpenStack Compute (nova): In Progress Bug description: In the fix for bug 1839560, soft-deleted compute nodes may be restored, to ensure we can reuse ironic node UUIDs as compute node UUIDs. While this seems to largely work, it results in some nasty errors being generated. Steps to reproduce == Same as bug 1839560. Expected results Compute node is restored in an orderly fashion. Actual results == Example error: http://paste.openstack.org/show/786350/ Despite the error, all my testing shows that the node is actually restored. However, the exception raised breaks the execution of the resource tracker update, which no doubt has some unintended consequences. Environment === Seen on Rocky 18.2.0, and master (in functional testing). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1853159/+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 1851500] Re: "test_show_port_chain" conflicts with Flow Classifier
Just remembering that "old" in-repo tempest tests were running with
OS_TESTR_CONCURRENCY=1 there is probably a LP for networking-sfc about
parallel tests still open
Though I had made some changes (unique IDs etc) at some point that
should allow parallel run, it looks like there is still something to fix
** Also affects: networking-sfc
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/1851500
Title:
"test_show_port_chain" conflicts with Flow Classifier
Status in networking-sfc:
New
Status in neutron:
Confirmed
Bug description:
Test case:
neutron_tempest_plugin.sfc.tests.api.test_sfc_extensions.SfcExtensionTestJSON.test_show_port_chain
Error:
```
Details: {'type': 'PortChainFlowClassifierInConflict', 'message': 'Flow
Classifier a3d6ec45-5ea8-4e3a-a602-d24baa3ca360 conflicts with Flow Classifier
a978b8ee-651b-4a7f-9475-58b224486827 in port chain
b9fb54ee-1868-46ba-9abd-b09e69360a2d.', 'detail': ''}
```
Log:
https://storage.bhs1.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_6e4/692822/4/check/neutron-tempest-plugin-sfc/6e436c3/testr_results.html.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-sfc/+bug/1851500/+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 1853089] Re: openstack env in Stein, CLI or Dashboard response slowly
This is going to require profiling on your part. This isn't a nova bug. ** Changed in: nova Status: New => 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/1853089 Title: openstack env in Stein, CLI or Dashboard response slowly Status in neutron: New Status in OpenStack Compute (nova): Invalid Bug description: Installed Stein OpenStack via Kolla, OpenStack node info as below: 3 * Controller node which running in Virtualbox --- each machine memory: 32G and Disk:300G 2 * Compute node which is physical rack server after operating in some days, the OpenStack response become very slow, the dashboard response is more slower. for example: run "openstack port list --timing" in CLI, it would spent about 13s when got 60 port data, and dashboard would spent more than 20s. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1853089/+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 1852665] Re: HostMappingNotFound in wigi.py
*** This bug is a duplicate of bug 1780727 *** https://bugs.launchpad.net/bugs/1780727 What release are you using? You must not have this fix: https://review.opendev.org/#/q/I0d7644db3537a67b94e75972b3c4fce25a623763 I'm going to mark this as a duplicate of bug 1780727. ** This bug has been marked a duplicate of bug 1780727 Handle HostMappingNotFound when deleting a service -- 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/1852665 Title: HostMappingNotFound in wigi.py Status in OpenStack Compute (nova): New Bug description: It seems to be diffrent from #1780727. # openstack compute service delete 26 Failed to delete compute service with ID '26': 发生意外 API 错误。请在 http://bugs.launchpad.net/nova/ 处报告此错误，并且附上 Nova API 日志（如果可能）。 (HTTP 500) (Request-ID: req-a693a664-5834-48c6-acd9-c92d8b2eea28) nova-api-log: 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi [req-099cb32c-dfbb-4eaf-a067-a3737720977f 7c177645d83f4a769d51ab4b9801a90d 04627ab3503248cb8d714ac1a44f543f - default default] Unexpected exception in API method: HostMappingNotFound: \u4e3b\u673a 'computer3713hpdl580'\u6ca1\u6709\u6620\u5c04\u5230\u4efb\u4f55\u5355\u5143 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi Traceback (most recent call last): 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py", line 801, in wrapped 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi return f(*args, **kwargs) 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/services.py", line 237, in delete 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi service.host) 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 79, in wrapped 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi function_name, call_dict, binary, tb) 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi self.force_reraise() 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi six.reraise(self.type_, self.value, self.tb) 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 69, in wrapped 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi return f(self, context, *args, **kw) 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 5416, in remove_host_from_aggregate 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi mapping = objects.HostMapping.get_by_host(context, host_name) 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/oslo_versionedobjects/base.py", line 184, in wrapper 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi result = fn(cls, context, *args, **kwargs) 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/objects/host_mapping.py", line 100, in get_by_host 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi db_mapping = cls._get_by_host_from_db(context, host) 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", line 993, in wrapper 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi return fn(*args, **kwargs) 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi File "/usr/lib/python2.7/site-packages/nova/objects/host_mapping.py", line 95, in _get_by_host_from_db 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi raise exception.HostMappingNotFound(name=host) 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi HostMappingNotFound: \u4e3b\u673a 'computer3713hpdl580'\u6ca1\u6709\u6620\u5c04\u5230\u4efb\u4f55\u5355\u5143 2019-11-15 08:41:23.576 11235 ERROR nova.api.openstack.wsgi 。 # openstack compute service list |egrep "(3713|ID)" | ID | Binary | Host| Zone | Status | State | Updated At | | 26 | nova-compute | computer3713hpdl580 | sugonZone | disabled | down | 2019-07-24T01:25:20.00 | # nova service-list |egrep "(3713|Id)" | Id | Binary | Host | Zone | Status | State | Updated_at
[Yahoo-eng-team] [Bug 1853146] [NEW] Invalid runcmd script format makes it ignored without marking cloud init as failed
Public bug reported: Info : - cloud-init version `/usr/bin/cloud-init 19.2-36-g059d049c-0ubuntu2~16.04.1` Issue: If user-data script contains a malformed runcmd script, cloud-init fails to parse it but do not mark cloud-init as failed. Example: ``` runcmd: - echo "begin runcmd" - # empty - echo "end" ``` The second line is empty, and causes the following warning in `/var/log /cloud-init.log`: ``` 2019-11-19 12:39:10,124 - helpers.py[DEBUG]: Running config-runcmd using lock () 2019-11-19 12:39:10,124 - schema.py[DEBUG]: Ignoring schema validation. python-jsonschema is not present 2019-11-19 12:39:10,124 - util.py[WARNING]: Failed to shellify ['echo "begin runcmd"', None, 'echo "end"'] into file /var/lib/cloud/instances/0B44BE6F-81FA-FF44-AB96-A0D9AB8B7171/scripts/runcmd 2019-11-19 12:39:10,124 - util.py[DEBUG]: Failed to shellify ['echo "begin runcmd"', None, 'echo "end"'] into file /var/lib/cloud/instances/0B44BE6F-81FA-FF44-AB96-A0D9AB8B7171/scripts/runcmd Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/config/cc_runcmd.py", line 91, in handle content = util.shellify(cmd) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2117, in shellify "Got: %s" % (type_utils.obj_name(args), args)) TypeError: Unable to shellify type 'NoneType'. Expected list, string, tuple. Got: None 2019-11-19 12:39:10,154 - handlers.py[DEBUG]: finish: modules-config/config-runcmd: SUCCESS: config-runcmd ran successfully ``` There is no error log in `/var/log/cloud-init-output.log` But cloud-init status is "done" I expect the status to be "error" ** Affects: cloud-init Importance: Undecided Status: New ** Summary changed: - Invalid runcmd script format make it ignored without marking cloud init as failed + Invalid runcmd script format makes it ignored without marking cloud init as failed -- 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/1853146 Title: Invalid runcmd script format makes it ignored without marking cloud init as failed Status in cloud-init: New Bug description: Info : - cloud-init version `/usr/bin/cloud-init 19.2-36-g059d049c-0ubuntu2~16.04.1` Issue: If user-data script contains a malformed runcmd script, cloud-init fails to parse it but do not mark cloud-init as failed. Example: ``` runcmd: - echo "begin runcmd" - # empty - echo "end" ``` The second line is empty, and causes the following warning in `/var/log/cloud-init.log`: ``` 2019-11-19 12:39:10,124 - helpers.py[DEBUG]: Running config-runcmd using lock () 2019-11-19 12:39:10,124 - schema.py[DEBUG]: Ignoring schema validation. python-jsonschema is not present 2019-11-19 12:39:10,124 - util.py[WARNING]: Failed to shellify ['echo "begin runcmd"', None, 'echo "end"'] into file /var/lib/cloud/instances/0B44BE6F-81FA-FF44-AB96-A0D9AB8B7171/scripts/runcmd 2019-11-19 12:39:10,124 - util.py[DEBUG]: Failed to shellify ['echo "begin runcmd"', None, 'echo "end"'] into file /var/lib/cloud/instances/0B44BE6F-81FA-FF44-AB96-A0D9AB8B7171/scripts/runcmd Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/config/cc_runcmd.py", line 91, in handle content = util.shellify(cmd) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2117, in shellify "Got: %s" % (type_utils.obj_name(args), args)) TypeError: Unable to shellify type 'NoneType'. Expected list, string, tuple. Got: None 2019-11-19 12:39:10,154 - handlers.py[DEBUG]: finish: modules-config/config-runcmd: SUCCESS: config-runcmd ran successfully ``` There is no error log in `/var/log/cloud-init-output.log` But cloud-init status is "done" I expect the status to be "error" To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1853146/+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 1852835] Re: the parameter "--public" has been removed in new version
Reviewed: https://review.opendev.org/694782 Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=c540d54a352f631d2f791abf12fdb695b62c6230 Submitter: Zuul Branch:master commit c540d54a352f631d2f791abf12fdb695b62c6230 Author: Erno Kuvaja Date: Mon Nov 18 14:17:08 2019 + Fix old --public from install verify docs Change-Id: I4128eb7e8d6a6827026d4454e1eaba188e19cf3a Closes-Bug: #1852835 ** Changed in: glance Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1852835 Title: the parameter "--public" has been removed in new version Status in Glance: Fix Released Bug description: glance: error: unrecognized arguments: --public the parameter "--public" has been removed in new version 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: __ - [ ] This is a doc addition request. - [ ] 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: on 2019-09-27 09:57:38 SHA: 6e3ced8251cd6e273aa73f553a24fc475b219db5 Source: https://opendev.org/openstack/glance/src/doc/source/install/verify.rst URL: https://docs.openstack.org/glance/train/install/verify.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1852835/+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
