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

Fix update driven refresh initialization #108

Merged
merged 1 commit into from
Sep 27, 2017

Conversation

agrare
Copy link
Member

@agrare agrare commented Sep 15, 2017

The change in the base RefreshWorker::Runner (ManageIQ/manageiq@984a3a2) to allow an array of EMSes
caused issues in this case where we were using the @ems var directly in
the runner for update driven refresh.

The change in the base RefreshWorker::Runner to allow an array of EMSes
caused issues in this case where we were using the @ems var directly in
the runner for update driven refresh.
@agrare agrare added the bug label Sep 15, 2017
@miq-bot
Copy link
Member

miq-bot commented Sep 15, 2017

Checked commit agrare@7da5750 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
1 file checked, 0 offenses detected
Everything looks fine. 🏆

@blomquisg blomquisg merged commit 1343012 into ManageIQ:master Sep 27, 2017
@blomquisg blomquisg added this to the Sprint 70 Ending Oct 2, 2017 milestone Sep 27, 2017
@agrare agrare deleted the fix_update_drive_refresh branch September 27, 2017 13:55
agrare pushed a commit to agrare/manageiq-providers-vmware that referenced this pull request Apr 15, 2019
…eck_powered_off

Automate - Refactoring infra vm check_powered_off method.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants