Skip to content

Conversation

@aravindhp
Copy link
Contributor

This is needed to allow "oc adm node-logs" to work on OCP 4.14+ clusters where the node log query feature is present upstream and needs to be explicitly enabled.

This is needed to allow "oc adm node-logs" to work on OCP 4.14+ clusters
where the node log query feature is present upstream and needs to be
explicitly enabled.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 11, 2023
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 11, 2023
@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels May 11, 2023
@openshift-ci-robot
Copy link
Contributor

@aravindhp: This pull request references Jira Issue OCPBUGS-11652, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.0) matches configured target version for branch (4.14.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @zhouying7780

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is needed to allow "oc adm node-logs" to work on OCP 4.14+ clusters where the node log query feature is present upstream and needs to be explicitly enabled.

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.

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@aravindhp: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-kubevirt-ssp-operator-master-e2e-single-node-functests kubevirt/ssp-operator presubmit Registry content changed
pull-ci-kubevirt-ssp-operator-release-v0.16-e2e-single-node-functests kubevirt/ssp-operator presubmit Registry content changed
pull-ci-kubevirt-ssp-operator-release-v0.15-e2e-single-node-functests kubevirt/ssp-operator presubmit Registry content changed
pull-ci-kubevirt-ssp-operator-release-v0.14-e2e-single-node-functests kubevirt/ssp-operator presubmit Registry content changed
pull-ci-kubevirt-ssp-operator-release-v0.17-e2e-single-node-functests kubevirt/ssp-operator presubmit Registry content changed
pull-ci-kubevirt-ssp-operator-release-v0.13-e2e-single-node-functests kubevirt/ssp-operator presubmit Registry content changed
pull-ci-openshift-console-operator-master-e2e-aws-ovn-single-node openshift/console-operator presubmit Registry content changed
pull-ci-openshift-console-operator-release-4.15-e2e-aws-ovn-single-node openshift/console-operator presubmit Registry content changed
pull-ci-openshift-console-operator-release-4.14-e2e-aws-ovn-single-node openshift/console-operator presubmit Registry content changed
pull-ci-openshift-console-operator-release-4.13-e2e-aws-ovn-single-node openshift/console-operator presubmit Registry content changed
pull-ci-openshift-console-operator-release-4.12-e2e-aws-ovn-single-node openshift/console-operator presubmit Registry content changed
pull-ci-openshift-console-operator-release-4.11-e2e-aws-single-node openshift/console-operator presubmit Registry content changed
pull-ci-openshift-console-operator-release-4.10-e2e-aws-single-node openshift/console-operator presubmit Registry content changed
pull-ci-openshift-console-operator-release-4.9-e2e-aws-single-node openshift/console-operator presubmit Registry content changed
pull-ci-openshift-console-operator-release-4.8-e2e-aws-single-node openshift/console-operator presubmit Registry content changed
pull-ci-openshift-cluster-etcd-operator-master-e2e-aws-ovn-single-node openshift/cluster-etcd-operator presubmit Registry content changed
pull-ci-openshift-cluster-etcd-operator-release-4.15-e2e-aws-ovn-single-node openshift/cluster-etcd-operator presubmit Registry content changed
pull-ci-openshift-cluster-etcd-operator-release-4.14-e2e-aws-ovn-single-node openshift/cluster-etcd-operator presubmit Registry content changed
pull-ci-openshift-cluster-etcd-operator-release-4.13-e2e-aws-ovn-single-node openshift/cluster-etcd-operator presubmit Registry content changed
pull-ci-openshift-cluster-etcd-operator-release-4.12-e2e-aws-ovn-single-node openshift/cluster-etcd-operator presubmit Registry content changed
pull-ci-openshift-cluster-etcd-operator-release-4.11-e2e-aws-single-node openshift/cluster-etcd-operator presubmit Registry content changed
pull-ci-openshift-cluster-etcd-operator-release-4.10-e2e-aws-single-node openshift/cluster-etcd-operator presubmit Registry content changed
pull-ci-openshift-cluster-etcd-operator-release-4.9-e2e-aws-single-node openshift/cluster-etcd-operator presubmit Registry content changed
pull-ci-openshift-cluster-etcd-operator-release-4.8-e2e-aws-single-node openshift/cluster-etcd-operator presubmit Registry content changed
pull-ci-openshift-cluster-monitoring-operator-master-e2e-aws-ovn-single-node openshift/cluster-monitoring-operator presubmit Registry content changed
pull-ci-openshift-cluster-monitoring-operator-release-4.15-e2e-aws-ovn-single-node openshift/cluster-monitoring-operator presubmit Registry content changed
pull-ci-openshift-cluster-monitoring-operator-release-4.14-e2e-aws-ovn-single-node openshift/cluster-monitoring-operator presubmit Registry content changed
pull-ci-openshift-cluster-monitoring-operator-release-4.13-e2e-aws-ovn-single-node openshift/cluster-monitoring-operator presubmit Registry content changed
pull-ci-openshift-cluster-monitoring-operator-release-4.12-e2e-aws-ovn-single-node openshift/cluster-monitoring-operator presubmit Registry content changed
pull-ci-openshift-cluster-monitoring-operator-release-4.11-e2e-aws-single-node openshift/cluster-monitoring-operator presubmit Registry content changed
pull-ci-openshift-cluster-monitoring-operator-release-4.10-e2e-aws-single-node openshift/cluster-monitoring-operator presubmit Registry content changed
pull-ci-openshift-cluster-monitoring-operator-release-4.9-e2e-aws-single-node openshift/cluster-monitoring-operator presubmit Registry content changed
pull-ci-openshift-cluster-monitoring-operator-release-4.8-e2e-aws-single-node openshift/cluster-monitoring-operator presubmit Registry content changed
pull-ci-openshift-installer-master-e2e-aws-ovn-single-node openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.15-e2e-aws-ovn-single-node openshift/installer presubmit Registry content changed

A total of 202 jobs have been affected by this change. The above listing is non-exhaustive and limited to 35 jobs.

A full list of affected jobs can be found here
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 10 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 20 rehearsals
Comment: /pj-rehearse max to run up to 35 rehearsals
Comment: /pj-rehearse auto-ack to run up to 10 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@aravindhp
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-origin-release-4.14-e2e-aws-ovn-single-node

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 12, 2023

@aravindhp: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 15, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 15, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: aravindhp, soltysh
Once this PR has been reviewed and has the lgtm label, please assign osherdp for approval. For more information see the Kubernetes Code Review Process.

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

Details Needs approval from an approver in each of these files:

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

@aravindhp
Copy link
Contributor Author

/retitle OCPBUGS-11652: SNO: Add enableSystemLogQuery to kubelet conf

@openshift-ci openshift-ci bot changed the title WIP: OCPBUGS-11652: SNO: Add enableSystemLogQuery to kubelet conf OCPBUGS-11652: SNO: Add enableSystemLogQuery to kubelet conf May 15, 2023
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 15, 2023
@ingvagabund
Copy link
Member

@aravindhp this looks finished :) is there anything else missing besides getting the approval?

@aravindhp
Copy link
Contributor Author

aravindhp commented Jun 7, 2023

The only question is whether the fix for OCPBUGS-13656 will fix SNO also. So we should wait for that fix to go in and check if it works for SNO.

Slack thread about this.

@aravindhp
Copy link
Contributor Author

/close

openshift/machine-config-operator#3735 fixed the issue and was confirmed in openshift/origin#27992 (comment)

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 27, 2023
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

Details

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.

@openshift-ci openshift-ci bot closed this Jun 27, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 27, 2023

@aravindhp: Closed this PR.

Details

In response to this:

/close

openshift/machine-config-operator#3735 fixed the issue and was confirmed in openshift/origin#27992 (comment)

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.

@openshift-ci-robot
Copy link
Contributor

@aravindhp: This pull request references Jira Issue OCPBUGS-11652. The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

This is needed to allow "oc adm node-logs" to work on OCP 4.14+ clusters where the node log query feature is present upstream and needs to be explicitly enabled.

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

Labels

bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants