Flag 'use_gateway' cannot be provided without gateway" error when discarding cluster changes

Bug #1587365 reported by Alexey. Kalashnikov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel Sustaining
Mitaka
Won't Fix
Medium
Fuel Sustaining
Newton
Confirmed
Medium
Fuel Sustaining

Bug Description

Environment configuration:
[root@nailgun ~]# shotgun2 short-report
cat /etc/fuel_build_id:
 417
cat /etc/fuel_build_number:
 417
cat /etc/fuel_release:
 9.0
cat /etc/fuel_openstack_version:
 mitaka-9.0

steps to reproduce:
1. create environment (default wizard settings), add some nodes and deploy the env
2. go to Networks tab, add a new node network group
3. click Show All Networks checkbox to observe all node network groups on the one page
4. click Load Deployed Settings button
5. delete created node group
6. go to dashboard and discard changes

Actual result:
Changes were not discarded, error message in console:
PUT http://172.16.17.43:8417/api/clusters/1/network_configuration/neutron 400 (Bad Request)
Uncaught TypeError: newNetworkConfiguration.get(...).get is not a function
PUT http://172.16.17.43:8417/api/clusters/1/network_configuration/neutron 400 (Bad Request)
Uncaught TypeError: newNetworkConfiguration.get(...).get is not a function

Expected result:
Changes were discarded

Revision history for this message
Alexey. Kalashnikov (akalashnikov) wrote :
Changed in fuel:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Julia Aranovich (jkirnosova)
milestone: none → 10.0
Revision history for this message
Aleksey Kasatkin (alekseyk-ru) wrote :

AFAIC, it's not HIGH. It's not a common case when user adds then deletes a node group. Much more common is when user just adds a node group.

Changed in fuel:
importance: High → Medium
Revision history for this message
Julia Aranovich (jkirnosova) wrote :

So, the issue looks like a feature: restoring of network configuration should be executed in backend to take into account all corner cases like changes in node network groups, VIPs, etc.

tags: added: area-python
tags: added: feature
Changed in fuel:
assignee: Julia Aranovich (jkirnosova) → nobody
Changed in fuel:
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
Revision history for this message
Aleksey Kasatkin (alekseyk-ru) wrote :

A separate API handler can be implemented that will deal with restoring of environment configuration. So that VIPs, network template, node network groups, etc. can be taken into account. As VIPs depend on plugins, it's better to restore environment attributes together with network settings in one call.

tags: added: team-enhancements
Changed in fuel:
milestone: 10.0 → 10.1
Changed in fuel:
milestone: 10.1 → 11.0
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.