Skip to content

Conversation

@gauravaradhye
Copy link

Cleanup list should be declared before returning from setUpClass() so that tearDownClass() works properly.

Currently the test cases are failing with "Class does not have cleanup attribute".

Tested with passing LXC as hypervisor and test cases skipped successfully without giving any error.

Test the timing issue of root disk data sync ... SKIP: Template creation from root volume is not supported in LXC
TS_BUG_009-Test the size of template created from root disk ... SKIP: Template creation from root volume is not supported in LXC
TS_BUG_010-Test check size of snapshot and template ... SKIP: Template creation from root volume is not supported in LXC
TS_BUG_011-Test Reusing deleted template name ... SKIP: Template creation from root volume is not supported in LXC


Ran 4 tests in 28.247s

OK (SKIP=4)

Test Create/Delete a manual snap shot and verify ... SKIP: Snapshots are not supported on LXC
Test Create/delete a volume and verify correct usage is recorded ... SKIP


Ran 2 tests in 10.303s

OK (SKIP=2)

@sanju1010
Copy link
Contributor

LGTM...Please commit

@asfgit asfgit closed this in c841d68 Jun 23, 2015
@asfbot
Copy link

asfbot commented Jun 23, 2015

cloudstack-pull-requests #631 SUCCESS
This pull request looks good

@gauravaradhye gauravaradhye deleted the 8579 branch June 24, 2015 10:41
kishankavala pushed a commit to kishankavala/cloudstack that referenced this pull request Jun 25, 2015
rohityadavcloud pushed a commit that referenced this pull request Jan 20, 2021
…resources and enables settings (#517)

Fixes #511

Signed-off-by: Rohit Yadav <[email protected]>
weizhouapache pushed a commit to shapeblue/cloudstack that referenced this pull request Mar 4, 2025
…ession (apache#519)

Fixes apache#511

For HA work items that are created for host state change, checks must be done when execution is called in a new management server session.

A new column, reason, has been added in cloud.op_ha_work table to track the reason for HA work.

When HighAvailabilityManager starts it finds and puts all pending HA work items in Investigating state. During execution of the HA work if it is found in investigating state, checks are done to verify if the work is still valid. If the jobs is found to be invalid it is cancelled.

Upstream PR: apache#10167

Signed-off-by: Abhishek Kumar <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants