Fuel 9.0 - when deploying an OS ENV it fails when the controller node tries to create a vlan interface during deployment process

OPNFV Danube is based on Fuel10/newton.
As a workaround in UI you could set "net.ifnames=0 biosdevname=1" in kernel parameters at settings/general tab.

Hi Michael - thanks for the note - I will give this a try tonight and let you know of the results. thank you! Dan

i gave it a try, no change - some more details, when I assign the compute/cinder and controller node to each hardware device, the fuel UI already knows the the logical name of the nic's in each device. In my case I have 3 nic cards in my two devices (controller and compute/cinder). see attached img. I think my only work around is to login into each device and change the logical name of the nic's on the two devices after the PXE load, then bring up the fuel UI and add the nodes. are there any other suggestions or workarounds?

Dan, try out the "biosdevname=0 net.ifnames=0" settings.
It should do a trick.

Hi Micheal - I made the recommended change and the controller still fails during openstack load. see attached puppet log page 9 first ERR message.

Hi Michael,

just checking in to see if there is any additional suggestions you can provide that will allow me to get my OS ENV up and running? I'm at a standstill at this point. Any suggestions would be helpful.

thanks,
dan

Dan, please make sure suggested params is in place, additionally reset the env before deploy.

Hi Mike,

here is what I did - deleted the current env. created new env and in setting assigned the following.
net.ifnames=0 biosdevname=0

then went into networking add assgined vlan's and ip address then ran connectivity test.
then added the two nodes, controller and compute/ cinder.

Ran the deployment and it failed again on the controller with same error messages.

Error: argument "enp0s29u1u2u3.101" is wrong: "name" too long
2017-05-12 13:23:46 ERR Command 'ip link add link enp0s29u1u2u3 name enp0s29u1u2u3.101 type vlan id 101' has been failed with exit_code=255:

are there any other work arounda I could try?

thanks,
dan

Hello all - due to this error I cannot create an opestack environment.

This has become a serious problem where I cannot get openstack up and running. Anyone reading this post please advise a viable workaround or a fix to this issue.

thgank you!

dan

We are not planning to fix this issue.