Fuel for OpenStack

How to resume install/config after fixing Broadcom 57810 driver issue

Asked by Christian Hedegaard

We're trying to use Fuel 6.0 which has the broadcom firmware problem (See: https://bugs.launchpad.net/fuel/+bug/1416610). I've gotten Fuel installed, but it appears that the docker containers don't want to start because there is no network config. I extracted the correct firmware based on the above ticket and added it to the Fuel host and rebooted it, and it now has and recognizes eth0-eth3.

I'm still not sure where to go from here. When I launch fuelmenu, it sees eth0-3, but not docker0, even though that interface exists (when doing ifconfig) and is configured with an IP.

Now that the correct NIC firmware is installed is there a way to sorta... "reboot" the install/configuration process so that everything will get back up and running?

Question information

Language:
English Edit question
Status:
Answered
For:
Fuel for OpenStack Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Fabrizio Soppelsa (fsoppelsa) said : 		#1

Hello Christian,

if you don't have sensible data and you can erase them (reset) you can try to rebuild all the containers:
# `dockerctl destroy all`
# `dockerctl build`

Followed by a reboot.

Best regards,
Fabrizio
Mirantis Fuel Team

Revision history for this message
Evgeny Kozhemyakin (ekozhemyakin) said : 		#2

Hello,

you can't see docker0 interface in fuelmenu in 6.0. We should renew screenshots from the docs.
Sorry for misleading. Will correct it asap.

In order to check docker containers please run
dockerctl list -l
dockerctl check

You can see the fuel install process in /usr/local/sbin/bootstrap_admin_node.sh
script on master node.

Regards,

Can you help with this problem?

Provide an answer of your own, or ask Christian Hedegaard for more information if necessary.

To post a message you must log in.