Repository navigation
Conversation
|
/test limit=local |
|
❗ By default, the pull request is configured to backport to all release branches.
|
|
@litaocdl, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/6296239281 |
|
/test feature_type=backup-restore |
|
@NiccoloFei, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/6298252998 |
ad08b86 to
a49d879
Compare
|
/test |
|
@NiccoloFei, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/6302235120 |
5ab5634 to
f555cc0
Compare
|
/test feature_type=backup-restore,replication |
|
@NiccoloFei, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/6312117962 |
Since the introduction of phaseWaitingForInstancesToBeActive, PhaseUpgrade/PhaseFailOver (and other phases) are now properly being replaced by the newly introduced phase right after the related operation is complete. Because these phases get superseded very quickly, we should not rely passing through them during the E2E tests. Signed-off-by: Niccolò Fei <[email protected]>
Signed-off-by: Niccolò Fei <[email protected]>
Since the introduction of phaseWaitingForInstancesToBeActive, PhaseUpgrade/PhaseFailOver (and other phases) are now properly being replaced by the newly introduced phase right after the related operation is complete. Because these phases get superseded very quickly, we should not rely passing through them during the E2E tests. Signed-off-by: Niccolò Fei <[email protected]> Co-authored-by: Niccolò Fei <[email protected]> (cherry picked from commit 451c581)
Since the introduction of phaseWaitingForInstancesToBeActive, PhaseUpgrade/PhaseFailOver (and other phases) are now properly being replaced by the newly introduced phase right after the related operation is complete. Because these phases get superseded very quickly, we should not rely passing through them during the E2E tests. Signed-off-by: Niccolò Fei <[email protected]> Co-authored-by: Niccolò Fei <[email protected]> (cherry picked from commit 451c581)
…native-pg#2858) Since the introduction of phaseWaitingForInstancesToBeActive, PhaseUpgrade/PhaseFailOver (and other phases) are now properly being replaced by the newly introduced phase right after the related operation is complete. Because these phases get superseded very quickly, we should not rely passing through them during the E2E tests. Signed-off-by: Niccolò Fei <[email protected]> Co-authored-by: Niccolò Fei <[email protected]> Signed-off-by: Lennart Krauch <[email protected]>
Closes #2857