Skip to content

OCPBUGS-44056: Remove unused vnet package #122

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
merged 1 commit into from
Oct 31, 2024

Conversation

fahlmant
Copy link
Contributor

@fahlmant fahlmant commented Oct 30, 2024

The virtualnetworks package is not used anywhere directly in MAPI. This PR removes the package and the unnecessary requirements for Azure permissions to perform highly sensitive actions, specifically the ability to delete vnets. MAPI doesn't manage the vnet that a given cluster is installed in, so should not have the ability to delete the vnet or other vnets in the Azure subscription/resource group.

Related CredentialsRequest update: openshift/machine-api-operator#1307

@openshift-ci openshift-ci bot requested review from nrb and sub-mod October 30, 2024 13:33
@fahlmant
Copy link
Contributor Author

/retest

@fahlmant
Copy link
Contributor Author

/test e2e-azure-operator

@jharrington22
Copy link

@sdodson @JoelSpeed could have someone look at this PR?

Copy link
Contributor

openshift-ci bot commented Oct 30, 2024

@fahlmant: 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.

@nrb
Copy link
Contributor

nrb commented Oct 30, 2024

/lgtm

@fahlmant if there's no Jira issue created for this, you can prefix the PR title with NOJIRA:

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 30, 2024
@fahlmant fahlmant changed the title Remove unused vnet package NOJIRA: Remove unused vnet package Oct 31, 2024
@fahlmant
Copy link
Contributor Author

@nrb added, what's the best way to get prow to see that without running all the tests again?

@JoelSpeed JoelSpeed changed the title NOJIRA: Remove unused vnet package NO-JIRA: Remove unused vnet package Oct 31, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 31, 2024
@openshift-ci-robot
Copy link

@fahlmant: This pull request explicitly references no jira issue.

In response to this:

The virtualnetworks package is not used anywhere directly in MAPI. This PR removes the package and the unnecessary requirements for Azure permissions to perform highly sensitive actions, specifically the ability to delete vnets. MAPI doesn't manage the vnet that a given cluster is installed in, so should not have the ability to delete the vnet or other vnets in the Azure subscription/resource group.

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 openshift-eng/jira-lifecycle-plugin repository.

@JoelSpeed
Copy link
Contributor

It needed NO-JIRA

Is there no jira related to this? I assume removing this then also results in a PR to remove the permissions from the credentials request, is that also coming?

@fahlmant
Copy link
Contributor Author

I can create a jira. This came up during review of required permissions as we implement MiWi for ARO. I can also make a PR for the CredentialsRequest, where is that defined? I don't see that in this repo but I could be easily missing it

@fahlmant
Copy link
Contributor Author

@fahlmant fahlmant changed the title NO-JIRA: Remove unused vnet package OCPBUGS-44056: Remove unused vnet package Oct 31, 2024
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 31, 2024
@openshift-ci-robot
Copy link

@fahlmant: This pull request references Jira Issue OCPBUGS-44056, which is invalid:

  • expected the bug to target the "4.18.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

In response to this:

The virtualnetworks package is not used anywhere directly in MAPI. This PR removes the package and the unnecessary requirements for Azure permissions to perform highly sensitive actions, specifically the ability to delete vnets. MAPI doesn't manage the vnet that a given cluster is installed in, so should not have the ability to delete the vnet or other vnets in the Azure subscription/resource group.

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 openshift-eng/jira-lifecycle-plugin repository.

@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. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 31, 2024
@openshift-ci-robot
Copy link

@fahlmant: This pull request references Jira Issue OCPBUGS-44056, which is valid.

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

Requesting review from QA contact:
/cc @sunzhaohua2

In response to this:

The virtualnetworks package is not used anywhere directly in MAPI. This PR removes the package and the unnecessary requirements for Azure permissions to perform highly sensitive actions, specifically the ability to delete vnets. MAPI doesn't manage the vnet that a given cluster is installed in, so should not have the ability to delete the vnet or other vnets in the Azure subscription/resource group.

Related CredentialsRequest update: openshift/machine-api-operator#1307

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 openshift-eng/jira-lifecycle-plugin repository.

@fahlmant
Copy link
Contributor Author

@JoelSpeed created jira and created CredentialsRequest update PR openshift/machine-api-operator#1307

@openshift-ci openshift-ci bot requested a review from sunzhaohua2 October 31, 2024 16:15
@fahlmant
Copy link
Contributor Author

/test e2e-azure-manual-oidc

Copy link
Contributor

openshift-ci bot commented Oct 31, 2024

@fahlmant: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test e2e-azure-operator
  • /test goimports
  • /test govet
  • /test images
  • /test unit

The following commands are available to trigger optional jobs:

  • /test e2e-azure-ovn
  • /test e2e-azure-ovn-upgrade
  • /test okd-scos-images

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

  • pull-ci-openshift-machine-api-provider-azure-main-e2e-azure-operator
  • pull-ci-openshift-machine-api-provider-azure-main-e2e-azure-ovn
  • pull-ci-openshift-machine-api-provider-azure-main-e2e-azure-ovn-upgrade
  • pull-ci-openshift-machine-api-provider-azure-main-goimports
  • pull-ci-openshift-machine-api-provider-azure-main-govet
  • pull-ci-openshift-machine-api-provider-azure-main-images
  • pull-ci-openshift-machine-api-provider-azure-main-unit

In response to this:

/test e2e-azure-manual-oidc

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.

@JoelSpeed
Copy link
Contributor

/approve

Copy link
Contributor

openshift-ci bot commented Oct 31, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 31, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit e2405dc into openshift:main Oct 31, 2024
8 checks passed
@openshift-ci-robot
Copy link

@fahlmant: Jira Issue OCPBUGS-44056: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-44056 has not been moved to the MODIFIED state.

In response to this:

The virtualnetworks package is not used anywhere directly in MAPI. This PR removes the package and the unnecessary requirements for Azure permissions to perform highly sensitive actions, specifically the ability to delete vnets. MAPI doesn't manage the vnet that a given cluster is installed in, so should not have the ability to delete the vnet or other vnets in the Azure subscription/resource group.

Related CredentialsRequest update: openshift/machine-api-operator#1307

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-machine-api-provider-azure
This PR has been included in build ose-machine-api-provider-azure-container-v4.18.0-202410311939.p0.ge2405dc.assembly.stream.el9.
All builds following this will include this PR.

@theobarberbany
Copy link
Contributor

/cherry-pick release-4.17

@openshift-cherrypick-robot

@theobarberbany: new pull request created: #130

In response to this:

/cherry-pick release-4.17

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants