jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Bayer (JIRA)" <j...@apache.org>
Subject [jira] [Created] (JCLOUDS-199) Live test failures for CloudStack against ACS 4.2 latest
Date Mon, 22 Jul 2013 15:20:53 GMT
Andrew Bayer created JCLOUDS-199:

             Summary: Live test failures for CloudStack against ACS 4.2 latest
                 Key: JCLOUDS-199
                 URL: https://issues.apache.org/jira/browse/JCLOUDS-199
             Project: jclouds
          Issue Type: Bug
          Components: jclouds-compute
    Affects Versions: 1.6.1
            Reporter: Andrew Bayer
            Assignee: Andrew Bayer
             Fix For: 1.7.0, 1.6.2

I've been able to start running tests against the ACS 4.2 simulator (see https://github.com/vogxn/docs/blob/master/Marvin.md
for how to set it up - basically, run every mvn command on there, then go find the user it
creates besides admin, create API keys for that user, and run the jclouds live tests with
that user's creds) and am finding a number of failures we can actually do something about
(as well as a bunch of failures that are, I think, simulator-specific - listed below):

- Any test that tries to create an instance and SSH into it, since the simulator instances
obviously aren't *real* instances
- HypervisorApiLiveTest, which expects to find the same hypervisor list for all zones as in
a specific zone, which isn't the case since the only zone only supports the simulator hypervisor.
- ISOApiLiveTest can create ISOs, and mark them public, but they never hit "ready" and so
listing them fails.
- TemplateApiLiveTest seems to only want to create/register templates on basic networks, and
at the moment, the simulator only works with advanced networks.
- VolumeApiLiveTest seems to be failing due to the simulator hypervisor not actually supporting
attaching volumes, but I could be wrong about this.

More work to come - thanks to [~tsp] for getting me this far!

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message