Bug 1338965
| Summary: | necessary tag is not imported, preventing logging deployment | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Luke Meyer <lmeyer> |
| Component: | Logging | Assignee: | Luke Meyer <lmeyer> |
| Status: | CLOSED ERRATA | QA Contact: | chunchen <chunchen> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.2.0 | CC: | aos-bugs, boris.ruppert, chunchen, dyocum, jkaur, lmeyer, pep, tdawson, wsun, xiazhao |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
Cause:
When ImageStreams are created, only a subset of the available tags are imported, and this often excluded the desired tag.
Consequence:
If the desired tag isn't imported, then the corresponding component never deploys.
Workaround (if any):
Import each tag manually like so:
oc import-image <name>:<version> --from <prefix><name>:<tag>
The bug is fixed in 3.3 by not relying on ImageStreams and DC triggers for deployment.
Result:
Deployment occurs as expected.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-09-27 09:33:03 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1267746 | ||
|
Description
Luke Meyer
2016-05-23 18:31:41 UTC
Commit pushed to master at https://github.com/openshift/openshift-docs https://github.com/openshift/openshift-docs/commit/0e6244897c81dabf0a6634d69a683d0dd2c48bd7 logging: manually import tags for deployment Docs fix to bug 1338965 https://bugzilla.redhat.com/show_bug.cgi?id=1338965 This is an ugly workaround, but hopefully short-term. *** Bug 1339060 has been marked as a duplicate of this bug. *** Docs workaround at https://github.com/openshift/openshift-docs/pull/2141 FYI, The change is also needed in upgrade doc https://docs.openshift.com/enterprise/3.2/install_config/upgrading/manual_upgrades.html#manual-upgrading-efk-logging-stack While there's a docs workaround that helps in the logging deployment (and possibly others), shouldn't this track the problem of import-image? I.e. https://github.com/openshift/origin/pull/9163 and if so, we should probably move it from Logging to CLI. (In reply to Josep 'Pep' Turro Mauri from comment #5) > While there's a docs workaround that helps in the logging deployment (and > possibly others), shouldn't this track the problem of import-image? > > I.e. https://github.com/openshift/origin/pull/9163 I wouldn't expect that to get into Enterprise before 3.3, and by that time I fully expect to have eliminated the problem by removing the usage of ImageStreams in logging deployment. Agree a note in the upgrade doc would help too until then. (In reply to Xia Zhao from comment #4) > FYI, The change is also needed in upgrade doc > https://docs.openshift.com/enterprise/3.2/install_config/upgrading/ > manual_upgrades.html#manual-upgrading-efk-logging-stack Could you validate that https://github.com/openshift/openshift-docs/pull/2428 addresses the problem and the upgrade sequence works with this in place? I think we'll want to keep this bug open to track the ultimate solution to this; docs are a stopgap. @lmeyer The modification on upgrade doc and also the sequence mentioned looks good to me. Note published in the upgrade docs https://docs.openshift.com/enterprise/latest/install_config/upgrading/manual_upgrades.html#manual-upgrading-efk-logging-stack Keeping the bug open for tracking removing imagestreams entirely. As of 3.3 imagestreams and DC triggers are not a part of the deployment, so this should not be a problem. Yes, we never encountered this issue with the 3.3.0 logging deployer, set to verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1933 |