no manifest for deploying nova-metadata specific resources

Bug #1625679 reported by Juan Antonio Osorio Robles
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet-nova
Triaged
Low
Unassigned
tripleo
Expired
Undecided
Unassigned

Bug Description

so, currently for deploying nova-metadata in a different node, we need to use api.pp which sets up several things which are not really needed. It would be nice to get the ability to deploy only metadata-specific things. We notice this in tripleo, since we can't have the api and metadata in separate nodes due to this.

Changed in tripleo:
milestone: none → ocata-1
importance: Undecided → Low
Changed in puppet-nova:
importance: Undecided → Low
status: New → Confirmed
Steven Hardy (shardy)
Changed in tripleo:
milestone: ocata-1 → ocata-2
Changed in tripleo:
status: New → Confirmed
Changed in tripleo:
milestone: ocata-2 → ocata-3
Changed in tripleo:
status: Confirmed → Triaged
Changed in puppet-nova:
status: Confirmed → Triaged
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
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: Low → 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.