Bug 1518806
| Summary: | logging-es-data-master DC images using "v3.7" tag instead of using openshift_image_tag | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Justin Pierce <jupierce> |
| Component: | Installer | Assignee: | Scott Dodson <sdodson> |
| Status: | CLOSED DUPLICATE | QA Contact: | Johnny Liu <jialiu> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.7.0 | CC: | aos-bugs, jokerman, mmccomas, pportant, sdodson, vrutkovs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-01-17 14:44:36 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: | |||
Linked a related bug, if we're 100% certain that openshift_image_tag will always exist for all the images I think it's fine to default everything to using that image tag. This would then mean that they'd unless they override the values they'll only ever run a version matched to the master though. Do we want that? I think it makes sense for any component considered "core" -- which logging effectively is now. Without a pretty broad default, we might find ourselves regularly discovering new components that need inventory changes. That process of discovery is going to be very error prone since it is extremely easy (as in this case) for it to go undetected. Sounds like its another duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1530183 Yeah, same general problem. *** This bug has been marked as a duplicate of bug 1530183 *** |
Description of problem: Installed v3.7.9 (~GA) and found that logging/logging-es-data-master-* DCs were all using a "v3.7" tag instead of the value of openshift_image_tag ("v3.7.9" set in our inventory). Version-Release number of selected component (if applicable): v3.7.9 How reproducible: 100% . Seems to be by design. From openshift-ansible/roles/openshift_logging_elasticsearch/vars/openshift-enterprise.yml: __openshift_logging_elasticsearch_image_version: "{{ openshift_logging_image_version | default ('v3.7') }}" __openshift_logging_elasticsearch_proxy_image_prefix: "{{ openshift_logging_image_prefix | default('registry.access.redhat.com/openshift3/') }}" __openshift_logging_elasticsearch_proxy_image_version: "{{ openshift_logging_image_version | default ('v3.7') }}" Expected results: openshift_image_tag should provide a basis for all OCP component image versions. Description of problem: Version-Release number of the following components: rpm -q openshift-ansible rpm -q ansible ansible --version How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Please include the entire output from the last TASK line through the end of output if an error is generated Expected results: Additional info: Please attach logs from ansible-playbook with the -vvv flag