-
Notifications
You must be signed in to change notification settings - Fork 175
Open
Labels
component/infrastructureInfrastructure related to building and testingInfrastructure related to building and testingcomponent/testTests not covered by a more specific component labelTests not covered by a more specific component labelkind/defect/performanceBehavior that is functionally correct, but performs worse than intendedBehavior that is functionally correct, but performs worse than intended
Description
This is a set of areas in the integration tests (nimbus) that bear further investigation.
- All the suites have a hard coded number of retries and wait times for testbed deployment failure. If this is a common deployment pattern then these values should be parameterized so it's simple to adjust as the backend infra (or our usage pattern) is improved. This is compounded by the fact that we have a retry cycle in Nimbus Testbed Deploy meaning we're trying 50x and have 340min of sleeping before failing for each suite.
- Failed testbed deployments do not appear to clean up before retrying - unclear if it's simply not needed or is missing.
- There are tests that define their own testbeddeploy keywords ([search])(https://github.com/vmware/vic/search?q=nimbus-testbeddeploy&unscoped_q=nimbus-testbeddeploy&type=Code) however there can be only one
- Nimbus Cleanup failure
No keyword with name 'Cleanup Nimbus PXE folder' found. Did you mean:
Nimbus-Util.Cleanup Nimbus Folders -
--vcfvtBuildPathoptions in VSAN tests reference non-existent /dbc/ path- possibly we can revert to using
vcqa-vsan-simple-pxeBoot-vcvawhich I found in Nightlies test fails while creating a VSAN Cluster. #4630. Need to track down why this was changed. Change was from [skip ci] Update vsan test bed to include DVS and DVPG #5842 - may try using the testbed supplied there.
- possibly we can revert to using
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
component/infrastructureInfrastructure related to building and testingInfrastructure related to building and testingcomponent/testTests not covered by a more specific component labelTests not covered by a more specific component labelkind/defect/performanceBehavior that is functionally correct, but performs worse than intendedBehavior that is functionally correct, but performs worse than intended