SOSQE-2371: ShiftStack periodic additional-ipv6-network job deduplication

[MiguelCarpio]

This PR intends to drop e2e-openstack-additional-ipv6-network jobs that are already running and testing on ShiftStack QE CI.

In ShiftStack QE CI, shiftstack_periodic/Periodic multijobs at DFG-osasinfra-shiftstack_periodic-multijob-provider_network_secondary already perform an IPI OCP installation on OpenStack with nodes configured
with additional ipv6 network (install-config.yaml example) and run Conformance Parallel test suit on it.

To achieve it, the DFG-osasinfra-shiftstack_periodic-multijob-provider_network_secondary executes the following steps:

1. DFG-osasinfra-shiftstack_periodic_subjob-ocp_install-4.18-ovnkubernetes-ipi
2. DFG-osasinfra-shiftstack_periodic_subjob-ocp_testing. This is a build example 1464

DFG-osasinfra-shiftstack_periodic-multijob-provider_network_secondary covers the OCP releases from 4.15 to 4.18 and is configured to run every 3 weeks.

[openshift-ci-robot]

@MiguelCarpio: This pull request references SOSQE-2371 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 task to target the "4.19.0" version, but no target version was set.

In response to this:

This PR intends to drop e2e-openstack-additional-ipv6-network jobs that are already running and testing on ShiftStack QE CI.

In ShiftStack QE CI, shiftstack_periodic/Periodic multijobs at DFG-osasinfra-shiftstack_periodic-multijob-provider_network_secondary already perform an IPI OCP installation on OpenStack with nodes configured
with additional ipv6 network (install-config.yaml example) and run Conformance Parallel test suit on it.

To achieve it, the DFG-osasinfra-shiftstack_periodic-multijob-provider_network_secondary executes the following steps:

1. DFG-osasinfra-shiftstack_periodic_subjob-ocp_install-4.18-ovnkubernetes-ipi
2. DFG-osasinfra-shiftstack_periodic_subjob-ocp_testing. This is a build example 1464

DFG-osasinfra-shiftstack_periodic-multijob-provider_network_secondary covers the OCP releases from 4.15 to 4.18 and is configured to run every 3 weeks.

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MiguelCarpio

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:

• ci-operator/config/shiftstack/ci/OWNERS [MiguelCarpio]
• ci-operator/jobs/shiftstack/ci/OWNERS [MiguelCarpio]

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]

[REHEARSALNOTIFIER]
@MiguelCarpio: no rehearsable tests are affected by this change

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 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.

[openshift-ci]

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