d8dfun/virtual-kubelet
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity
Files
513cebe7b7cf590cd53c02ea8da1a20b58dd8f18
virtual-kubelet/vendor/github.com/vmware/vic/tests/test-cases/Group11-Upgrade/11-04-Upgrade-UpdateInProgress.md
Loc Nguyen 513cebe7b7 VMware vSphere Integrated Containers provider (#206) 
* Add Virtual Kubelet provider for VIC

Initial virtual kubelet provider for VMware VIC.  This provider currently
handles creating and starting of a pod VM via the VIC portlayer and persona
server.  Image store handling via the VIC persona server.  This provider
currently requires the feature/wolfpack branch of VIC.

* Added pod stop and delete.  Also added node capacity.

Added the ability to stop and delete pod VMs via VIC.  Also retrieve
node capacity information from the VCH.

* Cleanup and readme file

Some file clean up and added a Readme.md markdown file for the VIC
provider.

* Cleaned up errors, added function comments, moved operation code

1. Cleaned up error handling.  Set standard for creating errors.
2. Added method prototype comments for all interface functions.
3. Moved PodCreator, PodStarter, PodStopper, and PodDeleter to a new folder.

* Add mocking code and unit tests for podcache, podcreator, and podstarter

Used the unit test framework used in VIC to handle assertions in the provider's
unit test.  Mocking code generated using OSS project mockery, which is compatible
with the testify assertion framework.

* Vendored packages for the VIC provider

Requires feature/wolfpack branch of VIC and a few specific commit sha of
projects used within VIC.

* Implementation of POD Stopper and Deleter unit tests (#4)

* Updated files for initial PR
2018-06-04 15:41:32 -07:00

1.6 KiB
Raw Blame History

Test 11-04 - Upgrade UpdateInProgress

Purpose:

To verify that vic-machine inspect could detect the upgrade status of a VCH

Environment:

This test requires that a vSphere server is running and available

Test Steps:

  1. Download vic_7315.tar.gz from gcp
  2. Deploy VIC 7315 to vsphere server
  3. Set UpdateInProgress to true using govc
  4. Upgrade VCH
  5. Run vic-machine upgrade --resetInProgressFlag to reset UpdateInProgress to false
  6. Upgrade VCH
  7. Run vic-machine inspect to check the upgrade status of the VCH (this should run in parallel with step 6)
  8. After step 3 finishes, run step 4 again.

Expected Outcome:

  • In step 4, output should contain "Upgrade failed: another upgrade/configure operation is in progress"
  • In step 5, output should contain "Reset UpdateInProgress flag successfully"
  • In step 6, output should contain "Completed successfully"
  • In step 7, output should contain "Upgrade/configure in progress"
  • In step 8, output should not contain "Upgrade/configure in progress"

Possible Problems:

  • This suite may fail when run locally due to a vic-machine upgrade issue. Since vic-machine checks the build number of its binary to determine upgrade status and a locally-built vic-machine binary may not have the BUILD_NUMBER set correctly, vic-machine upgrade may fail with the message foo-VCH has same or newer version x than installer version y. No upgrade is available. To resolve this, follow these steps:
    • Set BUILD_NUMBER to a high number at the top of the Makefile - BUILD_NUMBER ?= 9999999999
    • Re-build binaries - sudo make distclean && sudo make clean && sudo make all