-
Notifications
You must be signed in to change notification settings - Fork 120
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 their container groups #225
Conversation
da50cfe
to
ab43065
Compare
@lfu Please review |
LGTM 👍 |
@@ -4,9 +4,11 @@ version: 1.0 | |||
object: | |||
attributes: | |||
display_name: | |||
name: CONTAINER_FAILED | |||
name: POD_CONTAINERCREATED |
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.
I can't find where this event is created?
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.
Looks like a weird git error.
container_created and container_failed got criss-crossed in file rename
Kubernetes.class/container_created.yaml → ...Kubernetes.class/pod_containerfailed.yaml
Kubernetes.class/container_failed.yaml → ...Kubernetes.class/pod_containercreated.yaml
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.
OK didn't found where the POD prefix is being added. @zeari located it
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.
@cben so adding the policies, we will likely see a lot of failures with target not found in log.
Should we first solve that target is always refreshed before running the policy?
@cben <https://github.com/cben> so adding the policies, we will likely
see a lot of failures with target not found in log.
Yes but same is true of existing Pod & Replicator policies support :-(
They are nearly unusable.
We need to add these events, and independently we need to solve
event-before-refresh.
|
Checked commits zeari/manageiq-content@ab43065~...a6f4ba0 with ruby 2.3.3, rubocop 0.47.1, haml-lint 0.20.0, and yamllint 1.10.0 **
|
@lfu @gmcculloug Please merge. |
Make container events belong to their container groups (cherry picked from commit 1696ac1) https://bugzilla.redhat.com/show_bug.cgi?id=1530651
Gaprindashvili backport details:
|
@simaishi how do |
@zeari If there is a conflict with cherry-pick, I will request a separate PR. Until then, nothing is needed. |
Make container events belong to their container groups (cherry picked from commit 1696ac1) https://bugzilla.redhat.com/show_bug.cgi?id=1530653
Fine backport details:
|
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1496179
part of ManageIQ/manageiq#16583
@cben @moolitayer @enoodle Please review