Bug 1949818: test/e2e: add e2e test for Single Node OpenShift#2507
Conversation
openshift-ci-robot
added
the
do-not-merge/work-in-progress
openshift-ci-robot
added
the
approved
|
Require openshift/release#17357 |
sinnykumari
force-pushed
the
e2e-gcp-op-sno
branch
from
e4f0634 to
da2fc2d
Compare
|
/retest |
sinnykumari
changed the title
openshift-ci-robot
removed
the
do-not-merge/work-in-progress
|
@sinnykumari: PR needs rebase. DetailsInstructions 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/test-infra repository. |
openshift-ci-robot
added
the
needs-rebase
sinnykumari
force-pushed
the
e2e-gcp-op-sno
branch
from
da2fc2d to
fe3ef8a
Compare
openshift-ci
Bot
removed
the
needs-rebase
|
Rebased and fixed merge conflict |
|
Did a first pass and the general code lgtm. Quick question, when you say:
Does't 17357 require this to merge first such that it can run |
No, openshift/release#17357 needs to merge first so that |
|
/retest |
|
/test e2e-gcp-op-single-node |
|
@sinnykumari: The specified target(s) for
Use
DetailsIn response to this:
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/test-infra repository. |
|
/test e2e-gcp-op-single-node |
sinnykumari
force-pushed
the
e2e-gcp-op-sno
branch
from
fe3ef8a to
fe37e33
Compare
|
There is a known issue that on Single Node OpenShift, load is too high for any pod to be deployed when RT kernel profile is being used. As a result, MCO operation gets impacted and are very slow causing our further ci tests to fail like rollback of RT kernel. This is because when we are perform rollback operation, RHCOS node is booted into RT kernel. Corresponding bug: https://bugzilla.redhat.com/show_bug.cgi?id=1939133 . I have moved RealTime kernel test as last test and removed rollback. We can add rollback test once bug#1939133 has been fixed or we have resources in ci to run SNO that is optimized for RT kernel. |
|
/test e2e-gcp-op-single-node |
sinnykumari
changed the title
openshift-ci-robot
added
the
bugzilla/severity-medium
|
@sinnykumari: This pull request references Bugzilla bug 1949818, which is invalid:
Comment DetailsIn response to this:
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/test-infra repository. |
openshift-ci-robot
added
the
bugzilla/invalid-bug
|
/bugzilla refresh |
|
@sinnykumari: This pull request references Bugzilla bug 1949818, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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/test-infra repository. |
openshift-ci-robot
added
bugzilla/valid-bug
sinnykumari
force-pushed
the
e2e-gcp-op-sno
branch
from
fe37e33 to
059816f
Compare
|
/test e2e-gcp-op-single-node |
|
Hmm, from the log e2e-gcp-op-single-node succeeded: But, gathering must-gather logs failed. Looks like having RT kernel installed on node is making node cry for resources. I am going to completely remove TestKernelType test until https://bugzilla.redhat.com/show_bug.cgi?id=1939133 is resolved. |
Also, refactor existing e2e test so that common functionalities can be shared between both SNO and regular cluster We will include kernelType test once https://bugzilla.redhat.com/show_bug.cgi?id=1939133 has been resolved
sinnykumari
force-pushed
the
e2e-gcp-op-sno
branch
from
059816f to
9c2b4ef
Compare
|
/test e2e-gcp-op-single-node |
|
/retest |
1 similar comment
|
/retest |
|
/test e2e-gcp-op-single-node |
|
Finally, e2e-gcp-op-single-node is green 🎉 |
|
/lgtm Looks great! Thanks for working on this! |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sinnykumari, yuqi-zhang The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
4 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@sinnykumari: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
|
/test e2e-agnostic-upgrade |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@sinnykumari: All pull requests linked via external trackers have merged: Bugzilla bug 1949818 has been moved to the MODIFIED state. DetailsIn response to this:
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/test-infra repository. |
6 participants
Also, refactor existing e2e test so that common functionalities
can be shared between both SNO and regular cluster