Bug 1264765
Summary: | Upgrade failed if some imagesteam/template doesn't exist | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Anping Li <anli> |
Component: | Cluster Version Operator | Assignee: | Scott Dodson <sdodson> |
Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 3.0.0 | CC: | aos-bugs, bleanhar, jokerman, mmccomas, sdodson |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-19 23:29:08 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
Anping Li
2015-09-21 07:19:18 UTC
I've switched to oc replace, please pull the latest code and re-test, thanks. I can saw the 'oc replace' after pull the latest code. How about the template/imagestream replace issue. There are no jenkins imagestream in a prior /usr/share/openshift/examples/image-streams/image-streams-rhel7.json. so there is the strong possibility that the customer hit "Error from server: imageStream "jenkins" not found". Could we fix it? I think the sequence for 'replace imagestream/template' is illogical. it is better to replace them after package was upgraded. How do you think about that? Thanks, I've changed it such that it runs the normal install to create them later runs the update command. This should avoid the issue you're seeing while ensuring that newly created image streams are installed. Please pull the latest and give it another test. Thanks The 'update is/template' work fine, no error was reported now. 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/RHEA-2015:2492 |