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
[release 4.6] Bug 1887759: Adds MachineConfigPool gatherer #213
Conversation
@0sewa0: This pull request references Bugzilla bug 1887759, which is invalid:
Comment In response to this:
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. |
/bugzilla refresh |
@0sewa0: This pull request references Bugzilla bug 1887759, which is invalid:
Comment In response to this:
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. |
/retest |
Verified on QuickLab clusters. We should just doublecheck the permission for the new apiGroup. |
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/bugzilla refresh Recalculating validity in case the underlying Bugzilla bug has changed. |
@openshift-bot: This pull request references Bugzilla bug 1887759, which is invalid:
Comment In response to this:
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. |
/bugzilla refresh |
@martinkunc: This pull request references Bugzilla bug 1887759, which is invalid:
Comment In response to this:
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. |
/bugzilla refresh |
@0sewa0: This pull request references Bugzilla bug 1887759, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 6 validation(s) were run on this bug
In response to this:
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. |
@sdodson Can you please take a look at this one and add cherry-pick approved label please? |
Does this in any way impact cluster stability or upgrade success?
…On Thu, Oct 29, 2020 at 10:22 AM Tomas Remes ***@***.***> wrote:
@sdodson <https://github.com/sdodson> Can you please take a look at this
one and add cherry-pick approved label please?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#213 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYIMQV3BASQMRXXCVJR3SNF3CTANCNFSM4SOQCPXQ>
.
|
(Patch Manager) This PR was reviewed for inclusion last week, however this adds feature work during the weeks immediately after release where we're focused on stability, upgrade success, and anything which blocks backports of critical customer impacting bugs. Since this doesn't meet those criteria it was not accepted last week and likely will not until we've been able to promote the 4.5 to 4.6 upgrade to the stable channel. |
@sdodson if PX approves backports like, this would that help unstick this PR's current state? |
@0sewa0: This pull request references Bugzilla bug 1887759, which is valid. 6 validation(s) were run on this bug
In response to this:
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. |
/bugzilla refresh |
@sdodson: This pull request references Bugzilla bug 1887759, which is valid. 6 validation(s) were run on this bug
In response to this:
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. |
/retest |
2 similar comments
/retest |
/retest |
Verified again. Works as expected. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 0sewa0, tremes 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:
Approvers can indicate their approval by writing |
/retest |
4 similar comments
/retest |
/retest |
/retest |
/retest |
@0sewa0: All pull requests linked via external trackers have merged: Bugzilla bug 1887759 has been moved to the MODIFIED state. In response to this:
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. |
Backports (4.6) a new data enhancement for gathering MachineConfigPools.
Categories
Sample archive
docs/insights-archive-sample/config/machineconfigpools/master.json
docs/insights-archive-sample/config/machineconfigpools/worker.json
Documentation
docs/gathered-data.md
Unit Tests
pkg/gather/clusterconfig/clusterconfig_test.go
Privacy
Yes. There are no sensitive data in the newly collected information.
References
https://issues.redhat.com/browse/CCXDEV-3285
https://issues.redhat.com/browse/INSIGHTOCP-84
https://bugzilla.redhat.com/show_bug.cgi?id=1887759