Closed ghost closed 12 years ago
It has also been reported that for rackspace-cloudservers-us, the node list only lists 5 nodes. I am wondering which of the two is the root cause.
So far I don't see any reason, why cli would behave like this, do u have a log (can be found at data/log/jclouds.log)?
The log file does exist but remains empty. I tested with "tail -f jclouds.log" and attempted to list nodes with the nextgen provider via the shell and cli with no errors. Just a short a list.
Jclouds displays most staff as debug and the current threshold is set to INFO, so an empty log means that there are no errors.
I guess you can set the threshold to DEBUG by modifying the etc/log4j.properties file.
Hmm, it working now? Perhaps an issue on the Rackspace side. Closing the issue.
I am unable to list all the server in a test account. The listing stops at a server with ! in the name.
Same result in CLI and shell. ./jcloudsnode list --provider rackspace-cloudservers-us --identity XXX --credential XXX
jclouds:node-list --provider rackspace-cloudserus --identity XXX --credential XXX