| 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. |
| The User Console exhibits odd behavior (EUCA-4530) |
TThe User Console is intended to work with normal
user accounts. If you log in with the
eucalyptus account, the
User Console will not work correctly on some pages,
such as Elastic IPs. |
| 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. |
| BFEBS fails in some cases when running new
instances, with error RollbackException:
Error while committing the transaction
(EUCA-4271) |
If a new instance is constructed in a group
concurrently with network resources being freed in
that group, a RollbackException: Error while
committing the transaction error is
thrown. This also results in an orphaned volume that
cannot be deleted until the VM metadata has timed
out and the volume is recognised as unused. Running
the new instance a second time should succeed.
|
| euca-reboot-instances only
reboots one instance, even if multiple instances are
specified (EUCA-4268) |
euca-reboot-instances reboots
the first instance specified. To reboot multiple
instances, run
euca-reboot-instances once per
instance. |
| Changing LOCALE does not change the language of
the fault message in fault logs (EUCA-4233) |
Changing the system LOCALE does not change the
language of the fault message logged in
[component]-fault.log.
Create customized fault messages in the
/etc/eucalyptus/faults/en_US
directory if you do not wish to use the provided
messages. |
| User console hangs when launching an instance
with large user data file (EUCA-4223) |
Launching an instance through the console may
hang if the user data file is too big. Launch
instances on the command line if the user data file
is larger than 16KB. |
| A snapshot registered as an image must be
deregistered twice to be fully removed (EUCA-4207) |
Running deregister-image does
not initially delete the image record for a snapshot
that was registered as an image. You must run
deregister-image twice to
ensure the image is deleted. |
| CC image caching does not work with some symlinks
(EUCA-4181) |
If CC_IMAGE_PROXY_PATH in
eucalyptus.conf is set to a
symlink, CC image caching may not work. Ensure the
symlink is placed in a path that is readable by the
'eucalyptus' user. |
| 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. |
| Attempts to create an instance from an uncached
image stay pending indefinitely (EUCA-4112) |
If the cluster controller image cache is set to
zero, attempts to create an instance from an
uncached image will remain pending indefinitely. To
prevent images being cached, remove the
CC_IMAGE_PROXY line from
eucalyptus.conf. |
| [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.0 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. |
| 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. |
| euca-describe-nodes does not return consistent
results (EUCA-3456) |
The output of euca-describe-nodes is not
consistent. |
| 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. |
| euca-start-instances does not return correct
information (EUCA-3311) |
euca-start-instances only returns the instance
identifier and does not return the previous or the
current state of the instance. |
| 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. |
| 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.
|
| RollbackException error while committing
transaction failure when attempting to run a BFEBS
instance(EUCA-4271) |
In some cases, network resources (primarily vlan
tags for the network group) are freed concurrently
while a new instance is being constructed in that
same group. If the network group is seen to have no
more instances, then the CC can timeout the vlan tag
and then inform the CLC, which frees the vlan tag
resource. If there is a concurrent instance being
constructed, however, an attempt may be made to use
that vlan tag, and upon volume attach the database
update fails because the vlan/network tag record
doesn't exist. When this happens, the instance will
stay in a 'pending' state with an IP address of
0.0.0.0 for a very long time. There is no long-term
negative effect of this condition. To resolve this
issue, you should proceed with terminating the
instance, deleting its resulting volume if
necessary, and then re-running the instance.
|
| 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. |