A slight error in the templates can get you thrown out of the GUI

Bug #1666000 reported by Udi Kalifon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

I had this in my network-isolation.yaml:

parameters:
  NeutronExternalNetworkBridge: "''"

The mistake is that this should be under parameter_defaults instead of parameters... When this plan was loaded into the GUI it was nearly impossible to work with it:

=> You get thrown out within 2 minutes, even if you don't touch anything. You get this alert when it happens:
Failed to run Action
Failed to run action [action_ex_id=None, action_cls='<class 'mistral.actions.action_factory.GetParametersAction'>', attributes='{}', params='{u'container': u'broken2'}'] ERROR: The Parameter (NeutronExternalNetworkBridge) was not defined in template.

=> When you open the plan parameters, it doesn't list a single parameter in the dialog. Instead it just shows:
There are currently no parameters to configure in this section

=> When you try to edit a role it also doesn't list any parameters or any services. You see on of these 2 messages in the different dialog pages:
1) There are currently no parameters to configure in this section
2) Please select service to configure

=> Delete plan starts and stops almost immediately, and the plan is not deleted. After several retries the plan is deleted, but sometimes the swift container is still not deleted (you're in a half-deleted state).

The same plan exactly without this mistake deploys with no problems and the GUI works smoothly. These tests were done on Newton, and I don't have a working environment with Ocata to see if the bug happens there too, but I'm guessing it would still be relevant there also.

Changed in tripleo:
status: New → Triaged
importance: Undecided → Medium
milestone: none → pike-1
tags: added: ocata-backport-potential
Changed in tripleo:
milestone: pike-1 → pike-2
Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

Changed in tripleo:
importance: Medium → Undecided
status: Triaged → Expired
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.