Known Issues

The following known issues exist in Eucalyptus 4.0.1 and its dependencies. Please contact Eucalyptus support for known workarounds to these issues.

New known issues for this release:

Issue Description
The delete on terminate checkbox on the Launch Configuration Wizard of the Eucalyptus Management Console is always enabled. (GUI-1039)

The delete on terminate value is always be set to True despite the checkbox value set in the Device Mapping editor for EBS-backed images.

Creating an IAM policy for a user or group whose name contains a + character causes errors. (GUI-1030)

When adding an IAM policy, and the user or group name contains a + character, a 502 Bad Gateway error results. Upon returning to the previous page using the browser's back button, another error message displays on the top of the Management Console.

Workaround: Use the CLI commands (e.g. euare-useraddpolicy or euare-groupaddpolicy) instead.

Setting any quota to 0 for an IAM user causes errors. (GUI-1029)

When setting quotas for a particular IAM user, entering a value of 0 causes errors.

Workaround: Some users find it more useful to define a quota limit with the value 0 instead of using a 'Deny' action. Since we currently do not support using 0 as a value, use the CLI commands ec2-deny-vmtypes or ec2-vmquota) instead to enforce the policy at the account level.

No Session Timeout notification displays after the Eucalyptus Management Console times out. (GUI-263)

The default timeout for the admin user is one hour, while the timeout for non-admin users is 12 hours (assuming the 30-minute idle timeout has not already been reached first). However, when either timeout is reached, clicking the dashboard or the screens in the Management Console appears to do nothing. Reloading the page or visiting another page in the application causes the page to be redirected to the login screen without notificaton that they have timed out.

The Node Controller (NC) does not support the cancel-bundle-task operation. (EUCA-9351)

The cancel-bundle-task operation has no effect on bundle tasks already under way (on both KVM and VMware), allowing the bundling process to complete and then marking it as failed/canceled.

The Broker does not support the cancel-bundle-task operation. (EUCA-9350)

The cancel-bundle-task operation has no effect on bundle tasks already under way (on both KVM and VMware), allowing the bundling process to complete and then marking it as failed/canceled.

Multiple user-facing services nodes cause slowness on bootstrap (EUCA-9165)

If you install multiple user-facing services nodes, you must wait for them to become enabled (during bootstrap or restart), which can take 15-20 minutes.

The default password has been removed from Eucalyptus installs to enhance security. (EUCA-8497) The default password for the the eucalyptus/admin user has been removed from Eucalyptus installs. To set a password allowing access to the admin/user consoles, run the following commands using your Eucalyptus account credentials:
euare-useraddloginprofile -u admin -p $PASSWORD
euare-userupdateinfo -u admin -k email -i $EMAIL							

Setting the email is not required, but doing so prevents the user from being prompted to change the password upon first log in.

Manual cleanup of cached EMI images are required when upgrading VMWare Broker. (DOC-1220) After shutting down the VMware Broker, remove all the cached VM images with the name, emi-XXXX-YYYY before starting the upgraded Broker. For details on how to access these images and remove them, see Eucalyptus Upgrade or Migration in the Eucalyptus Installation Guide.

Outstanding known issues from previous releases:

Issue Description
Instance Migration Fails on CentOS/RHEL 6.5 (EUCA-8650) Instance live migration does not work with the default qemu-kvm version.

Workaround: after installing the eucalyptus-nc package (for a fresh install) or immediately after upgrading the cloud and the base OS to CentOS 6.5, downgrade the qemu-kvm and qemu-img packages by running the following commands on the node controllers:

