Chris Chien

Close this ticket, for newest master head pipeline result(build [220](https://ci.longhorn.io/job/public/job/master/job/sles/job/amd64/job/longhorn-tests-sles-amd64/220/)) , I will create another ticket to trace.

Not sure if they were related but https://github.com/longhorn/longhorn/issues/4383 also failed at volume status = detaching (expect deteched )

Test passed in [v1.2.x](https://ci.longhorn.io/job/public/job/v1.2.x/job/v1.2.x-longhorn-tests-sles-amd64/187/testReport/) pipeline and [v1.3.x](https://ci.longhorn.io/job/public/job/v1.3.x/job/v1.3.x-longhorn-tests-sles-amd64/103/testReport/). But in master branch the result were [failed](https://ci.longhorn.io/job/private/job/longhorn-tests-regression/1851/), need more time to wait daily build result

I can reproduce 1.3.x fail [result](https://ci.longhorn.io/job/public/job/v1.3.x/job/v1.3.x-longhorn-tests-sles-amd64/104/testReport/junit/tests/test_backing_image/test_ha_salvage_with_backing_image/) with master-head in my local side, failed at `check_volume_data` as below shown ``` crash_replica_processes(client, core_api, volume_name) volume = common.wait_for_volume_healthy(client, volume_name) assert len(volume.replicas) == 3...

Close this ticket because after PR https://github.com/longhorn/longhorn-tests/pull/1075 merged, test case were pass in recently build [225](https://ci.longhorn.io/job/public/job/master/job/sles/job/amd64/job/longhorn-tests-sles-amd64/225/), [226](https://ci.longhorn.io/job/public/job/master/job/sles/job/amd64/job/longhorn-tests-sles-amd64/226/), [227](https://ci.longhorn.io/job/public/job/master/job/sles/job/amd64/job/longhorn-tests-sles-amd64/227/). Also in v1.3.x build [116](https://ci.longhorn.io/job/public/job/v1.3.x/job/v1.3.x-longhorn-tests-sles-amd64/116/#showFailuresLink) and v1.2.x build [200](https://ci.longhorn.io/job/public/job/v1.2.x/job/v1.2.x-longhorn-tests-sles-amd64/200/#showFailuresLink) were passed after...

From https://github.com/longhorn/longhorn/issues/4066, the cascading fail caused by `cleanup_all_volumes` can be traced from [May](https://ci.longhorn.io/job/public/job/master/job/sles/job/arm64/job/longhorn-upgrade-tests-sles-arm64/129/)

Close this ticket as test stpes [verified](https://github.com/longhorn/longhorn/issues/2293#issuecomment-1301743625) and document merged

Hi @mantissahz, I use 5 Gi data in a recurring backup job, during backup in progress, I changed a invalid back target from UI. In my environment, the recurring backup...

Verified **pass** in longhorn-manager with test [steps](https://github.com/longhorn/longhorn/issues/4255#issuecomment-1664846767) - master `840dbf` - v1.5.x `e8cfdc` - v1.4.x `718b7f` The recurring job status will eventually failed after change backup target to an invalid...

Verified in longhorn master `0e002d` Result **Pass** 1. With test steps [here](https://github.com/longhorn/longhorn/issues/4107#issuecomment-1327334347), volumesnapshot can be deleted when backup removed first. 2. If create volumesanpshot without backup target set, when deleting...