TripleO Satellite Registration functionality overwrite Operator integration point

Bug #1709441 reported by James Slagle on 2017-08-08
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
High
Unassigned

Bug Description

From Graeme Gillies (<email address hidden>):

Hi,

When using TripleO command openstack overcloud deploy with any of the satellite options, we can see in the code that it actually does this by leveraging the heat resource OS::TripleO::NodeExtraConfig

https://github.com/openstack/tripleo-heat-templates/blob/master/extraconfig/pre_deploy/rhel-registration/rhel-registration-resource-registry.yaml#L2

The documentation we give users however tells them they can use OS::TripleO::NodeExtraConfig to extend and apply their own arbitrary configuration across all nodes. So if a user passes the rhel registration parameters to the overcloud deploy command, and then supplies their own implementation of OS::TripleO::NodeExtraConfig, then only 1 wins (usually the users work), meaning you silently never get registration happening, with no feedback on why, leaving the user very confused.

The rhel registration stuff should be moved to its own resources (and set to none when not used)

Regards,

Graeme

Changed in tripleo:
status: New → In Progress
importance: Undecided → High
assignee: nobody → James Slagle (james-slagle)
milestone: none → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → pike-rc2
Changed in tripleo:
milestone: pike-rc2 → 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

Change abandoned by James Slagle (<email address hidden>) on branch: master
Review: https://review.openstack.org/491881

Changed in tripleo:
status: In Progress → Triaged
assignee: James Slagle (james-slagle) → nobody
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
Changed in tripleo:
milestone: stein-2 → stein-3

Is this still an issue?

Changed in tripleo:
milestone: stein-3 → stein-rc1
Changed in tripleo:
milestone: stein-rc1 → train-1
Changed in tripleo:
milestone: train-1 → train-2
Changed in tripleo:
milestone: train-2 → train-3
Changed in tripleo:
milestone: train-3 → ussuri-1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers