Bug 1808282
| Summary: | Deploy Image: "Image name from internal registry" with Knative Service creates a broken ImageStream | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jaivardhan Kumar <jakumar> | ||||
| Component: | Dev Console | Assignee: | Jaivardhan Kumar <jakumar> | ||||
| Status: | CLOSED ERRATA | QA Contact: | spathak <spathak> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.3.0 | CC: | aos-bugs, cvogt, gamore, nmukherj, rgarg, spathak, talessio | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.3.z | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Cause: In case of Container image deployment if internal image stream sis selected for knative then as well it tries to create new Image Stream and thus may fail
Consequence: Unable to deploy image (internal image stream) as knative service
Fix: Don create new Image Stream for internal image selection as it already exists.
Result: Able to deploy as knative service for internal image registry
|
Story Points: | --- | ||||
| Clone Of: | 1808280 | Environment: | |||||
| Last Closed: | 2020-03-24 14:34:23 UTC | Type: | --- | ||||
| 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: | 1808280 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Jaivardhan Kumar
2020-02-28 07:08:25 UTC
@cvogt @jakumar @rgarg It has been blocked because of https://issues.redhat.com/browse/ODC-3363 Created attachment 1671249 [details]
Deploy Image: "Image name from internal registry" with Knative Service creates a fine ImageStream
Verified on build: 4.3.0-0.ci-2020-03-18-122927 Chrome browser: 76.0.3809.132 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-2020:0858 |