yum downgrade \
service libvirtd restart
On Security groups landing page "More actions" button sometimes fails to activate in Windows7 / IE10 (EUCA-8166) Workaround: refresh the page.
Cannot change launch config of autoscaling group from the user console while running Internet Explorer 10 and Windows 7 (EUCA-7952) Attempting to change a launch configuration with the user console while running Internet Explorer 10 on Windows 7 results in the error " "Failed to update sclaing group. Please try again.". Workaround: use the Firefox or Google Chrome browser, or use the command line tools.
EBS image registration ignores user-supplied architecture argument (EUCA-7337) EBS image registration defaults to x86_64. The default should be i386. In addition, if you attempt to change the architecture explicitly, it's ignored and stays x86_64. The is cosmetic, as the backend ignores the architecture argument.
euca-describe-nodes does not return output in certain distributed topologies (EUCA-7039) When the CLC, CC, and NCs are distributed components, euca-describe-nodes returns nothing. This is an issue with the CLC. Workaround: see linked bug. Note: This workaround just allows you to figure out how many nodes are attached to running instances as an administrator.
Misleading error from euca_conf --configure-vmware (EUCA-378) When using VMware Broker with direct connection to ESXi machine - if there is no virtual network created, "euca_conf --configure-vmware" will error out. Workaround: see linked bug.
Eucalyptus keeps the previous IPs in VNET_PUBLICIPS even after the field is modified and CC cleanrestarted. (EUCA-3856) Eucalyptus keeps the previous IPs in VNET_PUBLICIPS even after the field is modified and CC cleanrestarted.
Registering image after euca-bundle-instance differs for vmware. (EUCA-7847) Name of the manifest file on vmware differs from other virtualization types. Please check content of the backet used for bundling to find out correct manifest name. Generally it should be backet/prefix.manifest.xml for instances started from linux paravirtualized images and backet/prefix.raw.manifest.xml for instances started from all other images. For example:
  • <bundle_name>/<prefix>.manifest.xml for paravirtualized instances
  • <bundle_name>/<prefix>.raw.manifest.xml for all other instances
Volume attachments fail with EBS backed guests using ephemeral disks post stop/start (EUCA-7460) Workaround: see linked bug.
euca_imager does not honour cacheDirectoryLimitMb property (EUCA-6531) The cacheDirectoryLimitMb property does not work on VMware even after adding it to the config and euca_imager left cache directory with all files after image creation.
Broker does not support some host configurations (BROKER-36) When using VMware, all hosts must either be managed by VCenter or the Eucalyptus VMware Broker. Mixed management of the hosts is not supported and will result connectivity issues with the Broker.
Eucalyptus cloud service JVM SIGSEGV in HA configuration (EUCA-7030) In an HA configuration, the eucalyptus-cloud service exits with a SIGSEGV fatal error after a fairly short period. When this occurs the current thread is always "C2 CompilerThread0" and the method under compilation is "java.sql.DriverManager::getDriver". A workaround for this issue is to add "-Xint" to CLOUD_OPTS in eucalyptus.conf to disable hotspot. However, please note that this workaround might have some performance impact.
When LDAP/AD integration is enabled, login profiles are not enabled (EUCA-6760) When LDAP/AD integration is enabled, euare-userloginprofiles are not created. To make sure that users can log into the Administration Console, do the following:
  1. Create a login profile using a "dummy" password:
    euare-useraddloginprofile --delegate account1 -u user03 -p test
  2. Check to see that the user's login profile has been created:
    euare-usergetloginprofile --delegate account1 -u user03

The user can now log into the Administration Console using their user ID and LDAP/AD password.

