Synchronize release-4.12 with master #27541
Conversation
Adding a test case for the bond-cni. The test checks if a pod with a bond is created successfully, and then checks connectivity between two pods with bond interfaces.
This will be used to submit to a new sippy risk analysis API to determine how risky the test failures in this job run are. As with junit xmls, there can be multiple as we often invoke openshift-tests multiple times in one job run. Includes a change to make timestamp suffixes on junit artifacts more consistent.
… and upload. This merges test-flake files, submits them to sippy, and writes the returned risk analysis as an additional artifact. It is intended to be called from the workflow steps that run openshift-tests in the release repo.
Signed-off-by: ehila <ehila@redhat.com>
upkeep: test data update
Write test failure summary, and add new command to request failure risk analysis from sippy.
only print the timeline into artifact dir to reduce noise
Add more resource to watch
Add bond cni test
Store monitor events in artifact directory at the end of run monitor
refactor how tests are run
This was causing the test to be skipped: : [sig-scheduling][Early] The openshift-console console pods [apigroup:console.openshift.io should be scheduled on different nodes [Suite:openshift/conformance/parallel] Reason: skipped because the following required API groups are missing: console.openshift.io should be scheduled on different nodes [Suite:openshift/conformance/parallel
OCPBUGS-3282: Fix apigroup tag missing closing brace.
Merge upgrade and conformance alert backstop tests
|
@stbenjam: No Bugzilla bug is referenced in the title of this pull request. 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
bot
added
vendor-update
stbenjam
changed the title
|
@stbenjam: No Bugzilla bug is referenced in the title of this pull request. 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. |
stbenjam
changed the title
|
@stbenjam: No Bugzilla bug is referenced in the title of this pull request. 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
bot
added
the
do-not-merge/work-in-progress
stbenjam
force-pushed
the
update-4.12
branch
from
e34ad3e to
06548f5
Compare
stbenjam
force-pushed
the
update-4.12
branch
from
06548f5 to
b1dc0df
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, stbenjam 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 |
|
/test verify |
stbenjam
changed the title
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
@stbenjam: No Bugzilla bug is referenced in the title of this pull request. 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. |
|
@stbenjam: The following tests 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. |
|
/label bugzilla/valid-bug |
|
@stbenjam: Can not set label bugzilla/valid-bug: Must be member in one of these teams: [openshift-patch-managers openshift-staff-engineers] 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. |
deads2k
added
bugzilla/valid-bug
11 participants
After discussing with the team, there were a number of changes that landed in master recently we want to ensure make it into release-4.12. As 4.12 is an EUS release, there are late arriving commits such as risk analysis, refactoring how tests run, creating the etcd/scaling suite, etc.