[release-4.15] OCPBUGS-39521: UPSTREAM: <carry>:Add AWSMachine fields to control vpc placement for the instance, Drop the VPC field from the AWSMachine spec, look up the VPC from the subnet instead, Add support to specify PlacementGroupPartition of placement group, Ensure Volumes and Network Interfaces are also tagged on creation

[Patryk-Stefanski]

UPSTREAM: :Add AWSMachine fields to control vpc placement for the instance, Drop the VPC field from the AWSMachine spec, look up the VPC from the subnet instead, Add support to specify PlacementGroupPartition of placement group, Ensure Volumes and Network Interfaces are also tagged on creation

cherry picks

• https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/4541/commits
• https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/4883/commits
• https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/5057/commits

[openshift-ci-robot]

@Patryk-Stefanski: An error was encountered adding this pull request to the external tracker bugs for bug OCPBUGS-39521 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 add remote link: failed to add link: title - The length of the 'Link Text' field cannot exceed 255 characters.: request failed. Please analyze the request body for more details. Status code: 400:

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

In response to this:

UPSTREAM: :Add AWSMachine fields to control vpc placement for the instance, Drop the VPC field from the AWSMachine spec, look up the VPC from the subnet instead, Add support to specify PlacementGroupPartition of placement group, Ensure Volumes and Network Interfaces are also tagged on creation

cherry picks

• https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/4541/commits
• https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/4883/commits
• https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/5057/commits

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]

[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 enxebre 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:

• OWNERS

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

[nrb]

/jira refresh

[openshift-ci-robot]

@nrb: An error was encountered adding this pull request to the external tracker bugs for bug OCPBUGS-39521 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 add remote link: failed to add link: title - The length of the 'Link Text' field cannot exceed 255 characters.: request failed. Please analyze the request body for more details. Status code: 400:

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

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]

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