A vm's port is in down state after compute node reboot
Bug #1577721 reported by
Sergey Kolekonov
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Mirantis OpenStack | Status tracked in 10.0.x | |||||
10.0.x |
Invalid
|
High
|
Oleg Bondarev | |||
8.0.x |
Invalid
|
High
|
Anatolii Neliubin | |||
9.x |
Fix Released
|
High
|
Oleg Bondarev |
Bug Description
Steps to reproduce:
- Deploy an environment with Neutron + VXLAN (MOS 9.0 + CentOS-based compute node)
- Create required security groups
- Spawn an instance, assign a floating IP address and check that it's available
- Properly reboot a compute node
Expected results:
The instance is available by floating IP
Actual result:
The instance can't obtain an IP address, the floating IP address doesn't work, instance's port is in down state
Detailed bug description:
MOS 9.0 ISO fuel-9.0-274
Time on compute and controller nodes are different (6 mins). This can be a root cause of the issue.
Swarm run: https:/
Changed in mos: | |
assignee: | nobody → Sergey Kolekonov (skolekonov) |
Changed in mos: | |
status: | New → Confirmed |
tags: | added: area-neutron |
Changed in mos: | |
importance: | Undecided → High |
Changed in mos: | |
assignee: | MOS Neutron (mos-neutron) → Oleg Bondarev (obondarev) |
Changed in mos: | |
status: | Confirmed → In Progress |
Changed in mos: | |
status: | Incomplete → Confirmed |
Changed in mos: | |
status: | Confirmed → In Progress |
tags: | added: on-verification |
tags: | added: customer-found |
To post a comment you must log in.
Logs from the compute node