Page Comparison

Table of Contents

maxLevel	5

...

Excerpt

The Events view allows users to find out what is happening in Abiquo. To open the Events view, click on the Events icon in the main menu bar.

Panel
Privilege: Display all events for current enterprise

Event viewing can be restricted using privileges assigned to user roles. Users can have: no event privileges; the Display all events for current enterprise privilege; or the Display all events privilege. Users with no event privileges will not see the Events icon or the Events window in the Home view.

The default ordinary User and the default Enterprise Admin role have the Display all events for current enterprise. The default Cloud Admin role has the Display all events privilege.

Panel
Privilege: Display all events

If the events you expected to display do not appear in Events view, check with your System Administrator.

The event list

The event list has the following columns:

Column	Description
Source	Shows the system object that is the source of the event or error and its full hierarchy. For example, it could be a MACHINE MODIFY event, where the source is myMachine (the name of the machine) which is part of a rack named myRack which is part of a datacenter named myDatacenter which belongs to the Abiquo enterprise.
Severity	The severity of the event. Can be INFO, WARN or ERROR
Action	The action that generated the event. See Entity and Action Tables
Performed by	The user who performed the Action.
Date/time	The date and time when the event was generated.
User	The user affected by the action
Trace	Additional information about the event. The trace displayed in Events view are documented under Logs in the Troubleshooting section of the Abiquo Administrator's Guide. See Abiquo Logs

There is also the Update automatically checkbox. If checked, new events will be automatically added to the list as they arrive. Otherwise, you must refresh the list manually.

Double-click on an event to see the event detail in the panel below the event list

Filtering events

To make it easier to find a specific event, use the filter tool. Click the filter button at the top right of Events view. Enter your filter criteria and click Accept. To remove the filter, click Clear at the bottom of the popup.

Basic event filtering

Basic event filtering enables you to filter with the following fields:

Event field	Description
Severity	Pull-down list of Severity types
Action	Pull-down list of Actions from Entity and Action Tables
Performed by	The name of the user who performed the action
Date from	Start date in format YYYY/MM/DD
Date to	End date in format YYYY/MM/DD
Enterprise	Enterprise

Advanced event filtering

Click "See more" on the basic filter panel to filter on more fields.

You can search for events related to a datacenter, a user, an enterprise, and so on. You can filter by:

In the following screenshot, the user is searching for events related to the main cloud admin user.

Severity table

Events on the Abiquo platform are classified into three severity categories: info, warning and error.

Severity	Description
INFO	General information events for the user as part of the normal use of the platform
WARNING	Warning about an abnormal situation that does not block normal use of the platform
ERROR	Error that blocks the normal use of the platform

Component List

These values can be used to filter the events by Component.

PLATFORM
DATACENTER
RACK
MACHINE
VIRTUAL_STORAGE
STORAGE_POOL
STORAGE_DEVICE
ENTERPRISE
USER
ROLE
ROLE_LDAP
VIRTUAL_APPLIANCE
VIRTUAL_MACHINE
VOLUME
NETWORK
APPLIANCE_MANAGER
IMAGE_CONVERTER
LICENSE_MANAGER
PERSISTENT_CONVERTER
INSTANCE_CONVERTER
API
WORKLOAD
HIGH_AVAILABILITY
PRICING_TEMPLATE
COSTCODE_CURRENCY
COSTCODE
UCS

Storage System List

These values can be used to filter the Events list by Storage System:

GENERIC_ISCSI
LVM
NETAPP
NEXENTA

Entity and Action Tables

These tables show events that will be displayed for Cloud Users, with a basic cloud user role and privileges.

Div

class	landsc

