Wallably/Master: Overcloud deploy steps contains services that are not enabled
Bug #1932584 reported by
Ronelle Landy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Triaged
|
High
|
Unassigned |
Bug Description
In Wallaby/Master, the overcloud/
This results in CI pulling containers, the jobs will never use - and also distorts the information of what is actually deployed.
This was not the case in Train. See comparative overcloud log below:
Note from Alex:
We lost the prune unused service code somewhere along the line https:/
Changed in tripleo: | |
milestone: | none → xena-1 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in tripleo: | |
milestone: | xena-1 → xena-2 |
Changed in tripleo: | |
milestone: | xena-2 → xena-3 |
To post a comment you must log in.
Related fix proposed to branch: master /review. opendev. org/c/openstack /python- tripleoclient/ +/797150
Review: https:/