-
Notifications
You must be signed in to change notification settings - Fork 63
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
Make container events belong to pod #181
Conversation
67d0116
to
09b20cc
Compare
For some reason I feel I'd keep the EmsEvents names and translate in automate definitions (ManageIQ/manageiq-content#225), eg. CONTAINER_FAILED would raise MiqEvent containergroup_containerfailed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
@miq-bot add_label gaprindashvili/yes |
@miq-bot add_label fine/yes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
eb04b65
to
471155e
Compare
471155e
to
8a1ffe7
Compare
8a1ffe7
to
419f802
Compare
Checked commits zeari/manageiq-providers-kubernetes@5a4b012~...419f802 with ruby 2.3.3, rubocop 0.47.1, haml-lint 0.20.0, and yamllint 1.10.0 |
ManageIQ/manageiq#16583 was merged. |
Make container events belong to pod (cherry picked from commit ba505c1) https://bugzilla.redhat.com/show_bug.cgi?id=1530651
Gaprindashvili backport details:
|
Fine backport (to manageiq repo) details:
|
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1496179
This makes
event_data[:event_type]
equalPOD_FAILED
instead of
CONTAINER_FAILED
part of ManageIQ/manageiq#16583
@cben @moolitayer @enoodle Please review