Known Issues

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

Issue Description
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.
VMware Broker requires eucalyptus user to have write access to the /etc/eucalyptus directory (BROKER-9) If the eucalyptus user does not have write access to the /etc/eucalyptus directory, the VMware Broker will stay in a BROKEN state, and euca-configure-vmware will fail. Run chown -R eucalyptus:eucalyptus /etc/eucalyptus/ on the VMware Broker machine to ensure that the eucalyptus user owns the necessary files.
Requests to create volume fail on startup or initial restart of components (EUCA-6479) In some cases, a Failed to marshall response error occurs on create volume requests. Restarting the components again solves this issue.
Issue adding secondary CLC after upgrade (EUCA-6462) It is not possible to move a non-HA CLC to HA after an upgrade to 3.3.0. A fresh install is recommended in this situation. See linked issue for workaround.
User should be able to set the limit for request timeouts (EUCA-6456) The User Console may time out when displaying resource pages. This occurs when a user has many resources, such as volumes.
In multi-cluster configuration, migrations using --source broken for all clusters but first registered (EUCA-6400) In a multi-cluster cloud migrations using --source are broken for all clusters but the first one registered. Use --instance to work around this issue.
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.
Can't bundle the same instance twice (EUCA-6075) The first attempt to run euca-bundle-instance on an instance will succeed. Subsequent attempts to run this on the same instance will fail. The workaround is to terminate the instance then try again with anotherinstance.
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: com.eucalyptus.ws.WebServicesException: com.eucalyptus.ws.WebServicesException: 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.
A user in non-eucalyptus account does not see a public image (EUCA-5901) A user in an account that is not the eucalyptus account mustuse the -a option with euca-describe-images in order to display public images.
Instance running time instance types in report not consistent with UI and CLI (EUCA-4847) As of Eucalyptus 3.3.0, the instance summary report will no longer be available from the command line tools nor the User Console
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.
DBResourceCheck exceptions logged at ERROR log level (EUCA-4177) The DBResourceCheck class frequently polls to determine the number of active database connections for a given alias. This can result in a DBResourceCheck exception. This exception is expected, and is not fatal.
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.
The euca-describe-bundle-tasks command does not keep task status after task completes (EUCA-4140) When bundling a Windows instance, the task is removed from the task list as soon as the bundle completes, so euca-describe-bundle-tasks never shows a 'complete' status.
[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.
httpd-cc_error_log Grows without bound (EUCA-3909) The httpd-cc_error_log is not rotated and can grow quite large. To reduce this file size, do cp /dev/null $EUCALYPTUS/var/log/eucalyptus/httpd-cc_error_log. This will truncate the file. Removing the file is not recommended.
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.
Quota limiting run instances against availabilityzone resource does not work (EUCA-3614) A policy which limits the number of instances which can be run within an availability zone has no effect.
ENABLED CC have two NAT rules about 169.254.169.254 (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.
Cloud controller listen ports should be predictable (EUCA-3110) It is possible to make configuration changes such that CLC port usage is predictable. Detailed changes are required in order to ensure this. Please contact Eucalyptus support for details
euca-create-image from ebs backed instance fails, returns 0 (EUCA-1333) euca-create-image is currently unsupported.
IP pages do not work properly for admin user in Eucalyptus User Console (EUCA-3548) All user IP addresses are shown, rather than just the admin user's IP addresses.
Must use user-friendly names for mulitpathing(DOC-504) Eucalyptus connect scripts assume multipathing uses user friendly names instead of WWID for the multipath device names, so the "user_friendly_names" option must be enabled in /etc/multipath.conf.
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.
Eucalyptus Console https redirect doesn't work (EUCA-4104) When SSL is enabled for the user console, http requests do not automatically redirect to the proper https address, which can result in a blank page.
Eucalyptus 3.3 now requires JVM version 7 (EUCA-5807) Eucalyptus 3.3 requires version 7 of the Java Virtual Machine. Make sure that your CLOUD_OPTS settings in the /etc/eucalyptus/eucalyptus.conf file either do not set --java-home, or that --java-home points to a version 7 JVM. This needs to happen before services are started but after the upgraded packages are installed.
Netapp SAN: admin will have to set chapuser explicitly after upgrade (DOC-791) If you are a subscriber and use NetApp as the storage SAN backend, you must onfigure the CHAP username to be used by the Eucalyptus on the CLC (the primary CLC in an HA setup) using euca-modify-property -p <partition>.storage.chapuser=<Chap_username>. The CHAP username can be any value, however it should be unique when sharing a NetApp Filer across multiple Eucalyptus clusters. The SC will not transition to ENABLED state until the CHAP username is configured.
The admin console does not provide the correct error message when a password has expired. (EUCA-6543) When attempting a login to the admin console with an expired password, the error message does not provide the correct prescriptive information advising the user reset their password.
x