Skip to content

Fix libvirt_events engine running on master#46928

Merged
rallytime merged 3 commits into
saltstack:developfrom
cbosdo:libvirt-events-fix
Apr 10, 2018
Merged

Fix libvirt_events engine running on master#46928
rallytime merged 3 commits into
saltstack:developfrom
cbosdo:libvirt-events-fix

Conversation

@cbosdo
Copy link
Copy Markdown
Contributor

@cbosdo cbosdo commented Apr 6, 2018

What does this PR do?

Parameters order is different when firing events on master or minion.
The order for master was wrong. Also added documentation on how to setup
polkit to run the engine on a master node.

What issues does this PR fix or reference?

None reported

Previous Behavior

Error when firing libvirt events when running on master node

New Behavior

Libvirt events sent on master node as well

Tests written?

No - trivial fix

Commits signed with GPG?

Yes

Copy link
Copy Markdown
Contributor

@cachedout cachedout left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tiny grammatical change. The rest looks great!

Comment thread salt/engines/libvirt_events.py Outdated
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

non-root

Parameters order is different when firing events on master or minion.
The order for master was wrong. Also added documentation on how to setup
polkit to run the engine on a master node.
@cbosdo cbosdo force-pushed the libvirt-events-fix branch from 4013ecd to 4ca6f2c Compare April 9, 2018 07:52
@cbosdo
Copy link
Copy Markdown
Contributor Author

cbosdo commented Apr 9, 2018

Fixed the non-root

@rallytime rallytime merged commit 32f7259 into saltstack:develop Apr 10, 2018
@cbosdo cbosdo deleted the libvirt-events-fix branch April 27, 2018 08:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants