-
Notifications
You must be signed in to change notification settings - Fork 898
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
[V2V] Provide placeholder params for the ConversionHost#disable method #18691
Conversation
@miq-bot add_label bug, transformation, hammer/yes |
@djberg96 can you add specs to cover these cases? |
@agrare Working on it. I'm actually somewhat baffled that the existing |
@djberg96 that doesn't actually deliver the message so it never tried to call the disable method, you could call |
@agrare Ok, added a spec, and confirmed that it fails if the params are removed. Only downside is that I couldn't get it to work without resorting to Or, if you have any suggestions... :) |
Specifically, if I use the usual This results in a Does it have a different internal reference when the |
@djberg96 I think that's because MiqQueue is doing a query for the record so it is getting its own copy not the mocked object from the spec. You could possibly doing something like |
@agrare Fantastic, thanks, updated. |
Checked commits https://github.com/djberg96/manageiq/compare/c6515e93ed4ee0826e184e606efa12a67fe30221~...6941105053dac1d57e010a8e3624666a38906314 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
[V2V] Provide placeholder params for the ConversionHost#disable method (cherry picked from commit 32fa034) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1704457
Hammer backport details:
|
Currently the
disable_queue
method will fail withwrong number of arguments (given 2, expected 0)
. This is because thedisable_queue
method calls thequeue_configuration
method which automatically passesparams
andargs
to whatever the op is.So, this PR just adds a couple dummy placeholder parameters in order to comply with the interface.
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1703254