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

kola testiso iSCSI test fails in prow #1492

Open
jbtrystram opened this issue Apr 22, 2024 · 3 comments
Open

kola testiso iSCSI test fails in prow #1492

jbtrystram opened this issue Apr 22, 2024 · 3 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@jbtrystram
Copy link
Contributor

The kola testiso iscsi boot test is failing in prow, but not in the fedora jenkins pipeline neither the rhcos pipeline.

I am unable to pin down why prow fails the test, as manually running the test steps from within a debug pod in the prow pipeline works.

See #1461 discussion for more details

jbtrystram added a commit to jbtrystram/openshift-os that referenced this issue Apr 22, 2024
The multi-arch tests are skipped in kola code and
the x86 test have been working for some time now

However, the iscsi test fails in prow unexpectedly
so skip it here so it can run in the RHCOS jenkins
pipeline at least.
See openshift#1492
See coreos/coreos-assembler#3705
jbtrystram added a commit to jbtrystram/openshift-os that referenced this issue Apr 22, 2024
The multi-arch tests are skipped in kola code and
the x86 test have been working for some time now

However, the iscsi test fails in prow unexpectedly
so skip it here so it can run in the RHCOS jenkins
pipeline at least.
See openshift#1492
See coreos/coreos-assembler#3705
jbtrystram added a commit to jbtrystram/openshift-os that referenced this issue Apr 22, 2024
The multi-arch tests are skipped in kola code and
the x86 test have been working for some time now

However, the iscsi test fails in prow unexpectedly
so skip it here so it can run in the RHCOS jenkins
pipeline at least.
See openshift#1492
See coreos/coreos-assembler#3705
jbtrystram added a commit to jbtrystram/openshift-os that referenced this issue Apr 22, 2024
The multi-arch tests are skipped in kola code and
the x86 test have been working for some time now

However, the iscsi test fails in prow unexpectedly
so skip it here so it can run in the RHCOS jenkins
pipeline at least.
See openshift#1492
See coreos/coreos-assembler#3705
jbtrystram added a commit to jbtrystram/openshift-os that referenced this issue Apr 22, 2024
The multi-arch tests are skipped in kola code and
the x86 test have been working for some time now

However, the iscsi test fails in prow unexpectedly
so skip it here so it can run in the RHCOS jenkins
pipeline at least.
See openshift#1492
See coreos/coreos-assembler#3705
jbtrystram added a commit to jbtrystram/openshift-os that referenced this issue Apr 22, 2024
The multi-arch tests are skipped in kola code and
the x86 test have been working for some time now

However, the iscsi test fails in prow unexpectedly
so skip it here so it can run in the RHCOS jenkins
pipeline at least.
See openshift#1492
See coreos/coreos-assembler#3705
@travier
Copy link
Member

travier commented Apr 23, 2024

/freeze

@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 Jul 23, 2024
@jbtrystram
Copy link
Contributor Author

/lifecycle frozen

@openshift-ci openshift-ci bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

3 participants