2 # ============LICENSE_START=======================================================
4 # ================================================================================
5 # Copyright (C) 2017-2018 AT&T Intellectual Property. All rights reserved.
6 # ================================================================================
7 # Copyright (C) 2017 Amdocs
8 # =============================================================================
9 # Licensed under the Apache License, Version 2.0 (the "License");
10 # you may not use this file except in compliance with the License.
11 # You may obtain a copy of the License at
13 # http://www.apache.org/licenses/LICENSE-2.0
15 # Unless required by applicable law or agreed to in writing, software
16 # distributed under the License is distributed on an "AS IS" BASIS,
17 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
18 # See the License for the specific language governing permissions and
19 # limitations under the License.
21 # ============LICENSE_END=========================================================
24 # This property file contains all message definitions used by APPC
26 # Message resources are identified by a key, which is defined in the Msg enumeration. This key is
27 # assigned a value which consists of 4 parts separated by a pipe (|) symbol. These parts are:
29 # 1. The message identifier
30 # 2. The Message text to be formatted and issued to the user
31 # 3. The suggested resolution text, how to fix the problem.
32 # 4. The description text, what is the problem so the user can understand
34 CONFIGURATION_STARTED=APPC0001I|\
35 ECOMP Application Controller (APP-C) initialization started at {0}|\
36 No resolution is required, this is an informational message|\
37 The APP-C component configuration has been started because the component is being \
38 initialized or loaded for the first time, or a new instance of the component is \
39 being created. This message indicates that the component is starting.
41 CONFIGURATION_CLEARED=APPC0002I|\
42 All prior configuration has been cleared|\
43 No resolution is required, this is an informational message|\
44 The APP-C component is being started or restarted and any prior configuration \
45 (if present), is cleared. This is normal.
47 LOADING_CONFIGURATION_OVERRIDES=APPC0003I|\
48 Loading configuration properties from file "{0}"|\
49 No resolution is required, this is an informational message|\
50 This message indicates that the configuration of the APP-C component was located \
51 and is being loaded from the specified file.
53 LOADING_DEFAULTS=APPC0004I|\
54 Configuration defaults loaded from resource file "{0}"|\
55 No resolution is required, this is an informational message|\
56 This is a normal indication that the default configuration settings were loaded \
57 from the resource file. The APP-C components load a default configuration first \
58 so that all configuration values have valid default settings. Any user configuation \
59 that may be specified then overrides these defaults.
61 NO_DEFAULTS_FOUND=APPC0005E|\
62 No default property resource "{0}" was found!|\
63 This is an internal error. Contact support.|\
64 This is an internal error that indicates that the default resource property file \
65 could not be located. This is likely a packaging error and is indicative of \
66 a construction problem. Refer this to development or level 3 support for assistance.
68 PROPERTY_VALUE=APPC0006I|\
69 Property "{0}" ="{1}"|\
70 No resolution is required, this is an informational message|\
71 This message is issued to show the value of configuration properties and is used to \
72 debug start up of the component.
74 NO_OVERRIDE_PROPERTY_FILE_LOADED=APPC0007E|\
75 No configuration file named [{0}] was found on the configuration search path [{1}]. \
76 If a configuration file should have been loaded, check the file name and search \
77 path specified. APPC will proceed using the default values and command-line \
79 If a configuration file was expected, verify the file name and that it exists on \
80 the search path for the configuration properties. The search path defaults to \
81 <em>${user.home},/opt/app/appc/etc,etc,../etc,/etc,.</em> and can be overridden \
82 by specification of the property <em>org.onap.appc.bootstrap.path</em>. The \
83 property file name defaults to <em>appc.properties</em> and can also be \
84 overridden by the <em>org.onap.appc.bootstrap.file</em> property.|\
85 This message indicates that the bootstrap path was searched for the bootstrap \
86 property file (a file that can be supplied to configure APPC) and that no file \
87 with the specified name was found on any of the path elements of the path.
89 SEARCHING_CONFIGURATION_OVERRIDES=APPC0008I|\
90 Searching path "{0}" for configuration settings "{1}"|\
91 No resolution is required|\
92 This message indicates that the specified path is being examined for a configuration \
93 file of the indicated name. The configuration file defaults to <em>appc.properties</em> \
94 but can be overridden by specification of the <em>org.onap.appc.bootstrap.file</em> \
95 property (using a command-line override, for example). This message is intended to \
96 assist in the debugging and analysis of configuration issues where the indicated \
97 file may not be processed or found. The path that is searched is a comma-delimited \
98 list of directories and defaults to <em>${user.home},/opt/app/appc/etc,etc,../etc,/etc,.</em> \
99 but can also be overridden by specification of the <em>org.onap.appc.bootstrap.path</em> \
102 LOADING_APPLICATION_OVERRIDES=APPC0009I|\
103 Loading application-specific override properties|\
104 No resolution required|\
105 This message indicates that the APPC component was invoked as an embedded component \
106 and that the caller has supplied an override property object.
108 NO_APPLICATION_OVERRIDES=APPC0010I|\
109 No application-specific override properties were provided!|\
110 No resolution required|\
111 This message indicates that the APPC component was invoked as an embedded component \
112 and that the caller has supplied an override property object, but that object was \
115 MERGING_SYSTEM_PROPERTIES=APPC0011I|\
116 Merging system properties into configuration|\
117 No resolution is required|\
118 This message indicates that the java virtual machine system properties are being \
119 examined and merged into the APP-C component configuration. This allows for command \
120 line specification of any APP-C configuration property as a standard java define \
121 JVM option (ex: -Dproperty=value).
123 SETTING_SPECIAL_PROPERTY=APPC0012I|\
124 Setting property "{0}={1}" in system properties|\
125 No resolution required.|\
126 This message indicates that the specified property loaded from defaults, property \
127 file overrides, application overrides, or command-line overrides is being placed \
128 in the system (java virtual machine) properties object. Some libraries that may \
129 be integrated with APP-C (for example, DME2 or AFT libraries) may only look for \
130 their properties in the system properties object. This allows those components \
131 to be configured from the APP-C configuration.
133 LOADING_RESOURCE_BUNDLE=APPC0013I|\
134 Loading resource bundle "{0}"|\
135 No resolution required|\
136 This message indicates that the specified resource bundle is being loaded.
138 LOGGING_ALREADY_INITIALIZED=APPC0014W|\
139 Logging has already been initialized, check the container logging definitions to ensure \
140 they represent your desired logging configuration.|\
141 If logging is configured incorrectly, move the definitions to the container or component \
142 that first initialized logging. If they are ok, no resolution is required.|\
143 This message indicates that the logging environment already exists and has been configured.
145 SEARCHING_LOG_CONFIGURATION=APPC0015I|\
146 Searching path "{0}" for log configuration file "{1}"|\
147 No resolution is required|\
148 This message indicates that the APP-C component configuration file specified a logging \
149 configuration file and/or search path and the path is being searched. This is used to \
150 assist in debugging the configuration process.
152 LOADING_DEFAULT_LOG_CONFIGURATION=APPC0016I|\
153 Loading default logging configuration from system resource file "{0}"|\
154 No resolution is required|\
155 A default logging configuration for the component is loaded from system resources to \
156 ensure that a valid logging environment exists. This is a normal message, and will \
157 be followed by APPC0019I if a user-specified logging configuration overrides the \
160 NO_LOG_CONFIGURATION=APPC0017E|\
161 No log configuration could be found or defaulted!|\
162 A valid logging configuration cannot be found, and no default configuration resource \
163 was loaded. This is likely a packaging issue and should be referred to development \
164 or level 3 support for assistance.|\
165 This is an internal error.
167 UNSUPPORTED_LOGGING_FRAMEWORK=APPC0018E|\
168 An unsupported logging framework is bound to SLF4J. Only Logback or Log4J are supported.|\
169 This is a compatibility error with logging frameworks used in the application environment \
170 and should be referred to development or level 3 support for assistance.|\
171 This is an internal error.
173 LOADING_LOG_CONFIGURATION=APPC0019I|\
174 Loading logging configuration from file "{0}"|\
175 No resolution is required|\
176 The specified logging configuration is being loaded.
178 UNKNOWN_PROVIDER=APPC0020E|\
179 Provider {0} cannot be found or cannot be resolved to one of the known providers, [{1}].|\
180 Specify the name of a valid provider. The IAAS adapter contains a set of providers \
181 that are defined. Each of these providers is assigned a logical name. The call \
182 to the IAAS adapter must specify the name of the provider that is desired. This \
183 could be the result of an incorrect call, or the IAAS adapter configuration is \
185 The APP-C IAAS adapter is being called to request a service on a specific provider, but \
186 the name of the provider cannot be found in the list of defined providers. This may \
187 be an error in the directed graph that contains the call to the IAAS adapter, or it \
188 may be an error in the request, or the configuration of the IAAS adapter may need \
191 SERVER_STATE_CHANGE_TIMEOUT=APPC0021E|\
192 Server name "{0}" with id "{1}" in tenant "{2}" and region "{3}" did not change state \
193 within the alloted time. Current state is "{4}" and the desired state(s) are "{5}"|\
194 This is likely a provider issue. If the provider is OpenStack, check the virtual \
195 machine on the horizon dashboard. If the machine is in an invalid state, you may \
196 need to contact Openstack support. The exact mechanisms for recovery of a machine \
197 in an invalid state are varied and will be different from provider to provider.|\
198 This message indicates that the IAAS adapter has performed some requested action \
199 on the specified server (virtual machine) but the server did not enter a valid \
200 state (running, stopped, etc) within the timeout period. The last state (current state) \
201 is shown, as well as the state that was expected. The servers name, UUID, containing \
202 tenant, and region are shown so that the correct provider can be examined.
204 SERVER_DELETED=APPC0022E|\
205 Server name "{0}" with id "{1}" in tenant "{2}" has a state of deleted and cannot be {3}.|\
206 The specified server has been deleted on the provider. This is likely an incorrect \
207 request. Make sure that you are specifying the correct server ID/name, provider, \
208 and region. If the self-link URL is used, make sure that the correct server resource \
209 is specified. If the machine was correct, recreate or rebuild the machine to make \
210 it usable. Correct the request.|\
211 This message indicates that the server specified was found to have been deleted in the \
212 target provider and that the requested action cannot be performed. This may be caused \
215 <li>The UUID of the server is wrong and specifies a machine that no longer exists</li>\
216 <li>The machine was deleted by a different process or request</li>\
217 <li>The wrong provider was requested</li>\
218 <li>The request was out-of-order</li>\
221 UNKNOWN_SERVER_STATE=APPC0023E|\
222 Server name "{0}" with id "{1}" in tenant "{2}" has an unknown state of "{3}".|\
223 Check the machine to determine the state of the machine. Correct that state to a valid \
224 state if possible. This may also be caused by an internal error in the PAL (Provider \
225 Abstraction Layer) used by the IAAS if a new state definition has been added to the \
226 provider (such as a new version or the installation of an unknown or unsupported \
227 extension). If the machine's state is valid, refer this error to development or \
228 level 3 support for assistance.|\
229 This message indicates that a request was made to the IAAS adapter to take some action \
230 on the specified virtual machine, but the machine was found to be in a state that \
231 prevents that action from being performed.
233 COMPONENT_INITIALIZING=APPC0024I|\
234 {0} component {1} is being initialized...|\
235 No resolution needed|\
236 The IAAS adapter is being initialized
238 COMPONENT_INITIALIZED=APPC0025I|\
239 {0} component {1} has completed initialization|\
240 No resolution needed|\
241 The IAAS adapter has been initialized
243 COMPONENT_TERMINATING=APPC0026I|\
244 {0} component {1} is terminating...|\
245 No resolution needed|\
246 The IAAS adapter is being terminated
248 COMPONENT_TERMINATED=APPC0027I|\
249 {0} component {1} has terminated|\
250 No resolution needed|\
251 The IAAS adapter has been terminated
253 IAAS_ADAPTER_UNSUPPORTED_OPERATION=APPC0028E|\
254 Operation {0} is not supported or implemented at this time.|\
255 Change the request to a supported operation|\
256 The IAAS adapter has been requested to perform some operation that it cannot \
257 perform at this time.
259 IAAS_ADAPTER_RPC_CALLED=APPC0029I|\
260 Operation [{0}] called. Input document:\n{1}|\
261 No resolution required|\
262 The IAAS adapter operation indicated was called with the requested input \
265 NO_SERVICE_FOUND=APPC0030E|\
266 Unable to locate the [{0}] service in the OSGi container|\
267 Ensure that the feature containing that service is installed and running|\
268 This indicates that the required feature could not be located
270 CONTEXT_PARAMETERS_DISPLAY=APPC0031I|\
271 Dump of context parameters for module [{0}], RPC [{1}], and version [{2}]|\
272 No resolution required|\
273 The specified RPC is being called and the context properties are being \
274 displayed. This is a debugging message and preceeds the display of \
275 each context property.
277 RESPONSE_PARAMETERS_DISPLAY=APPC0032I|\
278 Response properties from execution of module [{0}], RPC [{1}], and version [{2}] are:|\
279 No resolution required|\
280 The service logic directed graph has been executed and returned the response properties. \
281 This message preceeds the dump of the response properties. It is used for debugging \
282 of service logic and execution problems.
284 NULL_OR_INVALID_ARGUMENT=APPC0033E|\
285 Service {0}:{1} was provided a null (empty) or invalid argument, [{2}] = [{3}]|\
286 This is likely an internal error, refer to support for assistance|\
287 The indicated service was called, but the specified parameter or argument was either \
288 null or empty, or it was invalid. If it has a value, the value is shown. If the \
289 value is null, the value is shown as 'null'.
291 PROCESSING_REQUEST=APPC0034I|\
292 Service {0}:{1} is processing service [{2}] with request id [{3}]|\
293 No resolution required|\
294 The indicated application and RPC is processing the specified service request.
296 INVALID_SERVICE_REQUEST=APPC0035E|\
297 Service {0}:{1} received request for service [{2}] but that service is invalid or unknown.|\
298 Correct the service request, likely a directed graph issue|\
299 The RPC was invoked to process a service request, but the service is not valid.
301 REGISTERING_SERVICE=APPC0036I|\
302 {0} registering service {1} using class {2}|\
303 No resolution required|\
304 The indicated application service is registering itself with the OSGi container using the \
305 indicated java class name.
307 UNREGISTERING_SERVICE=APPC0037I|\
308 {0} unregistering service {1}|\
309 No resolution required|\
310 The application service is being unregistered from the OSGi container services list.
312 LOADING_PROVIDER_DEFINITIONS=APPC0038I|\
313 {0} IAAS Adapter initializing provider {1} as {2}|\
314 No resolution is required|\
315 The IAAS adapter is loading the definition of the specified provider from its \
318 RESTARTING_SERVER=APPC0039I|\
319 {0} IAAS Adapter restart of server requested|\
320 No resolution required|\
321 A graph has invoked the IAAS adapter and has requested the restart of a server. The \
322 properties that govern the request are echoed immediately following this message.
324 REBUILDING_SERVER=APPC0040I|\
325 {0} IAAS Adapter rebuild of server requested|\
326 No resolution required|\
327 A graph has invoked the IAAS adapter and has requested the rebuilding of a server. The \
328 properties that govern the request are echoed immediately following this message.
330 INVALID_SELF_LINK_URL=APPC0041E|\
331 {0} IAAS Adapter cannot perform requested service, VM url [{1}] is invalid|\
332 Correct the call to the adapter with a valid self-link URL|\
333 The IAAS adapter has been called to perform some operation on a virtual machine \
334 but the vm_id of the virtual machine is not valid.
336 SERVER_FOUND=APPC0042I|\
337 Located server {0} on tenant [{1}] and in state [{2}]|\
338 No resolution required|\
339 This message indicates that a service request was made to perform some action on the server \
340 and the indicated server was located on the specified tenant.\
343 STACK_FOUND=APPC0042I|\
344 Located stack {0} on tenant [{1}] and in state [{2}]|\
345 No resolution required|\
346 This message indicates that a service request was made to perform some action on the server \
347 and the indicated server was located on the specified tenant.
351 SERVER_NOT_FOUND=APPC0043E|\
352 No server found in provider with self-link URL [{0}]|\
353 Correct the server URL|\
354 The requested server, identified by its self link URL, could not be found in the provider
356 SERVER_OPERATION_EXCEPTION=APPC0044E|\
357 Exception {0} was caught attempting {1} of server [{2}] on tenant [{3}]|\
358 Contact support for assistance|\
359 An exception was caught while trying to perform the indicated operation on the server. The \
360 exception may yield more information about the cause of the error. This may be because \
361 of access security, or the server is in an invalid state, or any number of reasons. This \
362 message should be referred to support for assistance.
365 STACK_NOT_FOUND=APPC0043E|\
366 No stack found in provider with self-link URL [{0}]|\
367 Correct the server URL|\
368 The requested stack, identified by its self link URL, could not be found in the provider
370 STACK_OPERATION_EXCEPTION=APPC0044E|\
371 Exception {0} was caught attempting {1} of server [{2}] on tenant [{3}]|\
372 Contact support for assistance|\
373 An exception was caught while trying to perform the indicated operation on the stack. The \
374 exception may yield more information about the cause of the error. This may be because \
375 of access security, or the stack is in an invalid state, or any number of reasons. This \
376 message should be referred to support for assistance.
378 MISSING_REQUIRED_PROPERTIES=APPC0045E|\
379 One or more properties for [{0}] are missing, null, or empty. They are:|\
380 A request to execute the adapter indicated was made from a directed graph, but the properties \
381 of the request that are required by the adapter are missing or do not have a value. Correct \
382 the directed graph to supply the missing properties.|\
383 The specified properties for the indicated adapter operation are invalid or missing.
385 SERVER_ERROR_STATE=APPC0046E|\
386 The server [{0}] (id={1}) in tenant {2} is in error state, {3} is not allowed|\
387 Destroy and recreate the instance|\
388 A request to restart or rebuild a server in an error state was received, but those operations \
389 are not allowed on a server in this state. OpenStack only allows a deletion of a server \
390 that is in the error state.
392 IMAGE_NOT_FOUND=APPC0047E|\
393 The image {0} could not be located for {1}.|\
394 The image indicated could not be found. If the operation being requested is a rebuild of \
395 a server, then there is no action that can be taken other than to destroy the server and \
396 rebuild it using an image that exists.|\
397 This is likely caused by an image being deleted after it was used to build a server. If the \
398 request is for a server rebuild, then the image used to create the server was later deleted \
399 and no longer exists. The server cannot be rebuilt, because the image doesnt exist. \
400 The server must be deleted and reconstructed using a valid, existing image.
402 STATE_CHANGE_TIMEOUT=APPC0048E|\
403 Time out waiting for {0} with name {1} (and id {2}) to reach one of {3} states, current state is {4}|\
404 Recover the resource in whatever means is appropriate|\
405 The resource indicated (by name and id) was expected to change it's state (status) to one of the \
406 indicated expected states within a specified timeout but the resource did not complete the \
407 state change. It's current state is also shown. This can be caused by any number of factors \
408 but is normally a problem or conflict within the IaaS provider (OpenStack).
410 STATE_CHANGE_EXCEPTION=APPC0049E|\
411 Exception {0} waiting for {1} with name {2} (and id {3}) to reach one of {4} states, current state is {5}\n\
413 Recover the resource in whatever means is appropriate|\
414 The resource indicated (by name and id) was expected to change it's state (status) to one of the \
415 indicated expected states within a specified timeout but the resource did not complete the \
416 state change. It's current state is also shown. This can be caused by any number of factors \
417 but is normally a problem or conflict within the IaaS provider (OpenStack).
419 STOP_SERVER=APPC0050I|\
420 Server {0} is being stopped...|\
421 No recovery required|\
422 The processing being performed by APPC requires that the indicated server be stopped.
424 START_SERVER=APPC0051I|\
425 Server {0} is being started...|\
426 No recovery required|\
427 The processing being performed by APPC requires that the indicated server be started.
429 RESUME_SERVER=APPC0052I|\
430 Server {0} is being resumed...|\
431 No recovery required|\
432 The processing being performed by APPC requires that the indicated server be resumed from a suspended state.
434 UNPAUSE_SERVER=APPC0053I|\
435 Server {0} is being unpaused...|\
436 No recovery required|\
437 The processing being performed by APPC requires that the indicated server be unpaused from a paused state.
439 CONNECTION_FAILED_RETRY=APPC0054E|\
440 Connection to provider {0} at identity {1} using tenant name {2} (id {3}) failed, reason={4}, \
441 retrying in {5} seconds, attempt {6} of {7}.|\
442 The connection to the provider could not be obtained for the indicated reason. The application \
443 controller will retry the attempt to connect to the provider a maximum number of times. The \
444 message contains the amount of time the system will wait to retry the connection, and the \
445 current attempt and the maximum number of attempts.|\
446 Correct the cause of the connection failure as indicated by the reason.
448 CONNECTION_FAILED=APPC0055E|\
449 Connection to provider {0} at service {1} failed after all retry attempts.|\
450 The connection to the named provider at the indicated service URL cannot be opened. All \
451 retries have been exhausted. The application controller is giving up on the connection and will \
453 Correct the cause of the connection failure as indicated by the reason(s) in previous APPC0054E \
456 STOPPING_SERVER=APPC0056I|\
457 {0} IAAS Adapter stop server requested|\
458 No resolution required|\
459 A graph has invoked the IAAS adapter and has requested the server to be stopped. The \
460 properties that govern the request are echoed immediately following this message.
462 STARTING_SERVER=APPC0057I|\
463 {0} IAAS Adapter start server requested|\
464 No resolution required|\
465 A graph has invoked the IAAS adapter and has requested the server to be start. The \
466 properties that govern the request are echoed immediately following this message.
468 REBUILD_SERVER_FAILED=APPC0057E|\
469 Server {0} (id {1}) failed to rebuild, reason {2}|\
470 The server rebuild failed for the indicated reason. Correct the cause of the failure and \
471 rerun, if applicable.|\
472 The adapter has attempted to rebuild the indicated server but the rebuild request has \
473 been failed by the provider for some reason. The reason returned by the provider is \
474 included in the message.
476 PARAMETER_IS_MISSING=APPC0058E|\
477 Application {0} graph {1} response did not set the {2} parameter. This parameter is \
478 required for synchronization with the controller. Absence of this parameter is assumed \
479 to be a failure. Please correct the DG.|\
480 The indicated directed graph was called from the application controller but when the \
481 graph returned the indicated property was not defined in the return parameters. The \
482 controller requires that property to be defined and set to a value that is used to \
483 inform the controller of the outcome of operations in the graph. Failure to set \
484 the required parameter is assumed to be a failure regardless if the graph actually \
486 Correct the DG to set the specified parameter to a value that is expected and understood \
489 PARAMETER_NOT_NUMERIC=APPC0059E|\
490 Application {0} graph {1} did not set parameter {2} to a valid numeric value ({3}). \
491 Please correct the DG.|\
492 The indicated directed graph was called by the application controller and the graph \
493 did set the specified property, however the property is not a valid numeric \
494 value. The parameter is used to convey a numeric quantity and the controller \
495 cannot convert the value specified to a number. |\
498 DG_FAILED_RESPONSE=APPC0060E|\
499 Application {0} graph {1} completed with failure: error code = {2}, message = {3}|\
500 The directed graph indicated was called by the application controller and when \
501 the graph returned, an error code was set indicating that the graph failed. This \
502 is a message that echoes the results of the graph, and shows the returned error \
504 Correct the cause of the error.
506 EXCEPTION_CALLING_DG=APPC0061E|\
507 Application {0} received exception {1} attempting to call graph {2}, exception \
509 The application controller attempted to call the service logic interpreter (SLI) \
510 to execute the indicated graph, but an exception was caught. The class of the \
511 exception is shown, as is the message associated with the exception. An \
512 abbreviated stack trace is also displayed to provide information as to the \
513 state of the thread at the time of the exception.|\
514 Correct the cause of the exception and rerun.
516 GRAPH_NOT_FOUND=APPC0062E|\
517 Application {0} was unable to locate graph {1}|\
518 The application controller attempted to call the service logic interpreter (SLI) \
519 to execute the specified graph but the graph does not exist in the SLI database.|\
520 Correct the database and install the correct graph.
522 DEBUG_GRAPH_RESPONSE_HEADER=APPC0063D|\
523 Application {0} graph {1} responded with {2} properties|\
524 This is a debugging message that is output immediately after the call to the \
525 directed graph and before any processing is performed to determine the success \
526 or failure of that call. The heading is output prior to dumping all the parameters \
527 that were returned by the graph.|\
528 No recovery action is required.
530 DEBUG_GRAPH_RESPONSE_DETAIL=APPC0064D|\
531 {0}:{1} - {2} = {3}|\
532 This is a debugging message that is output immediately after the call to the \
533 directed graph and before any processing is performed to determine the success \
534 or failure of that call. This message is repeated for each parameter that \
535 exists in the return context from the graph.|\
536 No recovery action is required.
538 INVALID_REQUIRED_PROPERTY=APPC0065E|\
539 Application {0} request "{1}" was supplied a property "{2}" with the value "{3}" \
540 that does not meet the required form(s):|\
541 This message indicates that the specified requested operation was passed the \
542 specific property named and the property value did not meet the expected \
543 format requirements. For example, if the property is expected to be a \
544 numeric quantity and it contains alphabetic characters, or if it is expected \
545 to be a URL and it is not valid. The message also contains a list of one \
546 or more regular expressions that were used to validate the input, and which \
547 supply the syntax required for the property.|\
548 Correct the property and retry.
550 ATTACHINGVOLUME_SERVER=APPC0068I|\
551 {0} IAAS Adapter attaching of volume to server requested|\
552 No resolution required|\
553 A graph has invoked the IAAS adapter and has requested the attaching of volume to server. The \
554 properties that govern the request are echoed immediately following this message.
556 DETTACHINGVOLUME_SERVER=APPC0069I|\
557 {0} IAAS Adapter detaching of volume from server requested|\
558 No resolution required|\
559 A graph has invoked the IAAS adapter and has requested the detaching of volume from server. The \
560 properties that govern the request are echoed immediately following this message.
562 MIGRATING_SERVER=APPC066I|\
563 {0} IAAS Adapter migrate of server requested|\
564 No resolution required|\
565 A graph has invoked the IAAS adapter and has requested the migration of a server. The \
566 properties that govern the request are echoed immediately following this message.
568 EVACUATING_SERVER=APPC0067I|\
569 {0} IAAS Adapter evacuate of server requested|\
570 No resolution required|\
571 A graph has invoked the IAAS adapter and has requested the evacuation of a server. The \
572 properties that govern the request are echoed immediately following this message.
574 MIGRATE_SERVER_FAILED=APPC0068E|\
575 Server {0} (id {1}) failed to migrate during {2} phase, reason {3}|\
576 The server migration failed for the indicated reason. Correct the cause of the failure and \
577 rerun, if applicable.|\
578 The adapter has attempted to migrate the indicated server but the migration request has \
579 been failed by the provider for some reason. The reason returned by the provider is \
580 included in the message.
582 EVACUATE_SERVER_FAILED=APPC0069E|\
583 Server {0} (id {1}) failed to evacuate, reason {2}|\
584 The server evacuation failed for the indicated reason. Correct the cause of the failure and \
585 rerun, if applicable.|\
586 The adapter has attempted to evacuate the indicated server but the evacuation request has \
587 been failed by the provider for some reason. The reason returned by the provider is \
588 included in the message.
590 APPC_TOO_BUSY=APPC0080E|\
591 APP-C instance is too busy|\
592 The APP-C instance handles too many requests and cannot accept new ones as its internal \
593 execution queue is full. The problem can appear when the APP-C instance gets more requests \
594 than it can handle simultaneously.|\
595 Check the server KPIs for possible performance issues (e.g. insufficient memory, \
596 high network latency, slow responsiveness of southbound systems and so on) which can affect \
597 the system throughput.
599 VF_SERVER_BUSY=APPC0081E|\
600 Concurrent access to server "{0}"|\
601 APP-C currently executes a command on the specified server and cannot accept yet another request \
603 Try to resubmit the request at later time.
605 VF_ILLEGAL_COMMAND=APPC0082E|\
606 Server "{0}" does not support command "{1}" in the current state "{2}"|\
607 APP-C cannot perform the requested command on the server in the current state as no state transition \
608 is defined for that.|\
609 Contact support for assistance.
611 VF_UNDEFINED_STATE=APPC0083E|\
612 Server "{0}" cannot handle command "{1}" because of its doubtful state|\
613 The resource has undefined working state as result of abnormal termination of a previous command.|\
614 Recover the resource in whatever means is appropriate.
616 APPC_NO_RESOURCE_FOUND=APPC0084E|\
617 No resource found with ID "{0}" in A&AI system.|\
618 APP-C is unable to resolve the VF details given the instance ID.|\
619 Check whether the resource has been deleted (terminated) before.
621 APPC_EXPIRED_REQUEST=APPC0085E|\
622 The request "{0}" for server "{1}" has exceeded its TTL limit of "{2}" seconds|\
623 The received expired event won't be handled by APP-C instance. Normally the problem might be \
624 related to asynchronous requests arriving to APP-C instance via DMaaP channel.|\
625 Try to submit a new request if still relevant.
627 APPC_WORKFLOW_NOT_FOUND=APPC0086E|\
628 Workflow for vnfType = "{0}" and command = "{1}" not found.|\
629 Unable to retrive Workflow related to mention VNF type and command.|\
630 Check provided VNF and Command details are correct.
632 APPC_INVALID_INPUT=APPC0087E|\
633 Null vnfId and command provided|\
634 Request contains Null vnfId and command|\
635 Provided non-null VNF and Command details.
637 APPC_AUDIT_MSG=APPC0090A|\
638 Operation "{0}" for VNF type "{1}" from Source "{2}" with RequestID "{3}" \
639 was started at "{4}" and ended at "{5}" with status code "{6}"|\
643 AAI_CONNECTION_FAILED=APPC0106E|\
644 APP-C is unable to communicate with A&AI|\
645 Connection to A&AI at service {0} failed after all retry attempts.|\
646 The connection to the A&AI at the indicated service URL cannot be opened. \
647 All retries have been exhausted. APP-C is giving up on the connection and will \
648 reject the operation request.|\
651 AAI_UPDATE_FAILED=APPC0107E|\
652 APP-C is unable to update COMPONENT_ID {0} to {1} for reason {2}|\
653 The update at the end of the operation wasn't performed as a result of \
654 A&AI communication failure or its internal error.|\
657 AAI_GET_DATA_FAILED=APPC0108E|\
658 APP-C is unable to retrieve VF/VFC {0} data for Transaction ID {1} as a \
659 result of A&AI communication failure or its internal error.|\
660 Operation request will be rejected by APP-C|\
663 AAI_CONNECTION_FAILED_RETRY=APPC0105W|\
664 A&AI at identity {0} using VNF_ID {1} failed, reason={2}, retrying in {3} seconds, attempt {4} of {5}.|\
665 The connection to the A&AI could not be obtained for the indicated reason. APP-C will retry to connect \
666 to the A&AI. The message contains the retry delay, the current attempt and the maximum number of attempts.|\
667 Correct the cause of the connection failure as indicated by the reason.
669 AAI_DELETE_FAILED=APPC0114E|\
670 APP-C is unable to delete COMPONENT_ID {0} for reason {1}|\
671 The deletion at the end of the operation wasn't performed as a result of \
672 A&AI communication failure or its internal error.|\
675 AAI_QUERY_FAILED=APPC0115E|\
676 Error Querying AAI with vnfID = {0}|\
677 Querying AAI for the given vnf id returns failure to APPC|\
680 VNF_CONFIGURED=APPC0118I|\
681 VNF {0} is configured|\
682 No resolution is required, this is an informational message|\
683 The VNF configuration has been completed.
685 VNF_CONFIGURATION_STARTED=APPC0116I|\
686 VNF {0} is being configured|\
687 No resolution is required, this is an informational message|\
688 The VNF configuration has been started
690 VNF_CONFIGURATION_FAILED=APPC0119E|\
691 VNF {0} configuration failed for reason {1}|\
692 The configuration operation wasn't performed as a result of VNF communication failure or its internal error.|\
695 VNF_TEST_STARTED=APPC0120I|\
696 VNF {0} is being tested|\
697 No resolution is required, this is an informational message|\
698 The VNF test has been started
700 VNF_TESTED=APPC0121I|\
702 No resolution is required, this is an informational message|\
703 The VNF test has been completed
705 VNF_TEST_FAILED=APPC0122E|\
706 VNF {0} test failed for reason {1}|\
707 The test operation wasn't performed as a result of VNF communication failure or its internal error.|\
710 VNF_NOT_FOUND=APPC0123E|\
711 VNF not found with vnf_id {0}|\
712 The VNF wasn't found for the given vnf-id.|\
715 VNF_HEALTHCECK_FAILED=APPC0124E|\
716 VNF {0} Healthcheck operation failed, reason {1}|\
717 The health check operation wasn't performed as a result of VNF communication failure or its internal error.|\
720 VM_HEALTHCECK_FAILED=APPC0125E|\
721 VM {0} Healthcheck operation failed, reason {1}|\
722 The health check operation wasn't performed as a result of VNF communication failure or its internal error.|\
725 STOP_SERVER_FAILED=APPC0112E|\
726 Server {0} (id {1}) failed to stop during {2} phase, reason {3}|\
727 The server stop failed for the indicated reason. Correct the cause of the failure and \
728 rerun, if applicable.|\
729 The adapter has attempted to stop the indicated server but the stop request has \
730 been failed by the provider for some reason. The reason returned by the provider is \
731 included in the message.
733 TERMINATE_SERVER_FAILED=APPC0113E|\
734 Server {0} (id {1}) failed to terminate during {2} phase, reason {3}|\
735 The server termination failed for the indicated reason. Correct the cause of the failure and \
736 rerun, if applicable.|\
737 The adapter has attempted to terminate the indicated server but the migration request has \
738 been failed by the provider for some reason. The reason returned by the provider is \
739 included in the message.
741 TERMINATE_STACK_FAILED=APPC0113E|\
742 Server {0} (id {1}) failed to terminate during {2} phase, reason {3}|\
743 The server termination failed for the indicated reason. Correct the cause of the failure and \
744 rerun, if applicable.|\
745 The adapter has attempted to terminate the indicated server but the migration request has \
746 been failed by the provider for some reason. The reason returned by the provider is \
747 included in the message.
749 TERMINATING_SERVER=APPC0114I|\
750 {0} IAAS Adapter terminate server requested|\
751 No resolution required|\
752 A graph has invoked the IAAS adapter and has requested the server to be terminated. The \
753 properties that govern the request are echoed immediately following this message.
756 TERMINATING_STACK=APPC0115I|\
757 {0} IAAS Adapter terminate stack requested|\
758 No resolution required|\
759 A graph has invoked the IAAS adapter and has requested the server to be terminated. The \
760 properties that govern the request are echoed immediately following this message.
762 TERMINATE_SERVER=APPC0116I|\
763 Server {0} is being terminated...|\
764 No recovery required|\
765 The processing being performed by APPC requires that the indicated server be terminated.
767 TERMINATE_STACK=APPC0117I|\
768 Stack {0} is being terminated...|\
769 No recovery required|\
770 The processing being performed by APPC requires that the indicated server be terminated.
772 MIGRATE_COMPLETE=APPC0118I|\
773 Migrate {0} finished with status {1}. Start Time: {2}. End Time: {3}. Request ID: {4}. Reason:{5}...|\
774 No resolution is required, this is an informational message|\
775 APP-C Migrate Operation has completed.
777 RESTART_COMPLETE=APPC0119I|\
778 Restart {0} finished with status {1}. Start Time: {2}. End Time: {3}. Request ID: {4}. Reason:{5}...|\
779 No resolution is required, this is an informational message|\
780 APP-C Restart Operation has completed.
782 REBUILD_COMPLETE=APPC0120I|\
783 Rebuild {0} finished with status {1}. Start Time: {2}. End Time: {3}. Request ID: {4}. Reason:{5}...|\
784 No resolution is required, this is an informational message|\
785 APP-C Rebuild Operation has completed.
787 CLOSE_CONTEXT_FAILED=APPC0121E|\
788 Exception {0} was caught attempting to close provider context for {1}.|\
789 Contact support for assistance|\
790 An exception was caught while trying to close the provider context. The \
791 exception may yield more information about the cause of the error. This may be because \
792 of access security, or the server is in an invalid state, or any number of reasons. This \
793 message should be referred to support for assistance.
795 SNAPSHOTING_STACK=APPC0122I|\
796 Stack {0} is being snapshoted...|\
797 No resolution is required|\
800 STACK_SNAPSHOTED==APPC0123I|\
801 Stack {0} snapshoted, snapshot ID = [{1}].|\
802 No resolution is required|\
803 Stack snapshoted successfully.
806 RESTORING_STACK=APPC0124I|\
807 Stack {0} is being restored to snapshot {1}...|\
808 No resolution is required|\
811 STACK_RESTORED=APPC0125I|\
812 Stack {0} is restored to snapshot {1}.|\
813 No resolution is required|\
814 Stack restored successfully.
816 MISSING_PARAMETER_IN_REQUEST=APPC0126E|\
817 Parameter {0} is missing in svc request of {1}.|\
818 Check DG node definition to pass missing parameter's value.|\
819 Node definition in DG missing indicated parameter value or value is incorrect, \
820 check the graph definition.
822 CANNOT_ESTABLISH_CONNECTION=APPC0127E|\
823 Cannot establish connection to server {0} port {1} with user {2}.|\
824 Check server IP, port and user credentials.|\
825 Wrong data sent in request's payload.
828 APPC_METRIC_MSG=APPC0128I|\
829 Operation "{0}" for VNF type "{1}" from Source "{2}" with RequestID "{3}" on "{4}" with action "{5}" \
830 ended in {6} ms with result "{7}"|\
831 No resolution is required, this is an informational message|\
832 This message indicates that the APPC logged some operation to metric
834 SNAPSHOTING_SERVER=APPC0129I|\
835 {0} IAAS Adapter create snapshot of server requested|\
836 No resolution is required, this is an informational message|\
837 This message indicates that a IAAS Adapter create snapshot of server was requested.
839 INPUT_PAYLOAD_PARSING_FAILED = APPC0130E|\
840 Failed to parsing the input payload: {0}|\
841 Please provide correct input string for parsing.|\
844 APPC_EXCEPTION = APPC0132E|\
845 Error occurred for VNF type : {0}, reason {1}|\
846 Runtime exception thrown by APPC.|\
849 SSH_DATA_EXCEPTION = APPC0133E|\
850 SSH Data Exception occurred, reason {0}|\
851 SSH Data exception occurred.|\
854 JSON_PROCESSING_EXCEPTION = APPC0134E|\
855 Json processing exception occurred, reason {0}|\
856 Json processing Exception|\
859 SUCCESS_EVENT_MESSAGE = APPC0136I|\
860 Operation {0} succeed for {1}|\
863 DEPENDENCY_MODEL_NOT_FOUND = APPC0137E|\
864 Dependency model not found for VNF type {0}, reason {1}|\
865 Please provide dependency model|\
868 INVALID_DEPENDENCY_MODEL = APPC0138E|\
869 Invalid Dependency model for VNF Type {0}, reason {1}|\
870 Invalid dependency model found |\
874 FAILURE_RETRIEVE_VNFC_DG = APPC0139E|\
875 Failed to retrieve DG for VNFC Type: {0}|\
876 Failed to retrieve VNFC DG |\
880 SERVER_NETWORK_ERROR=APPC0140E|\
881 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|\
882 Please ensure they are UP and running before requested operation|\
883 It is critical that the VM Server is reachable by the Provider(ex: OpenStack) in order to be able to perform \
884 the requested operation on it.
887 REBUILD_SERVER=APPC0140I|\
888 Server {0} is being rebuilt...|\
889 No recovery required|\
890 The processing being performed by APPC requires that the indicated server be rebuilt.
892 HYPERVISOR_DOWN_ERROR=APPC0141E|\
893 Hypervisor {0} for the Server {1} is either NOT ENABLED, or its status is DOWN or UNKNOWN|\
894 Please ensure the Hypervisor is UP and running before proceeding with the requested operation|\
895 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 \
896 the requested operation on it.
899 HYPERVISOR_STATUS_UKNOWN=APPC0158E|\
900 Unable to determine the status of the Hypervisor for the Server {0} |\
901 Please ensure the userid has privileges enabled to query for the Hypervisor status. |\
902 If you wish to proceed with the requested operation, either obtain the privileges from the Cloud provider, or skip the Hypervisor check and retry the request.
905 HYPERVISOR_NETWORK_ERROR=APPC0142E|\
906 Hypervisor {0} for the Server {1} is NOT Reachable by APPC for initiating the requested operation|\
907 Please ensure the Hypervisor is connected to the network before proceeding with the requested operation|\
908 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 \
909 the requested operation on it.
911 EVACUATE_SERVER_REBUILD_FAILED=APPC0143E|\
912 Server {0} evacuate from host {1} to host {2} failed during the rebuild on host {2}, reason {3}|\
913 The server rebuild after evacuation failed for the indicated reason. Correct the cause of the failure and \
914 run a rebuild, if applicable.|\
915 The adapter has attempted to rebuild after evacuating the indicated server but the rebuild request has \
916 been failed by the provider for some reason. The reason returned by the provider is \
917 included in the message.
919 RESTART_APPLICATION=APPC0144I|\
920 Application on server {0} is being restarted...|\
921 No recovery required|\
922 The processing being performed by APPC requires that the application on the indicated server be restarted.
924 START_APPLICATION=APPC0145I|\
925 Application on server {0} is being started...|\
926 No recovery required|\
927 The processing being performed by APPC requires that the application on the indicated server be started.
929 APPLICATION_RESTART_FAILED=APPC0146E|\
930 Restart application operation failed on server : {0}, reason {1}|\
931 Restart application operation failure.|\
932 Correct the cause of the failure as indicated by the reason.
934 APPLICATION_START_FAILED=APPC0147E|\
935 Start application operation failed on server : {0}, reason {1}|\
936 Start application operation failure.|\
937 Correct the cause of the failure as indicated by the reason.
939 LOOKING_SERVER_UP=APPC0148I|\
940 {0} IAAS Adapter looking up for the server requested|\
941 No resolution is required, this is an informational message|\
942 This message indicates that a IAAS Adapter lookup of server was requested.
944 EVACUATE_SERVER_REBUILD_FAILED=APPC0149E|\
945 Server {0} evacuate from host {1} to host {2} failed during the rebuild on host {2}, reason {3}|\
946 The server rebuild after evacuation failed for the indicated reason. Correct the cause of the failure and \
947 run a rebuild, if applicable.|\
948 The adapter has attempted to rebuild after evacuating the indicated server but the rebuild request has \
949 been failed by the provider for some reason. The reason returned by the provider is \
950 included in the message.
952 APPLICATION_STOP_FAILED=APPC0150E|\
953 Stop application operation failed on server : {0}, reason {1}|\
954 Stop application operation failure.|\
955 Correct the cause of the failure as indicated by the reason.
957 STOP_APPLICATION=APPC0151I|\
958 Application on server {0} is being stopped...|\
959 No recovery required|\
960 The processing being performed by APPC requires that the application on the indicated server be stopped.
962 LCM_OPERATIONS_DISABLED=APPC0152E|\
963 APPC LCM operations have been administratively disabled|\
964 No recovery required|\
965 This is a indication that the APPC LCM operations are disabled.
967 OAM_OPERATION_EXCEPTION=APPC0153E|\
968 Application {0} received exception {1} while attempting to execute oam operation {2}, exception message = {3}|\
969 The application controller attempted to perform an OAM operation \
970 but an exception was caught. The class of the \
971 exception is shown, as is the message associated with the exception. An \
972 abbreviated stack trace is also displayed to provide information as to the \
973 state of the thread at the time of the exception.|\
974 Correct the cause of the exception and rerun.
976 OAM_OPERATION_ENTERING_MAINTENANCE_MODE=APPC0154W|\
977 Application {0} is {1}|\
978 No recovery required|\
979 The APPC will no longer accept new LCM requests. Previously accepted LCM requests will be allowed to complete.
981 OAM_OPERATION_MAINTENANCE_MODE=APPC0155W|\
982 Application {0} is in {1}|\
983 No recovery required|\
984 The APPC is not accepting new LCM requests and all previously accepted LCM requests have completed.
986 OAM_OPERATION_STARTING=APPC0156I|\
987 Application {0} is {1}|\
988 No recovery required|\
989 The APPC has initiated its startup procedure. Its internal components are coming online. Once completed it will start accepting LCM requests.
991 OAM_OPERATION_STARTED=APPC0157I|\
992 Application {0} is {1}|\
993 No recovery required|\
994 The APPC will now accept new LCM requests for processing.
996 INVALID_STATE_TRANSITION=APPC0158E|\
997 A {1} API is not allowed when {0} in the {2} state|\
998 No recovery required|\
999 The Operation requested cannot be performed as per the current state of APPC.
1001 OAM_OPERATION_STOPPING=APPC0159W|\
1002 Application {0} is {1}|\
1003 No recovery required|\
1004 The APPC has initiated its stop procedure. Its internal LCM bundles are stopping.
1006 OAM_OPERATION_STOPPED=APPC0160W|\
1007 Application {0} is {1}|\
1008 No recovery required|\
1009 The APPC LCM bundles have now stopped.
1011 REQUEST_HANDLER_UNAVAILABLE=APPC0161E|\
1012 Application {0} was unable to find the Request Handler service |\
1013 The application controller attempted to get a handle on Request Handler service \
1014 but was unable to locate it in the OSGi Service Registry.|\
1015 Verify if the Request Handler bundle is running.
1017 OAM_OPERATION_RESTARTING=APPC0162W|\
1018 Application {0} is {1}|\
1019 No recovery required|\
1020 The APPC has initiated its restart procedure. Its internal LCM bundles are stopping and will then start again.
1022 OAM_OPERATION_RESTARTED=APPC0163W|\
1023 Application {0} is {1} for restart|\
1024 No recovery required|\
1025 The APPC LCM bundles have been restared (stopped and then started).
1027 OAM_OPERATION_INVALID_INPUT=APPC0162E|\
1029 No recovery required|\
1030 Fix the input parameter and retry.
1032 IAAS_UNSUPPORTED_IDENTITY_SERVICE=APPC0163E|\
1033 Unsupported identity service version, unable to retrieve ServiceCatalog for identity service {0}|\
1034 Verify the identity url provided is correct. Currently supported version of the OpenStack identity servicer\
1035 are v2 and v3. If a support for a new version in required contact development.|\
1036 This message indicates that a request was made to connect to an unsupported version of \
1039 SFTP_TRANSFER_FAILED=APPC0164E|\
1040 Sftp data transfer failed on connection to host {0} with user {1} for {2} operation, reason : {3}|\
1041 Correct the cause of the failure as indicated by the reason and retry.|\
1042 This message indicates that a failure occured during data transfer over sftp connection.\
1043 The reason returned by the target instance is included in the message.
1045 SSH_CONNECTION_TIMEOUT=APPC0165E|\
1046 Ssh session with host {0} has timed out during command {1} execution|\
1047 Check connection to host and validate executed command.|\
1048 The APPC tried to execute ssh command on specified host, and the execution took longer time than expected.
1050 SSH_SESSION_CONFIG_ERROR=APPC0166E|\
1051 Could not configure existing ssh session, reason: {0}|\
1052 Correct the cause of the failure as indicated by the reason.|\
1053 This message indicates that additional configuration for already opened ssh session has failed.\
1054 The reason returned by the session provider is included in the message.
1056 REBOOT_SERVER=APPC0167I|\
1057 {0} IAAS Adapter reboot of server requested|\
1058 No resolution required|\
1059 A graph has invoked the IAAS adapter and has requested the reboot of a server. The \
1060 properties that govern the request are echoed immediately following this message.
1062 IMAGE_SERVICE_FAILED=APPC0157E|\
1063 IAAS Adapter image service fail|\
1064 Connection to provider OpenStackProvider service Image at {0} failed.|\
1065 Correct the cause of the failure as indicated by the reason.