davidtclin58
davidtclin58
### Test Plan 2 Result: PASS In the airgapped environment where Harvester `v1.1 head` have been integrated with Rancher `v2.7.0` When we add the following proxy settings in Harvester ```...
Verified **fixed** on `v1.1-26c395ac-head` .Close this issue. ### Result - **Pass** the test plan 1 as result: https://github.com/harvester/harvester/issues/2782#issuecomment-1362525952 - **Pass** the test plan 2 as result: https://github.com/harvester/harvester/issues/2782#issuecomment-1362755325 ### Test Information...
### Test Plan #### Positive - Installation Mode Plan to validate on v1.2.0-rc3 - [x] Ensure can create image node correctly - [x] Ensure can create Harvester in create mode...
During the negative testing, found an potential issue that when we `directly shutdown` an harvester installed via binary mode. After we start the installed Harvester image node again. it failed...
Update the streaming mode test plan and use the predefined v1.2-head image file on verification.
Verified **fixed** on `v1.2.0-rc4` and `v1.2-37aeb5ff`. Close this issue. ### Result According to test plan in https://github.com/harvester/harvester/issues/2198#issuecomment-1637703769 We verified can work on the following types of image installation mode 1....
During the test, we found on the second node, the following images not deleted and remains after upgrade from v1.2.1 to v1.2.2-rc2 * docker.io/longhornio/longhorn-engine:v1.4.3 * docker.io/rancher/mirrored-fluent-fluent-bit:1.9.5 ``` avidtclin@localhost:~/Documents/Harvester/issues/5473> ./check_package2.sh node2/n2-v1.2.2-rc2-purged.txt...
Verified **fixed** on `v1.2-3974e2a8-head` (24/05/09). Close this issue. ### Result #### Four nodes environment Only these images are kept after the upgrade, after confirmed, they are in the expected list...