Skip to content

Update the controller names from the propagator #664

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

Merged

Conversation

JustinKuli
Copy link
Contributor

A change in the propagator split up the policy-propagator controller into a 2 controllers: root-policy-spec, and replicated-policy. So the old metrics are no longer reported, and these tests should check for the new ones.

Refs:

A change in the propagator split up the `policy-propagator` controller
into a 2 controllers: `root-policy-spec`, and `replicated-policy`. So
the old metrics are no longer reported, and these tests should check for
the new ones.

Refs:
 - open-cluster-management-io/governance-policy-propagator#130

Signed-off-by: Justin Kulikauskas <[email protected]>
@JustinKuli
Copy link
Contributor Author

/retest

dhaiducek
dhaiducek previously approved these changes Oct 12, 2023
Copy link
Contributor

@dhaiducek dhaiducek left a comment

Choose a reason for hiding this comment

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

Thanks, @JustinKuli!

@JustinKuli
Copy link
Contributor Author

I think this one has now failed twice:

Summarizing 1 Failure:
  [FAIL] GRC: [P1][Sev1][policy-grc] Test the ACM Hardening generated PolicySet in an App subscription [It] Validates the propagated policies [policy-collection, stable]
  /go/src/github.com/stolostron/governance-policy-framework/test/integration/policy_generator_acm_hardening_test.go:124

@JustinKuli
Copy link
Contributor Author

Something seems to be happening with a PolicySet. The test that is failing is because a policy in a set is not being distributed to local-cluster. The binding/placement that should make that happen are attached to the acm-hardening PolicySet.

Based on the logs from the propagator, when it tries to look up that PolicySet (from a reference in a PlacementBinding, I think), it gets a "not found". And earlier, the policyset-controller logs a similar error, on its reconciles for that PolicySet:

2023-10-12T15:09:20.882Z	info	policy-set	policyset/policyset_controller.go:49	Reconciling policy sets...	{"Request.Namespace": "policies", "Request.Name": "acm-hardening"}
2023-10-12T15:09:20.882Z	info	policy-set	policyset/policyset_controller.go:59	Policy set not found, so it may have been deleted.	{"Request.Namespace": "policies", "Request.Name": "acm-hardening"}

@JustinKuli
Copy link
Contributor Author

/retest

@openshift-ci openshift-ci bot removed the lgtm label Oct 12, 2023
@JustinKuli JustinKuli force-pushed the update-propagator-controller-names branch 2 times, most recently from 27af7b7 to 530cc31 Compare October 13, 2023 14:59
@dhaiducek
Copy link
Contributor

/retest

@JustinKuli JustinKuli force-pushed the update-propagator-controller-names branch from 530cc31 to d4aa155 Compare October 13, 2023 19:40
@dhaiducek
Copy link
Contributor

Oh my goodness. It finally worked. 🎉 🤯 Good work! Do you want to keep the debug in there or take it out before merging it?

dhaiducek
dhaiducek previously approved these changes Oct 16, 2023
Copy link
Contributor

@dhaiducek dhaiducek left a comment

Choose a reason for hiding this comment

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

/hold (in case the debug logs should be removed)

The default clusterset was causing some problems in some envs.

Signed-off-by: Justin Kulikauskas <[email protected]>
@JustinKuli JustinKuli force-pushed the update-propagator-controller-names branch from d4aa155 to fca8c40 Compare October 16, 2023 14:16
@openshift-ci openshift-ci bot removed the lgtm label Oct 16, 2023
@JustinKuli
Copy link
Contributor Author

I feel like I'm tempting fate by removing the debugs logs and trying again, but here it goes!

@JustinKuli
Copy link
Contributor Author

/retest

@openshift-ci openshift-ci bot added the lgtm label Oct 16, 2023
@openshift-ci
Copy link

openshift-ci bot commented Oct 16, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhaiducek, JustinKuli

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [JustinKuli,dhaiducek]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@JustinKuli
Copy link
Contributor Author

/unhold

@openshift-ci openshift-ci bot merged commit ab16752 into stolostron:main Oct 16, 2023
@JustinKuli JustinKuli deleted the update-propagator-controller-names branch October 16, 2023 18:15
@dhaiducek
Copy link
Contributor

/cherry-pick release-2.9

@openshift-cherrypick-robot

@dhaiducek: new pull request created: #665

In response to this:

/cherry-pick release-2.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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.

3 participants