-
Sub-task
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
2
-
False
-
-
False
-
ToDo
-
-
-
0
-
0.000
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
Sometime Dpa can take few seconds in order to popup the status field on CR. Inside test we are directly accessing that field which causes the panic issue as field doesn't exists yet.
[PANICKED] Test Panicked
In [It] at: /usr/local/go/src/runtime/panic.go:114 @ 06/28/24 02:17:24.424
runtime error: index out of range [0] with length 0
Full Stack Trace
gitlab.cee.redhat.com/app-mig/oadp-e2e-qe/e2e/dpa_deploy.init.func5.4(0x0)
/home/jenkins/ws/workspace/cam/oadp-1.4-tier1-tests/oadp-e2e-qe/e2e/dpa_deploy/no_default_backuplocation.go:150 +0x95a
reflect.Value.call({0x3a83720?, 0xc000b0af00?, 0x13?}, {0x411e0fd, 0x4}, {0xc000d1e1f8, 0x1, 0x1?})
/usr/local/go/src/reflect/value.go:596 +0xca6
reflect.Value.Call({0x3a83720?, 0xc000b0af00?, 0x4b6f430?}, {0xc000d1e1f8?, 0x0?, 0x0?})
/usr/local/go/src/reflect/value.go:380 +0xb9
Report portal link:- https://reportportal-migration-qe.apps.ocp-c1.prod.psi.redhat.com/ui/#oadp/launches/all/6211/356621/log?item0Params=filter.in.status%3DFAILED%26page.page%3D1
