2 # ============LICENSE_START=======================================================
4 # ================================================================================
5 # Copyright (C) 2017 AT&T Intellectual Property. All rights
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=========================================================
22 # This property file contains all message definitions used by APPC
24 # Message resources are identified by a key, which is defined in the Msg enumeration. This key is
25 # assigned a value which consists of 4 parts separated by a pipe (|) symbol. These parts are:
27 # 1. The message identifier
28 # 2. The Message text to be formatted and issued to the user
29 # 3. The suggested resolution text, how to fix the problem.
30 # 4. The description text, what is the problem so the user can understand
32 CONFIGURATION_STARTED=APPC0001I|\
33 ECOMP Application Controller (APP-C) initialization started at {0}|\
34 No resolution is required, this is an informational message|\
35 The APP-C component configuration has been started because the component is being \
36 initialized or loaded for the first time, or a new instance of the component is \
37 being created. This message indicates that the component is starting.
39 CONFIGURATION_CLEARED=APPC0002I|\
40 All prior configuration has been cleared|\
41 No resolution is required, this is an informational message|\
42 The APP-C component is being started or restarted and any prior configuration \
43 (if present), is cleared. This is normal.
45 LOADING_CONFIGURATION_OVERRIDES=APPC0003I|\
46 Loading configuration properties from file "{0}"|\
47 No resolution is required, this is an informational message|\
48 This message indicates that the configuration of the APP-C component was located \
49 and is being loaded from the specified file.
51 LOADING_DEFAULTS=APPC0004I|\
52 Configuration defaults loaded from resource file "{0}"|\
53 No resolution is required, this is an informational message|\
54 This is a normal indication that the default configuration settings were loaded \
55 from the resource file. The APP-C components load a default configuration first \
56 so that all configuration values have valid default settings. Any user configuation \
57 that may be specified then overrides these defaults.
59 NO_DEFAULTS_FOUND=APPC0005E|\
60 No default property resource "{0}" was found!|\
61 This is an internal error. Contact support.|\
62 This is an internal error that indicates that the default resource property file \
63 could not be located. This is likely a packaging error and is indicative of \
64 a construction problem. Refer this to development or level 3 support for assistance.
66 PROPERTY_VALUE=APPC0006I|\
67 Property "{0}" ="{1}"|\
68 No resolution is required, this is an informational message|\
69 This message is issued to show the value of configuration properties and is used to \
70 debug start up of the component.
72 NO_OVERRIDE_PROPERTY_FILE_LOADED=APPC0007E|\
73 No configuration file named [{0}] was found on the configuration search path [{1}]. \
74 If a configuration file should have been loaded, check the file name and search \
75 path specified. APPC will proceed using the default values and command-line \
77 If a configuration file was expected, verify the file name and that it exists on \
78 the search path for the configuration properties. The search path defaults to \
79 <em>${user.home},/opt/app/appc/etc,etc,../etc,/etc,.</em> and can be overridden \
80 by specification of the property <em>org.openecomp.appc.bootstrap.path</em>. The \
81 property file name defaults to <em>appc.properties</em> and can also be \
82 overridden by the <em>org.openecomp.appc.bootstrap.file</em> property.|\
83 This message indicates that the bootstrap path was searched for the bootstrap \
84 property file (a file that can be supplied to configure APPC) and that no file \
85 with the specified name was found on any of the path elements of the path.
87 SEARCHING_CONFIGURATION_OVERRIDES=APPC0008I|\
88 Searching path "{0}" for configuration settings "{1}"|\
89 No resolution is required|\
90 This message indicates that the specified path is being examined for a configuration \
91 file of the indicated name. The configuration file defaults to <em>appc.properties</em> \
92 but can be overridden by specification of the <em>org.openecomp.appc.bootstrap.file</em> \
93 property (using a command-line override, for example). This message is intended to \
94 assist in the debugging and analysis of configuration issues where the indicated \
95 file may not be processed or found. The path that is searched is a comma-delimited \
96 list of directories and defaults to <em>${user.home},/opt/app/appc/etc,etc,../etc,/etc,.</em> \
97 but can also be overridden by specification of the <em>org.openecomp.appc.bootstrap.path</em> \
100 LOADING_APPLICATION_OVERRIDES=APPC0009I|\
101 Loading application-specific override properties|\
102 No resolution required|\
103 This message indicates that the APPC component was invoked as an embedded component \
104 and that the caller has supplied an override property object.
106 NO_APPLICATION_OVERRIDES=APPC0010I|\
107 No application-specific override properties were provided!|\
108 No resolution required|\
109 This message indicates that the APPC component was invoked as an embedded component \
110 and that the caller has supplied an override property object, but that object was \
113 MERGING_SYSTEM_PROPERTIES=APPC0011I|\
114 Merging system properties into configuration|\
115 No resolution is required|\
116 This message indicates that the java virtual machine system properties are being \
117 examined and merged into the APP-C component configuration. This allows for command \
118 line specification of any APP-C configuration property as a standard java define \
119 JVM option (ex: -Dproperty=value).
121 SETTING_SPECIAL_PROPERTY=APPC0012I|\
122 Setting property "{0}={1}" in system properties|\
123 No resolution required.|\
124 This message indicates that the specified property loaded from defaults, property \
125 file overrides, application overrides, or command-line overrides is being placed \
126 in the system (java virtual machine) properties object. Some libraries that may \
127 be integrated with APP-C (for example, DME2 or AFT libraries) may only look for \
128 their properties in the system properties object. This allows those components \
129 to be configured from the APP-C configuration.
131 LOADING_RESOURCE_BUNDLE=APPC0013I|\
132 Loading resource bundle "{0}"|\
133 No resolution required|\
134 This message indicates that the specified resource bundle is being loaded.
136 LOGGING_ALREADY_INITIALIZED=APPC0014W|\
137 Logging has already been initialized, check the container logging definitions to ensure \
138 they represent your desired logging configuration.|\
139 If logging is configured incorrectly, move the definitions to the container or component \
140 that first initialized logging. If they are ok, no resolution is required.|\
141 This message indicates that the logging environment already exists and has been configured.
143 SEARCHING_LOG_CONFIGURATION=APPC0015I|\
144 Searching path "{0}" for log configuration file "{1}"|\
145 No resolution is required|\
146 This message indicates that the APP-C component configuration file specified a logging \
147 configuration file and/or search path and the path is being searched. This is used to \
148 assist in debugging the configuration process.
150 LOADING_DEFAULT_LOG_CONFIGURATION=APPC0016I|\
151 Loading default logging configuration from system resource file "{0}"|\
152 No resolution is required|\
153 A default logging configuration for the component is loaded from system resources to \
154 ensure that a valid logging environment exists. This is a normal message, and will \
155 be followed by APPC0019I if a user-specified logging configuration overrides the \
158 NO_LOG_CONFIGURATION=APPC0017E|\
159 No log configuration could be found or defaulted!|\
160 A valid logging configuration cannot be found, and no default configuration resource \
161 was loaded. This is likely a packaging issue and should be referred to development \
162 or level 3 support for assistance.|\
163 This is an internal error.
165 UNSUPPORTED_LOGGING_FRAMEWORK=APPC0018E|\
166 An unsupported logging framework is bound to SLF4J. Only Logback or Log4J are supported.|\
167 This is a compatibility error with logging frameworks used in the application environment \
168 and should be referred to development or level 3 support for assistance.|\
169 This is an internal error.
171 LOADING_LOG_CONFIGURATION=APPC0019I|\
172 Loading logging configuration from file "{0}"|\
173 No resolution is required|\
174 The specified logging configuration is being loaded.
176 UNKNOWN_PROVIDER=APPC0020E|\
177 Provider {0} cannot be found or cannot be resolved to one of the known providers, [{1}].|\
178 Specify the name of a valid provider. The IAAS adapter contains a set of providers \
179 that are defined. Each of these providers is assigned a logical name. The call \
180 to the IAAS adapter must specify the name of the provider that is desired. This \
181 could be the result of an incorrect call, or the IAAS adapter configuration is \
183 The APP-C IAAS adapter is being called to request a service on a specific provider, but \
184 the name of the provider cannot be found in the list of defined providers. This may \
185 be an error in the directed graph that contains the call to the IAAS adapter, or it \
186 may be an error in the request, or the configuration of the IAAS adapter may need \
189 SERVER_STATE_CHANGE_TIMEOUT=APPC0021E|\
190 Server name "{0}" with id "{1}" in tenant "{2}" and region "{3}" did not change state \
191 within the alloted time. Current state is "{4}" and the desired state(s) are "{5}"|\
192 This is likely a provider issue. If the provider is OpenStack, check the virtual \
193 machine on the horizon dashboard. If the machine is in an invalid state, you may \
194 need to contact Openstack support. The exact mechanisms for recovery of a machine \
195 in an invalid state are varied and will be different from provider to provider.|\
196 This message indicates that the IAAS adapter has performed some requested action \
197 on the specified server (virtual machine) but the server did not enter a valid \
198 state (running, stopped, etc) within the timeout period. The last state (current state) \
199 is shown, as well as the state that was expected. The servers name, UUID, containing \
200 tenant, and region are shown so that the correct provider can be examined.
202 SERVER_DELETED=APPC0022E|\
203 Server name "{0}" with id "{1}" in tenant "{2}" has a state of deleted and cannot be {3}.|\
204 The specified server has been deleted on the provider. This is likely an incorrect \
205 request. Make sure that you are specifying the correct server ID/name, provider, \
206 and region. If the self-link URL is used, make sure that the correct server resource \
207 is specified. If the machine was correct, recreate or rebuild the machine to make \
208 it usable. Correct the request.|\
209 This message indicates that the server specified was found to have been deleted in the \
210 target provider and that the requested action cannot be performed. This may be caused \
213 <li>The UUID of the server is wrong and specifies a machine that no longer exists</li>\
214 <li>The machine was deleted by a different process or request</li>\
215 <li>The wrong provider was requested</li>\
216 <li>The request was out-of-order</li>\
219 UNKNOWN_SERVER_STATE=APPC0023E|\
220 Server name "{0}" with id "{1}" in tenant "{2}" has an unknown state of "{3}".|\
221 Check the machine to determine the state of the machine. Correct that state to a valid \
222 state if possible. This may also be caused by an internal error in the PAL (Provider \
223 Abstraction Layer) used by the IAAS if a new state definition has been added to the \
224 provider (such as a new version or the installation of an unknown or unsupported \
225 extension). If the machine's state is valid, refer this error to development or \
226 level 3 support for assistance.|\
227 This message indicates that a request was made to the IAAS adapter to take some action \
228 on the specified virtual machine, but the machine was found to be in a state that \
229 prevents that action from being performed.
231 COMPONENT_INITIALIZING=APPC0024I|\
232 {0} component {1} is being initialized...|\
233 No resolution needed|\
234 The IAAS adapter is being initialized
236 COMPONENT_INITIALIZED=APPC0025I|\
237 {0} component {1} has completed initialization|\
238 No resolution needed|\
239 The IAAS adapter has been initialized
241 COMPONENT_TERMINATING=APPC0026I|\
242 {0} component {1} is terminating...|\
243 No resolution needed|\
244 The IAAS adapter is being terminated
246 COMPONENT_TERMINATED=APPC0027I|\
247 {0} component {1} has terminated|\
248 No resolution needed|\
249 The IAAS adapter has been terminated
251 IAAS_ADAPTER_UNSUPPORTED_OPERATION=APPC0028E|\
252 Operation {0} is not supported or implemented at this time.|\
253 Change the request to a supported operation|\
254 The IAAS adapter has been requested to perform some operation that it cannot \
255 perform at this time.
257 IAAS_ADAPTER_RPC_CALLED=APPC0029I|\
258 Operation [{0}] called. Input document:\n{1}|\
259 No resolution required|\
260 The IAAS adapter operation indicated was called with the requested input \
263 NO_SERVICE_FOUND=APPC0030E|\
264 Unable to locate the [{0}] service in the OSGi container|\
265 Ensure that the feature containing that service is installed and running|\
266 This indicates that the required feature could not be located
268 CONTEXT_PARAMETERS_DISPLAY=APPC0031I|\
269 Dump of context parameters for module [{0}], RPC [{1}], and version [{2}]|\
270 No resolution required|\
271 The specified RPC is being called and the context properties are being \
272 displayed. This is a debugging message and preceeds the display of \
273 each context property.
275 RESPONSE_PARAMETERS_DISPLAY=APPC0032I|\
276 Response properties from execution of module [{0}], RPC [{1}], and version [{2}] are:|\
277 No resolution required|\
278 The service logic directed graph has been executed and returned the response properties. \
279 This message preceeds the dump of the response properties. It is used for debugging \
280 of service logic and execution problems.
282 NULL_OR_INVALID_ARGUMENT=APPC0033E|\
283 Service {0}:{1} was provided a null (empty) or invalid argument, [{2}] = [{3}]|\
284 This is likely an internal error, refer to support for assistance|\
285 The indicated service was called, but the specified parameter or argument was either \
286 null or empty, or it was invalid. If it has a value, the value is shown. If the \
287 value is null, the value is shown as 'null'.
289 PROCESSING_REQUEST=APPC0034I|\
290 Service {0}:{1} is processing service [{2}] with request id [{3}]|\
291 No resolution required|\
292 The indicated application and RPC is processing the specified service request.
294 INVALID_SERVICE_REQUEST=APPC0035E|\
295 Service {0}:{1} received request for service [{2}] but that service is invalid or unknown.|\
296 Correct the service request, likely a directed graph issue|\
297 The RPC was invoked to process a service request, but the service is not valid.
299 REGISTERING_SERVICE=APPC0036I|\
300 {0} registering service {1} using class {2}|\
301 No resolution required|\
302 The indicated application service is registering itself with the OSGi container using the \
303 indicated java class name.
305 UNREGISTERING_SERVICE=APPC0037I|\
306 {0} unregistering service {1}|\
307 No resolution required|\
308 The application service is being unregistered from the OSGi container services list.
310 LOADING_PROVIDER_DEFINITIONS=APPC0038I|\
311 {0} IAAS Adapter initializing provider {1} as {2}|\
312 No resolution is required|\
313 The IAAS adapter is loading the definition of the specified provider from its \
316 RESTARTING_SERVER=APPC0039I|\
317 {0} IAAS Adapter restart of server requested|\
318 No resolution required|\
319 A graph has invoked the IAAS adapter and has requested the restart of a server. The \
320 properties that govern the request are echoed immediately following this message.
322 REBUILDING_SERVER=APPC0040I|\
323 {0} IAAS Adapter rebuild of server requested|\
324 No resolution required|\
325 A graph has invoked the IAAS adapter and has requested the rebuilding of a server. The \
326 properties that govern the request are echoed immediately following this message.
328 INVALID_SELF_LINK_URL=APPC0041E|\
329 {0} IAAS Adapter cannot perform requested service, VM url [{1}] is invalid|\
330 Correct the call to the adapter with a valid self-link URL|\
331 The IAAS adapter has been called to perform some operation on a virtual machine \
332 but the vm_id of the virtual machine is not valid.
334 SERVER_FOUND=APPC0042I|\
335 Located server {0} on tenant [{1}] and in state [{2}]|\
336 No resolution required|\
337 This message indicates that a service request was made to perform some action on the server \
338 and the indicated server was located on the specified tenant.\
341 STACK_FOUND=APPC0042I|\
342 Located stack {0} on tenant [{1}] and in state [{2}]|\
343 No resolution required|\
344 This message indicates that a service request was made to perform some action on the server \
345 and the indicated server was located on the specified tenant.
349 SERVER_NOT_FOUND=APPC0043E|\
350 No server found in provider with self-link URL [{0}]|\
351 Correct the server URL|\
352 The requested server, identified by its self link URL, could not be found in the provider
354 SERVER_OPERATION_EXCEPTION=APPC0044E|\
355 Exception {0} was caught attempting {1} of server [{2}] on tenant [{3}]|\
356 Contact support for assistance|\
357 An exception was caught while trying to perform the indicated operation on the server. The \
358 exception may yield more information about the cause of the error. This may be because \
359 of access security, or the server is in an invalid state, or any number of reasons. This \
360 message should be referred to support for assistance.
363 STACK_NOT_FOUND=APPC0043E|\
364 No stack found in provider with self-link URL [{0}]|\
365 Correct the server URL|\
366 The requested stack, identified by its self link URL, could not be found in the provider
368 STACK_OPERATION_EXCEPTION=APPC0044E|\
369 Exception {0} was caught attempting {1} of server [{2}] on tenant [{3}]|\
370 Contact support for assistance|\
371 An exception was caught while trying to perform the indicated operation on the stack. The \
372 exception may yield more information about the cause of the error. This may be because \
373 of access security, or the stack is in an invalid state, or any number of reasons. This \
374 message should be referred to support for assistance.
376 MISSING_REQUIRED_PROPERTIES=APPC0045E|\
377 One or more properties for [{0}] are missing, null, or empty. They are:|\
378 A request to execute the adapter indicated was made from a directed graph, but the properties \
379 of the request that are required by the adapter are missing or do not have a value. Correct \
380 the directed graph to supply the missing properties.|\
381 The specified properties for the indicated adapter operation are invalid or missing.
383 SERVER_ERROR_STATE=APPC0046E|\
384 The server [{0}] (id={1}) in tenant {2} is in error state, {3} is not allowed|\
385 Destroy and recreate the instance|\
386 A request to restart or rebuild a server in an error state was received, but those operations \
387 are not allowed on a server in this state. OpenStack only allows a deletion of a server \
388 that is in the error state.
390 IMAGE_NOT_FOUND=APPC0047E|\
391 The image {0} could not be located for {1}.|\
392 The image indicated could not be found. If the operation being requested is a rebuild of \
393 a server, then there is no action that can be taken other than to destroy the server and \
394 rebuild it using an image that exists.|\
395 This is likely caused by an image being deleted after it was used to build a server. If the \
396 request is for a server rebuild, then the image used to create the server was later deleted \
397 and no longer exists. The server cannot be rebuilt, because the image doesnt exist. \
398 The server must be deleted and reconstructed using a valid, existing image.
400 STATE_CHANGE_TIMEOUT=APPC0048E|\
401 Time out waiting for {0} with name {1} (and id {2}) to reach one of {3} states, current state is {4}|\
402 Recover the resource in whatever means is appropriate|\
403 The resource indicated (by name and id) was expected to change it's state (status) to one of the \
404 indicated expected states within a specified timeout but the resource did not complete the \
405 state change. It's current state is also shown. This can be caused by any number of factors \
406 but is normally a problem or conflict within the IaaS provider (OpenStack).
408 STATE_CHANGE_EXCEPTION=APPC0049E|\
409 Exception {0} waiting for {1} with name {2} (and id {3}) to reach one of {4} states, current state is {5}\n\
411 Recover the resource in whatever means is appropriate|\
412 The resource indicated (by name and id) was expected to change it's state (status) to one of the \
413 indicated expected states within a specified timeout but the resource did not complete the \
414 state change. It's current state is also shown. This can be caused by any number of factors \
415 but is normally a problem or conflict within the IaaS provider (OpenStack).
417 STOP_SERVER=APPC0050I|\
418 Server {0} is being stopped...|\
419 No recovery required|\
420 The processing being performed by APPC requires that the indicated server be stopped.
422 START_SERVER=APPC0051I|\
423 Server {0} is being started...|\
424 No recovery required|\
425 The processing being performed by APPC requires that the indicated server be started.
427 RESUME_SERVER=APPC0052I|\
428 Server {0} is being resumed...|\
429 No recovery required|\
430 The processing being performed by APPC requires that the indicated server be resumed from a suspended state.
432 UNPAUSE_SERVER=APPC0053I|\
433 Server {0} is being unpaused...|\
434 No recovery required|\
435 The processing being performed by APPC requires that the indicated server be unpaused from a paused state.
437 CONNECTION_FAILED_RETRY=APPC0054E|\
438 Connection to provider {0} at identity {1} using tenant name {2} (id {3}) failed, reason={4}, \
439 retrying in {5} seconds, attempt {6} of {7}.|\
440 The connection to the provider could not be obtained for the indicated reason. The application \
441 controller will retry the attempt to connect to the provider a maximum number of times. The \
442 message contains the amount of time the system will wait to retry the connection, and the \
443 current attempt and the maximum number of attempts.|\
444 Correct the cause of the connection failure as indicated by the reason.
446 CONNECTION_FAILED=APPC0055E|\
447 Connection to provider {0} at service {1} failed after all retry attempts.|\
448 The connection to the named provider at the indicated service URL cannot be opened. All \
449 retries have been exhausted. The application controller is giving up on the connection and will \
451 Correct the cause of the connection failure as indicated by the reason(s) in previous APPC0054E \
454 STOPPING_SERVER=APPC0056I|\
455 {0} IAAS Adapter stop server requested|\
456 No resolution required|\
457 A graph has invoked the IAAS adapter and has requested the server to be stopped. The \
458 properties that govern the request are echoed immediately following this message.
460 REBUILD_SERVER_FAILED=APPC0057E|\
461 Server {0} (id {1}) failed to rebuild, reason {2}|\
462 The server rebuild failed for the indicated reason. Correct the cause of the failure and \
463 rerun, if applicable.|\
464 The adapter has attempted to rebuild the indicated server but the rebuild request has \
465 been failed by the provider for some reason. The reason returned by the provider is \
466 included in the message.
468 PARAMETER_IS_MISSING=APPC0058E|\
469 Application {0} graph {1} response did not set the {2} parameter. This parameter is \
470 required for synchronization with the controller. Absence of this parameter is assumed \
471 to be a failure. Please correct the DG.|\
472 The indicated directed graph was called from the application controller but when the \
473 graph returned the indicated property was not defined in the return parameters. The \
474 controller requires that property to be defined and set to a value that is used to \
475 inform the controller of the outcome of operations in the graph. Failure to set \
476 the required parameter is assumed to be a failure regardless if the graph actually \
478 Correct the DG to set the specified parameter to a value that is expected and understood \
481 PARAMETER_NOT_NUMERIC=APPC0059E|\
482 Application {0} graph {1} did not set parameter {2} to a valid numeric value ({3}). \
483 Please correct the DG.|\
484 The indicated directed graph was called by the application controller and the graph \
485 did set the specified property, however the property is not a valid numeric \
486 value. The parameter is used to convey a numeric quantity and the controller \
487 cannot convert the value specified to a number. |\
490 DG_FAILED_RESPONSE=APPC0060E|\
491 Application {0} graph {1} completed with failure: error code = {2}, message = {3}|\
492 The directed graph indicated was called by the application controller and when \
493 the graph returned, an error code was set indicating that the graph failed. This \
494 is a message that echoes the results of the graph, and shows the returned error \
496 Correct the cause of the error.
498 EXCEPTION_CALLING_DG=APPC0061E|\
499 Application {0} received exception {1} attempting to call graph {2}, exception \
501 The application controller attempted to call the service logic interpreter (SLI) \
502 to execute the indicated graph, but an exception was caught. The class of the \
503 exception is shown, as is the message associated with the exception. An \
504 abbreviated stack trace is also displayed to provide information as to the \
505 state of the thread at the time of the exception.|\
506 Correct the cause of the exception and rerun.
508 GRAPH_NOT_FOUND=APPC0062E|\
509 Application {0} was unable to locate graph {1}|\
510 The application controller attempted to call the service logic interpreter (SLI) \
511 to execute the specified graph but the graph does not exist in the SLI database.|\
512 Correct the database and install the correct graph.
514 DEBUG_GRAPH_RESPONSE_HEADER=APPC0063D|\
515 Application {0} graph {1} responded with {2} properties|\
516 This is a debugging message that is output immediately after the call to the \
517 directed graph and before any processing is performed to determine the success \
518 or failure of that call. The heading is output prior to dumping all the parameters \
519 that were returned by the graph.|\
520 No recovery action is required.
522 DEBUG_GRAPH_RESPONSE_DETAIL=APPC0064D|\
523 {0}:{1} - {2} = {3}|\
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. This message is repeated for each parameter that \
527 exists in the return context from the graph.|\
528 No recovery action is required.
530 INVALID_REQUIRED_PROPERTY=APPC0065E|\
531 Application {0} request "{1}" was supplied a property "{2}" with the value "{3}" \
532 that does not meet the required form(s):|\
533 This message indicates that the specified requested operation was passed the \
534 specific property named and the property value did not meet the expected \
535 format requirements. For example, if the property is expected to be a \
536 numeric quantity and it contains alphabetic characters, or if it is expected \
537 to be a URL and it is not valid. The message also contains a list of one \
538 or more regular expressions that were used to validate the input, and which \
539 supply the syntax required for the property.|\
540 Correct the property and retry.
542 MIGRATING_SERVER=APPC066I|\
543 {0} IAAS Adapter migrate of server requested|\
544 No resolution required|\
545 A graph has invoked the IAAS adapter and has requested the migration of a server. The \
546 properties that govern the request are echoed immediately following this message.
548 EVACUATING_SERVER=APPC0067I|\
549 {0} IAAS Adapter evacuate of server requested|\
550 No resolution required|\
551 A graph has invoked the IAAS adapter and has requested the evacuation of a server. The \
552 properties that govern the request are echoed immediately following this message.
554 MIGRATE_SERVER_FAILED=APPC0068E|\
555 Server {0} (id {1}) failed to migrate during {2} phase, reason {3}|\
556 The server migration failed for the indicated reason. Correct the cause of the failure and \
557 rerun, if applicable.|\
558 The adapter has attempted to migrate the indicated server but the migration request has \
559 been failed by the provider for some reason. The reason returned by the provider is \
560 included in the message.
562 EVACUATE_SERVER_FAILED=APPC0069E|\
563 Server {0} (id {1}) failed to evacuate, reason {2}|\
564 The server evacuation failed for the indicated reason. Correct the cause of the failure and \
565 rerun, if applicable.|\
566 The adapter has attempted to evacuate the indicated server but the evacuation request has \
567 been failed by the provider for some reason. The reason returned by the provider is \
568 included in the message.
570 APPC_TOO_BUSY=APPC0080E|\
571 APP-C instance is too busy|\
572 The APP-C instance handles too many requests and cannot accept new ones as its internal \
573 execution queue is full. The problem can appear when the APP-C instance gets more requests \
574 than it can handle simultaneously.|\
575 Check the server KPIs for possible performance issues (e.g. insufficient memory, \
576 high network latency, slow responsiveness of southbound systems and so on) which can affect \
577 the system throughput.
579 VF_SERVER_BUSY=APPC0081E|\
580 Concurrent access to server "{0}"|\
581 APP-C currently executes a command on the specified server and cannot accept yet another request \
583 Try to resubmit the request at later time.
585 VF_ILLEGAL_COMMAND=APPC0082E|\
586 Server "{0}" does not support command "{1}" in the current state "{2}"|\
587 APP-C cannot perform the requested command on the server in the current state as no state transition \
588 is defined for that.|\
589 Contact support for assistance.
591 VF_UNDEFINED_STATE=APPC0083E|\
592 Server "{0}" cannot handle command "{1}" because of its doubtful state|\
593 The resource has undefined working state as result of abnormal termination of a previous command.|\
594 Recover the resource in whatever means is appropriate.
596 APPC_NO_RESOURCE_FOUND=APPC0084E|\
597 No resource found with ID "{0}" in A&AI system.|\
598 APP-C is unable to resolve the VF details given the instance ID.|\
599 Check whether the resource has been deleted (terminated) before.
601 APPC_EXPIRED_REQUEST=APPC0085E|\
602 The request "{0}" for server "{1}" has exceeded its TTL limit of "{2}" seconds|\
603 The received expired event won't be handled by APP-C instance. Normally the problem might be \
604 related to asynchronous requests arriving to APP-C instance via DMaaP channel.|\
605 Try to submit a new request if still relevant.
607 APPC_WORKFLOW_NOT_FOUND=APPC0086E|\
608 Workflow for vnfType = "{0}" and command = "{1}" not found.|\
609 Unable to retrive Workflow related to mention VNF type and command.|\
610 Check provided VNF and Command details are correct.
612 APPC_INVALID_INPUT=APPC0087E|\
613 Null vnfId and command provided|\
614 Request contains Null vnfId and command|\
615 Provided non-null VNF and Command details.
617 APPC_AUDIT_MSG=APPC0090A|\
618 Operation "{0}" for VNF type "{1}" from Source "{2}" with RequestID "{3}" \
619 was started at "{4}" and ended at "{5}" with status code "{6}"|\
623 AAI_CONNECTION_FAILED=APPC0106E|\
624 APP-C is unable to communicate with A&AI|\
625 Connection to A&AI at service {0} failed after all retry attempts.|\
626 The connection to the A&AI at the indicated service URL cannot be opened. \
627 All retries have been exhausted. APP-C is giving up on the connection and will?\
628 reject the operation request.|\
631 AAI_UPDATE_FAILED=APPC0107E|\
632 APP-C is unable to update COMPONENT_ID {0} to {1} for reason {2}|\
633 The update at the end of the operation wasn't performed as a result of \
634 A&AI communication failure or its internal error.|\
637 AAI_GET_DATA_FAILED=APPC0108E|\
638 APP-C is unable to retrieve VF/VFC {0} data for Transaction ID?{1}?as a \
639 result of A&AI communication failure or its internal error.|\
640 Operation request will be rejected by APP-C|\
643 AAI_CONNECTION_FAILED_RETRY=APPC0105W|\
644 A&AI at identity {0} using VNF_ID {1} failed, reason={2}, retrying in {3} seconds, attempt {4} of {5}.|\
645 The connection to the A&AI could not be obtained for the indicated reason. APP-C will retry to connect \
646 to the A&AI. The?message contains the retry delay, the current attempt and the maximum number of attempts.|\
647 Correct the cause of the connection failure as indicated by the reason.?
649 AAI_DELETE_FAILED=APPC0114E|\
650 APP-C is unable to delete COMPONENT_ID {0} for reason {1}|\
651 The deletion at the end of the operation wasn't performed as a result of \
652 A&AI communication failure or its internal error.|\
655 VNF_CONFIGURED=APPC0118I|\
656 VNF {0} is configured|\
657 No resolution is required, this is an informational message|\
658 The VNF configuration has been completed.
660 VNF_CONFIGURATION_STARTED=APPC0116I|\
661 VNF {0} is being configured|\
662 No resolution is required, this is an informational message|\
663 The VNF configuration has been started
665 VNF_CONFIGURATION_FAILED=APPC0119E|\
666 VNF {0} configuration failed for reason {1}|\
667 The configuration operation wasn't performed as a result of VNF communication failure or its internal error.|\
670 VNF_TEST_STARTED=APPC0120I|\
671 VNF {0} is being tested|\
672 No resolution is required, this is an informational message|\
673 The VNF test has been started
675 VNF_TESTED=APPC0121I|\
677 No resolution is required, this is an informational message|\
678 The VNF test has been completed
680 VNF_TEST_FAILED=APPC0122E|\
681 VNF {0} test failed for reason {1}|\
682 The test operation wasn't performed as a result of VNF communication failure or its internal error.|\
685 STOP_SERVER_FAILED=APPC0112E|\
686 Server {0} (id {1}) failed to stop during {2} phase, reason {3}|\
687 The server stop failed for the indicated reason. Correct the cause of the failure and \
688 rerun, if applicable.|\
689 The adapter has attempted to stop the indicated server but the stop request has \
690 been failed by the provider for some reason. The reason returned by the provider is \
691 included in the message.
693 TERMINATE_SERVER_FAILED=APPC0113E|\
694 Server {0} (id {1}) failed to terminate during {2} phase, reason {3}|\
695 The server termination failed for the indicated reason. Correct the cause of the failure and \
696 rerun, if applicable.|\
697 The adapter has attempted to terminate the indicated server but the migration request has \
698 been failed by the provider for some reason. The reason returned by the provider is \
699 included in the message.
701 TERMINATE_STACK_FAILED=APPC0113E|\
702 Server {0} (id {1}) failed to terminate during {2} phase, reason {3}|\
703 The server termination failed for the indicated reason. Correct the cause of the failure and \
704 rerun, if applicable.|\
705 The adapter has attempted to terminate the indicated server but the migration request has \
706 been failed by the provider for some reason. The reason returned by the provider is \
707 included in the message.
709 TERMINATING_SERVER=APPC0114I|\
710 {0} IAAS Adapter?terminate server requested|\
711 No resolution required|\
712 A graph has invoked the IAAS adapter and has requested the server to be terminated. The \
713 properties that govern the request are echoed immediately following this message.
716 TERMINATING_STACK=APPC0115I|\
717 {0} IAAS Adapter?terminate stack requested|\
718 No resolution required|\
719 A graph has invoked the IAAS adapter and has requested the server to be terminated. The \
720 properties that govern the request are echoed immediately following this message.
722 TERMINATE_SERVER=APPC0116I|\
723 Server {0} is being?terminated...|\
724 No recovery required|\
725 The processing being performed by APPC requires that the indicated server be terminated.
727 TERMINATE_STACK=APPC0117I|\
728 Stack {0} is being?terminated...|\
729 No recovery required|\
730 The processing being performed by APPC requires that the indicated server be terminated.
732 MIGRATE_COMPLETE=APPC0118I|\
733 Migrate {0} finished with status {1}. Start Time: {2}. End Time: {3}. Request ID: {4}. Reason:{5}...|\
734 No resolution is required, this is an informational message|\
735 APP-C Migrate Operation has completed.
737 RESTART_COMPLETE=APPC0119I|\
738 Restart {0} finished with status {1}. Start Time: {2}. End Time: {3}. Request ID: {4}. Reason:{5}...|\
739 No resolution is required, this is an informational message|\
740 APP-C Restart Operation has completed.
742 REBUILD_COMPLETE=APPC0120I|\
743 Rebuild {0} finished with status {1}. Start Time: {2}. End Time: {3}. Request ID: {4}. Reason:{5}...|\
744 No resolution is required, this is an informational message|\
745 APP-C Rebuild Operation has completed.
747 CLOSE_CONTEXT_FAILED=APPC0121E|\
748 Exception {0} was caught attempting to close provider context for {1}.|\
749 Contact support for assistance|\
750 An exception was caught while trying to close the provider context. The \
751 exception may yield more information about the cause of the error. This may be because \
752 of access security, or the server is in an invalid state, or any number of reasons. This \
753 message should be referred to support for assistance.
755 SNAPSHOTING_STACK=APPC0122I|\
756 Stack {0} is being?snapshoted...|\
757 No resolution is required|\
760 STACK_SNAPSHOTED==APPC0123I|\
761 Stack {0} snapshoted, snapshot ID = [{1}].|\
762 No resolution is required|\
763 Stack snapshoted successfully.
766 RESTORING_STACK=APPC0124I|\
767 Stack {0} is being?restored to snapshot {1}...|\
768 No resolution is required|\
771 STACK_RESTORED=APPC0125I|\
772 Stack {0} is restored to snapshot {1}.|\
773 No resolution is required|\
774 Stack restored successfully.
776 MISSING_PARAMETER_IN_REQUEST=APPC0126E|\
777 Parameter {0} is missing in svc request of {1}.|\
778 Check DG node definition to pass missing parameter's value.|\
779 Node definition in DG missing indicated parameter value or value is incorrect, \
780 check the graph definition.
782 CANNOT_ESTABLISH_CONNECTION=APPC0127E|\
783 Cannot establish connection to server {0} port {1} with user {2}.|\
784 Check server IP, port and user credentials.|\
785 Wrong data sent in request's payload.
788 APPC_METRIC_MSG=APPC0128I|\
789 Operation "{0}" for VNF type "{1}" from Source "{2}" with RequestID "{3}" on "{4}" with action "{5}" \
790 ended in {6} ms with result "{7}"|\
791 No resolution is required, this is an informational message|\
792 This message indicates that the APPC logged some operation to metric