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

[Neon] Grains in minion startup event #54948 #55870

Closed
max-arnold opened this issue Jan 15, 2020 · 2 comments
Closed

[Neon] Grains in minion startup event #54948 #55870

max-arnold opened this issue Jan 15, 2020 · 2 comments
Labels
Bug broken, incorrect, or confusing behavior fixed-pls-verify fix is linked, bug author to confirm fix severity-critical top severity, seen by most users, serious issues
Milestone

Comments

@max-arnold
Copy link
Contributor

I just discovered that this feature (when enabled) will append grains to other events sent from a minion (not just the start event):

Both commands:

sudo salt minion1 state.single event.send name='tag' data='{"data":"my event data"}'
sudo salt minion1 event.fire_master '{"data":"my event data"}' 'tag'

result in the following master event:

tag	{
    "_stamp": "2020-01-15T07:55:24.548188",
    "cmd": "_minion_event",
    "data": {
        "data": "my event data"
    },
    "grains": {
        "machine_id": "599118d5b9619443ac3166fb0e59349e",
        "uuid": "599118d5-b961-9443-ac31-66fb0e59349e"
    },
    "id": "minion1",
    "pretag": null,
    "tag": "tag"
}

def _fire_master_minion_start(self) seems to be better suited for this code.

was that a suggestion that we should create a new PR to update this behavior? If so, would you mind opening an issue so it doesn't get lost here in the PR? Otherwise feel free to ignore this comment

@waynew Yes, that was a suggestion that something should be fixed - either the actual behavior, or the setting name and docs.

CC: @admd

@Ch3LL
Copy link
Contributor

Ch3LL commented Jan 16, 2020

thanks for opening up the issue with the details. really appreciate it.

@Ch3LL Ch3LL added Bug broken, incorrect, or confusing behavior fixed-pls-verify fix is linked, bug author to confirm fix severity-critical top severity, seen by most users, serious issues labels Jan 16, 2020
@Ch3LL Ch3LL added this to the Approved milestone Jan 16, 2020
@sagetherage
Copy link
Contributor

@max-arnold @admd looks like the PR is merged ok to close this ticket knowing it is getting into the Neon release?

@Ch3LL Ch3LL closed this as completed Jan 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior fixed-pls-verify fix is linked, bug author to confirm fix severity-critical top severity, seen by most users, serious issues
Projects
None yet
Development

No branches or pull requests

3 participants