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

SPLAT-1638: Added multi vCenter support #1241

Merged
merged 3 commits into from
May 30, 2024

Conversation

vr4manta
Copy link
Contributor

@vr4manta vr4manta commented May 17, 2024

SPLAT-1638

Changes

  • Bump API to get VSphereMultiVCenters feature gate
  • Enhanced operator to use new YAML vSphere cloud config

Dependencies

Notes

I currently have same changes as https://github.com/openshift/machine-api-operator/pull/1250/files due to hitting the same things earlier. Talked to Joel and having these done as separate PR.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 17, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 17, 2024

@vr4manta: This pull request references SPLAT-1638 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 story to target the "4.16.0" version, but no target version was set.

In response to this:

SPLAT-1638

Changes

  • Bump API to get VSphereMultiVCenters feature gate
  • Enhanced operator to use new YAML vSphere cloud config

Dependencies

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.

Copy link
Contributor

openshift-ci bot commented May 17, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@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 May 17, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 17, 2024

@vr4manta: This pull request references SPLAT-1638 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 story to target the "4.16.0" version, but no target version was set.

In response to this:

SPLAT-1638

Changes

  • Bump API to get VSphereMultiVCenters feature gate
  • Enhanced operator to use new YAML vSphere cloud config

Dependencies

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.

Copy link
Contributor

openshift-ci bot commented May 17, 2024

@vr4manta: This PR was included in a payload test run from openshift/installer#8221
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-installer-master-altinfra-periodics-e2e-vsphere-capi-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/652f0350-144a-11ef-979c-c7c5c682dc9f-0

Copy link
Contributor

openshift-ci bot commented May 17, 2024

@vr4manta: This PR was included in a payload test run from openshift/installer#8221
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-installer-master-altinfra-periodics-e2e-vsphere-capi-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/3383e5f0-1486-11ef-8537-9fe6a0f164a0-0

@vr4manta vr4manta marked this pull request as ready for review May 20, 2024 13:36
@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 May 20, 2024
@vr4manta
Copy link
Contributor Author

/hold
Looking at upgrade scenarios.

@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 May 20, 2024
@vr4manta vr4manta force-pushed the SPLAT-1638 branch 3 times, most recently from cd2bfdf to 06553d1 Compare May 20, 2024 18:18
@vr4manta vr4manta marked this pull request as draft May 20, 2024 19:07
@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 May 20, 2024
@vr4manta
Copy link
Contributor Author

/test all

@vr4manta
Copy link
Contributor Author

/test unit

@vr4manta
Copy link
Contributor Author

/test unit

@vr4manta
Copy link
Contributor Author

/test all

@vr4manta
Copy link
Contributor Author

/test e2e-vsphere-ovn

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 22, 2024

@vr4manta: This pull request references SPLAT-1638 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 story to target the "4.17.0" version, but no target version was set.

In response to this:

SPLAT-1638

Changes

  • Bump API to get VSphereMultiVCenters feature gate
  • Enhanced operator to use new YAML vSphere cloud config

Dependencies

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-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 22, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 22, 2024

@vr4manta: This pull request references SPLAT-1638 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 story to target the "4.17.0" version, but no target version was set.

In response to this:

SPLAT-1638

Changes

  • Bump API to get VSphereMultiVCenters feature gate
  • Enhanced operator to use new YAML vSphere cloud config

Dependencies

Notes

I currently have same changes as #1243 due to hitting the same things earlier. Talked to Joel and having these done as separate PR.

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.

hack/crds-sync.sh Outdated Show resolved Hide resolved
pkg/controller/vsphere/actuator_test.go Outdated Show resolved Hide resolved
pkg/controller/vsphere/actuator_test.go Outdated Show resolved Hide resolved
pkg/controller/vsphere/actuator_test.go Outdated Show resolved Hide resolved
testInsecureFlag = "1"
testInsecureFlag = true
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a change in the accepted values?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

no, its a boolean that comes out of the object, not a "1". below you can see "1" is still used in creating ini file.

@vr4manta vr4manta force-pushed the SPLAT-1638 branch 2 times, most recently from d7714c4 to 5c4cc08 Compare May 23, 2024 11:54
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 23, 2024

@vr4manta: This pull request references SPLAT-1638 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 story to target the "4.17.0" version, but no target version was set.

In response to this:

SPLAT-1638

Changes

  • Bump API to get VSphereMultiVCenters feature gate
  • Enhanced operator to use new YAML vSphere cloud config

Dependencies

Notes

I currently have same changes as hhttps://github.com//pull/1234 due to hitting the same things earlier. Talked to Joel and having these done as separate PR.

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.

@vr4manta
Copy link
Contributor Author

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 23, 2024
@jcpowermac
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 23, 2024
@vr4manta
Copy link
Contributor Author

/assign @JoelSpeed

@vr4manta
Copy link
Contributor Author

/test e2e-vsphere-ovn

Copy link
Contributor

openshift-ci bot commented May 29, 2024

@vr4manta: This PR was included in a payload test run from openshift/installer#8221
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-installer-master-altinfra-periodics-e2e-vsphere-capi-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/bad92410-1dba-11ef-9194-5efcb977bc4b-0

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 29, 2024

@vr4manta: This pull request references SPLAT-1638 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 story to target the "4.17.0" version, but no target version was set.

In response to this:

SPLAT-1638

Changes

  • Bump API to get VSphereMultiVCenters feature gate
  • Enhanced operator to use new YAML vSphere cloud config

Dependencies

Notes

I currently have same changes as https://github.com/openshift/machine-api-operator/pull/1250/files due to hitting the same things earlier. Talked to Joel and having these done as separate PR.

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 removed the lgtm Indicates that a PR is ready to be merged. label May 30, 2024
@vr4manta
Copy link
Contributor Author

/retest-required

@JoelSpeed
Copy link
Contributor

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 30, 2024
Copy link
Contributor

openshift-ci bot commented May 30, 2024

[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

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 May 30, 2024
@vr4manta
Copy link
Contributor Author

/retest-required

Copy link
Contributor

openshift-ci bot commented May 30, 2024

@vr4manta: 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 5199567 link false /test e2e-azure-ovn
ci/prow/e2e-openstack 5199567 link false /test e2e-openstack

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-merge-bot openshift-merge-bot bot merged commit f280849 into openshift:master May 30, 2024
24 of 26 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-machine-api-operator-container-v4.17.0-202405310013.p0.gf280849.assembly.stream.el9 for distgit ose-machine-api-operator.
All builds following this will include this PR.

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.

None yet

6 participants