Skip to content

do not merge, vsphere privilege logging #1384

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.

Sign up for GitHub

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

Jump to bottom
Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

do not merge, vsphere privilege logging #1384

wants to merge 3 commits into from

Conversation

jcpowermac
Copy link
Contributor

our continued issue determining what privileges are required for components

@jcpowermac
do not merge, vsphere privelge logging
4a62d4b 
our continued issue determining what privelges are required
for components
@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 Jun 27, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jun 27, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@jcpowermac
Copy link
Contributor Author

/test ?

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jun 27, 2025

@jcpowermac: The following commands are available to trigger required jobs:

/test e2e-aws-operator

/test e2e-aws-ovn

/test e2e-aws-ovn-upgrade

/test goimports

/test golint

/test govet

/test images

/test security

/test unit

/test verify-crds-sync

/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-aws-operator-techpreview

/test e2e-azure-manual-oidc

/test e2e-azure-operator

/test e2e-azure-ovn

/test e2e-gcp-operator

/test e2e-gcp-ovn

/test e2e-metal-ipi

/test e2e-metal-ipi-ovn-dualstack

/test e2e-metal-ipi-ovn-ipv6

/test e2e-metal-ipi-upgrade

/test e2e-metal-ipi-virtualmedia

/test e2e-nutanix

/test e2e-openstack

/test e2e-vsphere-host-groups-ovn

/test e2e-vsphere-operator

/test e2e-vsphere-ovn

/test e2e-vsphere-ovn-multi-vcenter

/test e2e-vsphere-ovn-serial

/test e2e-vsphere-ovn-techpreview

/test e2e-vsphere-ovn-techpreview-serial

/test e2e-vsphere-ovn-upgrade

/test e2e-vsphere-static-ovn

/test okd-scos-e2e-aws-ovn

/test okd-scos-images

/test regression-clusterinfra-aws-ipi-mapi

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-machine-api-operator-main-e2e-aws-ovn

pull-ci-openshift-machine-api-operator-main-e2e-vsphere-host-groups-ovn

pull-ci-openshift-machine-api-operator-main-e2e-vsphere-operator

pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn

pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-multi-vcenter

pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-serial

pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-techpreview

pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-techpreview-serial

pull-ci-openshift-machine-api-operator-main-e2e-vsphere-ovn-upgrade

pull-ci-openshift-machine-api-operator-main-e2e-vsphere-static-ovn

pull-ci-openshift-machine-api-operator-main-goimports

pull-ci-openshift-machine-api-operator-main-golint

pull-ci-openshift-machine-api-operator-main-govet

pull-ci-openshift-machine-api-operator-main-images

pull-ci-openshift-machine-api-operator-main-okd-scos-e2e-aws-ovn

pull-ci-openshift-machine-api-operator-main-security

pull-ci-openshift-machine-api-operator-main-unit

pull-ci-openshift-machine-api-operator-main-verify-crds-sync

pull-ci-openshift-machine-api-operator-main-verify-deps

In response to this:

/test ?

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-sigs/prow repository.

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jun 27, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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

@jcpowermac
Copy link
Contributor Author

/test e2e-vsphere-ovn

@jcpowermac
Copy link
Contributor Author

/test e2e-vsphere-ovn

2 similar comments
@jcpowermac
Copy link
Contributor Author

/test e2e-vsphere-ovn

@jcpowermac
Copy link
Contributor Author

/test e2e-vsphere-ovn

@jcpowermac jcpowermac force-pushed the do-not-merge-privs-logging branch from f833d5f to 49817b1 Compare June 30, 2025 19:17
@jcpowermac
Copy link
Contributor Author

/test e2e-vsphere-ovn

1 similar comment
@jcpowermac
Copy link
Contributor Author

/test e2e-vsphere-ovn

@jcpowermac jcpowermac force-pushed the do-not-merge-privs-logging branch from 49817b1 to 50b5201 Compare July 2, 2025 14:10
@jcpowermac
Copy link
Contributor Author

/test e2e-vsphere-ovn

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jul 2, 2025

@jcpowermac: all tests passed!

Full PR test history. Your PR dashboard.

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

@jcpowermac jcpowermac mentioned this pull request Jul 2, 2025
Draft
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@jcpowermac @openshift-bot