Comment 12 for bug 1182679

Many recheck issues are not related to this issue at all, and even not ec2, they are not correctly categorized here.

Mostly The Instance vs. SecurityGroup issues are visible and the cinder behaves strangely.

The common thing are:
- Quantum SMOKE job
- They are related to the security groups

tempest.scenario.test_minimum_basic.TestMinimumBasicScenario.test_minimum_basic_scenario is the closest nova test in functionality.
It has servers volumes and security groups, but looks like, it does not adds the security group to the server.
It changes the default security group.
NOT SMOKE

tempest/scenario/test_network_basic_ops.py
Adds a security group, but it does not have a volume.
NOT SMOKE

tempest.api.compute.security_groups.test_security_groups.SecurityGroupsTestJSON.test_server_security_groups
Adds a security group to the server without rules.
NOT SMOKE

The volume tests (tempest.thirdparty.boto.test_ec2_volumes.EC2VolumesTest.test_create_get_delete) fails after the
tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest.test_integration_1.

I did not found any other test case with the 'smoke' attribute, which touches the security groups.
Just only the ec2 test does it as SMOKE.

On tempest side we could wait between several steps, but where are they missing ?
1. create sec group (no wait)
2. add rules (no wait)
3. starting a server with security group (Hanging with timeout , before the ACTIVE state)

The meaning of this line:
AssertionError: State change timeout exceeded!(400s) While waitingfor set(['running', '_GONE']) at "pending"

The _GONE special state, means the listing does not shows the status.
The 'running' is the nova 'ACTIVE' status.
The 'pending' is a general transitional state in this case it is the nova ' BUILD' status.