2 # ============LICENSE_START=======================================================
4 # ================================================================================
5 # Copyright (C) 2017 AT&T Intellectual Property. All rights reserved.
6 # Copyright (C) 2017 Amdocs
7 # ================================================================================
8 # Licensed under the Apache License, Version 2.0 (the "License");
9 # you may not use this file except in compliance with the License.
10 # You may obtain a copy of the License at
12 # http://www.apache.org/licenses/LICENSE-2.0
14 # Unless required by applicable law or agreed to in writing, software
15 # distributed under the License is distributed on an "AS IS" BASIS,
16 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
17 # See the License for the specific language governing permissions and
18 # limitations under the License.
19 # ============LICENSE_END=========================================================
20 # ECOMP is a trademark and service mark of AT&T Intellectual Property.
23 # This property file contains all message definitions used by APPC
25 # Message resources are identified by a key, which is defined in the Msg enumeration. This key is
26 # assigned a value which consists of 4 parts separated by a pipe (|) symbol. These parts are:
28 # 1. The message identifier
29 # 2. The Message text to be formatted and issued to the user
30 # 3. The suggested resolution text, how to fix the problem.
31 # 4. The description text, what is the problem so the user can understand
33 CONFIGURATION_STARTED=APPC0001I|\
34 ECOMP Application Controller (APP-C) initialization started at {0}|\
35 No resolution is required, this is an informational message|\
36 The APP-C component configuration has been started because the component is being \
37 initialized or loaded for the first time, or a new instance of the component is \
38 being created. This message indicates that the component is starting.
40 CONFIGURATION_CLEARED=APPC0002I|\
41 All prior configuration has been cleared|\
42 No resolution is required, this is an informational message|\
43 The APP-C component is being started or restarted and any prior configuration \
44 (if present), is cleared. This is normal.
46 LOADING_CONFIGURATION_OVERRIDES=APPC0003I|\
47 Loading configuration properties from file "{0}"|\
48 No resolution is required, this is an informational message|\
49 This message indicates that the configuration of the APP-C component was located \
50 and is being loaded from the specified file.
52 LOADING_DEFAULTS=APPC0004I|\
53 Configuration defaults loaded from resource file "{0}"|\
54 No resolution is required, this is an informational message|\
55 This is a normal indication that the default configuration settings were loaded \
56 from the resource file. The APP-C components load a default configuration first \
57 so that all configuration values have valid default settings. Any user configuation \
58 that may be specified then overrides these defaults.
60 NO_DEFAULTS_FOUND=APPC0005E|\
61 No default property resource "{0}" was found!|\
62 This is an internal error. Contact support.|\
63 This is an internal error that indicates that the default resource property file \
64 could not be located. This is likely a packaging error and is indicative of \
65 a construction problem. Refer this to development or level 3 support for assistance.
67 PROPERTY_VALUE=APPC0006I|\
68 Property "{0}" ="{1}"|\
69 No resolution is required, this is an informational message|\
70 This message is issued to show the value of configuration properties and is used to \
71 debug start up of the component.
73 NO_OVERRIDE_PROPERTY_FILE_LOADED=APPC0007E|\
74 No configuration file named [{0}] was found on the configuration search path [{1}]. \
75 If a configuration file should have been loaded, check the file name and search \
76 path specified. APPC will proceed using the default values and command-line \
78 If a configuration file was expected, verify the file name and that it exists on \
79 the search path for the configuration properties. The search path defaults to \
80 <em>${user.home},/opt/app/appc/etc,etc,../etc,/etc,.</em> and can be overridden \
81 by specification of the property <em>org.openecomp.appc.bootstrap.path</em>. The \
82 property file name defaults to <em>appc.properties</em> and can also be \
83 overridden by the <em>org.openecomp.appc.bootstrap.file</em> property.|\
84 This message indicates that the bootstrap path was searched for the bootstrap \
85 property file (a file that can be supplied to configure APPC) and that no file \
86 with the specified name was found on any of the path elements of the path.
88 SEARCHING_CONFIGURATION_OVERRIDES=APPC0008I|\
89 Searching path "{0}" for configuration settings "{1}"|\
90 No resolution is required|\
91 This message indicates that the specified path is being examined for a configuration \
92 file of the indicated name. The configuration file defaults to <em>appc.properties</em> \
93 but can be overridden by specification of the <em>org.openecomp.appc.bootstrap.file</em> \
94 property (using a command-line override, for example). This message is intended to \
95 assist in the debugging and analysis of configuration issues where the indicated \
96 file may not be processed or found. The path that is searched is a comma-delimited \
97 list of directories and defaults to <em>${user.home},/opt/app/appc/etc,etc,../etc,/etc,.</em> \
98 but can also be overridden by specification of the <em>org.openecomp.appc.bootstrap.path</em> \
101 LOADING_APPLICATION_OVERRIDES=APPC0009I|\
102 Loading application-specific override properties|\
103 No resolution required|\
104 This message indicates that the APPC component was invoked as an embedded component \
105 and that the caller has supplied an override property object.
107 NO_APPLICATION_OVERRIDES=APPC0010I|\
108 No application-specific override properties were provided!|\
109 No resolution required|\
110 This message indicates that the APPC component was invoked as an embedded component \
111 and that the caller has supplied an override property object, but that object was \
114 MERGING_SYSTEM_PROPERTIES=APPC0011I|\
115 Merging system properties into configuration|\
116 No resolution is required|\
117 This message indicates that the java virtual machine system properties are being \
118 examined and merged into the APP-C component configuration. This allows for command \
119 line specification of any APP-C configuration property as a standard java define \
120 JVM option (ex: -Dproperty=value).
122 SETTING_SPECIAL_PROPERTY=APPC0012I|\
123 Setting property "{0}={1}" in system properties|\
124 No resolution required.|\
125 This message indicates that the specified property loaded from defaults, property \
126 file overrides, application overrides, or command-line overrides is being placed \
127 in the system (java virtual machine) properties object. Some libraries that may \
128 be integrated with APP-C (for example, DME2 or AFT libraries) may only look for \
129 their properties in the system properties object. This allows those components \
130 to be configured from the APP-C configuration.
132 LOADING_RESOURCE_BUNDLE=APPC0013I|\
133 Loading resource bundle "{0}"|\
134 No resolution required|\
135 This message indicates that the specified resource bundle is being loaded.
137 LOGGING_ALREADY_INITIALIZED=APPC0014W|\
138 Logging has already been initialized, check the container logging definitions to ensure \
139 they represent your desired logging configuration.|\
140 If logging is configured incorrectly, move the definitions to the container or component \
141 that first initialized logging. If they are ok, no resolution is required.|\
142 This message indicates that the logging environment already exists and has been configured.
144 SEARCHING_LOG_CONFIGURATION=APPC0015I|\
145 Searching path "{0}" for log configuration file "{1}"|\
146 No resolution is required|\
147 This message indicates that the APP-C component configuration file specified a logging \
148 configuration file and/or search path and the path is being searched. This is used to \
149 assist in debugging the configuration process.
151 LOADING_DEFAULT_LOG_CONFIGURATION=APPC0016I|\
152 Loading default logging configuration from system resource file "{0}"|\
153 No resolution is required|\
154 A default logging configuration for the component is loaded from system resources to \
155 ensure that a valid logging environment exists. This is a normal message, and will \
156 be followed by APPC0019I if a user-specified logging configuration overrides the \
159 NO_LOG_CONFIGURATION=APPC0017E|\
160 No log configuration could be found or defaulted!|\
161 A valid logging configuration cannot be found, and no default configuration resource \
162 was loaded. This is likely a packaging issue and should be referred to development \
163 or level 3 support for assistance.|\
164 This is an internal error.
166 UNSUPPORTED_LOGGING_FRAMEWORK=APPC0018E|\
167 An unsupported logging framework is bound to SLF4J. Only Logback or Log4J are supported.|\
168 This is a compatibility error with logging frameworks used in the application environment \
169 and should be referred to development or level 3 support for assistance.|\
170 This is an internal error.
172 LOADING_LOG_CONFIGURATION=APPC0019I|\
173 Loading logging configuration from file "{0}"|\
174 No resolution is required|\
175 The specified logging configuration is being loaded.
177 UNKNOWN_PROVIDER=APPC0020E|\
178 Provider {0} cannot be found or cannot be resolved to one of the known providers, [{1}].|\
179 Specify the name of a valid provider. The IAAS adapter contains a set of providers \
180 that are defined. Each of these providers is assigned a logical name. The call \
181 to the IAAS adapter must specify the name of the provider that is desired. This \
182 could be the result of an incorrect call, or the IAAS adapter configuration is \
184 The APP-C IAAS adapter is being called to request a service on a specific provider, but \
185 the name of the provider cannot be found in the list of defined providers. This may \
186 be an error in the directed graph that contains the call to the IAAS adapter, or it \
187 may be an error in the request, or the configuration of the IAAS adapter may need \
190 SERVER_STATE_CHANGE_TIMEOUT=APPC0021E|\
191 Server name "{0}" with id "{1}" in tenant "{2}" and region "{3}" did not change state \
192 within the alloted time. Current state is "{4}" and the desired state(s) are "{5}"|\
193 This is likely a provider issue. If the provider is OpenStack, check the virtual \
194 machine on the horizon dashboard. If the machine is in an invalid state, you may \
195 need to contact Openstack support. The exact mechanisms for recovery of a machine \
196 in an invalid state are varied and will be different from provider to provider.|\
197 This message indicates that the IAAS adapter has performed some requested action \
198 on the specified server (virtual machine) but the server did not enter a valid \
199 state (running, stopped, etc) within the timeout period. The last state (current state) \
200 is shown, as well as the state that was expected. The servers name, UUID, containing \
201 tenant, and region are shown so that the correct provider can be examined.
203 SERVER_DELETED=APPC0022E|\
204 Server name "{0}" with id "{1}" in tenant "{2}" has a state of deleted and cannot be {3}.|\
205 The specified server has been deleted on the provider. This is likely an incorrect \
206 request. Make sure that you are specifying the correct server ID/name, provider, \
207 and region. If the self-link URL is used, make sure that the correct server resource \
208 is specified. If the machine was correct, recreate or rebuild the machine to make \
209 it usable. Correct the request.|\
210 This message indicates that the server specified was found to have been deleted in the \
211 target provider and that the requested action cannot be performed. This may be caused \
214 <li>The UUID of the server is wrong and specifies a machine that no longer exists</li>\
215 <li>The machine was deleted by a different process or request</li>\
216 <li>The wrong provider was requested</li>\
217 <li>The request was out-of-order</li>\
220 UNKNOWN_SERVER_STATE=APPC0023E|\
221 Server name "{0}" with id "{1}" in tenant "{2}" has an unknown state of "{3}".|\
222 Check the machine to determine the state of the machine. Correct that state to a valid \
223 state if possible. This may also be caused by an internal error in the PAL (Provider \
224 Abstraction Layer) used by the IAAS if a new state definition has been added to the \
225 provider (such as a new version or the installation of an unknown or unsupported \
226 extension). If the machine's state is valid, refer this error to development or \
227 level 3 support for assistance.|\
228 This message indicates that a request was made to the IAAS adapter to take some action \
229 on the specified virtual machine, but the machine was found to be in a state that \
230 prevents that action from being performed.
232 COMPONENT_INITIALIZING=APPC0024I|\
233 {0} component {1} is being initialized...|\
234 No resolution needed|\
235 The IAAS adapter is being initialized
237 COMPONENT_INITIALIZED=APPC0025I|\
238 {0} component {1} has completed initialization|\
239 No resolution needed|\
240 The IAAS adapter has been initialized
242 COMPONENT_TERMINATING=APPC0026I|\
243 {0} component {1} is terminating...|\
244 No resolution needed|\
245 The IAAS adapter is being terminated
247 COMPONENT_TERMINATED=APPC0027I|\
248 {0} component {1} has terminated|\
249 No resolution needed|\
250 The IAAS adapter has been terminated
252 IAAS_ADAPTER_UNSUPPORTED_OPERATION=APPC0028E|\
253 Operation {0} is not supported or implemented at this time.|\
254 Change the request to a supported operation|\
255 The IAAS adapter has been requested to perform some operation that it cannot \
256 perform at this time.
258 IAAS_ADAPTER_RPC_CALLED=APPC0029I|\
259 Operation [{0}] called. Input document:\n{1}|\
260 No resolution required|\
261 The IAAS adapter operation indicated was called with the requested input \
264 NO_SERVICE_FOUND=APPC0030E|\
265 Unable to locate the [{0}] service in the OSGi container|\
266 Ensure that the feature containing that service is installed and running|\
267 This indicates that the required feature could not be located
269 CONTEXT_PARAMETERS_DISPLAY=APPC0031I|\
270 Dump of context parameters for module [{0}], RPC [{1}], and version [{2}]|\
271 No resolution required|\
272 The specified RPC is being called and the context properties are being \
273 displayed. This is a debugging message and preceeds the display of \
274 each context property.
276 RESPONSE_PARAMETERS_DISPLAY=APPC0032I|\
277 Response properties from execution of module [{0}], RPC [{1}], and version [{2}] are:|\
278 No resolution required|\
279 The service logic directed graph has been executed and returned the response properties. \
280 This message preceeds the dump of the response properties. It is used for debugging \
281 of service logic and execution problems.
283 NULL_OR_INVALID_ARGUMENT=APPC0033E|\
284 Service {0}:{1} was provided a null (empty) or invalid argument, [{2}] = [{3}]|\
285 This is likely an internal error, refer to support for assistance|\
286 The indicated service was called, but the specified parameter or argument was either \
287 null or empty, or it was invalid. If it has a value, the value is shown. If the \
288 value is null, the value is shown as 'null'.
290 PROCESSING_REQUEST=APPC0034I|\
291 Service {0}:{1} is processing service [{2}] with request id [{3}]|\
292 No resolution required|\
293 The indicated application and RPC is processing the specified service request.
295 INVALID_SERVICE_REQUEST=APPC0035E|\
296 Service {0}:{1} received request for service [{2}] but that service is invalid or unknown.|\
297 Correct the service request, likely a directed graph issue|\
298 The RPC was invoked to process a service request, but the service is not valid.
300 REGISTERING_SERVICE=APPC0036I|\
301 {0} registering service {1} using class {2}|\
302 No resolution required|\
303 The indicated application service is registering itself with the OSGi container using the \
304 indicated java class name.
306 UNREGISTERING_SERVICE=APPC0037I|\
307 {0} unregistering service {1}|\
308 No resolution required|\
309 The application service is being unregistered from the OSGi container services list.
311 LOADING_PROVIDER_DEFINITIONS=APPC0038I|\
312 {0} IAAS Adapter initializing provider {1} as {2}|\
313 No resolution is required|\
314 The IAAS adapter is loading the definition of the specified provider from its \
317 RESTARTING_SERVER=APPC0039I|\
318 {0} IAAS Adapter restart of server requested|\
319 No resolution required|\
320 A graph has invoked the IAAS adapter and has requested the restart of a server. The \
321 properties that govern the request are echoed immediately following this message.
323 REBUILDING_SERVER=APPC0040I|\
324 {0} IAAS Adapter rebuild of server requested|\
325 No resolution required|\
326 A graph has invoked the IAAS adapter and has requested the rebuilding of a server. The \
327 properties that govern the request are echoed immediately following this message.
329 INVALID_SELF_LINK_URL=APPC0041E|\
330 {0} IAAS Adapter cannot perform requested service, VM url [{1}] is invalid|\
331 Correct the call to the adapter with a valid self-link URL|\
332 The IAAS adapter has been called to perform some operation on a virtual machine \
333 but the vm_id of the virtual machine is not valid.
335 SERVER_FOUND=APPC0042I|\
336 Located server {0} on tenant [{1}] and in state [{2}]|\
337 No resolution required|\
338 This message indicates that a service request was made to perform some action on the server \
339 and the indicated server was located on the specified tenant.\
342 STACK_FOUND=APPC0042I|\
343 Located stack {0} on tenant [{1}] and in state [{2}]|\
344 No resolution required|\
345 This message indicates that a service request was made to perform some action on the server \
346 and the indicated server was located on the specified tenant.
350 SERVER_NOT_FOUND=APPC0043E|\
351 No server found in provider with self-link URL [{0}]|\
352 Correct the server URL|\
353 The requested server, identified by its self link URL, could not be found in the provider
355 SERVER_OPERATION_EXCEPTION=APPC0044E|\
356 Exception {0} was caught attempting {1} of server [{2}] on tenant [{3}]|\
357 Contact support for assistance|\
358 An exception was caught while trying to perform the indicated operation on the server. The \
359 exception may yield more information about the cause of the error. This may be because \
360 of access security, or the server is in an invalid state, or any number of reasons. This \
361 message should be referred to support for assistance.
364 STACK_NOT_FOUND=APPC0043E|\
365 No stack found in provider with self-link URL [{0}]|\
366 Correct the server URL|\
367 The requested stack, identified by its self link URL, could not be found in the provider
369 STACK_OPERATION_EXCEPTION=APPC0044E|\
370 Exception {0} was caught attempting {1} of server [{2}] on tenant [{3}]|\
371 Contact support for assistance|\
372 An exception was caught while trying to perform the indicated operation on the stack. The \
373 exception may yield more information about the cause of the error. This may be because \
374 of access security, or the stack is in an invalid state, or any number of reasons. This \
375 message should be referred to support for assistance.
377 MISSING_REQUIRED_PROPERTIES=APPC0045E|\
378 One or more properties for [{0}] are missing, null, or empty. They are:|\
379 A request to execute the adapter indicated was made from a directed graph, but the properties \
380 of the request that are required by the adapter are missing or do not have a value. Correct \
381 the directed graph to supply the missing properties.|\
382 The specified properties for the indicated adapter operation are invalid or missing.
384 SERVER_ERROR_STATE=APPC0046E|\
385 The server [{0}] (id={1}) in tenant {2} is in error state, {3} is not allowed|\
386 Destroy and recreate the instance|\
387 A request to restart or rebuild a server in an error state was received, but those operations \
388 are not allowed on a server in this state. OpenStack only allows a deletion of a server \
389 that is in the error state.
391 IMAGE_NOT_FOUND=APPC0047E|\
392 The image {0} could not be located for {1}.|\
393 The image indicated could not be found. If the operation being requested is a rebuild of \
394 a server, then there is no action that can be taken other than to destroy the server and \
395 rebuild it using an image that exists.|\
396 This is likely caused by an image being deleted after it was used to build a server. If the \
397 request is for a server rebuild, then the image used to create the server was later deleted \
398 and no longer exists. The server cannot be rebuilt, because the image doesnt exist. \
399 The server must be deleted and reconstructed using a valid, existing image.
401 STATE_CHANGE_TIMEOUT=APPC0048E|\
402 Time out waiting for {0} with name {1} (and id {2}) to reach one of {3} states, current state is {4}|\
403 Recover the resource in whatever means is appropriate|\
404 The resource indicated (by name and id) was expected to change it's state (status) to one of the \
405 indicated expected states within a specified timeout but the resource did not complete the \
406 state change. It's current state is also shown. This can be caused by any number of factors \
407 but is normally a problem or conflict within the IaaS provider (OpenStack).
409 STATE_CHANGE_EXCEPTION=APPC0049E|\
410 Exception {0} waiting for {1} with name {2} (and id {3}) to reach one of {4} states, current state is {5}\n\
412 Recover the resource in whatever means is appropriate|\
413 The resource indicated (by name and id) was expected to change it's state (status) to one of the \
414 indicated expected states within a specified timeout but the resource did not complete the \
415 state change. It's current state is also shown. This can be caused by any number of factors \
416 but is normally a problem or conflict within the IaaS provider (OpenStack).
418 STOP_SERVER=APPC0050I|\
419 Server {0} is being stopped...|\
420 No recovery required|\
421 The processing being performed by APPC requires that the indicated server be stopped.
423 START_SERVER=APPC0051I|\
424 Server {0} is being started...|\
425 No recovery required|\
426 The processing being performed by APPC requires that the indicated server be started.
428 RESUME_SERVER=APPC0052I|\
429 Server {0} is being resumed...|\
430 No recovery required|\
431 The processing being performed by APPC requires that the indicated server be resumed from a suspended state.
433 UNPAUSE_SERVER=APPC0053I|\
434 Server {0} is being unpaused...|\
435 No recovery required|\
436 The processing being performed by APPC requires that the indicated server be unpaused from a paused state.
438 CONNECTION_FAILED_RETRY=APPC0054E|\
439 Connection to provider {0} at identity {1} using tenant name {2} (id {3}) failed, reason={4}, \
440 retrying in {5} seconds, attempt {6} of {7}.|\
441 The connection to the provider could not be obtained for the indicated reason. The application \
442 controller will retry the attempt to connect to the provider a maximum number of times. The \
443 message contains the amount of time the system will wait to retry the connection, and the \
444 current attempt and the maximum number of attempts.|\
445 Correct the cause of the connection failure as indicated by the reason.
447 CONNECTION_FAILED=APPC0055E|\
448 Connection to provider {0} at service {1} failed after all retry attempts.|\
449 The connection to the named provider at the indicated service URL cannot be opened. All \
450 retries have been exhausted. The application controller is giving up on the connection and will \
452 Correct the cause of the connection failure as indicated by the reason(s) in previous APPC0054E \
455 STOPPING_SERVER=APPC0056I|\
456 {0} IAAS Adapter stop server requested|\
457 No resolution required|\
458 A graph has invoked the IAAS adapter and has requested the server to be stopped. The \
459 properties that govern the request are echoed immediately following this message.
461 REBUILD_SERVER_FAILED=APPC0057E|\
462 Server {0} (id {1}) failed to rebuild, reason {2}|\
463 The server rebuild failed for the indicated reason. Correct the cause of the failure and \
464 rerun, if applicable.|\
465 The adapter has attempted to rebuild the indicated server but the rebuild request has \
466 been failed by the provider for some reason. The reason returned by the provider is \
467 included in the message.
469 PARAMETER_IS_MISSING=APPC0058E|\
470 Application {0} graph {1} response did not set the {2} parameter. This parameter is \
471 required for synchronization with the controller. Absence of this parameter is assumed \
472 to be a failure. Please correct the DG.|\
473 The indicated directed graph was called from the application controller but when the \
474 graph returned the indicated property was not defined in the return parameters. The \
475 controller requires that property to be defined and set to a value that is used to \
476 inform the controller of the outcome of operations in the graph. Failure to set \
477 the required parameter is assumed to be a failure regardless if the graph actually \
479 Correct the DG to set the specified parameter to a value that is expected and understood \
482 PARAMETER_NOT_NUMERIC=APPC0059E|\
483 Application {0} graph {1} did not set parameter {2} to a valid numeric value ({3}). \
484 Please correct the DG.|\
485 The indicated directed graph was called by the application controller and the graph \
486 did set the specified property, however the property is not a valid numeric \
487 value. The parameter is used to convey a numeric quantity and the controller \
488 cannot convert the value specified to a number. |\
491 DG_FAILED_RESPONSE=APPC0060E|\
492 Application {0} graph {1} completed with failure: error code = {2}, message = {3}|\
493 The directed graph indicated was called by the application controller and when \
494 the graph returned, an error code was set indicating that the graph failed. This \
495 is a message that echoes the results of the graph, and shows the returned error \
497 Correct the cause of the error.
499 EXCEPTION_CALLING_DG=APPC0061E|\
500 Application {0} received exception {1} attempting to call graph {2}, exception \
502 The application controller attempted to call the service logic interpreter (SLI) \
503 to execute the indicated graph, but an exception was caught. The class of the \
504 exception is shown, as is the message associated with the exception. An \
505 abbreviated stack trace is also displayed to provide information as to the \
506 state of the thread at the time of the exception.|\
507 Correct the cause of the exception and rerun.
509 GRAPH_NOT_FOUND=APPC0062E|\
510 Application {0} was unable to locate graph {1}|\
511 The application controller attempted to call the service logic interpreter (SLI) \
512 to execute the specified graph but the graph does not exist in the SLI database.|\
513 Correct the database and install the correct graph.
515 DEBUG_GRAPH_RESPONSE_HEADER=APPC0063D|\
516 Application {0} graph {1} responded with {2} properties|\
517 This is a debugging message that is output immediately after the call to the \
518 directed graph and before any processing is performed to determine the success \
519 or failure of that call. The heading is output prior to dumping all the parameters \
520 that were returned by the graph.|\
521 No recovery action is required.
523 DEBUG_GRAPH_RESPONSE_DETAIL=APPC0064D|\
524 {0}:{1} - {2} = {3}|\
525 This is a debugging message that is output immediately after the call to the \
526 directed graph and before any processing is performed to determine the success \
527 or failure of that call. This message is repeated for each parameter that \
528 exists in the return context from the graph.|\
529 No recovery action is required.
531 INVALID_REQUIRED_PROPERTY=APPC0065E|\
532 Application {0} request "{1}" was supplied a property "{2}" with the value "{3}" \
533 that does not meet the required form(s):|\
534 This message indicates that the specified requested operation was passed the \
535 specific property named and the property value did not meet the expected \
536 format requirements. For example, if the property is expected to be a \
537 numeric quantity and it contains alphabetic characters, or if it is expected \
538 to be a URL and it is not valid. The message also contains a list of one \
539 or more regular expressions that were used to validate the input, and which \
540 supply the syntax required for the property.|\
541 Correct the property and retry.
543 MIGRATING_SERVER=APPC066I|\
544 {0} IAAS Adapter migrate of server requested|\
545 No resolution required|\
546 A graph has invoked the IAAS adapter and has requested the migration of a server. The \
547 properties that govern the request are echoed immediately following this message.
549 EVACUATING_SERVER=APPC0067I|\
550 {0} IAAS Adapter evacuate of server requested|\
551 No resolution required|\
552 A graph has invoked the IAAS adapter and has requested the evacuation of a server. The \
553 properties that govern the request are echoed immediately following this message.
555 MIGRATE_SERVER_FAILED=APPC0068E|\
556 Server {0} (id {1}) failed to migrate during {2} phase, reason {3}|\
557 The server migration failed for the indicated reason. Correct the cause of the failure and \
558 rerun, if applicable.|\
559 The adapter has attempted to migrate the indicated server but the migration request has \
560 been failed by the provider for some reason. The reason returned by the provider is \
561 included in the message.
563 EVACUATE_SERVER_FAILED=APPC0069E|\
564 Server {0} (id {1}) failed to evacuate, reason {2}|\
565 The server evacuation failed for the indicated reason. Correct the cause of the failure and \
566 rerun, if applicable.|\
567 The adapter has attempted to evacuate the indicated server but the evacuation request has \
568 been failed by the provider for some reason. The reason returned by the provider is \
569 included in the message.
571 APPC_TOO_BUSY=APPC0080E|\
572 APP-C instance is too busy|\
573 The APP-C instance handles too many requests and cannot accept new ones as its internal \
574 execution queue is full. The problem can appear when the APP-C instance gets more requests \
575 than it can handle simultaneously.|\
576 Check the server KPIs for possible performance issues (e.g. insufficient memory, \
577 high network latency, slow responsiveness of southbound systems and so on) which can affect \
578 the system throughput.
580 VF_SERVER_BUSY=APPC0081E|\
581 Concurrent access to server "{0}"|\
582 APP-C currently executes a command on the specified server and cannot accept yet another request \
584 Try to resubmit the request at later time.
586 VF_ILLEGAL_COMMAND=APPC0082E|\
587 Server "{0}" does not support command "{1}" in the current state "{2}"|\
588 APP-C cannot perform the requested command on the server in the current state as no state transition \
589 is defined for that.|\
590 Contact support for assistance.
592 VF_UNDEFINED_STATE=APPC0083E|\
593 Server "{0}" cannot handle command "{1}" because of its doubtful state|\
594 The resource has undefined working state as result of abnormal termination of a previous command.|\
595 Recover the resource in whatever means is appropriate.
597 APPC_NO_RESOURCE_FOUND=APPC0084E|\
598 No resource found with ID "{0}" in A&AI system.|\
599 APP-C is unable to resolve the VF details given the instance ID.|\
600 Check whether the resource has been deleted (terminated) before.
602 APPC_EXPIRED_REQUEST=APPC0085E|\
603 The request "{0}" for server "{1}" has exceeded its TTL limit of "{2}" seconds|\
604 The received expired event won't be handled by APP-C instance. Normally the problem might be \
605 related to asynchronous requests arriving to APP-C instance via DMaaP channel.|\
606 Try to submit a new request if still relevant.
608 APPC_WORKFLOW_NOT_FOUND=APPC0086E|\
609 Workflow for vnfType = "{0}" and command = "{1}" not found.|\
610 Unable to retrive Workflow related to mention VNF type and command.|\
611 Check provided VNF and Command details are correct.
613 APPC_INVALID_INPUT=APPC0087E|\
614 Null vnfId and command provided|\
615 Request contains Null vnfId and command|\
616 Provided non-null VNF and Command details.
618 APPC_AUDIT_MSG=APPC0090A|\
619 Operation "{0}" for VNF type "{1}" from Source "{2}" with RequestID "{3}" \
620 was started at "{4}" and ended at "{5}" with status code "{6}"|\
624 AAI_CONNECTION_FAILED=APPC0106E|\
625 APP-C is unable to communicate with A&AI|\
626 Connection to A&AI at service {0} failed after all retry attempts.|\
627 The connection to the A&AI at the indicated service URL cannot be opened. \
628 All retries have been exhausted. APP-C is giving up on the connection and will \
629 reject the operation request.|\
632 AAI_UPDATE_FAILED=APPC0107E|\
633 APP-C is unable to update COMPONENT_ID {0} to {1} for reason {2}|\
634 The update at the end of the operation wasn't performed as a result of \
635 A&AI communication failure or its internal error.|\
638 AAI_GET_DATA_FAILED=APPC0108E|\
639 APP-C is unable to retrieve VF/VFC {0} data for Transaction ID {1} as a \
640 result of A&AI communication failure or its internal error.|\
641 Operation request will be rejected by APP-C|\
644 AAI_CONNECTION_FAILED_RETRY=APPC0105W|\
645 A&AI at identity {0} using VNF_ID {1} failed, reason={2}, retrying in {3} seconds, attempt {4} of {5}.|\
646 The connection to the A&AI could not be obtained for the indicated reason. APP-C will retry to connect \
647 to the A&AI. The message contains the retry delay, the current attempt and the maximum number of attempts.|\
648 Correct the cause of the connection failure as indicated by the reason.
650 AAI_DELETE_FAILED=APPC0114E|\
651 APP-C is unable to delete COMPONENT_ID {0} for reason {1}|\
652 The deletion at the end of the operation wasn't performed as a result of \
653 A&AI communication failure or its internal error.|\
656 AAI_QUERY_FAILED=APPC0115E|\
657 Error Querying AAI with vnfID = {0}|\
658 Querying AAI for the given vnf id returns failure to APPC|\
661 VNF_CONFIGURED=APPC0118I|\
662 VNF {0} is configured|\
663 No resolution is required, this is an informational message|\
664 The VNF configuration has been completed.
666 VNF_CONFIGURATION_STARTED=APPC0116I|\
667 VNF {0} is being configured|\
668 No resolution is required, this is an informational message|\
669 The VNF configuration has been started
671 VNF_CONFIGURATION_FAILED=APPC0119E|\
672 VNF {0} configuration failed for reason {1}|\
673 The configuration operation wasn't performed as a result of VNF communication failure or its internal error.|\
676 VNF_TEST_STARTED=APPC0120I|\
677 VNF {0} is being tested|\
678 No resolution is required, this is an informational message|\
679 The VNF test has been started
681 VNF_TESTED=APPC0121I|\
683 No resolution is required, this is an informational message|\
684 The VNF test has been completed
686 VNF_TEST_FAILED=APPC0122E|\
687 VNF {0} test failed for reason {1}|\
688 The test operation wasn't performed as a result of VNF communication failure or its internal error.|\
691 VNF_NOT_FOUND=APPC0123E|\
692 VNF not found with vnf_id {0}|\
693 The VNF wasn't found for the given vnf-id.|\
696 VNF_HEALTHCECK_FAILED=APPC0124E|\
697 VNF {0} Healthcheck operation failed, reason {1}|\
698 The health check operation wasn't performed as a result of VNF communication failure or its internal error.|\
701 VM_HEALTHCECK_FAILED=APPC0125E|\
702 VM {0} Healthcheck operation failed, reason {1}|\
703 The health check operation wasn't performed as a result of VNF communication failure or its internal error.|\
706 STOP_SERVER_FAILED=APPC0112E|\
707 Server {0} (id {1}) failed to stop during {2} phase, reason {3}|\
708 The server stop failed for the indicated reason. Correct the cause of the failure and \
709 rerun, if applicable.|\
710 The adapter has attempted to stop the indicated server but the stop request has \
711 been failed by the provider for some reason. The reason returned by the provider is \
712 included in the message.
714 TERMINATE_SERVER_FAILED=APPC0113E|\
715 Server {0} (id {1}) failed to terminate during {2} phase, reason {3}|\
716 The server termination failed for the indicated reason. Correct the cause of the failure and \
717 rerun, if applicable.|\
718 The adapter has attempted to terminate the indicated server but the migration request has \
719 been failed by the provider for some reason. The reason returned by the provider is \
720 included in the message.
722 TERMINATE_STACK_FAILED=APPC0113E|\
723 Server {0} (id {1}) failed to terminate during {2} phase, reason {3}|\
724 The server termination failed for the indicated reason. Correct the cause of the failure and \
725 rerun, if applicable.|\
726 The adapter has attempted to terminate the indicated server but the migration request has \
727 been failed by the provider for some reason. The reason returned by the provider is \
728 included in the message.
730 TERMINATING_SERVER=APPC0114I|\
731 {0} IAAS Adapter terminate server requested|\
732 No resolution required|\
733 A graph has invoked the IAAS adapter and has requested the server to be terminated. The \
734 properties that govern the request are echoed immediately following this message.
737 TERMINATING_STACK=APPC0115I|\
738 {0} IAAS Adapter terminate stack requested|\
739 No resolution required|\
740 A graph has invoked the IAAS adapter and has requested the server to be terminated. The \
741 properties that govern the request are echoed immediately following this message.
743 TERMINATE_SERVER=APPC0116I|\
744 Server {0} is being terminated...|\
745 No recovery required|\
746 The processing being performed by APPC requires that the indicated server be terminated.
748 TERMINATE_STACK=APPC0117I|\
749 Stack {0} is being terminated...|\
750 No recovery required|\
751 The processing being performed by APPC requires that the indicated server be terminated.
753 MIGRATE_COMPLETE=APPC0118I|\
754 Migrate {0} finished with status {1}. Start Time: {2}. End Time: {3}. Request ID: {4}. Reason:{5}...|\
755 No resolution is required, this is an informational message|\
756 APP-C Migrate Operation has completed.
758 RESTART_COMPLETE=APPC0119I|\
759 Restart {0} finished with status {1}. Start Time: {2}. End Time: {3}. Request ID: {4}. Reason:{5}...|\
760 No resolution is required, this is an informational message|\
761 APP-C Restart Operation has completed.
763 REBUILD_COMPLETE=APPC0120I|\
764 Rebuild {0} finished with status {1}. Start Time: {2}. End Time: {3}. Request ID: {4}. Reason:{5}...|\
765 No resolution is required, this is an informational message|\
766 APP-C Rebuild Operation has completed.
768 CLOSE_CONTEXT_FAILED=APPC0121E|\
769 Exception {0} was caught attempting to close provider context for {1}.|\
770 Contact support for assistance|\
771 An exception was caught while trying to close the provider context. The \
772 exception may yield more information about the cause of the error. This may be because \
773 of access security, or the server is in an invalid state, or any number of reasons. This \
774 message should be referred to support for assistance.
776 SNAPSHOTING_STACK=APPC0122I|\
777 Stack {0} is being snapshoted...|\
778 No resolution is required|\
781 STACK_SNAPSHOTED==APPC0123I|\
782 Stack {0} snapshoted, snapshot ID = [{1}].|\
783 No resolution is required|\
784 Stack snapshoted successfully.
787 RESTORING_STACK=APPC0124I|\
788 Stack {0} is being restored to snapshot {1}...|\
789 No resolution is required|\
792 STACK_RESTORED=APPC0125I|\
793 Stack {0} is restored to snapshot {1}.|\
794 No resolution is required|\
795 Stack restored successfully.
797 MISSING_PARAMETER_IN_REQUEST=APPC0126E|\
798 Parameter {0} is missing in svc request of {1}.|\
799 Check DG node definition to pass missing parameter's value.|\
800 Node definition in DG missing indicated parameter value or value is incorrect, \
801 check the graph definition.
803 CANNOT_ESTABLISH_CONNECTION=APPC0127E|\
804 Cannot establish connection to server {0} port {1} with user {2}.|\
805 Check server IP, port and user credentials.|\
806 Wrong data sent in request's payload.
809 APPC_METRIC_MSG=APPC0128I|\
810 Operation "{0}" for VNF type "{1}" from Source "{2}" with RequestID "{3}" on "{4}" with action "{5}" \
811 ended in {6} ms with result "{7}"|\
812 No resolution is required, this is an informational message|\
813 This message indicates that the APPC logged some operation to metric
815 SNAPSHOTING_SERVER=APPC0129I|\
816 {0} IAAS Adapter create snapshot of server requested|\
817 No resolution is required, this is an informational message|\
818 This message indicates that a IAAS Adapter create snapshot of server was requested.
820 INPUT_PAYLOAD_PARSING_FAILED = APPC0130E|\
821 Failed to parsing the input payload: {0}|\
822 Please provide correct input string for parsing.|\
825 APPC_EXCEPTION = APPC0132E|\
826 Error occurred for VNF type : {0}, reason {1}|\
827 Runtime exception thrown by APPC.|\
830 SSH_DATA_EXCEPTION = APPC0133E|\
831 SSH Data Exception occurred, reason {0}|\
832 SSH Data exception occurred.|\
835 JSON_PROCESSING_EXCEPTION = APPC0134E|\
836 Json processing exception occurred, reason {0}|\
837 Json processing Exception|\
840 SUCCESS_EVENT_MESSAGE = APPC0136I|\
841 Operation {0} succeed for {1}|\
844 DEPENDENCY_MODEL_NOT_FOUND = APPC0137E|\
845 Dependency model not found for VNF type {0}, reason {1}|\
846 Please provide dependency model|\
849 INVALID_DEPENDENCY_MODEL = APPC0138E|\
850 Invalid Dependency model for VNF Type {0}, reason {1}|\
851 Invalid dependency model found |\
855 FAILURE_RETRIEVE_VNFC_DG = APPC0139E|\
856 Failed to retrieve DG for VNFC Type: {0}|\
857 Failed to retrieve VNFC DG |\
861 SERVER_NETWORK_ERROR=APPC0140E|\
862 Server {0} either has a port {1} that is NOT online, or the status of the network to which the port is connected to is not ACTIVE|\
863 Please ensure they are UP and running before requested operation|\
864 It is critical that the VM Server is reachable by the Provider(ex: OpenStack) in order to be able to perform \
865 the requested operation on it.
868 REBUILD_SERVER=APPC0140I|\
869 Server {0} is being rebuilt...|\
870 No recovery required|\
871 The processing being performed by APPC requires that the indicated server be rebuilt.
873 HYPERVISOR_DOWN_ERROR=APPC0141E|\
874 Hypervisor {0} for the Server {1} is either NOT ENABLED, or its status is DOWN or UNKNOWN|\
875 Please ensure the Hypervisor is UP and running before proceeding with the requested operation|\
876 It is critical that the Hypervisor that manages the Virtual Machine for the Server is reachable by the Provider(ex: OpenStack) in order to be able to perform \
877 the requested operation on it.
881 HYPERVISOR_NETWORK_ERROR=APPC0142E|\
882 Hypervisor {0} for the Server {1} is NOT Reachable by APPC for initiating the requested operation|\
883 Please ensure the Hypervisor is connected to the network before proceeding with the requested operation|\
884 It is critical that the Hypervisor that manages the Virtual Machine for the Server is reachable by the Provider(ex: OpenStack) in order to be able to perform \
885 the requested operation on it.
887 EVACUATE_SERVER_REBUILD_FAILED=APPC0143E|\
888 Server {0} evacuate from host {1} to host {2} failed during the rebuild on host {2}, reason {3}|\
889 The server rebuild after evacuation failed for the indicated reason. Correct the cause of the failure and \
890 run a rebuild, if applicable.|\
891 The adapter has attempted to rebuild after evacuating the indicated server but the rebuild request has \
892 been failed by the provider for some reason. The reason returned by the provider is \
893 included in the message.
895 RESTART_APPLICATION=APPC0144I|\
896 Application on server {0} is being restarted...|\
897 No recovery required|\
898 The processing being performed by APPC requires that the application on the indicated server be restarted.
900 START_APPLICATION=APPC0145I|\
901 Application on server {0} is being started...|\
902 No recovery required|\
903 The processing being performed by APPC requires that the application on the indicated server be started.
905 APPLICATION_RESTART_FAILED=APPC0146E|\
906 Restart application operation failed on server : {0}, reason {1}|\
907 Restart application operation failure.|\
908 Correct the cause of the failure as indicated by the reason.
910 APPLICATION_START_FAILED=APPC0147E|\
911 Start application operation failed on server : {0}, reason {1}|\
912 Start application operation failure.|\
913 Correct the cause of the failure as indicated by the reason.
915 LOOKING_SERVER_UP=APPC0148I|\
916 {0} IAAS Adapter looking up for the server requested|\
917 No resolution is required, this is an informational message|\
918 This message indicates that a IAAS Adapter lookup of server was requested.
920 EVACUATE_SERVER_REBUILD_FAILED=APPC0149E|\
921 Server {0} evacuate from host {1} to host {2} failed during the rebuild on host {2}, reason {3}|\
922 The server rebuild after evacuation failed for the indicated reason. Correct the cause of the failure and \
923 run a rebuild, if applicable.|\
924 The adapter has attempted to rebuild after evacuating the indicated server but the rebuild request has \
925 been failed by the provider for some reason. The reason returned by the provider is \
926 included in the message.
928 APPLICATION_STOP_FAILED=APPC0150E|\
929 Stop application operation failed on server : {0}, reason {1}|\
930 Stop application operation failure.|\
931 Correct the cause of the failure as indicated by the reason.
933 STOP_APPLICATION=APPC0151I|\
934 Application on server {0} is being stopped...|\
935 No recovery required|\
936 The processing being performed by APPC requires that the application on the indicated server be stopped.
938 LCM_OPERATIONS_DISABLED=APPC0152E|\
939 APPC LCM operations have been administratively disabled|\
940 No recovery required|\
941 This is a indication that the APPC LCM operations are disabled.
943 OAM_OPERATION_EXCEPTION=APPC0153E|\
944 Application {0} received exception {1} while attempting to execute oam operation {2}, exception message = {3}|\
945 The application controller attempted to perform an OAM operation \
946 but an exception was caught. The class of the \
947 exception is shown, as is the message associated with the exception. An \
948 abbreviated stack trace is also displayed to provide information as to the \
949 state of the thread at the time of the exception.|\
950 Correct the cause of the exception and rerun.
952 OAM_OPERATION_STOPPING=APPC0154W|\
953 Application {0} is stopping... |\
954 No recovery required|\
955 The APPC will no longer accept new LCM requests. Previously accepted LCM requests will be allowed to complete.
957 OAM_OPERATION_STOPPED=APPC0155W|\
958 Application {0} is stopped|\
959 No recovery required|\
960 The APPC is not accepting new LCM requests and all previously accepted LCM requests have completed.
962 OAM_OPERATION_STARTING=APPC0156I|\
963 Application {0} is starting...|\
964 No recovery required|\
965 The APPC has initiated its startup procedure. Its internal components are coming online. Once completed it will start accepting LCM requests. \
967 OAM_OPERATION_STARTED=APPC0157I|\
968 Application {0} is started|\
969 No recovery required|\
970 The APPC will now accept new LCM requests for processing.