Skip to content

Conversation

@fahlmant
Copy link

Azure US Government Cloud has no restrictions on using resource tags. Recently, ARO tried to add userTags support to the install process but when deploying to the Government Cloud regions, clusters were unable to be created due to the limitation in the installer. Given that these Azure regions support tags, this PR allows user tags to be used in both Azure Public and US Government Clouds.

@openshift-ci openshift-ci bot requested review from jhixson74 and sadasu October 13, 2025 18:43
@fahlmant
Copy link
Author

/test e2e-azure-ovn-shared-vpc
/test okd-scos-e2e-aws-ovn
/test e2e-azurestack

1 similar comment
@fahlmant
Copy link
Author

/test e2e-azure-ovn-shared-vpc
/test okd-scos-e2e-aws-ovn
/test e2e-azurestack

@patrickdillon patrickdillon changed the title Expand Azure userTags to support Azure Government Cloud OCPBUGS-63065: Expand Azure userTags to support Azure Government Cloud Oct 14, 2025
@openshift-ci-robot openshift-ci-robot added the jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. label Oct 14, 2025
@patrickdillon
Copy link
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Oct 14, 2025
@openshift-ci-robot
Copy link
Contributor

@fahlmant: This pull request references Jira Issue OCPBUGS-63065, which is valid. The bug has been moved to the POST state.

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

Requesting review from QA contact:
/cc @gpei

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

In response to this:

Azure US Government Cloud has no restrictions on using resource tags. Recently, ARO tried to add userTags support to the install process but when deploying to the Government Cloud regions, clusters were unable to be created due to the limitation in the installer. Given that these Azure regions support tags, this PR allows user tags to be used in both Azure Public and US Government Clouds.

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
Copy link
Contributor

@patrickdillon: This pull request references Jira Issue OCPBUGS-63065, which is valid.

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

Requesting review from QA contact:
/cc @gpei

In response to this:

/jira refresh

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 openshift-ci bot requested a review from gpei October 14, 2025 17:25
@patrickdillon
Copy link
Contributor

@fahlmant don't worry too much about those failing tests. we are having some azure ci quota issues.

@patrickdillon
Copy link
Contributor

/approve
/lgtm

Let's wait for @gpei to verify

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Oct 14, 2025
@shubhadapaithankar
Copy link

/approve
/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 15, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon, shubhadapaithankar

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

@gpei
Copy link
Contributor

gpei commented Oct 16, 2025

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@gpei: This pull request references Jira Issue OCPBUGS-63065, which is valid.

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

Requesting review from QA contact:
/cc @jinyunma

In response to this:

/jira refresh

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 openshift-ci bot requested a review from jinyunma October 16, 2025 01:12
@fahlmant
Copy link
Author

@gpei Is there anything you need from me to help move this forward?

@gpei
Copy link
Contributor

gpei commented Oct 30, 2025

Hi @fahlmant , the test on the PR have been completed by @jinyunma and can be found here https://issues.redhat.com/browse/OCPBUGS-63065?focusedId=28262169&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28262169. We are currently awaiting Patrick's evaluation of the remaining issue.

@fahlmant
Copy link
Author

fahlmant commented Nov 7, 2025

@patrickdillon Could I get your thoughts on this?

@patrickdillon
Copy link
Contributor

/verified by @patrickdillon

Jinyun did the work, but marking this as verified by me because we are deferring some of the work to an existing bug OCPBUGS-36207

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 18, 2025
@openshift-ci-robot
Copy link
Contributor

@patrickdillon: This PR has been marked as verified by @patrickdillon.

In response to this:

/verified by @patrickdillon

Jinyun did the work, but marking this as verified by me because we are deferring some of the work to an existing bug OCPBUGS-36207

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
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 02535f7 and 2 for PR HEAD 15ad237 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 4b8f8de and 1 for PR HEAD 15ad237 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 61db26a and 0 for PR HEAD 15ad237 in total

@shubhadapaithankar shubhadapaithankar removed their assignment Nov 20, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 20, 2025

@fahlmant: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-azure-ovn-shared-vpc 15ad237 link false /test e2e-azure-ovn-shared-vpc
ci/prow/okd-scos-e2e-aws-ovn 15ad237 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-azurestack 15ad237 link false /test e2e-azurestack
ci/prow/e2e-aws-ovn 15ad237 link true /test e2e-aws-ovn

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.

@openshift-ci-robot
Copy link
Contributor

/hold

Revision 15ad237 was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 20, 2025
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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/severity-low Referenced Jira bug's severity is low 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants