unify parameter defininition

Bug #1640243 reported by Jiri Tomasek on 2016-11-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Undecided
Unassigned

Bug Description

Identical parameters defined in templates of tripleo-heat-templates repository should have the same definition. Result of this is that parameters list can be extracted from nested resources tree (result of heat-validate) where each parameter is uniquely identified by it's name.

It is possible that certain parameter defined in multiple templates has different definition in each of those, but in this case it must be ensured that such templates will never be used together.

Jiri Tomasek (jtomasek) wrote :

I'll try to provide a list of colliding parameters

Steven Hardy (shardy) wrote :

We should add a test for this in this validation (which runs in the gate):

https://github.com/openstack/tripleo-heat-templates/blob/master/tools/yaml-validate.py

Changed in tripleo:
status: New → Triaged
Steven Hardy (shardy) wrote :

Writing that test would also automatically generate the list of colliding parameters ;)

Changed in tripleo:
milestone: ocata-2 → ocata-3
Changed in tripleo:
milestone: ocata-3 → pike-1
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

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  Edit
Everyone can see this information.

Other bug subscribers