$ant package-marvin
will create a packaged source tarball of the testclient that is
redistributable and decoupled from the rest of the cloudstack build
reviewed-by: unittest
status 14608: resolved fixed
reviewed-by: Chirag Jog (chirag@clogeny.com)
Set the timeout countdown to start from beginning of each pollAsync instead
of setting it once for the entire run.
status 13234: resolved fixed
reviewed-by: unittest
Uncomment each decorator to test
- tests run as existing admin
- tests run as new user in new domain
- tests run as new user in existing domain
- tests run as old user in existing domain
- tests run as new domain admin in new domain
status 13234: resolved fixed
reviewed-by: unittest
When multiple tests in a user-decorator suite are run only the first
test runs successfully since the apiKey has been altered to that of a
regular user. Preventing failure of other tests by detecting user
context - user, admin, domain-admin.
@UserName decorator applies to a testSuite class not a testMethod
reviewed-by: Chirag Jog
Each testCase class will use its own logger to distinguish log
messages when multiple suites are run. This will aid debugging
Every cloudstackTestCase will also contiain a class level attr of the
testClient which was previously available only to setUp/tearDown. Now
even setUpClass/tearDownClass can use this attribute.
reviewed-by: Sangeetha Hariharan
corrected the sequence in which private and public IPs of the pods are
generated. each 8bit mask should remain in 0-255 range.
depends on python's internal socket implementation. Added an explicit 3m
timeout. Test code MUST NOT induce sleeps longer than 3m, instead check status
periodically to keep the HTTPConnection alive.
reviewed-by: Chirag Jog <chirag@clogeny.com>
tar command random failure may occur due to linux kernal bug (or feature) that tar can't handle well. The failuar happens when tar wants to package a newly created file before file system has fully synced
Summary of changes:
- Fix the order of source nat ip's : Static Nat IP's will be on top of Router source nat IP's. means Static NAT ip will take higher preference when compare to router ip while picking ip for source nat.
Reviewed-by: Abhi
Bug 13429 - copy template FAIL - HTTP Server returned 403
lots of things:
1. generate a IP list of all SSVM across all zones, set this IP list to my .htaccess allowable from.
so other SSVMs get privilege to access me.
2. broadcast my IP to other SSVMs instructing them set me to theirs .htacess allowable from. so I get
privilege to access others
3. set outbound route for downloading through public IP. Because public ip/private ip in the same subnet in basic
zone, the http download traffic may come in through public ip but go outside through private ip which finally causes
the VM where the traffic is from to drop response packets. To resolve this, set individual route for each SSVM public
ip making sure the inter-communication between system vm happens through public IP
however, I met certificate expiraton on one SSVM, will report another bug
reviewed-by: Sheng.yang
status 13526: resolved fixed
status 13429: resolved fixed
The fix is add a separate thread pool for all the reqests from mgt server(which may be time-consuming), so the pingaswer(which is response) is processed in another different thread pool. Make sure the pinganswer is get processed immeidately.
Reviewed-by: Alex