Flag 'use_gateway' cannot be provided without gateway" error when discarding cluster changes
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_
417
cat /etc/fuel_release:
9.0
cat /etc/fuel_
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://
Uncaught TypeError: newNetworkConfi
PUT http://
Uncaught TypeError: newNetworkConfi
Expected result:
Changes were discarded
Changed in fuel: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Julia Aranovich (jkirnosova) |
milestone: | none → 10.0 |
Changed in fuel: | |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
tags: | added: team-enhancements |
Changed in fuel: | |
milestone: | 10.0 → 10.1 |
Changed in fuel: | |
milestone: | 10.1 → 11.0 |
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.