-
Notifications
You must be signed in to change notification settings - Fork 91
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
Fix for refresh of dialog fields not being called in some circumstances #1454
Conversation
Checked commit eclarizio@119bd0f with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
@AllenBW or @chalettu can you please review and look at the travis failure? @eclarizio doesn't think the travis failure has anything to do with the code changes. Thx, Dan |
So one issue I see is that we have dialogs that are used in 3 places in Service UI and this PR seems to only cover 1 of those places. The other two places are custom button detail page and also service reconfigure page. Please take a look and ensure that this change if relevant is applied to these pages as well. |
@dclarizio, Travis sometimes fails, just gotta give it a kick, looks good now |
@AllenBW , I kicked the job back off and it seems to be going ok. |
@chalettu I think we're good to go here, those two places are unrelated to this change. |
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 change looks solid. Thank you for updating the tests.
@eclarizio if resourceActions is null, does looking for .id blow this up? |
@AllenBW You mean if the |
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.
Lg2m!!!
Fix for refresh of dialog fields not being called in some circumstances (cherry picked from commit 8bbdd5e) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1600738
Gaprindashvili backport details:
|
The root cause is that we were defaulting to use the first
resourceAction
as long as theaction
was'Provision'
. However, in this case,serviceTemplate.resourceActions
returned two, and theaction
property for the first one was'Retirement'
and the second was'Provision'
. However, since we were only checking theaction
for the first in the list, the id was ending up as an empty string and thus the API call was simply failing in the backend.So, this piece of code now finds the correct provision
resourceAction
.Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1598475
@miq-bot add_label gaprindashvili/yes, bug, blocker
/cc @tinaafitz , @d-m-u
@d-m-u Can you review?
@dclarizio Not sure who this should be assigned to, haven't done service-ui work in a while, please advise!