Nailgun marks node as offline after the node reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Dmitry Ilyin | ||
Mitaka |
Fix Committed
|
High
|
Vladimir Sharshov | ||
Newton |
Fix Released
|
High
|
Vladimir Sharshov |
Bug Description
Detailed bug description:
The issue was found by https:/
Steps to reproduce:
1. Create new environment with VXLAN segmentation for Neutron
2. Set KVM as Hypervisor
3. Add controller and compute nodes
4. Configure HugePages for compute nodes
5. Configure private network in DPDK mode
6. Run network verification
7. Deploy environment
8. Run network verification
9. Run OSTF
10. Reboot compute
11. Run OSTF
12. Run instance on compute with DPDK and check its availability
via floating IP
Expected results: all is fine
Actual result: step #10 fails, node is offline for nailgun, but node is available by ssh/ping. bellow is part of nailgun-agent.log from this node:
I, [2016-12-
/usr/bin/
from /usr/bin/
from /usr/bin/
from /usr/bin/
at depth 0 - 18: self signed certificate
@Georgy Kibardin found out the reason of this exception is absence of default route:
root@node-2:~# ip route
10.109.5.0/24 dev br-fw-admin proto kernel scope link src 10.109.5.4
https:/
https:/
Changed in fuel: | |
status: | New → Confirmed |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
milestone: | 9.2 → 11.0 |
Changed in fuel: | |
assignee: | Fuel Sustaining (fuel-sustaining-team) → Dmitry Ilyin (idv1985) |
Fix proposed to branch: master /review. openstack. org/418940
Review: https:/