Changing gateway in fuelmenu changes gateway in bootstrap but not in deployment

[Tudor Holton]

I installed Fuel 6.1 with the wrong gateway. Instead of specifying the remote hop 10.20.0.1, I specified the local hop 10.20.0.2. Network verification rightly failed.

I corrected this in fuelmenu, and the bootstrapped nodes correctly picked up the new gateway. However, when I deploy, the old gateway (10.20.0.2) keeps being supplied to the deployed nodes, and the deployment fails because it cannot then get access to external repositories.

I've tried restarting. I'd done a grep search of the filesystem and found some configs that hadn't been changed. However, when I changed them, it didn't fix the problem. :-(

[Artem Panchenko (apanchenko-8)]

Hi Tudor,

changing gateway for admin network using Fuel menu after master node deployment doesn't change GW stored in Nailgun database, so you need to do it manually:

# dockerctl shell postgres su - postgres -c "psql nailgun -c \"UPDATE network_groups SET gateway = '10.20.0.1' WHERE name = 'fuelweb_admin';\""

In 7.0 release we added an ability to manage network groups using CLI (https://docs.mirantis.com/openstack/fuel/fuel-master/operations.html#using-networking-templates), but unfortunately in 6.1 there is no such feature.

Also, I think this bug is about lack of Fuel documentation regarding changing admin network gateway. Python guys, please assign it to fuel-docs team if you agree.

[Tudor Holton (tudor)]

Hi Artem,

Thanks for the reply.

I'd humbly disagree that it's not a fuelmenu bug.

I see an implication by specifying the gateway in fuelmenu that it should affect all aspects of fuel, not just the master node config. If it were for the master node config only, then surely it should be "fuelmastermenu" or some such?

Furthermore, this gateway is used in the initial configuration of the admin network, so it is essentially responsible for more than just the master node config.

However, my point is moot since, as you say, it's fixed in 7.0. I'm more making an argument for the ongoing approach which has been already taken in 7.0. :-)

Thanks again!

Cheers,
Tudor.

[Dmitry Pyzhov (dpyzhov)]

We passed SCF for 8.0. Moving the bug to 9.0.

[Bug Checker Bot (bug-checker)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

version

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/310158

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/310191

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/310199

[OpenStack Infra (hudson-openstack)]

Change abandoned by Mikhail Zhnichkov (<email address hidden>) on branch: master
Review: https://review.openstack.org/310191

[OpenStack Infra (hudson-openstack)]

Change abandoned by Mikhail Zhnichkov (<email address hidden>) on branch: master
Review: https://review.openstack.org/310158

[OpenStack Infra (hudson-openstack)]

Change abandoned by Mikhail Zhnichkov (<email address hidden>) on branch: master
Review: https://review.openstack.org/310191

[OpenStack Infra (hudson-openstack)]

Change abandoned by Mikhail Zhnichkov (<email address hidden>) on branch: master
Review: https://review.openstack.org/310199

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/317916

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/320011

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/317916
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=d41348e8425e314723b646a2d6c90b3cebd4c98a
Submitter: Jenkins
Branch: master

commit d41348e8425e314723b646a2d6c90b3cebd4c98a
Author: Mikhail <email address hidden>
Date: Wed May 18 11:59:34 2016 +0300

    Allow to modify default admin network via API

    Nailgun cant change parameters in default admin network
    (such as gateway or ip range), but sometimes its needed.
    This patch allow to modify default admin network via API.

    Change-Id: I9200c90747dba1e5c5b4e5457e423cb4c3ff3062
    Partial-Bug: #1500667

[OpenStack Infra (hudson-openstack)]

Change abandoned by Mikhail Zhnichkov (<email address hidden>) on branch: master
Review: https://review.openstack.org/320011
Reason: it's not needed anymore

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/310158
Committed: https://git.openstack.org/cgit/openstack/fuel-menu/commit/?id=599d801eb0cd3058aae293ebae1a6e5dd0548f3b
Submitter: Jenkins
Branch: master

commit 599d801eb0cd3058aae293ebae1a6e5dd0548f3b
Author: mzhnichkov <email address hidden>
Date: Tue Apr 26 12:13:13 2016 +0300

    Added ability to update PXE DHCP parameters after deploy

    It's possible to change PXE settings on post deploy stage, but, in fact,
    dnsmasq configuration will not be changed. This patch introduce puppet
    call to get these changes applied.

    Function puppetApply was refactored to return Bool value,
    previously it has returned None or False.

    Change-Id: I3fc7097035f492ad24483205cedc0d2c773af24b
    Closes-Bug: #1500667
    Depends-On: I9200c90747dba1e5c5b4e5457e423cb4c3ff3062

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/414994

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/414996

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/414994
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=955c4d7afa020e1b18c1de81c1c94a690a38ae44
Submitter: Jenkins
Branch: stable/mitaka

commit 955c4d7afa020e1b18c1de81c1c94a690a38ae44
Author: Mikhail <email address hidden>
Date: Wed May 18 11:59:34 2016 +0300

    Allow to modify default admin network via API

    Nailgun cant change parameters in default admin network
    (such as gateway or ip range), but sometimes its needed.
    This patch allow to modify default admin network via API.

    Change-Id: I9200c90747dba1e5c5b4e5457e423cb4c3ff3062
    Partial-Bug: #1500667
    (cherry picked from commit d41348e8425e314723b646a2d6c90b3cebd4c98a)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/414996
Committed: https://git.openstack.org/cgit/openstack/fuel-menu/commit/?id=392b70480b9251df0a101bcb9520150bb3e7ba45
Submitter: Jenkins
Branch: stable/mitaka

commit 392b70480b9251df0a101bcb9520150bb3e7ba45
Author: mzhnichkov <email address hidden>
Date: Tue Apr 26 12:13:13 2016 +0300

    Added ability to update PXE DHCP parameters after deploy

    It's possible to change PXE settings on post deploy stage, but, in fact,
    dnsmasq configuration will not be changed. This patch introduce puppet
    call to get these changes applied.

    Function puppetApply was refactored to return Bool value,
    previously it has returned None or False.

    Change-Id: I3fc7097035f492ad24483205cedc0d2c773af24b
    Closes-Bug: #1500667
    Depends-On: I9200c90747dba1e5c5b4e5457e423cb4c3ff3062
    (cherry picked from commit 599d801eb0cd3058aae293ebae1a6e5dd0548f3b)

[Vladimir Khlyunev (vkhlyunev)]

Snapshot 801 - gateway of admin node itself was changed successfully