Skip to content
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.16] OCPBUGS-39522: UPSTREAM: <carry>: Add support to specify PlacementGroupPartition of placement group, Ensure Volumes and Network Interfaces are also tagged when created as part of instance creation #521

Open
wants to merge 1 commit into
base: release-4.16
Choose a base branch
from

Conversation

Patryk-Stefanski
Copy link

@Patryk-Stefanski Patryk-Stefanski commented Sep 4, 2024

OCPBUGS-39522: UPSTREAM: : Add support to specify PlacementGroupPartition of placement group, Ensure Volumes and Network Interfaces are also tagged when created as part of instance creation

Cherry picking

@Patryk-Stefanski Patryk-Stefanski changed the title [release-4.16] OCPBUGS-39522 [release-4.16] OCPBUGS-39522: UPSTREAM: <carry>: ✨ Add support to specify PlacementGroupPartition of placement group,Ensure Volumes and Network Interfaces are also tagged when created as part of instance creation Sep 4, 2024
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 4, 2024
@openshift-ci-robot
Copy link

@Patryk-Stefanski: This pull request references Jira Issue OCPBUGS-39522, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-33171 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

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:

Cherry picking

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.

@Patryk-Stefanski Patryk-Stefanski changed the title [release-4.16] OCPBUGS-39522: UPSTREAM: <carry>: ✨ Add support to specify PlacementGroupPartition of placement group,Ensure Volumes and Network Interfaces are also tagged when created as part of instance creation [release-4.16] OCPBUGS-39522: UPSTREAM: <carry>: ✨ Add support to specify PlacementGroupPartition of placement group,✨Ensure Volumes and Network Interfaces are also tagged when created as part of instance creation Sep 4, 2024
@openshift-ci openshift-ci bot requested review from elmiko and nrb September 4, 2024 10:03
Copy link

openshift-ci bot commented Sep 4, 2024

[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 joelspeed for approval. For more information see the Kubernetes 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

@Patryk-Stefanski Patryk-Stefanski changed the title [release-4.16] OCPBUGS-39522: UPSTREAM: <carry>: ✨ Add support to specify PlacementGroupPartition of placement group,✨Ensure Volumes and Network Interfaces are also tagged when created as part of instance creation [release-4.16] OCPBUGS-39522: UPSTREAM: <carry>: ✨ Add support to specify PlacementGroupPartition of placement group, ✨ Ensure Volumes and Network Interfaces are also tagged when created as part of instance creation Sep 4, 2024
@openshift-ci-robot
Copy link

@Patryk-Stefanski: An error was encountered adding this pull request to the external tracker bugs for bug OCPBUGS-39522 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message. failed to update remote link: failed to update link: request failed. Please analyze the request body for more details. Status code: 403: {"errorMessages":["No Link Issue Permission for issue 'OCPBUGS-39522'."],"errors":{}}

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

In response to this:

OCPBUGS-39522: UPSTREAM: : ✨ Add support to specify PlacementGroupPartition of placement group, ✨ Ensure Volumes and Network Interfaces are also tagged when created as part of instance creation

Cherry picking

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.

@Patryk-Stefanski Patryk-Stefanski changed the title [release-4.16] OCPBUGS-39522: UPSTREAM: <carry>: ✨ Add support to specify PlacementGroupPartition of placement group, ✨ Ensure Volumes and Network Interfaces are also tagged when created as part of instance creation [release-4.16] OCPBUGS-39522: UPSTREAM: <carry>: Add support to specify PlacementGroupPartition of placement group, Ensure Volumes and Network Interfaces are also tagged when created as part of instance creation Sep 4, 2024
@openshift-ci-robot
Copy link

@Patryk-Stefanski: This pull request references Jira Issue OCPBUGS-39522, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-33171 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

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:

OCPBUGS-39522: UPSTREAM: : Add support to specify PlacementGroupPartition of placement group, Ensure Volumes and Network Interfaces are also tagged when created as part of instance creation

Cherry picking

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.

placement group, Ensure Volumes and Network Interfaces are also tagged on creation
Copy link

openshift-ci bot commented Sep 4, 2024

@Patryk-Stefanski: 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants