Skip to content

Conversation

@MaysaMacedo
Copy link
Contributor

@MaysaMacedo MaysaMacedo commented Oct 25, 2024

This PR backports the following two commits:

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 25, 2024

[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 ask for approval from maysamacedo. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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

@MaysaMacedo
Copy link
Contributor Author

Backport of 262b49a
and 233f173

@MaysaMacedo
Copy link
Contributor Author

/test build

@MaysaMacedo
Copy link
Contributor Author

/cc @MiguelCarpio

@openshift-ci openshift-ci bot requested a review from MiguelCarpio October 25, 2024 17:58
@EmilienM
Copy link
Member

@MaysaMacedo is there a job we could trigger here to test the result?

KURYRQE-1414

While running openstack-test in ipv6primary dualstack cluster, there are
some tests that are not passing.

This patch performs the needed actions to make those tests available
in both ipv4 and ipv6 primary dualstack cluster.
SOSQE-1388
SOSQE-217

- Adapting existing ipv4 test to run in all type of dualstack clusters.
- Including test to cover OCPBUGS-27222
@MaysaMacedo MaysaMacedo force-pushed the dualstack-support-egressip branch from a7b10e0 to 1950980 Compare November 25, 2024 22:05
@MaysaMacedo
Copy link
Contributor Author

/test test

@MaysaMacedo
Copy link
Contributor Author

@EmilienM there is no job yet. I'm proposing it here openshift/release#59211

@MaysaMacedo
Copy link
Contributor Author

/retest-required

1 similar comment
@MaysaMacedo
Copy link
Contributor Author

/retest-required

@mandre
Copy link
Member

mandre commented Nov 27, 2024

@MaysaMacedo
Copy link
Contributor Author

Is this for https://issues.redhat.com/browse/OCPBUGS-42498 ?

@mandre Sort of, it's related to the same test case that it's failing, but it's for the dualstack job and not openstack-ccpmso-zone.

@MaysaMacedo
Copy link
Contributor Author

/test e2e-openstack-dualstack-techpreview

1 similar comment
@MaysaMacedo
Copy link
Contributor Author

/test e2e-openstack-dualstack-techpreview

@MiguelCarpio
Copy link

/retest-required

@MiguelCarpio
Copy link

/test e2e-openstack-dualstack-techpreview

2 similar comments
@MiguelCarpio
Copy link

/test e2e-openstack-dualstack-techpreview

@MiguelCarpio
Copy link

/test e2e-openstack-dualstack-techpreview

@MiguelCarpio
Copy link

MiguelCarpio commented Dec 9, 2024

@MaysaMacedo @mandre To pass the test we need to resolve this first https://issues.redhat.com/browse/OCPBUGS-43496

[sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for node-Service: udp [Suite:openshift/conformance/parallel] [Suite:k8s]
[sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for pod-Service: http [Suite:openshift/conformance/parallel] [Suite:k8s]

@rlobillo
Copy link
Contributor

rlobillo commented Dec 10, 2024

@MaysaMacedo Why do you want to backport these fixes? 4.14 does not officially support dualstack, right?

@MiguelCarpio
Copy link

/test e2e-openstack-dualstack-techpreview

4 similar comments
@MiguelCarpio
Copy link

/test e2e-openstack-dualstack-techpreview

@MiguelCarpio
Copy link

/test e2e-openstack-dualstack-techpreview

@MiguelCarpio
Copy link

/test e2e-openstack-dualstack-techpreview

@MiguelCarpio
Copy link

/test e2e-openstack-dualstack-techpreview

@MiguelCarpio
Copy link

/test e2e-openstack-dualstack-techpreview

4 similar comments
@MiguelCarpio
Copy link

/test e2e-openstack-dualstack-techpreview

@MiguelCarpio
Copy link

/test e2e-openstack-dualstack-techpreview

@MiguelCarpio
Copy link

/test e2e-openstack-dualstack-techpreview

@MiguelCarpio
Copy link

/test e2e-openstack-dualstack-techpreview

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 27, 2025

@MaysaMacedo: 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/test-kuryr 1950980 link false /test test-kuryr
ci/prow/e2e-openstack-dualstack-techpreview 1950980 link false /test e2e-openstack-dualstack-techpreview

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

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 29, 2025
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 28, 2025
@openshift-bot
Copy link

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Jul 29, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 29, 2025

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

@MiguelCarpio
Copy link

I opened a specific bug for this OCPBUGS-59907

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants