e2e: workaround fix for omap leaks

2 omap objects are getting leaked in the e2e tests, this change is to
workaround them for now.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
This commit is contained in:
Prasanna Kumar Kalever 2022-05-05 08:16:40 +05:30 committed by mergify[bot]
parent ea8a3548e6
commit ba6052e896

View File

@ -2767,6 +2767,10 @@ var _ = Describe("RBD", func() {
e2elog.Failf("failed to check csi journal in pool: %v", err)
}
err = deleteJournalInfoInPool(f, pvc, "replicapool")
if err != nil {
e2elog.Failf("failed to delete omap data: %v", err)
}
err = deletePVCAndApp("", f, pvc, app)
if err != nil {
e2elog.Failf("failed to delete PVC and application: %v", err)
@ -2807,6 +2811,10 @@ var _ = Describe("RBD", func() {
e2elog.Failf("failed to check data pool for image: %v", err)
}
err = deleteJournalInfoInPool(f, pvc, "replicapool")
if err != nil {
e2elog.Failf("failed to delete omap data: %v", err)
}
// cleanup and undo changes made by the test
err = deletePVCAndApp("", f, pvc, app)
if err != nil {