New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug 1871895: Use form data for application ImageStream name #6410
Conversation
@rottencandy: This pull request references Bugzilla bug 1871895, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/bugzilla refresh |
@rottencandy: This pull request references Bugzilla bug 1871895, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/kind bug |
@@ -239,6 +239,7 @@ export const getUserLabels = (resource: K8sResourceKind) => { | |||
'app.kubernetes.io/part-of', | |||
'app.openshift.io/runtime-version', | |||
'app.openshift.io/runtime-namespace', | |||
'app.openshift.io/runtime-icon', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please revert this change to use runtime
label. runtime label itself points the imagestream icon.
'app.openshift.io/runtime-icon', | |
'app.openshift.io/runtime', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
@rottencandy: This pull request references Bugzilla bug 1871895, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm |
@divyanshiGupta I'm still working on Sahil's comment. |
Oops missed that. Let me know once you are done. |
e4d729e
to
edc95ce
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/assign @invincibleJai |
@rottencandy: This pull request references Bugzilla bug 1871895, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
initialValues.imageStream.image && | ||
values.imageStream.image !== initialValues.imageStream.image | ||
) { | ||
initialValues.imageStream.image = values.imageStream.image; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
resetting initial values seems odd @rohitkrai03 @divyanshiGupta thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's generally not recommended to change the initial values but here I think resetting the initial value is fine if this solves the issue since we just need the initial value only when the form is opened.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This effect gets fired the first time ImageStreamDropdown
is changed, it's meant to verify the current namespace permissions, but ends up resetting the selected ImageStream name back to the initial value.
/approve Verified the changes , works as expected /cc @karthikjeeyar |
Verified locally and it works fine. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: divyanshiGupta, invincibleJai, karthikjeeyar, rottencandy The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@rottencandy: All pull requests linked via external trackers have merged: Bugzilla bug 1871895 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fixes:
https://issues.redhat.com/browse/ODC-4615
https://issues.redhat.com/browse/ODC-4649
Analysis / Root cause:
The add flow tries to get image name from imagestream labels, which may not be always present.
Solution Description:
Use application form data to get image stream name.
Screen shots / Gifs for design review:
Unit test coverage report:
Passing.
Browser conformance: