The instance's status is ACTIVE even though the TAP device is DOWN and it doesn't has an IP address
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Expired
|
Undecided
|
Unassigned |
Bug Description
During scale tests (80 instances) a few instances created and their status is ACTIVE (nova list/show) even though their TAP divices is DOWN and they don't have an IP address.
Version - Icehouse with RHEL7
GRE+ML2 - All-In-One+ Compute node
openstack-
openstack-
openstack-
openstack-
openstack-
nova list
19d932b1-
neutron port list
1d98786a-
ip a | grep 1d98786a-b4
569: qbr1d98786a-b4: <BROADCAST,
570: qvo1d98786a-b4: <BROADCAST,
571: qvb1d98786a-b4: <BROADCAST,
575: tap1d98786a-b4: <BROADCAST,
Steps to reproduce:
1. ifconfig tap1d98786a-b4 down
2. nova show <instance id>
summary: |
The instance's status is ACTIVE even though the TAP device is DOWN and - he doesn't has an IP address + it doesn't has an IP address |
description: | updated |
Changed in neutron: | |
status: | New → Confirmed |
assignee: | nobody → Andrey Epifanov (aepifanov) |
Changed in neutron: | |
status: | Confirmed → New |
assignee: | Andrey Epifanov (aepifanov) → nobody |
Changed in neutron: | |
status: | New → Incomplete |
I have no idea about the relation between quantity of instances and tap device's status.
Moreover, if you down tap device intentionally after instance booting, it looks like something natural that instance remain active.