Description of problem:
This is a bit of a random bug, but if you enable many environment files you can recreate it easily. When you switch to the "Parameters" tab in the configuration dialog and click on the various enabled environments to edit their parameters - you eventually get an error "Deployment parameters could not be loaded".
ConsoleAdapter.js:33 Deployment parameters could not be loaded t t
at m (https://puma01.scl.lab.tlv.redhat.com/tripleo_ui.js:38:13704)
at V (https://puma01.scl.lab.tlv.redhat.com/tripleo_ui.js:137:3076)
at j (https://puma01.scl.lab.tlv.redhat.com/tripleo_ui.js:137:2708)
at C.when (https://puma01.scl.lab.tlv.redhat.com/tripleo_ui.js:137:6557)
at E.run (https://puma01.scl.lab.tlv.redhat.com/tripleo_ui.js:137:5385)
at e._drain (https://puma01.scl.lab.tlv.redhat.com/tripleo_ui.js:126:542)
at drain (https://puma01.scl.lab.tlv.redhat.com/tripleo_ui.js:126:196)
at MutationObserver.t (https://puma01.scl.lab.tlv.redhat.com/tripleo_ui.js:62:322)s.value @ ConsoleAdapter.js:33
132 console messages are not shown.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Enable many environments (I selected all the Cinder backends)
2. Switch to the "Parameters" tab
3. Click to edit the parameters of some of the enabled environments
You get "Deployment parameters could not be loaded". It seems like maybe the operation took too long.
You should never get an error.
Proposing to make this a blocker for 12. This error, and other related websocket disconnection errors, occur now in an intolerable frequency during normal working with the UI (at all stages and not just in the configuration dialog). If you press F5 there is a good chance you'll get the error a second time in a row. Many times the error seems to have no real affect on the app, but still a user will get very upset that it doesn't stop happening.
Cannot easily reproduce. Not seeing it on other environments at this time I propose to not make it a blocker.
This error is usually caused by error in selected environments. If there is an error in environment file which gets enabled, Heat validation will fail and GUI/tripleo-common will fail to retrieve parameters.
Problem I see here is with the error message. It seems that error names are affected by minification in production code in GUI and that causes the relevant error message not to appear. I am going to try to reproduce this in production built code.
Fixing the launchpad bug ensures that production code correctly shows error message coming from Heat. Example:
Deployment parameters could not be loaded
404 Client Error: Not Found for url: http://192.168.24.1:8080/v1/AUTH_bca7e29c655a42d1b7018befd2a2e8a0/test-broken-environment/environments/puppet/extraconfig/tls/tls-cert-inject.yaml
Testing is blocked by bug https://bugzilla.redhat.com/show_bug.cgi?id=1567893
Verified in openstack-tripleo-ui-8.3.1-2.el7ost.noarch.
There are still references to non-existent yamls in the templates, but the error message you get is clear enough so from the GUI's point of view this bug is now handled properly.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.