After the openstack virtual machine fails to bind a network card with an existing port, then the virtual machine executes hard restart action will become in an error state
Bug #2027750 reported by
LiZekun
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned |
Bug Description
There is a physical network in neutron's ml2_conf.ini configuration file with only the ml2_type_vlan range configured but no bridge_mappings configured, when I add a NIC to the VM using the external network created by this physical network it will fail to be bound, and the VM state will be normal after the failure of adding the NIC bindings, but a hard restart of the VM will cause the VM state to change to an error afterward.
nova.exception.
summary: |
After the openstack virtual machine fails to bind a network card with an - existing port, the virtual machine will be hard restarted and become in - an error state + existing port, then the virtual machine executes hard restart action + will become in an error state |
To post a comment you must log in.
Thanks for submitting this bug, but it is incomplete and can not be treated without the following information. Please add them to the ticket.
- steps to reproduce
- the version of Nova and the novaclient (or os-client)
- logs (on debug level)
- environment details depending on the bug
libvirt/kvm versions, VMWare version, ...
storage type (ceph, LVM, GPFS, ...)
network type (nova-network or neutron)