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-2078: Removed VSphereStaticIPs feature gate #2232

Merged
merged 1 commit into from
Apr 9, 2025

Conversation

vr4manta
Copy link
Contributor

@vr4manta vr4manta commented Mar 13, 2025

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 13, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 13, 2025

@vr4manta: This pull request references SPLAT-2078 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.19.0" version, but no target version was set.

In response to this:

SPLAT-2078

Changes

  • Removed VSphereStaticIPs feature gate

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 added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 13, 2025
Copy link
Contributor

openshift-ci bot commented Mar 13, 2025

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

Copy link
Contributor

openshift-ci bot commented Mar 13, 2025

Hello @vr4manta! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 13, 2025
@vr4manta
Copy link
Contributor Author

/test all

@vr4manta vr4manta marked this pull request as ready for review April 1, 2025 13:28
@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 Apr 1, 2025
@openshift-ci openshift-ci bot requested review from deads2k and JoelSpeed April 1, 2025 13:29
@jcpowermac
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 1, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 1, 2025

@vr4manta: This pull request references SPLAT-2078 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.19.0" version, but no target version was set.

In response to this:

SPLAT-2078

Changes

  • Removed VSphereStaticIPs feature gate

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.

@vr4manta
Copy link
Contributor Author

vr4manta commented Apr 1, 2025

/assign @JoelSpeed

@vr4manta
Copy link
Contributor Author

vr4manta commented Apr 2, 2025

/retest

@vr4manta
Copy link
Contributor Author

vr4manta commented Apr 3, 2025

/retest-required

@JoelSpeed
Copy link
Contributor

This feature has been enabled for over a year, so is safe to remove

/lgtm

/hold but we do need to check that vSphere payload jobs are still passing with this removed

/payload-job periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn

@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 Apr 4, 2025
Copy link
Contributor

openshift-ci bot commented Apr 4, 2025

@JoelSpeed: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/554e2420-1147-11f0-8fae-50b1e402517f-0

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 4, 2025
@vr4manta
Copy link
Contributor Author

vr4manta commented Apr 4, 2025

@JoelSpeed , the payload-test finish, but failed. It looks to have failed during e2e tests that don't seem related. If it looks ok to you, are you good with removing the hold?

@JoelSpeed
Copy link
Contributor

/hold cancel

@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 Apr 7, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 7, 2025
# Conflicts:
#	payload-command/render/renderassets/rendered_manifests_test.go
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 7, 2025
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 7, 2025
@jcpowermac
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 7, 2025
Copy link
Contributor

openshift-ci bot commented Apr 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcpowermac, JoelSpeed, vr4manta

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-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 00e6260 and 2 for PR HEAD d4a3a8c in total

2 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 00e6260 and 2 for PR HEAD d4a3a8c in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 00e6260 and 2 for PR HEAD d4a3a8c in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6fb534f and 1 for PR HEAD d4a3a8c in total

@JoelSpeed
Copy link
Contributor

/retest-required

1 similar comment
@vr4manta
Copy link
Contributor Author

vr4manta commented Apr 9, 2025

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6fb534f and 2 for PR HEAD d4a3a8c in total

@vr4manta
Copy link
Contributor Author

vr4manta commented Apr 9, 2025

@JoelSpeed it seems the two aws jobs keep failing for what looks like DNS issues.

level=fatal msg=failed to fetch Common Manifests: failed to fetch dependency of "Common Manifests": failed to generate asset "DNS Config": getting public zone for "origin-ci-int-aws.dev.rhcloud.com": no public route53 zone found matching name "origin-ci-int-aws.dev.rhcloud.com"

Can we override these to get changes to merge?

@JoelSpeed
Copy link
Contributor

/override ci/prow/e2e-aws-serial
/override ci/prow/e2e-aws-serial-techpreview

On going issue with the build cluster, I'm confident this won't be an issue for us

Copy link
Contributor

openshift-ci bot commented Apr 9, 2025

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-aws-serial, ci/prow/e2e-aws-serial-techpreview

In response to this:

/override ci/prow/e2e-aws-serial
/override ci/prow/e2e-aws-serial-techpreview

On going issue with the build cluster, I'm confident this won't be an issue for us

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.

Copy link
Contributor

openshift-ci bot commented Apr 9, 2025

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

@openshift-merge-bot openshift-merge-bot bot merged commit 8fcc4e7 into openshift:master Apr 9, 2025
23 checks passed
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-config-api
This PR has been included in build ose-cluster-config-api-container-v4.19.0-202504091811.p0.g8fcc4e7.assembly.stream.el9.
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. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants