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.
DescriptionJaivardhan Kumar
2020-03-02 14:37:25 UTC
+++ This bug was initially created as a clone of Bug #1807868 +++
Description of problem:
On editing knative Service from topology view with different image not creating new revision.
Version-Release number of selected component (if applicable):4.4
How reproducible: Always
Steps to Reproduce:
1. Install serverless operator
2. Go to Add -> container image
3. search for `invincibleJai/tag-portal-v1` and create kn service
4. kn service is created can view in topology
5. Edit kn service
6. Change image from `invincibleJai/tag-portal-v1` to `invincibleJai/scrumola` and save
Actual results: No revision will be created
Expected results:The revision will be created
Additional info:
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:0581