mirror of
https://github.com/goharbor/harbor.git
synced 2024-09-12 05:58:23 +02:00
2.1 KiB
2.1 KiB
Test 5-02 - OVA Reboot
Purpose:
To verify that an OVA version of Harbor can be rebooted. Its configuration remains unchanged and should work the same way as before a reboot.
References:
User guide, installation guide of Harbor OVA version.
Environment:
- This test requires an OVA binary of Harbor.
- A vCenter, at least an ESX host, and a network that supports DHCP.
- A linux host with Docker CLI installed (Docker client).
Test Steps:
- From vSphere Web Client, import Harbor's OVA onto an ESX host.
- In the deployment wizard, enter different passwords of Linux root user, Harbor admin user and MySQL root user.
- Leave the networking settings blank.
- Configure email settings. (can be mail server that does not exist )
- Power on the imported OVA.
- Wait a few minutes for the VM's booting and its IP address comes up in vCenter. (may need to refresh in Web Client)
- Open a browser and enter http://VM_IP_address.
- Log in as admin user of Harbor.
- Create a new project.
- On a Docker client host, use
docker login <harbor_host>
command to log in as the admin user. - Run some
docker push
anddocker pull
commands to push images to the project and pull from the project. - On vSphere, open the console of Harbor's VM, log in as root user using the password entered during deployment.
- On vCenter Web Client, reboot the VM. (soft reboot)
- After the VM starts up, repeat Step 7-12, should work the same.
- Power off the VM, and the power it on. (hard reboot)
- After the VM starts up, repeat Step 7-12, should work the same.
- On vSphere, open the console of Harbor's VM, log in as root user, type
ovfenv
command to verify environment variables are the same as those entered during deployment.
Expected Outcome:
- In Step 1-12, everything should work without errors. The passwords entered during deployment should work in Step 7, 9 and 11.
- In Step 14, 16, the VM should work the same before the reboot or power-off.
- Step 17, environment variables should remain unchanged as those entered during deployment.
Possible Problems:
None