fuelmenu does not update /etc/fuel/astute.yaml

Bug #1437265 reported by TorstenSchlabach
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Matthew Mosesohn

Bug Description

I am booting a new master node using the latest fuel-6.1 iso CD, built from fuel-master branch.

The default is ".showmenu=yes", so at some time during the setup the fuel menu shows up.

We need to make some changes to the default, i.e.:

- our network interface isn't called "eth0" but differently
- we would like a different IP range

So we make the changes accordingly in fuel menu. We can properly select our network interface (it is recognized and offered as a choice), update it's ip address and gateway, then choose "Save" in fuelmenu.

Checking /etc/fuel/astute.yaml after having saved, the timestamp shows that the file got re-written, but it's content still says "eth0" and the default 10.20.0.2 address.

Revision history for this message
Stanislav Makar (smakar) wrote :

Could you please provide the content of file /etc/fuel/version.yaml ?
As I understand you are doing it on hardware ?
If yes could you share the info about this HW and the interface name you have instead of eth0 ?

Thanks

Changed in fuel:
assignee: nobody → Fuel Library Team (fuel-library)
status: New → Incomplete
importance: Undecided → High
milestone: none → 6.1
Revision history for this message
TorstenSchlabach (tschlabach) wrote :

Well, it's a bit more complicated than that. I intend to do it on hardware in the end, but it's VirtualBox right now and the interface which is not eth0 is a tun/tap device. But you can try it with a machine that has eth0 and eth1 as well. Choose eth1 as the interface and you will still see eth0 in the astute.yaml.

I did a bit of code reading of fuelmenu. To be honest, I failed to spot the piece of code where *anything* which is entered into the menu is written back to the YAML file.

There is the save_only method which just writes the defaults to the YAML file, but I did not find any other YAML serialization in the code.

I hope my assumption is right that whatever is in the YAML file will be picked up subsequently by Puppet to build docker containers and the like.

Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Matthew Mosesohn (raytrac3r)
status: Incomplete → Confirmed
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

Torsten, are you sure you selected "eth1" in PXE Setup? If you simply select "eth1" in "Network Setup" screen, that just displays its interface configuration. Are you able to make a screencast? I believe it's quite simple to do within VirtualBox if you're using that.

With regards to fuelmenu, look at these methods in the PXE setup code:
https://github.com/stackforge/fuel-web/blob/master/fuelmenu/fuelmenu/modules/cobblerconf.py#L259-L268
https://github.com/stackforge/fuel-web/blob/master/fuelmenu/fuelmenu/modules/cobblerconf.py#L293-L323

Changed in fuel:
status: Confirmed → Incomplete
Changed in fuel:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.