Page History

...

Each entry maps an error message key to a message template.

Error message keys follow a structured, hierarchical naming convention to ensure consistency, readability, and easy discoverability.

The general format is:

<actionable_resource>.<action>.<failing_resource_or_entity>.<cause_and_context>...

Where:

• actionable_resource
  The primary resource or feature being acted upon
  (e.g., vm, volume, network, template)

• action
  The operation being performed
  (e.g., deploy, start, attach, detach, update)

• failing_resource_or_entity
  The resource or entity that caused the failure
  (e.g., serviceoffering, diskoffering, host, cluster, ip)

• cause and context
  The specific reason for the failure
  (e.g., not.found, inactive, invalid, conflict, unsupported)

Templates support placeholder substitution using {{placeholder}} syntax.

...