Nodes go offline after reboot when using image-based provisioning
Bug #1398207 reported by
Ryan Moe
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Alexander Gordeev | ||
6.0.x |
Fix Committed
|
High
|
Alexander Gordeev |
Bug Description
After reboot only eth0 comes up on the node and there is no connectivity to the master node. All of the interface configuration files exist and are correct but the other interfaces never come up.
build_number: "16"
build_id: "2014-12-
description: | updated |
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | nobody → Aleksandr Gordeev (a-gordeev) |
milestone: | none → 6.0 |
milestone: | 6.0 → 6.1 |
importance: | Undecided → High |
tags: | added: cloud-init |
tags: | added: image-based provision |
tags: | added: system-test-not-required |
To post a comment you must log in.
This bug does not occur if you deploy a centos environment. Using image-based deployment, I deployed a single controller and single compute node on a linux server (nodes running under KVM). After I validated the environment is working fine by launching a VM and ensuring network connectivity between the nodes, I rebooted the compute node. After reboot, the compute node WAS able to reach the controller, and had the network was working fine. I also tried rebooting the controller node and after reboot there were no problems with the network.