Bug 1807868
Summary: | Edit flow for knative Service with image change not creating new revision | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jaivardhan Kumar <jakumar> | |
Component: | Dev Console | Assignee: | Jaivardhan Kumar <jakumar> | |
Status: | CLOSED ERRATA | QA Contact: | Gajanan More <gamore> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 4.4 | CC: | aos-bugs, gamore, nmukherj | |
Target Milestone: | --- | |||
Target Release: | 4.5.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Cause: On editing image name for knative service same existing ImageStream get's updated even if image is completely different.
Consequence: Change in image name while editing knative Service is not creating a new revision.
Fix: In case of knative service edit, generating new Image Stream with name-randomChars and update service with new image registry url and filtering image stream based on instance name.
Result: Change in image name while editing knative Service will trigger a new revision as expected.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1809178 (view as bug list) | Environment: | ||
Last Closed: | 2020-07-13 17:21:42 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: | 1809178 |
Description
Jaivardhan Kumar
2020-02-27 12:02:28 UTC
I have validated this bug on Build: 4.5.0-0.ci-2020-03-10-023720 Browser: Google Chrome 78.0.3904.108 Marking this bug as 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-2020:2409 |