Commit eacfe9f
OCPBUGS-59354: E2E add test to verify guaranteed pod is running after kubelet restart (#1361)
* verify Guranteed pod is running after kubelet restart
This PR addresses issue where we are verifying
if the cpu manager state file is same after kubelet restart
while we are verifying the above, we are not checking
if Guranteed pod started before kubelet restart is also
still running.
Refer: https://issues.redhat.com/browse/OCPBUGS-43280
Signed-off-by: Niranjan M.R <mrniranjan@redhat.com>
* avoid using indirect references and test negative pod status condition
Signed-off-by: Niranjan M.R <mrniranjan@redhat.com>
* typo fix and add more debug when pod fails
Signed-off-by: Niranjan M.R <mrniranjan@redhat.com>
---------
Signed-off-by: Niranjan M.R <mrniranjan@redhat.com>
Co-authored-by: Niranjan M.R <mrniranjan@redhat.com>1 parent 4f5c8b9 commit eacfe9f
File tree
1 file changed
+32
-0
lines changed- test/e2e/performanceprofile/functests/1_performance
1 file changed
+32
-0
lines changedLines changed: 32 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
346 | 346 | | |
347 | 347 | | |
348 | 348 | | |
| 349 | + | |
| 350 | + | |
| 351 | + | |
| 352 | + | |
| 353 | + | |
349 | 354 | | |
350 | 355 | | |
351 | 356 | | |
| |||
362 | 367 | | |
363 | 368 | | |
364 | 369 | | |
| 370 | + | |
| 371 | + | |
| 372 | + | |
| 373 | + | |
| 374 | + | |
| 375 | + | |
| 376 | + | |
| 377 | + | |
| 378 | + | |
| 379 | + | |
| 380 | + | |
| 381 | + | |
| 382 | + | |
| 383 | + | |
| 384 | + | |
| 385 | + | |
| 386 | + | |
| 387 | + | |
| 388 | + | |
| 389 | + | |
| 390 | + | |
| 391 | + | |
| 392 | + | |
| 393 | + | |
| 394 | + | |
| 395 | + | |
| 396 | + | |
365 | 397 | | |
366 | 398 | | |
367 | 399 | | |
| |||
0 commit comments