Public gateway always stay default

Bug #1246881 reported by Roman Sokolkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Critical
Aleksey Kasatkin

Bug Description

Fuel 3.2 iso, simple schema.

In webUI changed public network to 172.16.72.30-172.16.72.40 (Default: 172.16.0.2-172.16.0.127)

On first controller in /etc/astute.yaml

network_data:
...
  eth0:
    interface: eth0
    ipaddr:
    - 172.16.72.30/24
    gateway: 172.16.0.1
...

and in /etc/sysconfig/network-scripts/ifcfg-eth0:

DEVICE=eth0
IPADDR=172.16.72.30
NETMASK=255.255.255.0
BOOTPROTO=none
ONBOOT=yes
USERCTL=no
GATEWAY=172.16.0.1

This cause network config without default gateway.

Tags: networking
Changed in fuel:
assignee: nobody → Dmitry Pyzhov (lux-place)
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

Please attach diagnostic snapshot

Changed in fuel:
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Roman Sokolkov (rsokolkov) wrote :

Here is diagnostic snapshot

Changed in fuel:
status: Incomplete → New
Changed in fuel:
milestone: none → 3.2.1
importance: High → Critical
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
assignee: Dmitry Pyzhov (lux-place) → Aleksey Kasatkin (alekseyk-ru)
Evgeniy L (rustyrobot)
Changed in fuel:
status: New → Confirmed
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

Roman, in diagnostic snapshot you have '172.16.72.1' gateway in astute.yaml and in output of 'ip r' command.

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

Looks like we miss gateway in nailgun.
from database: "eth0": {"interface": "eth0", "ipaddr": ["172.16.72.31/24"], "gateway": "172.16.0.1"}

Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

Root cause: incorrect user input and absence of validation. Validation was added after 3.2 release

Changed in fuel:
status: In Progress → Invalid
Revision history for this message
Aleksey Kasatkin (alekseyk-ru) wrote :

'3.2-fixes' results: This input (where GW and ranged are not in one CIDRs) cannot pass validation, DB records and serialization output is correct (in case of changed CIDR).

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.