Skip to content
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

A correct ems_ref for saving #12021

Merged
merged 1 commit into from
Oct 18, 2016

Conversation

Ladas
Copy link
Contributor

@Ladas Ladas commented Oct 18, 2016

A correct ems_ref for saving, we were providing an id attribute,
which didn't exist in the hash, causing this code always
delete&create instead of updating of the rows.

A correct ems_ref for saving, we were providing an id attribute,
which didn't exist in the hash, causing this code always
delete&create instead of updating of the rows.
@Ladas
Copy link
Contributor Author

Ladas commented Oct 18, 2016

@blomquisg I am making specs for this in AWS, I actually discovered this bug using the stubbed specs. :-)

@miq-bot
Copy link
Member

miq-bot commented Oct 18, 2016

Checked commit Ladas@3b92d66 with ruby 2.2.5, rubocop 0.37.2, and haml-lint 0.16.1
1 file checked, 0 offenses detected
Everything looks good. 🏆

@blomquisg blomquisg merged commit 91c1c66 into ManageIQ:master Oct 18, 2016
@blomquisg blomquisg added this to the Sprint 48 Ending Oct 24, 2016 milestone Oct 18, 2016
chessbyte pushed a commit that referenced this pull request Oct 19, 2016
A correct ems_ref for saving
(cherry picked from commit 91c1c66)
@chessbyte
Copy link
Member

Euwe Backport details:

$ git log -1
commit 5988f516579c071dcbd03af40309e196e41c65d9
Author: Greg Blomquist <blomquisg@gmail.com>
Date:   Tue Oct 18 13:22:57 2016 -0400

    Merge pull request #12021 from Ladas/correct_ems_ref_for_saving

    A correct ems_ref for saving
    (cherry picked from commit 91c1c660ef0e249db6424995299bf379e1cf5857)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants