OCPBUGS-59907: Skip egressIP openstack test for 4.14-e2e-openstack-dualstack-techpreview jobs

[MiguelCarpio]

Skip egressIP openstack test for 4.14-e2e-openstack-dualstack-techpreview jobs

[openshift-ci]

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-robot]

@MiguelCarpio: This pull request references Jira Issue OCPBUGS-59907, which is invalid:

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

Details

In response to this:

Skip egressIP openstack test for 4.14-e2e-openstack-dualstack-techpreview jobs

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.

[MiguelCarpio]

/pj-rehearse

[openshift-ci-robot]

@MiguelCarpio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[MiguelCarpio]

/jira refresh

[openshift-ci-robot]

@MiguelCarpio: This pull request references Jira Issue OCPBUGS-59907, 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.20.0) matches configured target version for branch (4.20.0)
• bug is in the state New, 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 (mcarpio@redhat.com), skipping review request.

Details

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.

[MiguelCarpio]

/pj-rehearse

[openshift-ci-robot]

@MiguelCarpio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[MiguelCarpio]

/pj-rehearse

[openshift-ci-robot]

@MiguelCarpio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@MiguelCarpio: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
periodic-ci-shiftstack-ci-release-4.14-e2e-openstack-dualstack-techpreview	N/A	periodic	Ci-operator config changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[MiguelCarpio]

/pj-rehearse

[openshift-ci-robot]

@MiguelCarpio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[MiguelCarpio]

/pj-rehearse

[openshift-ci-robot]

@MiguelCarpio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[MiguelCarpio]

/pj-rehearse

[openshift-ci-robot]

@MiguelCarpio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[MiguelCarpio]

/pj-rehearse

[openshift-ci-robot]

@MiguelCarpio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[MiguelCarpio]

/pj-rehearse

[openshift-ci-robot]

@MiguelCarpio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[MiguelCarpio]

/pj-rehearse ack

[openshift-ci-robot]

@MiguelCarpio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci]

@MiguelCarpio: all tests passed!

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.

[dkokkino]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dkokkino, MiguelCarpio

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:

• ci-operator/config/shiftstack/ci/OWNERS [MiguelCarpio,dkokkino]

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

[mandre]

/hold

What is the rational for skipping the test? Have we looked at why it is failing?

[MiguelCarpio]

/hold

What is the rational for skipping the test? Have we looked at why it is failing?

Hi @mandre, I propose skipping the egressIP openstack test until fixed https://issues.redhat.com/browse/OCPBUGS-59907. This is a permanent failure test, for a while, and could be hiding other bugs that we can't see if we consider that periodic-ci-shiftstack-ci-release-4.14-e2e-openstack-dualstack-techpreview job will always fail. The last work on solving this was taken by @MaysaMacedo here openshift/openstack-test#200, but it is already closed. I'll work on a solution, but I prefer to skip the test while I run that challenge.

[mandre]

/hold
What is the rational for skipping the test? Have we looked at why it is failing?

Hi @mandre, I propose skipping the egressIP openstack test until fixed https://issues.redhat.com/browse/OCPBUGS-59907. This is a permanent failure test, for a while, and could be hiding other bugs that we can't see if we consider that periodic-ci-shiftstack-ci-release-4.14-e2e-openstack-dualstack-techpreview job will always fail. The last work on solving this was taken by @MaysaMacedo here openshift/openstack-test#200, but it is already closed. I'll work on a solution, but I prefer to skip the test while I run that challenge.

Well, it seems to me like we want to re-open openshift/openstack-test#200 and get it merged if that fixes our issue, instead of silencing the failure.

[MiguelCarpio]

Close in favour of openshift/openstack-test#249

[openshift-ci-robot]

@MiguelCarpio: This pull request references Jira Issue OCPBUGS-59907. The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

Skip egressIP openstack test for 4.14-e2e-openstack-dualstack-techpreview jobs

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.