Unsupported VIF type unbound convert '_nova_to_osvif_vif_unbound' on compute restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Stephen Finucane | ||
Ocata |
Fix Committed
|
Medium
|
Stephen Finucane | ||
Pike |
Fix Committed
|
Medium
|
Stephen Finucane | ||
Queens |
Fix Committed
|
Medium
|
Stephen Finucane | ||
Rocky |
Fix Committed
|
Medium
|
melanie witt |
Bug Description
This is a variant of an existing bug:
- https:/
There are also two other closely related bugs:
- https:/
- https:/
In addition, there are a few bugs which are likely the root cause of all of the above issues (and this one) in the first place:
- https:/
In this instance, as with bug 1738373, we are unable to start nova-compute service on compute node due to an os-vif invoked error.
nova-compute.log on compute shows:
2018-05-12 16:42:47.323 305978 INFO os_vif [req-0a72cdea-
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
2018-05-12 16:42:47.369 305978 ERROR oslo_service.
Inspecting the available ports shows the port does exist, so this looks like a caching issue.
[stack@director:~]$ neutron port-list | grep fa:16:3e:41:a9:2c
| 8d027ff4-
[stack@director:~]$ neutron port-show 8d027ff4-
+------
| Field | Value |
+------
| admin_state_up | True |
| allowed_
| binding:host_id | overcloud-
| binding:profile | {} |
| binding:vif_details | {"port_filter": true, "ovs_hybrid_plug": true} |
| binding:vif_type | ovs |
| binding:vnic_type | normal |
| created_at | 2017-10-
| description | |
| device_id | b4ef4d0b-
| device_owner | compute:nova |
| extra_dhcp_opts | |
| fixed_ips | {"subnet_id": "1f5ed9bc-
| id | 8d027ff4-
| mac_address | fa:16:3e:41:a9:2c |
| name | |
| network_id | 9a98b244-
| port_security_
| project_id | 3b2049626c954cd
| qos_policy_id | |
| revision_number | 184 |
| security_groups | 97aa0764-
| | c7addc13-
| | cecdad42-
| | de0a6da8-
| status | ACTIVE |
| tenant_id | 3b2049626c954cd
| updated_at | 2018-05-
+------
We should figure out why the invalid cache is getting saved, but we're going to track that effort separately. For now, we should just focus on letting the service start, putting instances with errors like this into error state.
This was originally reported here https:/
Changed in nova: | |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. openstack. org/626228
Review: https:/