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

Make container events belong to their container groups #225

Merged
merged 2 commits into from
Dec 21, 2017

Conversation

zeari
Copy link

@zeari zeari commented Dec 3, 2017

@zeari zeari changed the title make container events belong to their container groups instead Make container events belong to their container groups instead Dec 3, 2017
@zeari zeari changed the title Make container events belong to their container groups instead Make container events belong to their container groups Dec 3, 2017
@gmcculloug
Copy link
Member

@lfu Please review

@lfu
Copy link
Member

lfu commented Dec 4, 2017

LGTM 👍

@@ -4,9 +4,11 @@ version: 1.0
object:
attributes:
display_name:
name: CONTAINER_FAILED
name: POD_CONTAINERCREATED

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?

Copy link
Author

@zeari zeari Dec 7, 2017

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

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

Copy link

@moolitayer moolitayer left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@zeari
Copy link
Author

zeari commented Dec 7, 2017

@miq-bot add_label gaprindashvili/yes

@zeari
Copy link
Author

zeari commented Dec 7, 2017

@miq-bot add_label fine/yes

Copy link
Contributor

@Ladas Ladas left a 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
Copy link
Contributor

cben commented Dec 18, 2017 via email

@miq-bot
Copy link
Member

miq-bot commented Dec 21, 2017

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
12 files checked, 1 offense detected

**

  • 💣 💥 🔥 🚒 - Linter/Yaml - missing config files

@zeari
Copy link
Author

zeari commented Dec 21, 2017

@lfu @gmcculloug Please merge.

@gmcculloug gmcculloug merged commit 1696ac1 into ManageIQ:master Dec 21, 2017
@gmcculloug gmcculloug added this to the Sprint 76 Ending Jan 1, 2018 milestone Dec 21, 2017
@gmcculloug gmcculloug added the bug label Jan 2, 2018
simaishi pushed a commit that referenced this pull request Jan 3, 2018
Make container events belong to their container groups
(cherry picked from commit 1696ac1)

https://bugzilla.redhat.com/show_bug.cgi?id=1530651
@simaishi
Copy link
Contributor

simaishi commented Jan 3, 2018

Gaprindashvili backport details:

$ git log -1
commit 36ef4dc36493d592d8d60256ab42498d72808623
Author: Greg McCullough <[email protected]>
Date:   Thu Dec 21 11:37:02 2017 -0500

    Merge pull request #225 from zeari/container_to_pod
    
    Make container events belong to their container groups
    (cherry picked from commit 1696ac15e4d25e94015819b11d36c3c490226531)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1530651

@zeari
Copy link
Author

zeari commented Jan 4, 2018

@simaishi how do fine backports work in relation to this change? Do I need to create a PR?

@simaishi
Copy link
Contributor

simaishi commented Jan 4, 2018

@zeari If there is a conflict with cherry-pick, I will request a separate PR. Until then, nothing is needed.

simaishi pushed a commit that referenced this pull request Jan 4, 2018
Make container events belong to their container groups
(cherry picked from commit 1696ac1)

https://bugzilla.redhat.com/show_bug.cgi?id=1530653
@simaishi
Copy link
Contributor

simaishi commented Jan 4, 2018

Fine backport details:

$ git log -1
commit c57a0175b40bbac87a51dde9a9b019fb663da9f9
Author: Greg McCullough <[email protected]>
Date:   Thu Dec 21 11:37:02 2017 -0500

    Merge pull request #225 from zeari/container_to_pod
    
    Make container events belong to their container groups
    (cherry picked from commit 1696ac15e4d25e94015819b11d36c3c490226531)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1530653

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants