Bug 1710021
Summary: | openstack tripleo container image prepare default generates settings twice | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Ronelle Landy <rlandy> |
Component: | openstack-tripleo-common | Assignee: | Martin André <m.andre> |
Status: | CLOSED NOTABUG | QA Contact: | Alexander Chuzhoy <sasha> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 14.0 (Rocky) | CC: | aschultz, m.andre, mburns, slinaber, whayutin |
Target Milestone: | --- | Keywords: | PromotionBlocker, ZStream |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-17 11:13:04 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ronelle Landy
2019-05-14 18:38:41 UTC
Martin, the bug has nothing to do w/ the job passing or failing. The bug is only about the parameters getting generated twice. In manual runs, we have modified the output-env-file to remove the 'includes' section and the stack creation completed. Kicking off a run with the exact revert to check. Martin, help me understand... It doesn't make sense why the file would have both --include and --excludes openshift. Why would this be the case? Also why is there difference between rocky and osp-14 in this regard? (In reply to wes hayutin from comment #6) > Martin, help me understand... > It doesn't make sense why the file would have both --include and --excludes > openshift. Why would this be the case? > Also why is there difference between rocky and osp-14 in this regard? For all non OpenShift images (the struct with exludes: [openshift]), we want them to be processed the same way they used to be processed with tag_from_label, no changes for them. For all OpenShift images (the stuct with includes: [openshift]), we do not want to retag the images so we removed the tag_from_label key. However, in order to get tripleo-common to happily process the file we had to duplicate some of the openshift keys in the exclude block. That's what makes it confusing. Now, it's downstream only because it fixes a bug [1] that only manifests downstream. The bug is caused by the downstream image naming and sometime inconsistent tagging, and I didn't want to introduce the extra complexity uptream where it's not needed. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1659183 Closing as NOTABUG, we found the issue is in how tripleo-quickstart processes the containers-prepare-parameters.yaml file. |