Update velero module dependency #1732
Conversation
ShyamsundarR
force-pushed
the
update-velero
branch
from
6f45b5e to
4b13130
Compare
ShyamsundarR
force-pushed
the
update-velero
branch
from
4b13130 to
9224788
Compare
|
@raghavendra-talur I think we need to update e2e instance with later go lang version for this PR to go through. |
I think the issue is stale go 1.22 build container. I removed the image and triggered new e2e job run. It should work now. We probably need to remove the build container periodically, maybe in the e2e-daily job. |
|
e2e build passed: But we are still using velero 1.14 images: ramen/test/addons/velero/start Line 20 in fad02f2 We also need to move the velero images to ramendr repo and maybe build them in the CI instead of manually. |
Update required modifying backup phases that were observed during backup actions, as constants for the phases have changed. Signed-off-by: Shyamsundar Ranganathan <[email protected]>
ShyamsundarR
force-pushed
the
update-velero
branch
from
9224788 to
96f0c58
Compare
Update required modifying backup phases that were observed during backup actions, as constants for the phases have changed.