New Question
0

WMI job failed with status 10. Error details: Failed to add device 'Ethernet Connection' [closed]

asked 2018-06-29 17:11:43 +0300

Nebukazar gravatar image

Hi,

In addition to the issue we're having @ https://ask.cloudbase.it/question/275... we are having an issue with neutron and one of our instance. The instance appears to be running just fine, but we're seeing a bunch of errors within the neutron's logfile where the instance is running at.

The issue seems to be occurring on any hyperv node that is running the instance.

The error messages are as follow:

2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent [-] Exception encountered while processing port c17da5c8-61ea-4da8-ae81-a02989ab3226.
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent Traceback (most recent call last):
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent   File "C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\hyperv\neutron\hyperv_neutron_agent.py", line 336, in _process_added_port
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent     device_details['admin_state_up'])
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent   File "C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\hyperv\neutron\_common_utils.py", line 35, in wrapper
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent     return inner()
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent   File "C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\oslo_concurrency\lockutils.py", line 271, in inner
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent     return f(*args, **kwargs)
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent   File "C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\hyperv\neutron\_common_utils.py", line 34, in inner
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent     return f(*args, **kwargs)
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent   File "C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\hyperv\neutron\hyperv_neutron_agent.py", line 315, in _treat_vif_port
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent     physical_network, segmentation_id)
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent   File "C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\hyperv\neutron\hyperv_neutron_agent.py", line 251, in _port_bound
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent     self._utils.connect_vnic_to_vswitch(map['vswitch_name'], port_id)
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent   File "C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\os_win\utils\network\networkutils.py", line 284, in connect_vnic_to_vswitch
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent     self._jobutils.add_virt_resource(port, vm)
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent   File "C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\os_win\_utils.py", line 181, in inner
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent     time.sleep(sleep_time)
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent   File "C:\PROGRA~1\CLOUDB~1\OPENST~1\Nova\Python27\lib\site-packages\oslo_utils\excutils.py", line 220, in __exit__
2018-06-29 10:04:01.970 3648 ERROR hyperv.neutron.hyperv_neutron_agent     self.force_reraise()
2018-06-29 10:04:01.970 3648 ...
(more)
edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Nebukazar
close date 2018-07-16 15:50:01.703398

1 answer

Sort by » oldest newest most voted
0

answered 2018-06-29 17:30:09 +0300

lpetrut gravatar image

So you're saying that the instance is running fine, while neutron fails to attach the port "c17da5c8-61ea-4da8-ae81-a02989ab3226" to a vswitch. Is that instance reachable? What network type are you using?

I'm wondering if that port does actually get attached to a vswitch. It could be that we're reattempting to attach it because of other port binding errors.

edit flag offensive delete link more

Comments

Yes, the instance has a vnic configured, although it shows status degraded ? see: https://nextcloud.dataenligne.com/index.php/s/N848waxS4kpatby These VMs are running on a non tagged VLAN, IPv4. Let me know if you need further information. Thanks!

Nebukazar gravatar imageNebukazar ( 2018-06-29 17:40:06 +0300 )edit

Interesting, so it's already connected to a vswitch. What's the neutron port status? You can do: neutron port-show c17da5c8-61ea-4da8-ae81-a02989ab3226 I'd grep for log messages including the port id to see why the port may be handled as unbound, in which case we retry binding it.

lpetrut gravatar imagelpetrut ( 2018-06-29 18:58:49 +0300 )edit

there you go: https://nextcloud.dataenligne.com/index.php/s/NX93bedjD7wXr6p status is: BUILD which doesn't seem right to me ?

Nebukazar gravatar imageNebukazar ( 2018-06-29 22:59:48 +0300 )edit

Thanks, that confirms it, something else must've failed. We'll try to make the retry logic more robust, ensuring that the port bind operations are idempotent.

lpetrut gravatar imagelpetrut ( 2018-07-02 09:32:37 +0300 )edit

It would be really helpful if we could see what failed the first time the port was processed. You should check the logs around the time the VM was spawned.

lpetrut gravatar imagelpetrut ( 2018-07-02 09:34:18 +0300 )edit

Question Tools

1 follower

Stats

Asked: 2018-06-29 17:11:43 +0300

Seen: 61 times

Last updated: Jun 29