Important: This only applies to the Administration Console. You do not need to creat login profiles for the User Console.
Modify service does not work always (EUCA-6389) In some cases the euca-modify-service command does not work. A subsequent retry of this command should succeed.
NC often goes to NOTREADY state during multiple instance migration (EUCA-6366) During a multiple instance migration the user may see the source NC transition into NOTREADY state. There is no explicit action required. The NC will transition back to ENABLED and the migration will succeed.
Failure to create backing for instance migration (EUCA-6228) In some cases the user may see a failure when attempting multiple instance migration. The workaround is to run the migration a second time, which should succeed.
Instances become inaccessible if CC is clean restarted during migration (EUCA-6232) Performing a clean-restart operation during a migration may cause instances to become inaccessible. It is best to avoid a clean-restart operation during migration.
Walrus image cache is hidden to the user (EUCA-6068) When a registered image is deleted from Walrus the cache files stay behind, but they are not shown when listing bucket contents. An attempt to delete the bucket will return a 409 BucketNotEmpty. To workaround this issue de-register the deleted images and then delete the bucket.
Successfully started migration can be reported as failed (EUCA-6043) The user may see an error message when attempting to migrate an instance: Error(MigrateInstancesType): Migrating instance i-820A3F02 failed because of: Error parsing document (line -1, col -1, in SOAP-message) In spite of this error the migration has started and should successfully complete.
BundleInstance always produces x86_64 images (EUCA-5979,EUCA-5980) The euca-bundle-instance command defaults to the x86_64 architecture for both the NC and VMWare Broker. In order to ensure the appropriate architecture the user must always supply the --arch option to euca-register.
Some components are initialized rather than disabled after an unexpected reboot (EUCA-4354) This only occurs when CLC, Walrus, and SC are located on the same machine in an HA setting. In an unexpected reboot within that setting, when the redundant components switch roles, some secondary components can become initialized rather than disabled. For a workaround, restart the initialized components. We strongly recommend that you use one machine for each Eucalyptus component in HA mode.
User console requires upload of private key to access a Windows instance password (EUCA-4293) Passwords for Windows instances are encrypted for a specified key pair. The user console requires that you upload the appropriate private key to access an instance password. We strongly recommend against using this feature without HTTPS! To access the instance password without uploading your private key, use euca-get-password [instance id] -k [keyfile] on the command line.
User console cannot generate new Windows password on restarting a stopped instance (EUCA-4291) The user console continues to display an old password after a Windows instance is stopped and restarted. You must log out of the user console, log in again, and then generate a password, in order to log in to a Windows instance that has been stopped and restarted.
The reporting feature in the Eucalyptus Administrator Console show no metrics. (EUCA-4168) This occurs only if you run a report that includes the current date. The metrics that show no data are: CpuUsage%, Net Total In/Out, Disk R/W, Disk IOPS R/W, and DiskTime. For a workaround, use the CLI command, eureport-generate-report, to run reports from the Cloud Controller for a time period that includes the current date. You can also use the Eucalyptus Administrator Console and move the end date up the previous day.
No client side reporting on exceeding maxtotalvolumesizeingb (EUCA-4030) If an EBS-backed instance is launched that is larger than the cloud property maxtotalvolumesizeingb, then there is no error reported back to the client. The instance is terminated. The workaround is to increase the following cloud properties:
  • storage.maxtotalvolumesizeingb
  • storage.maxvolumesizeingb

Once these values are increased, the instances will launch.

[error:0290] message printed on upgrade (EUCA-4027) The Eucalyptus upgrade process requires a large number of file descriptors, and an error may occur if ulimit is not set to an appropriate value. To avoid this error, set ulimit -n 5000 before upgrading Eucalyptus. This error is not an indication of a failed upgrade.
Unable to start stopped instances after upgrade (EUCA-4026) Eucalyptus 3.2 manages ISCSI targets in a different way to previous versions. The first attempt to start any stopped instances relying on iscsiadm will fail, but the issue is resolved during cleanup so subsequent requests for that instance will work.
ERR-1009 "Mismatched cryptographical keys" gets written too many times in cc-fault.log (EUCA-3986) Currently, CC may log this fault once for each process in the pool. This is because the logic that suppresses duplicate faults relies on process-local memory rather than memory regions shared across CC processes.
Vague error message: Failed to find corresponding class mapping for element: RegisterVMwareBroker in namespace. (EUCA-3808) If you get this error message, you need to install the eucalyptus-enterprise-vmware-broker-libs on the CLC. Run yum install eucalyptus-enterprise-vmware-broker-libs on each CLC in your cloud.
Capacity report shows unordered list of VM types (EUCA-3707) When running a capacity report, the VM types are not ordered from smallest to largest instance type when displayed at the cloud or AZ property level.
ENABLED CC have two NAT rules about (EUCA-3440) In HA Mode, ENABLED CC can get into a state where it reports both ENABLED and DISABLED CLC in iptables for the metadata service.
Walrus does not failover in HA if eucalyptus-cloud process is forcibly killed on primary (EUCA-3202) If the eucalyptus-cloud process is forcibly terminated (kill -9) on the primary Walrus, failover to the secondary Walrus is not automatically triggered.