Steps to reproduce:
1. Install Fuel with default settings and kernel parameters (1 net interface)
2. Enter fuel-menu by pressing the key after reboot
3. Switch to Network Settings tab and enter new values in IP Address and Default Gateway fields:
orig values:
IP Address: 10.20.0.2
Default Gateway: 10.20.0.1
new values:
IP Address: 10.109.0.2
Default Gateway: 10.109.0.1
4. Select Apply at the bottom and press Enter
Expected result:
Gateway setting on the top of the tab and the input field Default Gateway contain the same value entered earlier
Actual result:
The input field is empty.
'Gateway: None' displayed in the top part of the tab, in interface settings.
VERSION:
feature_groups:
- mirantis
production: "docker"
release: "8.0"
api: "1.0"
build_number: "490"
build_id: "490"
fuel-nailgun_sha: "9c78c70c46a3463f9cfcfac78974fe27d32a5f05"
python-fuelclient_sha: "4f234669cfe88a9406f4e438b1e1f74f1ef484a5"
fuel-agent_sha: "e869072139670bb8bbfde00ef04dec3d189f5927"
fuel-nailgun-agent_sha: "b2bb466fd5bd92da614cdbd819d6999c510ebfb1"
astute_sha: "b81577a5b7857c4be8748492bae1dec2fa89b446"
fuel-library_sha: "f7a008e6801ba0072b08302a740174aec506078a"
fuel-ostf_sha: "ab5fd151fc6c1aa0b35bc2023631b1f4836ecd61"
fuel-mirror_sha: "88c9f2978f9bf38810941b596c2d435f89ad6943"
fuelmenu_sha: "fac143f4dfa75785758e72afbdc029693e94ff2b"
shotgun_sha: "63645dea384a37dde5c01d4f8905566978e5d906"
network-checker_sha: "a43cf96cd9532f10794dce736350bf5bed350e9d"
fuel-upgrade_sha: "616a7490ec7199f69759e97e42f9b97dfc87e85b"
fuelmain_sha: "3145e00d1fb780bd0d59e899f12a76143b256ea1"
Oleg, I can't reproduce this in my local environment, but I can tell you here's how the gateway feature works:
1 - If you modify a network interface where the gateway is currently set, it gets unset (so we can apply a new one)
or if it's a DHCP interface, we also unset gateway manually.
However, if you have eth1 with a gateway, then configure eth0 gateway, eth1's gateway stays. You must unset eth1's gateway before eth0's gateway becomes the default. The highest interface # wins in this case.
2 - we run l23network in Puppet to apply config changes. This ultimately sets the new gateway.
A new default gateway is left as None if the new config can't ping that gateway. That leads me to think that it's your network.
I need you to provide logs and if possible, access to your env to see this in action. There are logs in /var/log/puppet and /var/log/ fuelmenu. log to inspect.