-
Notifications
You must be signed in to change notification settings - Fork 897
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 inability to see dialog details passed to catalog after upgrade from 5.9.4 to 5.9.6 #18469
Conversation
@miq-bot add_label hammer/yes |
Checked commit eclarizio@142c158 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
@eclarizio I'm not sure where in the scheme of things this occurs, but we've found that if objects are created through the api, such as creating a request in a global region, the keys of options hashes become symbols because json has no notion of string/symbol keys so the api creates things with symbol keys. This could cause a failure down the line when another area of code, such as the code in this PR, tries to access activerecord objects and they have symbols keys when the code was expecting string keys. Making the hash indifferent is the easiest solution and should fix most problems in this area. 👍 |
@jrafanie The reported issue has to do with an upgrade and ordering a service from the global region. |
That sounds like it could be related. If the global region ordering is using the API from the global to create objects in the remote region, it's probably hitting this string/symbol issue. It's good to change this to indifferent access on the client |
Customer reported issue on 5.9. Erik said it should be okay to back port. |
Fix for inability to see dialog details passed to catalog after upgrade from 5.9.4 to 5.9.6 (cherry picked from commit 16dabe5) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1688870
Hammer backport details:
|
Fix for inability to see dialog details passed to catalog after upgrade from 5.9.4 to 5.9.6 (cherry picked from commit 16dabe5) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1688871
Gaprindashvili backport details:
|
I don't know the underlying cause of the issue, but when
#init_fields_with_values_for_request
is called, sometimes the keys of thevalues
hash that gets passed in are symbols instead of strings. This caused an issue of initializing dialog fields with nil values and the customer unable to view the data of the request they made.Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1670327
/cc @tinaafitz @d-m-u
@miq-bot add_label bug
@miq-bot add_reviewer @d-m-u
@miq-bot assign @tinaafitz