[Victoria][Python-3.9] dhcp-agent problem
System: LFS. Python-3.9.0, Neutron-17.0.0, oslo.privsep-2.4.0 Got Train+Py37, Usuri+Py38 working with the help of the install-guide. Victoria+Py39 Only eventlet needed a patch. Neutron only for neutron/plugins/ml2/drivers/linuxbridge/agent/arp_protect.py def ebtables(comm, table='nat'): execute = ip_lib.IPWrapper(NAMESPACE).netns.execute - return execute(['ebtables', '-t', table, '--concurrent'] + comm, + return execute(['/usr/sbin/ebtables', '-t', table, '--concurrent'] + comm, run_as_root=True) Possible not necessary but it avoids sudo errors. Controller logs (made readable): [-] Unable to enable dhcp for cb7948eb-e5c0-4764-a653-542c3e864f54.: TypeError: <lambda>() takes 6 positional arguments but 7 were given Traceback (most recent call last): File "/site-packages/neutron/agent/dhcp/agent.py", line 192, in call_driver rv = getattr(driver, action)(**action_kwargs) File "/site-packages/neutron/agent/linux/dhcp.py", line 249, in enable common_utils.wait_until_true(self._enable, timeout=300) File "/site-packages/neutron/common/utils.py", line 703, in wait_until_true while not predicate(): File "/site-packages/neutron/agent/linux/dhcp.py", line 261, in _enable interface_name = self.device_manager.setup(self.network) File "/site-packages/neutron/agent/linux/dhcp.py", line 1675, in setup if ip_lib.ensure_device_is_ready(interface_name, File "/site-packages/neutron/agent/linux/ip_lib.py", line 960, in ensure_device_is_ready if not dev.link.exists or not dev.link.address: File "/site-packages/neutron/agent/linux/ip_lib.py", line 513, in exists return privileged.interface_exists(self.name, self._parent.namespace) File "/site-packages/oslo_privsep/priv_context.py", line 247, in _wrap return self.channel.remote_call(name, args, kwargs) File "/site-packages/oslo_privsep/daemon.py", line 224, in remote_call raise exc_type(*result[2]) TypeError: <lambda>() takes 6 positional arguments but 7 were given Launching an instance: $ openstack server create --flavor m1.nano --image cirros \ --nic net-id=cb7948eb-e5c0-4764-a653-542c3e864f54 --security-group default \ --key-name mykey provider-instance results in status=BUILD and never ACTIVE Other logs on Controller after starting Compute1: Unable to access /var/lib/neutron/dhcp/cb7948eb-e5c0-4764-a653-542c3e864f54/pid; Error: [Errno 2] No such file or directory Ownerships and permissions are OK: drwxr-xr-x 2 neutron neutron 4096 Nov 15 19:49 cb7948eb-e5c0-4764-a653-542c3e864f54/ Anybody with the same problem? I am not a Python programmer so I am at a lost
Hi tjoen, Victoria release doesn't support Python3.9, the maximum python version is 3.8 (default for ubuntu focal). See https://governance.openstack.org/tc/reference/runtimes/victoria.html Em ter., 17 de nov. de 2020 às 17:25, tjoen <tjoen@dds.nl> escreveu:
System: LFS. Python-3.9.0, Neutron-17.0.0, oslo.privsep-2.4.0
Got Train+Py37, Usuri+Py38 working with the help of the install-guide. Victoria+Py39 Only eventlet needed a patch. Neutron only for neutron/plugins/ml2/drivers/linuxbridge/agent/arp_protect.py def ebtables(comm, table='nat'): execute = ip_lib.IPWrapper(NAMESPACE).netns.execute - return execute(['ebtables', '-t', table, '--concurrent'] + comm, + return execute(['/usr/sbin/ebtables', '-t', table, '--concurrent'] + comm, run_as_root=True) Possible not necessary but it avoids sudo errors.
Controller logs (made readable): [-] Unable to enable dhcp for cb7948eb-e5c0-4764-a653-542c3e864f54.: TypeError: <lambda>() takes 6 positional arguments but 7 were given Traceback (most recent call last): File "/site-packages/neutron/agent/dhcp/agent.py", line 192, in call_driver rv = getattr(driver, action)(**action_kwargs) File "/site-packages/neutron/agent/linux/dhcp.py", line 249, in enable common_utils.wait_until_true(self._enable, timeout=300) File "/site-packages/neutron/common/utils.py", line 703, in wait_until_true while not predicate(): File "/site-packages/neutron/agent/linux/dhcp.py", line 261, in _enable interface_name = self.device_manager.setup(self.network) File "/site-packages/neutron/agent/linux/dhcp.py", line 1675, in setup if ip_lib.ensure_device_is_ready(interface_name, File "/site-packages/neutron/agent/linux/ip_lib.py", line 960, in ensure_device_is_ready if not dev.link.exists or not dev.link.address: File "/site-packages/neutron/agent/linux/ip_lib.py", line 513, in exists return privileged.interface_exists(self.name, self._parent.namespace) File "/site-packages/oslo_privsep/priv_context.py", line 247, in _wrap return self.channel.remote_call(name, args, kwargs) File "/site-packages/oslo_privsep/daemon.py", line 224, in remote_call raise exc_type(*result[2])
TypeError: <lambda>() takes 6 positional arguments but 7 were given
Launching an instance: $ openstack server create --flavor m1.nano --image cirros \ --nic net-id=cb7948eb-e5c0-4764-a653-542c3e864f54 --security-group default \ --key-name mykey provider-instance results in status=BUILD and never ACTIVE
Other logs on Controller after starting Compute1: Unable to access /var/lib/neutron/dhcp/cb7948eb-e5c0-4764-a653-542c3e864f54/pid; Error: [Errno 2] No such file or directory
Ownerships and permissions are OK: drwxr-xr-x 2 neutron neutron 4096 Nov 15 19:49 cb7948eb-e5c0-4764-a653-542c3e864f54/
Anybody with the same problem? I am not a Python programmer so I am at a lost
-- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory@gmail.com <iurygregory@gmail.com>*
I think the plan to support Python3.9 is after Wallaby (I'm not 100% sure, maybe someone from the TC would have a better answer for when the projects should be compatible with py39) =) Em ter., 17 de nov. de 2020 às 18:52, tjoen <tjoen@dds.nl> escreveu:
On 11/17/20 6:27 PM, Iury Gregory wrote:
Victoria release doesn't support Python3.9, the maximum python version is 3.8 (default for ubuntu focal).
/Too bad. Just converted everything to 3.9/
/Only Openstack as the last one. I am willing to participate in testing /
-- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory@gmail.com <iurygregory@gmail.com>*
On 2020-11-17 19:16:49 +0100 (+0100), Iury Gregory wrote:
I think the plan to support Python3.9 is after Wallaby (I'm not 100% sure, maybe someone from the TC would have a better answer for when the projects should be compatible with py39) [...]
https://governance.openstack.org/tc/reference/runtimes/wallaby.html Yes it looks like for now the latest Python version Wallaby is targeting is 3.8 since that's the default Python version in the latest Ubuntu LTS, but there has been work done on adding (initially non-voting) 3.9 jobs to the default set run on official OpenStack deliverables: https://review.opendev.org/758813 https://review.opendev.org/760932 -- Jeremy Stanley
On 11/17/20 7:27 PM, Jeremy Stanley wrote:
but there has been work done on adding (initially non-voting) 3.9 jobs to the default set run on official OpenStack deliverables:
https://review.opendev.org/758813 https://review.opendev.org/76093 That looks promising. Up to Walaby. Forget Victoria
participants (3)
-
Iury Gregory
-
Jeremy Stanley
-
tjoen