RFE-6242: add an optional OpenStack job to cluster-ingress-operator

[EmilienM]

We didn't have a job and we want to be able to run one to test our PRs.

[EmilienM]

/assign Miciah

[EmilienM]

/pj-rehearse pull-ci-openshift-cluster-ingress-operator-master-e2e-openstack-ovn

[openshift-ci-robot]

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

[MaysaMacedo]

/lgtm

[EmilienM]

/pj-rehearse ack

[openshift-ci-robot]

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

[candita]

/assign @gcs278

[Miciah]

@EmilienM, could you also add an e2e-openstack-operator test to run the openshift/cluster-ingress-operator repository's E2E suite?

[Miciah]

@EmilienM, is there a Jira ticket that the PR and commit message should reference?

[openshift-ci-robot]

@EmilienM: This pull request references RFE-6242 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 feature request to target the "4.18.0" version, but no target version was set.

Details

In response to this:

We didn't have a job and we want to be able to run one to test our PRs.

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.

[EmilienM]

@EmilienM, could you also add an e2e-openstack-operator test to run the openshift/cluster-ingress-operator repository's E2E suite?

I don't think we need two OpenStack jobs for presubmit. So if you prefer we could run e2e-openstack-operator instead of the proposed one?
I'll try it and see how it works.

[EmilienM]

/pj-rehearse pull-ci-openshift-cluster-ingress-operator-master-e2e-openstack-operator

[openshift-ci-robot]

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

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@EmilienM: 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
pull-ci-openshift-cluster-ingress-operator-master-e2e-openstack-operator	openshift/cluster-ingress-operator	presubmit	Presubmit changed
pull-ci-openshift-cluster-ingress-operator-release-4.18-e2e-openstack-operator	openshift/cluster-ingress-operator	presubmit	Presubmit changed
pull-ci-openshift-cluster-ingress-operator-release-4.19-e2e-openstack-operator	openshift/cluster-ingress-operator	presubmit	Presubmit 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 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]

@EmilienM: The following test 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/rehearse/openshift/cluster-ingress-operator/master/e2e-openstack-operator	a65d5a9	link	unknown	/pj-rehearse pull-ci-openshift-cluster-ingress-operator-master-e2e-openstack-operator

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.

[EmilienM]

@Miciah running CIO e2e failed on OpenStack:

panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x1a774eb]

goroutine 11358 [running]:
testing.tRunner.func1.2({0x1d3d600, 0x3428a50})
	/usr/lib/golang/src/testing/testing.go:1631 +0x24a
testing.tRunner.func1()
	/usr/lib/golang/src/testing/testing.go:1634 +0x377
panic({0x1d3d600?, 0x3428a50?})
	/usr/lib/golang/src/runtime/panic.go:770 +0x132
github.com/openshift/cluster-ingress-operator/test/e2e.updateDNSConfig(...)
	/go/src/github.com/openshift/cluster-ingress-operator/test/e2e/dns_ingressdegrade_test.go:89
github.com/openshift/cluster-ingress-operator/test/e2e.TestIngressStatus(0xc000511380)
	/go/src/github.com/openshift/cluster-ingress-operator/test/e2e/dns_ingressdegrade_test.go:53 +0x34b
testing.tRunner(0xc000511380, 0x218c9f8)
	/usr/lib/golang/src/testing/testing.go:1689 +0xfb
created by testing.(*T).Run in goroutine 11200
	/usr/lib/golang/src/testing/testing.go:1742 +0x390
FAIL	github.com/openshift/cluster-ingress-operator/test/e2e	1612.553s
FAIL
make: *** [Makefile:56: test-e2e] Error 1

[EmilienM]

Fixing it here: openshift/cluster-ingress-operator#1153

[Miciah]

Thanks!
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: EmilienM, MaysaMacedo, Miciah

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/openshift/cluster-ingress-operator/OWNERS [Miciah]
• ci-operator/jobs/openshift/cluster-ingress-operator/OWNERS [Miciah]

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]

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

[EmilienM]

/pj-rehearse ack

[openshift-ci-robot]

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

[EmilienM]

let's merge it so we can test openshift/cluster-ingress-operator#1153 on OpenStack !