Entity	Action	Tracer	API Error
Disk
DISK	PERSISTENT_DELETE	The persistent disk 'DISK_LABEL' could not be deleted from template 'TEMPLATE_NAME'. CODE: MESSAGE
DISK	PERSISTENT_DELETE	Persistent disk 'DISK_LABEL' has been deleted.
Layer
LAYER	CHECK_CAPACITY	The anti-affinity layer requires more machines than currently available in the datacenter.	AAFFINITY-0
LAYER	CHECK_CAPACITY	Anti-affinity for layer 'LAYER' in VApp 'VAPP_NAME' cannot be honored: 'NUM_POSSIBLE_MACHINES' were available in Datacenter 'DC_NAME', Rack 'RACK_NAME', but 'MIN_REQUIRED_MACHINES' machines were required.	AAFFINITY-1
Nat_ip
NAT_IP	PURCHASE	NAT IP 'IP' has been purchased by virtual datacenter 'VDC_NAME'.
NAT_IP	RELEASE	NAT IP 'IP' has been released from virtual datacenter 'VDC_NAME'.
NAT_IP	SNAT_NET	NAT IP 'IP' will be used as default SNAT translated IP in all the private networks of virtual datacenter 'VDC_NAME'.
Nat_rule
NAT_RULE	CREATE	Created NAT rule in virtual machine 'VIRTUAL_MACHINE_NAME' original 'NAT_IP':'NAT_PORT_ORIGINAL' translated 'IP':'NAT_PORT_TRANSLATED' (snat
NAT_RULE	DELETE	Deleted NAT rule in virtual machine 'VIRTUAL_MACHINE_NAME' original 'NAT_IP':'NAT_PORT_ORIGINAL' translated 'IP':'NAT_PORT_TRANSLATED' (snat
Public_cloud_region
PUBLIC_CLOUD_REGION	SYNC	Sync 'name' failed. MESSAGE.
PUBLIC_CLOUD_REGION	SYNC FINISHED	A public cloud region synchronization process has been finished for 'name'.
PUBLIC_CLOUD_REGION	SYNC START	A public cloud region synchronization process has been started for 'name'.
Public_ip
PUBLIC_IP	PURCHASE	Public IP 'IP' has been purchased by virtual datacenter 'VDC_NAME'.
PUBLIC_IP	RELEASE	Public IP 'IP' has been released from virtual datacenter 'VDC_NAME'.
PUBLIC_IP	RELEASE FLOATINGIP	Floating IP 'IP' has been released and deleted from location 'DC_NAME' for enterprise 'ENT_NAME'.
PUBLIC_IP	RELEASE IMPORT_FLOATINGIP	Floating IP 'IP' has been released and deleted from location 'DC_NAME' for enterprise 'ENT_NAME'.
Rules
RULES	LOADLEVEL_CPU_EXCEEDED	LOADLEVEL_MESSAGE	RULE-10
RULES	LOADLEVEL_DATASTORE_EXCEEDED	LOADLEVEL_MESSAGE	RULE-12
RULES	LOADLEVEL_RAM_EXCEEDED	LOADLEVEL_MESSAGE	RULE-11
Scheduler
SCHEDULER	VIRTUAL_MACHINE	There are not enough resources to deploy the virtual machine.	SCH-NOT-ENOUGH-RESOURCES
SCHEDULER	VIRTUAL_MACHINE	Scheduler cannot fulfill user request due to SchedulerException: 'ERROR_MESSAGE'.	SCH-VM
Storage_device
STORAGE_DEVICE	INITIATOR_ADD	Unable to create the initiator mapping for initiator 'INITIATORIQN' and volume 'VOLUME_NAME'.	PERSISTENT-13
STORAGE_DEVICE	INITIATOR_ADD	Added initiator to the target storage technology 'INITIATORIQN' and volume 'VOLUME_NAME'.
Task
TASK	DEPLOY_CANCEL	Deploy task 'taskId' (virtual machine 'VIRTUAL_MACHINE_NAME' ('ENT_NAME', virtual appliance 'VAPP_NAME', virtual datacenter 'VDC_ORIGIN'), datacenter 'DC_NAME') workflow cancelation failed (custom message: 'CAUSE').	WKF-02
TASK	DEPLOY_CANCEL	Deploy task 'taskId' (virtual machine 'VIRTUAL_MACHINE_NAME' ('ENT_NAME', virtual appliance 'VAPP_NAME', virtual datacenter 'VDC_ORIGIN'), datacenter 'DC_NAME') workflow cancelation was successful (custom message: 'CAUSE').
TASK	DEPLOY_CONTINUE	Deploy task 'taskId' (virtual machine 'VIRTUAL_MACHINE_NAME' ('ENT_NAME', virtual appliance 'VAPP_NAME', virtual datacenter 'VDC_ORIGIN'), datacenter 'DC_NAME') workflow continuation failed (custom message: 'CAUSE').	WKF-03
TASK	DEPLOY_CONTINUE	Deploy task 'taskId' (virtual machine 'VIRTUAL_MACHINE_NAME' ('ENT_NAME', virtual appliance 'VAPP_NAME', virtual datacenter 'VDC_ORIGIN'), datacenter 'DC_NAME') workflow continuation was successful (custom message: 'CAUSE').
TASK	RECONFIGURE_CANCEL	Reconfigure task 'taskId' (virtual machine 'VIRTUAL_MACHINE_NAME' ('ENT_NAME', virtual appliance 'VAPP_NAME', virtual datacenter 'VDC_ORIGIN'), datacenter 'DC_NAME') workflow cancelation failed (custom message: 'CAUSE').	WKF-02
TASK	RECONFIGURE_CANCEL	Reconfigure task 'taskId' (virtual machine 'VIRTUAL_MACHINE_NAME' ('ENT_NAME', virtual appliance 'VAPP_NAME', virtual datacenter 'VDC_ORIGIN'), datacenter 'DC_NAME') workflow cancelation was successful (custom message: 'CAUSE').
TASK	RECONFIGURE_CONTINUE	Reconfigure task 'taskId' (virtual machine 'VIRTUAL_MACHINE_NAME' ('ENT_NAME', virtual appliance 'VAPP_NAME', virtual datacenter 'VDC_ORIGIN'), datacenter 'DC_NAME') workflow continuation failed (custom message: 'CAUSE').	WKF-03
TASK	RECONFIGURE_CONTINUE	Reconfigure task 'taskId' (virtual machine 'VIRTUAL_MACHINE_NAME' ('ENT_NAME', virtual appliance 'VAPP_NAME', virtual datacenter 'VDC_ORIGIN'), datacenter 'DC_NAME') workflow continuation was successful (custom message: 'CAUSE').
TASK	UNDEPLOY_CANCEL	Undeploy task 'taskId' (virtual machine 'VIRTUAL_MACHINE_NAME' ('ENT_NAME', virtual appliance 'VAPP_NAME', virtual datacenter 'VDC_ORIGIN'), datacenter 'DC_NAME') workflow cancelation failed (custom message: 'CAUSE').	WKF-02
TASK	UNDEPLOY_CANCEL	Undeploy task 'taskId' (virtual machine 'VIRTUAL_MACHINE_NAME' ('ENT_NAME', virtual appliance 'VAPP_NAME', virtual datacenter 'VDC_ORIGIN'), datacenter 'DC_NAME') workflow cancelation was successful (custom message: 'CAUSE').
TASK	UNDEPLOY_CONTINUE	Undeploy task 'taskId' (virtual machine 'VIRTUAL_MACHINE_NAME' ('ENT_NAME', virtual appliance 'VAPP_NAME', virtual datacenter 'VDC_ORIGIN'), datacenter 'DC_NAME') workflow continuation failed (custom message: 'CAUSE').	WKF-03
TASK	UNDEPLOY_CONTINUE	Undeploy task 'taskId' (virtual machine 'VIRTUAL_MACHINE_NAME' ('ENT_NAME', virtual appliance 'VAPP_NAME', virtual datacenter 'VDC_ORIGIN'), datacenter 'DC_NAME') workflow continuation was successful (custom message: 'CAUSE').
Virtual_appliance
VIRTUAL_APPLIANCE	COPY	Virtual appliance 'name' cannot be copied. The 'DISK_TYPE' template of this virtual machine is not compatible with the target hypervisor ('HYPERVISOR_TYPE') and no conversions are available.	VAPP-10
VIRTUAL_APPLIANCE	COPY	Virtual appliance 'name', cannot be copied. The expected state was NOT_DEPLOYED but the actual state is 'state'.	VAPP-13
VIRTUAL_APPLIANCE	COPY	Virtual appliance 'name' cannot be copied; the virtual datacenters (origin 'VDC_ORIGIN' and target 'VDC_DESTINATION') must belong to the same datacenter.	VAPP-7
VIRTUAL_APPLIANCE	COPY	Virtual appliance 'name' cannot be copied. Virtual appliance contains captured virtual machine(s).	VAPP-9
VIRTUAL_APPLIANCE	COPY	Virtual appliance 'VAPP_ORIGINAL_NAME' successfully copied from virtual datacenter 'VDC_ORIGIN' to virtual datacenter 'VDC_DESTINATION' with name 'VAPP_NAME'.
VIRTUAL_APPLIANCE	CREATE	Virtual appliance 'name' has been created.
VIRTUAL_APPLIANCE	DELETE	Delete of the virtual appliance 'VAPP_NAME' succeeded.
VIRTUAL_APPLIANCE	DEPLOY	Deploy of the virtual appliance 'name' failed due to an invalid state. Should have been NOT_DEPLOYED but was 'state'.	VAPP-3
VIRTUAL_APPLIANCE	DEPLOY	Virtual appliance 'name' is being deployed.
VIRTUAL_APPLIANCE	LOCK_DELETE	Delete of the virtual appliance 'name' failed due to an invalid state. Should have been NOT_DEPLOYED but was 'state'.	VAPP-5
VIRTUAL_APPLIANCE	MODIFY	Virtual appliance 'name' has been modified.
VIRTUAL_APPLIANCE	MOVE	Virtual appliance 'name' cannot be moved. The 'DISK_TYPE' template of this virtual machine is not compatible with the target hypervisor ('HYPERVISOR_TYPE') and no conversions are available.	VAPP-10
VIRTUAL_APPLIANCE	MOVE	Virtual appliance 'name' cannot be moved; the virtual datacenters (origin 'VDC_ORIGIN' and target 'VDC_DESTINATION') must belong to the same datacenter.	VAPP-7
VIRTUAL_APPLIANCE	MOVE	Virtual appliance 'name', cannot be moved. The expected state was NOT_DEPLOYED but the actual state is 'state'.	VAPP-8
VIRTUAL_APPLIANCE	MOVE	Virtual appliance 'name' cannot be moved. Virtual appliance contains captured virtual machine(s).	VAPP-9
VIRTUAL_APPLIANCE	MOVE	Virtual appliance 'VAPP_ORIGINAL_NAME' successfully moved from virtual datacenter 'VDC_ORIGIN' to virtual datacenter 'VDC_DESTINATION' with name 'VAPP_NAME'.
VIRTUAL_APPLIANCE	UNDEPLOY	Virtual appliance 'name' is being undeployed.
VIRTUAL_APPLIANCE	WORKFLOW_DEPLOY_BATCH	Virtual appliance 'name' deploy workflow webhook request for task 'TASK_ID' failed.	WKF-01
VIRTUAL_APPLIANCE	WORKFLOW_DEPLOY_BATCH	Virtual appliance 'name' deploy workflow webhook sent successfully.
VIRTUAL_APPLIANCE	WORKFLOW_UNDEPLOY_BATCH	Virtual appliance 'name' undeploy workflow webhook request for task 'TASK_ID' failed.	WKF-01
VIRTUAL_APPLIANCE	WORKFLOW_UNDEPLOY_BATCH	Virtual appliance 'name' undeploy workflow webhook sent successfully.
Virtual_appliance_spec
VIRTUAL_APPLIANCE_SPEC	MATERIALIZE	Failed to create virtual appliance 'VAPP_NAME'. Error processing task 'TASK_TYPE'. Failed job 'JOB_TYPE'. Error: 'TASK_ERROR'.
VIRTUAL_APPLIANCE_SPEC	MATERIALIZE	Task 'TASK_TYPE' finished successfully. Virtual appliance 'VAPP_NAME' was correctly configured.
VIRTUAL_APPLIANCE_SPEC	ROLLBACK_EXTERNAL_NETWORK	The external VLAN with ID 'EXTERNAL_NET_ID' in datacenter 'DC_NAME' for enterprise 'ENT_NAME' could not be rolled back. Error: 'TASK_ERROR'
VIRTUAL_APPLIANCE_SPEC	ROLLBACK_FIREWALL	The firewall policy with ID 'FIREWALL_ID' in virtual datacenter 'VDC_NAME' could not be rolled back. Error: 'TASK_ERROR'
VIRTUAL_APPLIANCE_SPEC	ROLLBACK_FLOATING_IP	The floating IP 'IP' in virtual datacenter 'VDC_NAME' could not be rolled back. Error: 'TASK_ERROR'
VIRTUAL_APPLIANCE_SPEC	ROLLBACK_LOAD_BALANCER	The load balancer with ID 'LOAD_BALANCER_ID' in virtual datacenter 'VDC_NAME' could not be rolled back. Error: 'TASK_ERROR'
VIRTUAL_APPLIANCE_SPEC	ROLLBACK_PRIVATE_NETWORK	The private VLAN with ID 'PRIVATE_NET_ID' in virtual datacenter 'VDC_NAME' could not be rolled back. Error: 'TASK_ERROR'
VIRTUAL_APPLIANCE_SPEC	ROLLBACK_PUBLIC_IP	The public IP 'IP' in virtual datacenter 'VDC_NAME' could not be rolled back. Error: 'TASK_ERROR'
VIRTUAL_APPLIANCE_SPEC	ROLLBACK_VIRTUAL_MACHINE	The virtual machine with ID 'VIRTUAL_MACHINE_ID' in virtual appliance 'VAPP_NAME' and virtual datacenter 'VDC_NAME' could not be rolled back. Error: 'TASK_ERROR'
VIRTUAL_APPLIANCE_SPEC	ROLLBACK_VOLUME	The volume with ID 'VOLUME_ID' in virtual datacenter 'VDC_NAME' could not be rolled back. Error: 'TASK_ERROR'
Virtual_image_conversion
VIRTUAL_IMAGE_CONVERSION	CONVERSION_INSTANCE_FINISH	Failed to create conversion of instance template 'TEMPLATE_NAME'.	JOB-2
VIRTUAL_IMAGE_CONVERSION	CONVERSION_INSTANCE_FINISH	Failed to create conversion of instance template 'TEMPLATE_NAME'.
VIRTUAL_IMAGE_CONVERSION	CONVERSION_INSTANCE_FINISH	Conversion created of instance template 'TEMPLATE_NAME'.
Virtual_machine
VIRTUAL_MACHINE	ALLOCATE_HD	The hard disk 'HARD_DISK_ID' cannot be attached to controller 'DISK_CONTROLLER', will use 'DISK_CONTROLLER_DEFAULT'.
VIRTUAL_MACHINE	ALLOCATE_HD	The hard disk resource of 'RASD_LIMIT' MB has been assigned to virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	ALLOCATE_NICS	Cannot add more NICs to virtual machine 'VIRTUAL_MACHINE_NAME'. NIC limit: 'NICS_PER_VM', Current NICs: CURRENT_NICS_SIZE, Requested NICs: REQUESTED_NICS_SIZE.	VM-49
VIRTUAL_MACHINE	ALLOCATE_NICS	Virtual machine 'VIRTUAL_MACHINE_NAME' has attached the NIC associated with IP Address 'IP' in VLAN 'VLAN_NAME'.
VIRTUAL_MACHINE	ALLOCATE_VOLUME	Volume 'VOLUME_NAME' of VOLUME_SIZE MB has been attached to virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	ASYNC_HANDLER_RESPONSE	Error processing task 'TASK_TYPE' in handler 'HANDLER_NAME'. Error: 'EXCEPTION_CLASS': 'TASK_ERROR'.	JOB-1
VIRTUAL_MACHINE	CHEF_CONNECT	Could not connect to the Chef server at 'CONNECTION_ENDPOINT' as 'CONNECTION_IDENTITY' to perform the request. Please check that the client has the appropriate permissions to perform the task.	CHEF-14
VIRTUAL_MACHINE	CHEF_CONNECT	Could not connect to the Chef server at 'CONNECTION_ENDPOINT'. Please check that the Chef server is running.	CHEF-6
VIRTUAL_MACHINE	CHEF_RUNLIST_DELETE	Removed run list element 'RUN_LIST_ELEMENT' because it no longer exists on the Chef Server.
VIRTUAL_MACHINE	CHEF_RUNLIST_UPDATE	The node does not exist on the Chef Server. If the virtual machine is bootstrapping, please wait until the process completes.
VIRTUAL_MACHINE	CLONE	Unable to clone virtual machine 'VIRTUAL_MACHINE_NAME' from virtual appliance 'VAPP_NAME': MESSAGE.
VIRTUAL_MACHINE	CLONE	The virtual machine 'name' from virtual appliance 'VAPP_NAME' was cloned successfully as virtual machine 'VIRTUAL_MACHINE_NAME'
VIRTUAL_MACHINE	CREATE	The virtual machine 'name' was created successfully.
VIRTUAL_MACHINE	DEALLOCATE_HD	The hard disk resource of HARD_DISK_SIZE MB has been released from virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	DEALLOCATE_NICS	Virtual machine 'VIRTUAL_MACHINE_NAME' has released the NIC associated with IP Address 'IP' in VLAN 'VLAN_NAME'.
VIRTUAL_MACHINE	DEALLOCATE_VOLUME	Volume 'VOLUME_NAME' of VOLUME_SIZE MB has been detached from virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	DEFINITION_SYNCER_CPU_CHANGED	CPU of virtual machine 'VIRTUAL_MACHINE_NAME' has been changed from 'OLD_VALUE' to 'NEW_VALUE'.
VIRTUAL_MACHINE	DEFINITION_SYNCER_DATASTORE_CHANGED	Datastore of virtual machine 'VIRTUAL_MACHINE_NAME' has been changed from 'OLD_VALUE' to 'NEW_VALUE'.
VIRTUAL_MACHINE	DEFINITION_SYNCER_DISK_ADDED	New disk 'DISK_URL' detected and attached to virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	DEFINITION_SYNCER_DISK_REMOVED	Disk 'DISK_URL' detached from virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	DEFINITION_SYNCER_DISK_RESIZE	Disk 'DISK_URL' in virtual machine 'VIRTUAL_MACHINE_NAME' resized from 'HARD_DISK_OLD_SIZE' MB to 'HARD_DISK_SIZE' MB.
VIRTUAL_MACHINE	DEFINITION_SYNCER_FLOATINGIP_ADDED	New floating IP 'IP' detected and attached to virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	DEFINITION_SYNCER_PROFILE_CHANGED	Hardware profile of virtual machine 'VIRTUAL_MACHINE_NAME' has been changed from 'OLD_VALUE' to 'NEW_VALUE'.
VIRTUAL_MACHINE	DEFINITION_SYNCER_RAM_CHANGED	RAM of virtual machine 'VIRTUAL_MACHINE_NAME' has been changed from 'OLD_VALUE' to 'NEW_VALUE'.
VIRTUAL_MACHINE	DEFINITION_SYNCER_VOLUME_ADDED	New volume 'VOLUME_URL' detected and attached to virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	DEFINITION_SYNCER_VOLUME_REMOVED	Volume 'VOLUME_URL' detached from virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	DEFINITION_SYNCER_VOLUME_REPLACED	Volume 'VOLUME_URL' replaced by disk 'DISK_URL' in virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	DELETE	Could not free VLAN network 'VLAN_NAME' from virtual machine 'name' delete.	VLAN-97
VIRTUAL_MACHINE	DELETE	The virtual machine 'VIRTUAL_MACHINE_NAME' was deleted successfully.
VIRTUAL_MACHINE	DEPLOY	The deploy task could not be queued in the virtual factory. RabbitMQ might be down or not properly configured.	TR-DEPLOY-VM
VIRTUAL_MACHINE	DEPLOY	The deploy of the virtual machine 'name' failed: 'EVENT'.	PL-CPROV-14
VIRTUAL_MACHINE	DEPLOY	The deploy of the virtual machine 'name' failed: 'EVENT'.	PL-CPROV-20
VIRTUAL_MACHINE	DEPLOY	The deploy of the virtual machine 'name' failed: 'EVENT'.	PL-CPROV-3
VIRTUAL_MACHINE	DEPLOY	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the virtual machine does not exist on the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-VAL-0
VIRTUAL_MACHINE	DEPLOY	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the virtual machine already exist on the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-VAL-1
VIRTUAL_MACHINE	DEPLOY	The deploy of the virtual machine 'name' failed: 'EVENT'.	PL-VM-01
VIRTUAL_MACHINE	DEPLOY	The virtual machine 'name' definition is invalid. Deploy failed: The supplied Chef attributes are not valid JSON.	CHEF-15
VIRTUAL_MACHINE	DEPLOY	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the IDE controller is full. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-ED-1
VIRTUAL_MACHINE	DEPLOY	There are CANDIDATES_SIZE candidate machines but all are oversubscribed by the current workload rules (RAM and CPU oversubscription or no suitable datastore with enough free space).\nPlease check the workload rules or the physical machine resources.\nVirtual machine requires REQUIREMENTS_CPU CPU – REQUIREMENTS_RAM RAM \nCandidate machines: CANDIDATES_NAMES.	SCH-NOK
VIRTUAL_MACHINE	DEPLOY	The virtual machine is now in state UNKNOWN. Unexpected Error: 'RS_ERROR'.	GEN-14
VIRTUAL_MACHINE	DEPLOY	The requested virtual machine definition cannot be applied by the hypervisor plugin: 'MESSAGE'.	GEN-20
VIRTUAL_MACHINE	DEPLOY	Virtual factory task 'TASK_ID' on virtual machine ID 'TASK_OWNER' ('VIRTUAL_MACHINE_NAME') failed on the platform due to a communication problem with the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN. The platform will perform a check on the hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	HYP-01
VIRTUAL_MACHINE	DEPLOY	The virtual machine 'name' has no owner defined. Could not generate and send the password for the guest operating system.	VM-154
VIRTUAL_MACHINE	DEPLOY	There are not enough resources available in the datacenter. Try again in a few minutes and if the error persists, please contact your System Administrator (Error code: 'CODE').	DC-10
VIRTUAL_MACHINE	DEPLOY	The deploy of the virtual machine 'VIRTUAL_MACHINE_NAME' failed: The port group attached to the virtual switch does not match the expected virtual switch. Error: 'EVENT'.	NET-1
VIRTUAL_MACHINE	DEPLOY	The virtual machine is now in state UNKNOWN. Unexpected Error: 'MESSAGE'.	VM-54
VIRTUAL_MACHINE	DEPLOY	The virtual machine is now in state UNKNOWN. Unexpected Error: 'MESSAGE'.	VM-55
VIRTUAL_MACHINE	DEPLOY	The virtual machine is now in state UNKNOWN. Unexpected Error: 'MESSAGE'.	VM-56
VIRTUAL_MACHINE	DEPLOY	The virtual machine 'name' definition is invalid. Deploy failed: 'EVENT'.	PL-2
VIRTUAL_MACHINE	DEPLOY	The virtual machine 'VIRTUAL_MACHINE_NAME' is now in state UNKNOWN. Unexpected Error: 'MESSAGE'.	500
VIRTUAL_MACHINE	DEPLOY	Could not deploy the virtual machine 'name': 'MESSAGE'.
VIRTUAL_MACHINE	DEPLOY	DHCP configuration for virtual machine 'name' failed: 'EVENT'.	PL-DHCP-0
VIRTUAL_MACHINE	DEPLOY	DHCP configuration for virtual machine 'name' failed: 'EVENT'.	PL-DHCP-1
VIRTUAL_MACHINE	DEPLOY	DHCP configuration for virtual machine 'name' failed: 'EVENT'.	PL-DHCP-2
VIRTUAL_MACHINE	DEPLOY	DHCP configuration for virtual machine 'name' failed: 'EVENT'.	PL-DHCP-3
VIRTUAL_MACHINE	DEPLOY	The virtual machine 'name' has a FQDN defined ('VIRTUAL_MACHINE_FQDN') but the template is not ready to be customized.
VIRTUAL_MACHINE	DEPLOY	The deploy of the virtual machine 'VIRTUAL_MACHINE_NAME' was successfully queued in the virtual factory.
VIRTUAL_MACHINE	DEPLOY FINISH	Deploy (task ID 'TASK_ID') on virtual machine 'VIRTUAL_MACHINE_NAME' failed. The virtual machine is in state NOT_ALLOCATED. On hypervisor 'MACHINE_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	TASK-3
VIRTUAL_MACHINE	DEPLOY FINISH	Deploy of virtual machine ID 'TASK_ID' and owner 'TASK_OWNER_ID' failed on the platform. Aborted the task created at 'TASK_TIMESTAMP'. Failed to set virtual machine state to UNKNOWN.	TASK-4
VIRTUAL_MACHINE	DEPLOY FINISH	Virtual machine deploy task with task ID 'TASK_ID' failed because the VM does not exist in the hypervisor. Setting virtual machine state to UNKNOWN 'name'.	JOB-2
VIRTUAL_MACHINE	DEPLOY FINISH	Deploy on virtual machine 'VIRTUAL_MACHINE_NAME' completed. Scheduled in hypervisor 'MACHINE_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.
VIRTUAL_MACHINE	DEPLOY FREE_RESOURCES	Deploy of virtual machine 'VIRTUAL_MACHINE_NAME' (task 'TASK_ID') could not queue the request to free resources in 'MACHINE_NAME' ('HYPERVISOR_TYPE' at 'HYPERVISOR_IP') . This means that some resources were not properly freed. This might be related to a RabbitMQ malfunction.	TASK-3
VIRTUAL_MACHINE	DEPLOY HA	The deploy task could not be queued in the virtual factory. RabbitMQ might be down or not properly configured.	TR-DEPLOY-VM
VIRTUAL_MACHINE	DEPLOY HA	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the IDE controller is full. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-ED-1
VIRTUAL_MACHINE	DEPLOY HA	Virtual factory task 'TASK_ID' on virtual machine ID 'TASK_OWNER' ('VIRTUAL_MACHINE_NAME') failed on the platform due to a communication problem with the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN. The platform will perform a check on the hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	HYP-01
VIRTUAL_MACHINE	DEPLOY HA	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the virtual machine does not exist on the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	VAL-0
VIRTUAL_MACHINE	DEPLOY HA	Could not deploy the virtual machine 'name' for HA: 'MESSAGE'.
VIRTUAL_MACHINE	GUEST_PASSWORD_EMAIL	The owner of the virtual machine 'VIRTUAL_MACHINE_NAME' does not have the email configured. The email with the password cannot be sent.
VIRTUAL_MACHINE	GUEST_PASSWORD_SMS	The owner of the virtual machine 'VIRTUAL_MACHINE_NAME' does not have the phone number configured. The SMS with the password cannot be sent.
VIRTUAL_MACHINE	GUEST_SETUP	The guest setup mechanism defined in the template is not supported by this hypervisor / cloud provider: 'GUEST_SETUP'. In virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	GUEST_SETUP	Using guest setup : 'GUEST_SETUP' in virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	INITIATOR_MAPPING	Could not add the mappings for virtual machine UUID 'uuid' name 'name'.	VOL-19
VIRTUAL_MACHINE	INSTANCE_CONVERSION_MASTER_START	Failed to queue conversion to master format for the instance of virtual machine 'VIRTUAL_MACHINE_NAME'.	JOB-4
VIRTUAL_MACHINE	INSTANCE_CONVERSION_MASTER_START	Conversion to master format queued for instance template 'TEMPLATE_NAME'.
VIRTUAL_MACHINE	INSTANCE_CONVERSION_START	Failed to queue conversions for the instance template 'TEMPLATE_NAME'.	500
VIRTUAL_MACHINE	INSTANCE_CONVERSION_START	Failed to queue conversions for the instance template 'TEMPLATE_NAME'.
VIRTUAL_MACHINE	INSTANCE_CONVERSION_START	Conversions queued for the instance template 'TEMPLATE_NAME'.
VIRTUAL_MACHINE	INSTANCE_DISK_COPY	Failed to copy disk of virtual machine 'VIRTUAL_MACHINE_NAME'. EVENT.	JOB-2
VIRTUAL_MACHINE	INSTANCE_DISK_COPY	Completed copy of disk of virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	INSTANCE_DUMP_VOLUME	Failed to dump volume for persistent virtual machine 'VIRTUAL_MACHINE_NAME'.	JOB-2
VIRTUAL_MACHINE	INSTANCE_DUMP_VOLUME	Completed dump to volume of persistent virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	INSTANCE_FINISH	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the virtual machine does not exist on the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-VAL-0
VIRTUAL_MACHINE	INSTANCE_FINISH	Virtual factory task 'TASK_OWNER' on virtual machine ID 'TASK_ID' ('VIRTUAL_MACHINE_NAME') failed on the platform due to a communication problem with the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN. The platform will perform a check on the hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	HYP-01
VIRTUAL_MACHINE	INSTANCE_FINISH	Instance (task ID 'TASK_OWNER') failed on virtual machine ID 'TASK_ID' ('VIRTUAL_MACHINE_NAME') on hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	TASK-3
VIRTUAL_MACHINE	INSTANCE_FINISH	Aborted instance (task ID 'TASK_OWNER') of virtual machine ID 'TASK_ID'.	TASK-4
VIRTUAL_MACHINE	INSTANCE_FINISH	Completed instance (task ID 'TASK_OWNER') on virtual machine ID 'TASK_ID' ('VIRTUAL_MACHINE_NAME') on hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.
VIRTUAL_MACHINE	INSTANCE_START	Unexpected error instancing virtual machine 'name'.	500
VIRTUAL_MACHINE	INSTANCE_START	Could not create an instance of the virtual machine 'name': 'MESSAGE'.
VIRTUAL_MACHINE	INSTANCE_TEMPLATE_CREATE	Inserted template 'TEMPLATE_NAME' for the instance of virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	LOCK_DELETE	Delete of the virtual machine 'name' failed due to an invalid state: 'state'.	VM-8
VIRTUAL_MACHINE	LOCK_DEPLOY	The virtual machine 'name' was expected to be in the not allocated state but was 'state'.	VM-7
VIRTUAL_MACHINE	LOCK_RECONFIGURE	Could not reconfigure the virtual machine 'name' : 'MESSAGE'.	VM-13
VIRTUAL_MACHINE	LOCK_UNDEPLOY	The virtual machine 'name' is in a state in which it cannot be undeployed.	VM-12
VIRTUAL_MACHINE	MODIFY	Virtual machine cannot be reconfigured due to unexpected errors. Contact your System Administrator.	VM-59
VIRTUAL_MACHINE	MODIFY	Cannot update the virtual machine because target physical NIC cannot be found. The physical NIC where the virtual NIC with IP 'VNIC_IP' was attached may have been removed directly in the hypervisor 'HYPERVISOR_IP' ('HYPERVISOR_NAME').	VM-66
VIRTUAL_MACHINE	PAUSE	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the virtual machine does not exist on the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-VAL-0
VIRTUAL_MACHINE	PAUSE	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the IDE controller is full. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-ED-1
VIRTUAL_MACHINE	PAUSE	Virtual factory task 'TASK_ID' on virtual machine ID 'TASK_OWNER' ('VIRTUAL_MACHINE_NAME') failed on the platform due to a communication problem with the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN. The platform will perform a check on the hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	HYP-01
VIRTUAL_MACHINE	PAUSE	Could not pause the virtual machine 'name': 'MESSAGE'.
VIRTUAL_MACHINE	POWEROFF	The virtual machine 'name' does not support the power off operation. Error: 'EVENT'.	PL-CPROV-21
VIRTUAL_MACHINE	POWEROFF	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the virtual machine does not exist on the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-VAL-0
VIRTUAL_MACHINE	POWEROFF	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the IDE controller is full. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-ED-1
VIRTUAL_MACHINE	POWEROFF	Virtual factory task 'TASK_ID' on virtual machine ID 'TASK_OWNER' ('VIRTUAL_MACHINE_NAME') failed on the platform due to a communication problem with the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN. The platform will perform a check on the hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	HYP-01
VIRTUAL_MACHINE	POWEROFF	Could not power off the virtual machine 'name': 'MESSAGE'.
VIRTUAL_MACHINE	POWERON	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the virtual machine does not exist on the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-VAL-0
VIRTUAL_MACHINE	POWERON	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the IDE controller is full. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-ED-1
VIRTUAL_MACHINE	POWERON	Virtual factory task 'TASK_ID' on virtual machine ID 'TASK_OWNER' ('VIRTUAL_MACHINE_NAME') failed on the platform due to a communication problem with the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN. The platform will perform a check on the hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	HYP-01
VIRTUAL_MACHINE	POWERON	Could not power on the virtual machine 'name': 'MESSAGE'.
VIRTUAL_MACHINE	RECONFIGURE	Failed to reconfigure the virtual machine 'name'. Cannot move a virtual machine between virtual datacenters while it is deployed.	PL-CPROV-16
VIRTUAL_MACHINE	RECONFIGURE	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the virtual machine does not exist on the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-VAL-0
VIRTUAL_MACHINE	RECONFIGURE	Failed to reconfigure the virtual machine 'name': 'EVENT'.	PL-VM-02
VIRTUAL_MACHINE	RECONFIGURE	Cannot reconfigure the virtual machine 'name' because there are no VLAN tags available.	ALLOC-2
VIRTUAL_MACHINE	RECONFIGURE	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the IDE controller is full. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-ED-1
VIRTUAL_MACHINE	RECONFIGURE	Virtual factory task 'TASK_ID' on virtual machine ID 'TASK_OWNER' ('VIRTUAL_MACHINE_NAME') failed on the platform due to a communication problem with the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN. The platform will perform a check on the hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	HYP-01
VIRTUAL_MACHINE	RECONFIGURE	Reconfigure on virtual machine 'VIRTUAL_MACHINE_NAME' (task 'TASK_ID') could not queue the request to free resources. This means that some resources were not properly freed. This might be related to a RabbitMQ malfunction.	TASK-3
VIRTUAL_MACHINE	RECONFIGURE	Reconfigure (task ID 'TASK_ID') on virtual machine ID 'TASK_OWNER_ID' failed: Updating the virtual machine to state 'VIRTUAL_MACHINE_STATE'.	TASK-4
VIRTUAL_MACHINE	RECONFIGURE	Could not reconfigure the virtual machine 'VIRTUAL_MACHINE_NAME'.
VIRTUAL_MACHINE	RECONFIGURE	Reconfigure (task ID 'TASK_ID') failed on virtual machine 'VIRTUAL_MACHINE_NAME'. The virtual machine is in state OFF. Hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'. Reason: 'MESSAGE'.	TASK-3
VIRTUAL_MACHINE	RECONFIGURE	The Virtual Machine 'name' has two NICs using IPs in the same VLAN. VLAN: 'VLAN_NAME'.
VIRTUAL_MACHINE	RECONFIGURE	The virtual machine 'VIRTUAL_MACHINE_NAME' has been reconfigured successfully. The changes were: CPU CPUs, RAM RAM and CORES_PER_SOCKET cores per socket. EXTRA_RECONFIGURE_MESSAGE.
VIRTUAL_MACHINE	REFRESH	Refresh resources (task ID 'TASK_ID') operation on virtual machine 'VIRTUAL_MACHINE_NAME' failed. On hypervisor 'MACHINE_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	TR-REFRESH-RESOURCES-VM
VIRTUAL_MACHINE	REFRESH	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the virtual machine does not exist on the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-VAL-0
VIRTUAL_MACHINE	REFRESH	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the IDE controller is full. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-ED-1
VIRTUAL_MACHINE	REFRESH	Virtual factory task 'TASK_ID' on virtual machine ID 'TASK_OWNER' ('VIRTUAL_MACHINE_NAME') failed on the platform due to a communication problem with the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN. The platform will perform a check on the hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	HYP-01
VIRTUAL_MACHINE	REFRESH	Could not refresh the virtual machine 'name': 'MESSAGE'.
VIRTUAL_MACHINE	REFRESH RESOURCES	Refresh resources (task ID 'TASK_ID') operation on virtual machine 'VIRTUAL_MACHINE_NAME' failed. On hypervisor 'MACHINE_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.
VIRTUAL_MACHINE	REFRESH RESOURCES	Resources of virtual machine 'name' have been refreshed.
VIRTUAL_MACHINE	REGISTER	Virtual machine 'VIRTUAL_MACHINE_NAME' wasn't registered in the configured devices: 'ERROR_MESSAGE'.	TASK-3
VIRTUAL_MACHINE	REGISTER	Virtual machine 'VIRTUAL_MACHINE_NAME' was registered in the configured devices.
VIRTUAL_MACHINE	REQUEST_ACCESS	User 'USER_NICK' request access to virtual machine 'VIRTUAL_MACHINE_NAME' in enterprise 'ENT_NAME'.
VIRTUAL_MACHINE	RESET	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the virtual machine does not exist on the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-VAL-0
VIRTUAL_MACHINE	RESET	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the IDE controller is full. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-ED-1
VIRTUAL_MACHINE	RESET	Virtual factory task 'TASK_ID' on virtual machine ID 'TASK_OWNER' ('VIRTUAL_MACHINE_NAME') failed on the platform due to a communication problem with the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN. The platform will perform a check on the hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	HYP-01
VIRTUAL_MACHINE	RESET	Could not reset the state of the virtual machine 'name': 'MESSAGE'.
VIRTUAL_MACHINE	RESET	Operation to reset the virtual machine 'VIRTUAL_MACHINE_NAME' queued in the virtual factory successfully. The virtual machine is locked.
VIRTUAL_MACHINE	RESTORE_BACKUP	The task for the restore requested for virtual machine 'VIRTUAL_MACHINE_NAME' has failed with error: TASK_ERROR.
VIRTUAL_MACHINE	RESTORE_BACKUP	Restore requested for backup with ID 'BACKUP_ID' name 'BACKUP_NAME' , date 'BACKUP_DATE', size 'BACKUP_SIZE', type 'BACKUP_TYPE'.
VIRTUAL_MACHINE	RESUME	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the virtual machine does not exist on the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-VAL-0
VIRTUAL_MACHINE	RESUME	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the IDE controller is full. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-ED-1
VIRTUAL_MACHINE	RESUME	Virtual factory task 'TASK_ID' on virtual machine ID 'TASK_OWNER' ('VIRTUAL_MACHINE_NAME') failed on the platform due to a communication problem with the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN. The platform will perform a check on the hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	HYP-01
VIRTUAL_MACHINE	RESUME	Could not resume the virtual machine 'name': 'MESSAGE'.
VIRTUAL_MACHINE	SHUTDOWN	The virtual machine 'name' does not support the shutdown operation. Error: 'EVENT'.	PL-CPROV-21
VIRTUAL_MACHINE	SHUTDOWN	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the virtual machine does not exist on the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-VAL-0
VIRTUAL_MACHINE	SHUTDOWN	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the IDE controller is full. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-ED-1
VIRTUAL_MACHINE	SHUTDOWN	Virtual factory task 'TASK_ID' on virtual machine ID 'TASK_OWNER' ('VIRTUAL_MACHINE_NAME') failed on the platform due to a communication problem with the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN. The platform will perform a check on the hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	HYP-01
VIRTUAL_MACHINE	SHUTDOWN	Could not shut down the virtual machine 'name': 'MESSAGE'.
VIRTUAL_MACHINE	STATE	The operation to apply the state of the virtual machine 'name' failed.
VIRTUAL_MACHINE	STATE	The operation to apply the state of the virtual machine 'name' in the hypervisor was successfully queued in the virtual factory. The virtual machine is now locked.
VIRTUAL_MACHINE	STATE CHANGE	Change state task ID 'TASK_ID' on virtual machine name 'TASK_OWNER' ('VIRTUAL_MACHINE_NAME') failed on hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.
VIRTUAL_MACHINE	STATE CHANGE	Change state task ID 'TASK_ID' on virtual machine name 'TASK_OWNER' ('VIRTUAL_MACHINE_NAME') done on hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.
VIRTUAL_MACHINE	STORE_RUNLIST	The run list for the Chef node 'name' could not be updated. Please verify that the 'abiquo' client on the Chef server has the appropriate permissions to perform this task.	CHEF-5
VIRTUAL_MACHINE	STORE_RUNLIST	The run list for the Chef node 'name' has been updated with RUN_LIST_SIZE recipes.
VIRTUAL_MACHINE	UNDEPLOY	The virtual machine 'name' is now in the UNKNOWN state. Unexpected Error: 'MESSAGE'.	TR-UNDEPLOY-VM
VIRTUAL_MACHINE	UNDEPLOY	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the virtual machine does not exist on the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-VAL-0
VIRTUAL_MACHINE	UNDEPLOY	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the IDE controller is full. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-ED-1
VIRTUAL_MACHINE	UNDEPLOY	The virtual machine is now in state UNKNOWN. Unexpected Error: 'MESSAGE'.	GEN-14
VIRTUAL_MACHINE	UNDEPLOY	Virtual factory task 'TASK_ID' on virtual machine ID 'TASK_OWNER' ('VIRTUAL_MACHINE_NAME') failed on the platform due to a communication problem with the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN. The platform will perform a check on the hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	HYP-01
VIRTUAL_MACHINE	UNDEPLOY	The undeploy operation for virtual machine 'name' could not be queued in the virtual factory.	500
VIRTUAL_MACHINE	UNDEPLOY	Could not undeploy the virtual machine 'name': 'MESSAGE'.
VIRTUAL_MACHINE	UNDEPLOY	The undeploy of the virtual machine 'VIRTUAL_MACHINE_NAME' was successfully queued in the virtual factory.
VIRTUAL_MACHINE	UNDEPLOY FINISH	Undeploy of virtual machine ID 'TASK_ID' and owner 'TASK_OWNER_ID' failed on the platform. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN.	TASK-4
VIRTUAL_MACHINE	UNDEPLOY FINISH	Undeploy of virtual machine ID 'TASK_ID' and owner 'TASK_OWNER_ID' failed on the platform. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN.
VIRTUAL_MACHINE	UNDEPLOY FINISH	The virtual machine 'VIRTUAL_MACHINE_NAME' with task ID 'TASK_ID' was undeployed successfully in the virtual factory on hypervisor 'MACHINE_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.
VIRTUAL_MACHINE	UNDEPLOY HA	The deploy task could not be queued in the virtual factory. RabbitMQ might be down or not properly configured.	TR-UNDEPLOY-VM
VIRTUAL_MACHINE	UNDEPLOY HA	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the virtual machine does not exist on the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-VAL-0
VIRTUAL_MACHINE	UNDEPLOY HA	Virtual factory task on virtual machine ID 'TASK_ID' and owner 'TASK_OWNER' failed on the platform because the IDE controller is full. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine 'VIRTUAL_MACHINE_NAME' state to 'VIRTUAL_MACHINE_STATE'. On hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	PL-ED-1
VIRTUAL_MACHINE	UNDEPLOY HA	Virtual factory task 'TASK_ID' on virtual machine ID 'TASK_OWNER' ('VIRTUAL_MACHINE_NAME') failed on the platform due to a communication problem with the hypervisor. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN. The platform will perform a check on the hypervisor 'HYPERVISOR_NAME' ('HYPERVISOR_TYPE') at IP 'HYPERVISOR_IP'.	HYP-01
VIRTUAL_MACHINE	UNDEPLOY HA	Undeploy of virtual machine ID 'TASK_ID' and owner 'TASK_OWNER_ID' failed on the platform. Finished the task created at 'TASK_TIMESTAMP'.	TASK-3
VIRTUAL_MACHINE	UNDEPLOY HA	Undeploy of virtual machine ID 'TASK_ID' and owner 'TASK_OWNER_ID' failed on the platform. Aborted the task created at 'TASK_TIMESTAMP'. Successfully updated virtual machine state to UNKNOWN.	TASK-4
VIRTUAL_MACHINE	UNDEPLOY HA	Could not undeploy the virtual machine 'name' for HA: 'MESSAGE'.
VIRTUAL_MACHINE	UNDEPLOY HA	The virtual machine 'VIRTUAL_MACHINE_NAME' with taskId 'TASK_ID' was undeployed successfully in the virtual factory. Finished the task created at 'TASK_TIMESTAMP'.
VIRTUAL_MACHINE	UNREGISTER	Virtual machine 'VIRTUAL_MACHINE_NAME' wasn't unregistered from the configured devices: 'ERROR_MESSAGE'.	TASK-3
VIRTUAL_MACHINE	UNREGISTER	Virtual machine 'VIRTUAL_MACHINE_NAME' was unregistered from the configured devices.
VIRTUAL_MACHINE	UPDATE_REGISTER	Virtual machine 'VIRTUAL_MACHINE_NAME' wasn't updated in the configured devices: 'ERROR_MESSAGE'.	TASK-3
VIRTUAL_MACHINE	UPDATE_REGISTER	Virtual machine 'VIRTUAL_MACHINE_NAME' was updated in the configured devices.
VIRTUAL_MACHINE	VALIDATE	Could not validate the virtual machine definition 'name': 'MESSAGE'.
VIRTUAL_MACHINE	WORKFLOW_DEPLOY_SEND	Virtual machine 'name' workflow undeploy webhook request for task 'TASK_ID' failed.	WKF-01
VIRTUAL_MACHINE	WORKFLOW_DEPLOY_SEND	Virtual machine 'name' workflow deploy webhook for task 'TASK_ID' sent successfully.
VIRTUAL_MACHINE	WORKFLOW_RECONFIGURE_SEND	Virtual machine 'name' workflow undeploy webhook request for task 'TASK_ID' failed.	WKF-01
VIRTUAL_MACHINE	WORKFLOW_RECONFIGURE_SEND	Virtual machine 'name' workflow reconfigure webhook for task 'TASK_ID' sent successfully.
VIRTUAL_MACHINE	WORKFLOW_UNDEPLOY_SEND	Virtual machine 'name' workflow undeploy webhook request for task 'TASK_ID' failed.	WKF-01
VIRTUAL_MACHINE	WORKFLOW_UNDEPLOY_SEND	Virtual machine 'name' workflow undeploy webhook for task 'TASK_ID' sent successfully.
Virtual_machine_template
VIRTUAL_MACHINE_TEMPLATE	CREATE_FROM_INST_FINISH	Virtual machine template 'name' is not available in the datacenter repository.	AM-3
VIRTUAL_MACHINE_TEMPLATE	CREATE_FROM_INST_FINISH	Virtual machine template 'name' available in the datacenter repository.
VIRTUAL_MACHINE_TEMPLATE	CREATE_FROM_INST_START	Requested disks 'DISKS_LABEL' from virtual machine template 'VIRTUAL_MACHINE_TEMPLATE_NAME' are not available in datacenter repository because it was not possible to save the associated task (Redis might be down or not configured).	REDIS-0
VIRTUAL_MACHINE_TEMPLATE	CREATE_FROM_INST_START	Requested disks 'DISKS_LABEL' from virtual machine template 'VIRTUAL_MACHINE_TEMPLATE_NAME' are not available in datacenter 'DC_NAME' repository.	AM-3
VIRTUAL_MACHINE_TEMPLATE	CREATE_FROM_INST_START	Requested new disks 'DISKS_LABEL' from virtual machine template 'VIRTUAL_MACHINE_TEMPLATE_NAME' in datacenter repository.
VIRTUAL_MACHINE_TEMPLATE	PERSISTENT_DELETE	Persistent virtual machine template 'VMT_PERSISTENT_NAME' has been deleted.
VIRTUAL_MACHINE_TEMPLATE	PERSISTENT_DUMP_FINISH	Volume dump failed for persistent virtual machine template 'VMT_PERSISTENT_NAME'.	JOB-1
VIRTUAL_MACHINE_TEMPLATE	PERSISTENT_DUMP_FINISH	Volume dump failed for persistent virtual machine template 'VMT_PERSISTENT_NAME'.	JOB-2
VIRTUAL_MACHINE_TEMPLATE	PERSISTENT_DUMP_FINISH	Volume dump successfully completed for persistent virtual machine template 'VMT_PERSISTENT_NAME'.
VIRTUAL_MACHINE_TEMPLATE	PERSISTENT_DUMP_START	Could not get the initiator of the BPM machine: MESSAGE.	PERSISTENT-6
VIRTUAL_MACHINE_TEMPLATE	PERSISTENT_FINISH	Persistent process failed for virtual machine template 'VMT_PERSISTENT_NAME'.
VIRTUAL_MACHINE_TEMPLATE	PERSISTENT_FINISH	Persistent process finished for virtual machine template 'VMT_PERSISTENT_NAME'.
VIRTUAL_MACHINE_TEMPLATE	PERSISTENT_MODIFY	Persistent virtual machine template 'VIRTUAL_MACHINE_TEMPLATE_OLD_NAME' has been updated.
VIRTUAL_MACHINE_TEMPLATE	PERSISTENT_RAW_CREATE	Dumps pending from raw conversion of template 'VMT_MASTER_NAME' have failed.	500
VIRTUAL_MACHINE_TEMPLATE	PERSISTENT_RAW_CREATE	Raw conversion finished successfully for virtual machine template 'VMT_MASTER_NAME'.
VIRTUAL_MACHINE_TEMPLATE	PERSISTENT_START	Persistent process started for template 'VMT_MASTER_NAME' with new name 'VMT_PERSISTENT_NAME'.
VIRTUAL_MACHINE_TEMPLATE	PERSISTENT_TASK_ENQUEUE	Task ID 'TASK_ID' queued successfully in the conversion manager.
VIRTUAL_MACHINE_TEMPLATE	PERSISTENT_VOLUME_ASSIGN	The selected volume is not large enough to hold the persistent virtual machine template.	VOL-1
VIRTUAL_MACHINE_TEMPLATE	PERSISTENT_VOLUME_ASSIGN	Using the selected volume 'VOLUME_NAME' to hold the persistent virtual machine template.
VIRTUAL_MACHINE_TEMPLATE	PERSISTENT_VOLUME_CREATE	Persistent volume created successfully for virtual machine template 'VMT_MASTER_NAME' in virtual datacenter 'VDC_NAME'.
Workload
WORKLOAD	HARD_LIMIT_EXCEEDED	LIMIT_MESSAGE	LIMIT-1
WORKLOAD	HARD_LIMIT_EXCEEDED SYSTEM	LIMIT_MESSAGE	LIMIT-1
WORKLOAD	SOFT_LIMIT_EXCEEDED	LIMIT_MESSAGE
WORKLOAD	SOFT_LIMIT_EXCEEDED SYSTEM	LIMIT_MESSAGE

Table of Contents

maxLevel	5

There is also the Update automatically checkbox. If checked, new events will be automatically added to the list as they arrive. Otherwise, you must refresh the list manually.

Double-click on an event to see the event detail in the panel below the event list

Image Removed

Filtering events

To make it easier to find a specific event, use the filter tool. Click the filter button Image Removed at the top right of Events view. Enter your filter criteria and click Accept. To remove the filter, click Clear at the bottom of the popup.

Basic event filtering

Basic event filtering enables you to filter with the following fields:

Image Removed

Excerpt

The Events view allows users to find out what is happening in Abiquo. To open the Events view, click on the Events icon Image Removed in the main menu bar.

Image Removed

Panel
Privilege: Display all events for current enterprise

Event viewing can be restricted using privileges assigned to user roles. Users can have: no event privileges; the Display all events for current enterprise privilege; or the Display all events privilege. Users with no event privileges will not see the Events icon or the Events window in the Home view.

The default ordinary User and the default Enterprise Admin role have the Display all events for current enterprise. The default Cloud Admin role has the Display all events privilege.

Panel
Privilege: Display all events

If the events you expected to display do not appear in Events view, check with your System Administrator.

The event list

The event list has the following columns:

Column

Description

Source

Shows the system object that is the source of the event or error and its full hierarchy. For example, it could be a MACHINE MODIFY event, where the source is myMachine (the name of the machine) which is part of a rack named myRack which is part of a datacenter named myDatacenter which belongs to the Abiquo enterprise.

Severity

The severity of the event. Can be INFO, WARN or ERROR

Action

The action that generated the event. See Entity and Action Tables

Performed by

The user who performed the Action.

Date/time

The date and time when the event was generated.

User

The user affected by the action

Trace

Additional information about the event. The trace displayed in Events view are documented under Logs in the Troubleshooting section of the Abiquo Administrator's Guide. See Abiquo Logs

Event field	Description
Severity	Pull-down list of Severity types
Action	Pull-down list of Actions from Entity and Action Tables
Performed by	The name of the user who performed the action
Date from	Start date
Date to	End date
Enterprise	Enterprise

Version	Old Version 13	New Version 14
Changes made by	MS	MS
Saved on	Jul 13, 2018	Aug 09, 2018

Page Comparison

Versions Compared

Key

The event list

Filtering events

Basic event filtering

Advanced event filtering

Severity table

Component List

Storage System List

Entity and Action Tables

Disk

Layer

Nat_ip

Nat_rule

Public_cloud_region

Public_ip

Rules

Scheduler

Storage_device

Task

Virtual_appliance

Virtual_appliance_spec

Virtual_image_conversion

Virtual_machine

Virtual_machine_template

Workload

The event list

Filtering events

Basic event filtering

Advanced event filtering

Severity table

Component List

Storage System List

Entity and Action Tables

Disk

Layer

Public_cloud_region

Public_ip

Rules

Scheduler

Storage_device

Task

Virtual_appliance

Virtual_appliance_spec

Virtual_image_conversion

Virtual_machine

Virtual_machine_template

Workload