[nailgun] settings.yaml upload is broken

[Vasiliy Pleshakov]

Detailed bug description:
  As a deployment engineer I want to upload settings.yaml for new environments to shorten time spent to manually configure similar clusters and to elimate human errors in cluster settings.

  Steps to reproduce:
1. I configured fuel cluster with all those plugins (have to mention I configured grafana, kibana, nagios to use LDAP for authentication) and made success deploy (there was lot of post-deployment steps which are unrelated to topic).
2. Then I downloaded settings.yaml and networks.yaml. Destoyed Fuel Master node and reinstalled it (exactly same MOS8) . Installed MU3 and al plugins (same versions).
3. I created new env (with same parameters in wizard)
4. I uploaded settings.yaml with 'fuel setting --env 1 upload' command.

  Expected results:
I expected I can open Fuel WebUI and check that all settings in UI.

  Actual result:
Instead WebUI does not respond to clicks at settings and network tabs.
In browsers javascript console I see error:
objects.js:73 Uncaught TypeError: Value of settings:lma_collector.influxdb_mode.value is undefined. Set options.strict to false to allow undefined values.
Screenshot attached.

  Reproducibility:
  always

Workaround:
  no

Description of the environment:
   Operation system: fuel 8 with Centos 7
   Versions of components: fuel 8 with plugins (LMA stack version 0.10.1 + Contrail plugin ver 4.0.1-1 with Juniper Contrail ver 3.0.2-4 + LDAP plugin ver 2.0.0-1)
   Reference architecture: N/A
   Network model: N/A
   Related projects installed: N/A

Additional information:
  customer found

[Vasiliy Pleshakov (vpleshakov)]

Settings.yaml I have problem with. All passwords and certificates was changed.

[Dmitry Sutyagin (dsutyagin)]

I reproduced the issue on my Fuel 8.0 VM updated to MU3. Database dump attached.

[Georgy Kibardin (gkibardin)]

It looks like one plugin settings are written into another plugin during the upload.

[Georgy Kibardin (gkibardin)]

In a part related to plugins settings.yaml format tied to a particular database instance, i.e. it contains ids from it. Therefore it cannot be downloaded from one database and uploaded to another.

[Georgy Kibardin (gkibardin)]

The workaround is to either install plugins in the same order in new env or to fix plugin ids in setttings.yaml.

[Vasiliy Pleshakov (vpleshakov)]

Georgy,
Am I understanding right that you're talking about chosen_id: XX field?
And where can I get new id's for plugins?

On Thu, Oct 20, 2016 at 3:08 AM, Georgy Kibardin <email address hidden>
wrote:

> The workaround is to either install plugins in the same order in new env
> or to fix plugin ids in setttings.yaml.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1634588
>
> Title:
> [nailgun] settings.yaml upload is broken
>
> Status in Fuel for OpenStack:
> Confirmed
> Status in Fuel for OpenStack 8.0.x series:
> In Progress
> Status in Fuel for OpenStack mitaka series:
> Confirmed
>
> Bug description:
> Detailed bug description:
> As a deployment engineer I want to upload settings.yaml for new
> environments to shorten time spent to manually configure similar clusters
> and to elimate human errors in cluster settings.
>
>
> Steps to reproduce:
> 1. I configured fuel cluster with all those plugins (have to mention I
> configured grafana, kibana, nagios to use LDAP for authentication) and made
> success deploy (there was lot of post-deployment steps which are unrelated
> to topic).
> 2. Then I downloaded settings.yaml and networks.yaml. Destoyed Fuel
> Master node and reinstalled it (exactly same MOS8) . Installed MU3 and al
> plugins (same versions).
> 3. I created new env (with same parameters in wizard)
> 4. I uploaded settings.yaml with 'fuel setting --env 1 upload' command.
>
> Expected results:
> I expected I can open Fuel WebUI and check that all settings in UI.
>
> Actual result:
> Instead WebUI does not respond to clicks at settings and network tabs.
> In browsers javascript console I see error:
> objects.js:73 Uncaught TypeError: Value of settings:lma_collector.influxdb_mode.value
> is undefined. Set options.strict to false to allow undefined values.
> Screenshot attached.
>
> Reproducibility:
> always
>
> Workaround:
> no
>
> Description of the environment:
> Operation system: fuel 8 with Centos 7
> Versions of components: fuel 8 with plugins (LMA stack version 0.10.1
> + Contrail plugin ver 4.0.1-1 with Juniper Contrail ver 3.0.2-4 + LDAP
> plugin ver 2.0.0-1)
> Reference architecture: N/A
> Network model: N/A
> Related projects installed: N/A
>
> Additional information:
> customer found
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/fuel/+bug/1634588/+subscriptions
>

--
Best Regards,
Vasiliy Pleshakov

[Georgy Kibardin (gkibardin)]

Vasiliy,

I mean that settings.yaml is not designed to be downloaded from one installation and uploaded to another where the database is different. Fixing ids is possible, however this requires looking up correct plugin ids in the database and this is just a hack - not a real solution.