Network settings 'Save Settings' button remains greyed out after network changes

Bug #1670621 reported by michael-mcaleer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel UI Team
Mitaka
Confirmed
Medium
Fuel UI Team
Newton
Confirmed
Medium
Fuel UI Team

Bug Description

I have been having a recurring issue with the Fuel 9.2 master and saving environment network configuration settings. The issue has persisted across clean installs, multiple environments, and with different node config groups, none of them will allow for the network settings to be saved. Has been replicated across browsers, java script confirmed enabled in both.

In a normal scenario I have the network configuration information completed and successfully run verification, after which I would save the respective network configuration. Recently it will not let any changes be saved even after verification.

A red arrow appears for adding a new network config group at all times, but this action is not allowed until network changes are saved. If the changes are discarded, and a new network config group added, again the changes cannot be saved. I have tried all sorts of different approaches but the only thing that I am allowed to do is discard settings.

I had been using the same environment for quite some time (also in 9.2) so didn’t spot this issue until recently when I performed a clean install of the fuel master.

Steps to repo:
1. Create Fuel environment
2. Navigate to 'Network Settings'
3. Add default network settings (public/storage/management)
4. Add L2 & L3 settings
5. Verify network settings in 'Connectivity Check'
6. 'Save settings' button remains greyed out (this state is constant, even with changes to the network settings it will not re-enable itself).

Bug has been flagged to Mirantis (Vyacheslav Struk) who advised I open a launchpad ticket.

If there is anything you need just let me know and ill send it over.

Thanks!

Tags: area-ui
tags: added: area-ui
Changed in fuel:
milestone: none → 11.0
Revision history for this message
Julia Aranovich (jkirnosova) wrote :

Hi Michael,

Thank you for providing such detailed description.
Unfortunately, I can not reproduce the issue so far.
Could you please check if any errors/exceptions are in your browser console?
Another suggestion is that there is a validation error among your network settings. Please check each subtab of the Networks tab. Probably, some setting is marked as invalid (highlighted with red color and red input border).

Changed in fuel:
status: New → Incomplete
Revision history for this message
michael-mcaleer (mmcaleer) wrote :

Hey Guys,

I have went a full clean install and have determined the cause of the issue. When you have a Fuel plugin installed and enabled, but not yet configured the settings for it, somehow it is disabling the save functionality in network configuration.

The plugin is located in settings::storage(cinder) and has no impact on any network functionality, but it is only when the plugin is disabled or has all associated settings filled in, will the save functionality return in network settings.

Changed in fuel:
status: Incomplete → Confirmed
assignee: nobody → Fuel UI Team (fuel-ui)
Revision history for this message
Julia Aranovich (jkirnosova) wrote :

Thanks for your help, Michael!
Yes, I can confirm that for now saving of networks data requires valid cluster setting configuration. In other words, enabling a plugin requires setting up its settings to proceed further.

Michael, are the following workarounds suitable for you?
To disable the plugin, then change networks data, save it, reenable the plugin and continue with its settings.
OR to set up the plugin settings first, save them, and then proceed to networks.

Changed in fuel:
importance: Undecided → Medium
Revision history for this message
michael-mcaleer (mmcaleer) wrote :

Hi Julia,

Yes the workarounds are suitable. For such a simple cause there is no information pointing towards requiring any and all plugins to be either configured or disabled before network settings can be applied, it seems a bit counter-intuitive. Some UI messages would be useful here, there is no indication that the error with network settings saving originates from outside the network section.

Thanks
Michael

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.