Skip to content

Comments

SPLAT-1272: create fixtures for Nutanix failure domains support#304

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
nutanix-cloud-native:nutanix-failuredomains
Nov 30, 2023
Merged

SPLAT-1272: create fixtures for Nutanix failure domains support#304
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
nutanix-cloud-native:nutanix-failuredomains

Conversation

@yanhua121
Copy link
Contributor

@yanhua121 yanhua121 commented Oct 24, 2023

SPLAT-1272: create fixtures for Nutanix failure domains support

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 24, 2023
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 24, 2023
@yanhua121 yanhua121 marked this pull request as draft October 24, 2023 16:32
@openshift-ci openshift-ci bot requested review from JoelSpeed and damdo October 24, 2023 16:33
@yanhua121 yanhua121 force-pushed the nutanix-failuredomains branch from 5e178e7 to c621225 Compare November 23, 2023 08:12
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 23, 2023
@yanhua121 yanhua121 marked this pull request as ready for review November 23, 2023 08:17
@openshift-ci openshift-ci bot requested a review from RadekManak November 23, 2023 08:18
@yanhua121 yanhua121 changed the title WIP: vendor bump to test Nutanix failure domains SPLAT-1272: create fixtures for Nutanix failure domains support Nov 23, 2023
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 23, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 23, 2023

@yanhua121: This pull request references SPLAT-1272 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.15.0" version, but no target version was set.

Details

In response to this:

SPLAT-1272: create fixtures for Nutanix failure domains support

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.

@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 23, 2023
Copy link
Contributor

@JoelSpeed JoelSpeed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just one concern on the machine provider config builder

Comment on lines 122 to 151
// withFailureDomains sets the withFailureDomains field with the input value.
func (n *NutanixMachineProviderConfigBuilder) WithFailureDomains(withFailureDomains bool) *NutanixMachineProviderConfigBuilder {
n.withFailureDomains = withFailureDomains
return n
}

// WithFailureDomainIndex sets the failureDomainIndex field with the input value.
func (n *NutanixMachineProviderConfigBuilder) WithFailureDomainIndex(index int32) *NutanixMachineProviderConfigBuilder {
n.failureDomainIndex = index
return n
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should take a name to a failure domain rather than an index, this should not rely on the infrastructure object since that can be created with custom failure domains

That or it needs to be passed the failure domain from an external infrastructure object, but it definitely should not be defaulting like that

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed to allow to set the failureDomains data externally with the "withFailureDomains()" function.

@yanhua121 yanhua121 force-pushed the nutanix-failuredomains branch 2 times, most recently from 8a27dc1 to 2a59562 Compare November 27, 2023 18:37
@yanhua121
Copy link
Contributor Author

/retest-required

@yanhua121
Copy link
Contributor Author

/assign @elmiko

@yanhua121 yanhua121 force-pushed the nutanix-failuredomains branch from 2a59562 to 3991b9c Compare November 29, 2023 21:34
@yanhua121
Copy link
Contributor Author

@elmiko @JoelSpeed The review comments are addressed. Please take another look. thanks.

Copy link
Contributor

@elmiko elmiko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this looks better to me, i'm happy with this. i'd like @JoelSpeed to give another review tomorrow.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 29, 2023
@JoelSpeed
Copy link
Contributor

Ok thanks, this alleviates my concern about constructing the infra within the Build() function, the test calling this can now pass in the failure domains from their own test scope and set the failure domain based on the name.

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 30, 2023

[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

Details 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 Nov 30, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b6681f5 and 2 for PR HEAD 3991b9c in total

@JoelSpeed
Copy link
Contributor

JoelSpeed commented Nov 30, 2023

/override ci/prow/e2e-vsphere-operator

These changes do not affect the E2E in any way

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 30, 2023

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-vsphere-operator

Details

In response to this:

/override ci/prow/e2e-vsphere-operator

These changes do not effect the E2E in any way

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 30, 2023

@yanhua121: The following test 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-openstack-operator 3991b9c link false /test e2e-openstack-operator

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit ea989e2 into openshift:master Nov 30, 2023
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-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.

5 participants