Closed trenukarya-px closed 9 months ago
@trenukarya-px , Can you please add some details what all tests failed and why, are these tests failed because of changes in 2.5.1 version.
Can you also please share following details
@trenukarya-px
Could you please highlight Bug fixes V/S TestCase mapping
, ie List of test cases that covers the Bug-Fix/Feature that has gone into this new release
@ambiknai refer the release notes for the bug fixes. It is difficult to get all details here.
@arahamad There were 2 failures and both failed with ticket - PWX-31227 and unrelated to the 2.5.1 release but old bug. Low priority bug.
@ambiknai Release notes - https://docs.portworx.com/release-notes/portworx-backup-on-prem
IKS version supported: 1.26.0 or lower ROkS version supported: 4.11.x or lower
What existing IKS/ROKS user(using 2.5.0 or old version) need to do to use 2.5.1 -> They can just upgrade to 2.5.1 as the k8s version supported is not bumped up. Most of the code change is just targeted bug fix.
Test cases executed for bugs:
Px Backup 2.5.1 Release Notes: https://docs.portworx.com/release-notes/portworx-backup-on-prem.html Release payload is mainly for Keycloak fix related to UI access in port forwarding case.
Tests:
Complete automated Px Backup Torpedo system tests with OCP, RKE, Vanilla, IBM including upgrade scenario for both Stork and Px Backup versions .
PX Backup UI access tests in fresh install and upgrade scenario for below configurations: K8s Flavours: Vanilla, OCP, GKE, AKS, EKS, RKE, IBM UI Access: Node port, Ingress, Load Balancer, HTTP/HTTPs, 1000 keycloak users, Azure AD
Screenshots attached for testrail screenshot