puppet functions like ensure_resource normally ignore tags, and containerized services templates may depend on those being tagged

Bug #1777393 reported by Bogdan Dobrelya on 2018-06-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

See https://review.openstack.org/#/c/575583 for the context of this issue.

There may be a few ensure_* functions in puppet-openstack/tripleo modules which is expected to be invoked or omitted based on tags specified in t-h-t for containerized services (puppet_config steps). This will not be the case unless we tag those functions, like indirectly, via tagged anchors for the resources those produce, e.g.:

anchor {'foo': tag => 'foo'}
ensure_resource('user', 'foo', {'ensure' => 'absent'})
Anchor['foo'] -> User['foo']

We need to inspect puppet modules used in tht for puppet_config dicts if there is any flaws in tags management. Otherwise, some of the existing ensure_* calls may be either missed or unexpected.

Changed in tripleo:
importance: Undecided → Medium
milestone: none → rocky-3
tags: added: containers tech-debt
Changed in tripleo:
status: New → Triaged
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Changed in tripleo:
milestone: stein-2 → stein-3
Changed in tripleo:
milestone: stein-3 → train-1
Changed in tripleo:
milestone: train-1 → train-2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers