Known problems with Eucalyptus 1.4

  • Changing cluster controller configuration via the Web UI may not work. If you need to change cluster controller's host or port, please, see the support forum for details. Proper fix will appear in v1.5.
  • Multiple VM Types do not work. If more than one VM Type is used simultaneously the cloud controller becomes unusable and must be restarted. In those situations ec2-run-instances will report Server: SERVICE: FinishedVerify PROBLEM: null MSG-TYPE: RunInstancesType. We recommend setting parameters for all 5 VM Types to the same values. The proper solution will appear in v1.5.
  • After changing more than one value in VM Types and clicking "Save VmTypes" you may see the "Failed to save! (Make sure values in each column are ordered.)" error. If the values are actually in order, the solution is to change them one-at-a-time.
  • ec2-describe-availability-zones verbose may incorrectly report the status of node certificates as 'false'. Unlike in version 1.3, non-administrative users cannot see the number of available nodes (this has been requested for the future versions).
  • The file axis2c.log contains errors:
    [error] rampart_handler_util.c(241) [rampart][rampart_handler_utils] 0 parameter is not set.
    [error] error.c(94) OXS ERROR [x509.c:284 in openssl_x509_get_subject_key_identifier] oxs defualt error , The extenension index of NID_subject_key_identifier is not valid
    
    while the file httpd-nc_error_log (on the nodes) may contain errors:
    [error] server reached MaxClients setting, consider raising the MaxClients setting
    
    These errors are benign and can be ignored.
  • EC2 command-line tools fail with Server: An error was discovered processing the <wsse:Security> header. (WSSecurityEngine: Invalid timestamp The security semantics of message have expired) Solution: Ensure that the clocks on the client and server machines are synchronized. This is not a Eucalyptus bug, but a consequence of the security policy enforced by the ec2 command-line tools.
  • Support for multiple clusters can only be enabled manually