-
Notifications
You must be signed in to change notification settings - Fork 897
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 event linking to a disconnected VM #16907
Fix event linking to a disconnected VM #16907
Conversation
I tried to find where we set
But we don't initialize event hashes like this anymore so I think it is safe to change to something more standard. If we want to be extra safe I can just do:
|
07f0d22
to
f1e873b
Compare
When linking events to a VM we first try [ems_id, ems_ref] which fails to find a disconnected VM because the ems_id is nullified. Next we try by uid_ems but no one was setting the field that we were using so this standardizes on an event key :vm_uid_ems (similar to :vm_location) which can be set by the EventParser to allow events to be connected to VMs after they are disconnected. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1538996
f1e873b
to
5bea3d8
Compare
Checked commit agrare@5bea3d8 with ruby 2.3.3, rubocop 0.52.0, haml-lint 0.20.0, and yamllint 1.10.0 |
|
…sing Fix event linking to a disconnected VM (cherry picked from commit 4f06547) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1552677
Gaprindashvili backport details:
|
When linking events to a VM we first try [ems_id, ems_ref] which fails
to find a disconnected VM because the ems_id is nullified. Next we try
by uid_ems but no one was setting the field that we were using so this
standardizes on an event key :vm_uid_ems (similar to :vm_location) which
can be set by the EventParser to allow events to be connected to VMs
after they are disconnected.
Depends:
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1538996