ec2-api jobs have been switched to use
ec2api-tempest-plugin for ec2-api tests, so
we can remove the in-tree tempest tests now.
Change-Id: I82ace9ebd1ca5216c2e3fc3d75f07146417ebf94
This patch adds a tempest decorator of UUID for each test in
the functional tests tree. .
This helps in discovering tests by their UUID using tempest
CLI and the decorator format is:
@decorators.idempotent_id('12345678-1234-1234-1234-123456789abc')
Change-Id: Ib4a4694600b1a28be6c23c73fa078960ce4efdec
1) fix bug with filtering
filters were applied before unpaired items is added to result
2) fix races in default security group creation
3) add waiter for associate/disassociate address
4) fix security group classic test
it should choose default group group only from classic groups
5) fix describe_vpc_with_filters test
it can run in parallel with other test with same CIDR
6) fix networks list for instance run at subnet creation/deletion
7) fix selective decsribe by names
it should not delete valid items from db
Change-Id: Iadadefb8b4abebbb3b8efc0e536e5de30ed23dab
when these tests runs in parallel them can fail.
it happens because checking of count addresses can fail.
Change-Id: Iad4dd6cc536b69335435d5d5c5d261b2bc29f59e
cloud can has addresses before test. and test must takes into account
this fact when it calls descibe_addressses
Change-Id: I882c1c8bf386bf2730656b4b7c667bb4d58207b7
If subnet['gateway_ip'] is not None, Neutron prevents manual setting of
0.0.0.0/0 route to subnet host routes.
So we set gateway_ip to None during subnet creation if not internet
gateway is used in an associated route table. As a result Neutron
doesn't add its own 0.0.0.0/0 route, and we don't need to redirect it to
127.0.0.1 if default route is not set for a subnet route table. It
simplifies mapping of VPC route table to Neutron subnet host routes.
Depends-On: I5c314d513922d8a21b3e63de632bb9cd3484b076
Change-Id: Ibeeea1f5d92cc0aa08ac6c360c3e73fa67a45373
AWS can associate an address to a subnet IP while the subnet is not
accessible from Internet due to its route table restriction.
We need to have this test case separated to have a clear mark of
supporting the feature by ec2api.
Change-Id: I86471b6656ceac2ef01002f5db0c27e6cdb69e42
from https://botocore.readthedocs.org/en/latest/client_upgrades.html#client-upgrades
Version 0.104.0 emitted an ImminentRemovalWarning when using the old interface. This warning is now printed to stderr by default. A user can still turn off these warnings via the warnings module.
The develop branch on github will be updated to completely remove the old interface. At this point the client interface will be the only interface available when using the develop branch on github.
A 1.0 alpha version will be released. By default, pip will not pick up any alpha/beta releases.
A 1.0 beta version will be released.
A GA (1.0) version of botocore will be released.
Change-Id: Id6661e3e1e73de018e9b4de7612972654bb27422
and add test cases for delete_on_termination preperty for NetworkInterface
Depends-On: I3d557dd95f442106c495249a5ef1d2ac36e6a2ea
Change-Id: Icf2b9739aaf87b4c9af13ad64a310081a68f776e