OCPBUGS-29115: Default NodeUpgradeType on day2 nodepool creation

[jparrill]

This bug regards on a day2 nodepool creation. If you creates a cluster using the CLI, it defaults the NodepoolUpgradeType according to the HostedCluster Platform Type. With this PR we also covers the day 2 Nodepool creation which is not using the default fixtures.

Signed-off-by: Juan Manuel Parrilla Madrid jparrill@redhat.com

Which issue(s) this PR fixes :
Fixes #OCPBUGS-29115

[openshift-ci-robot]

@jparrill: This pull request references Jira Issue OCPBUGS-29115, which is invalid:

• expected the bug to target the "4.16.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:

This bug regards on a day2 nodepool creation. If you creates a cluster using the CLI, it defaults the NodepoolUpgradeType according to the HostedCluster Platform Type. With this PR we also covers the day 2 Nodepool creation which is not using the default fixtures.

Signed-off-by: Juan Manuel Parrilla Madrid jparrill@redhat.com

Which issue(s) this PR fixes :
Fixes #OCPBUGS-29115

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 APPROVED

This pull-request has been approved by: jparrill

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:

• OWNERS [jparrill]

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

[jparrill]

/jira refresh

[openshift-ci-robot]

@jparrill: This pull request references Jira Issue OCPBUGS-29115, 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.16.0) matches configured target version for branch (4.16.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (gamado@redhat.com), skipping review request.

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.

[csrwng]

/lgtm

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD a58035c and 2 for PR HEAD 194665f in total

[jparrill]

/retest

[jparrill]

/retest

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD b121a20 and 1 for PR HEAD 194665f in total

[bryan-cox]

/test e2e-kubevirt-aws-ovn

[openshift-ci-robot]

@jparrill: Jira Issue OCPBUGS-29115: All pull requests linked via external trackers have merged:

• openshift/hypershift#3572

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

In response to this:

This bug regards on a day2 nodepool creation. If you creates a cluster using the CLI, it defaults the NodepoolUpgradeType according to the HostedCluster Platform Type. With this PR we also covers the day 2 Nodepool creation which is not using the default fixtures.

Signed-off-by: Juan Manuel Parrilla Madrid jparrill@redhat.com

Which issue(s) this PR fixes :
Fixes #OCPBUGS-29115

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.

[jparrill]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@jparrill: new pull request created: #3582

In response to this:

/cherry-pick release-4.15

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/test-infra repository.