2 # ============LICENSE_START=======================================================
4 # ================================================================================
5 # Copyright (C) 2017 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 # ECOMP is a trademark and service mark of AT&T Intellectual Property.
22 # ============LICENSE_END=========================================================
25 # This property file contains all message definitions used by APPC
27 # Message resources are identified by a key, which is defined in the Msg enumeration. This key is
28 # assigned a value which consists of 4 parts separated by a pipe (|) symbol. These parts are:
30 # 1. The message identifier
31 # 2. The Message text to be formatted and issued to the user
32 # 3. The suggested resolution text, how to fix the problem.
33 # 4. The description text, what is the problem so the user can understand
35 CONFIGURATION_STARTED=APPC0001I|\
36 ECOMP Application Controller (APP-C) initialization started at {0}|\
37 No resolution is required, this is an informational message|\
38 The APP-C component configuration has been started because the component is being \
39 initialized or loaded for the first time, or a new instance of the component is \
40 being created. This message indicates that the component is starting.
42 CONFIGURATION_CLEARED=APPC0002I|\
43 All prior configuration has been cleared|\
44 No resolution is required, this is an informational message|\
45 The APP-C component is being started or restarted and any prior configuration \
46 (if present), is cleared. This is normal.
48 LOADING_CONFIGURATION_OVERRIDES=APPC0003I|\
49 Loading configuration properties from file "{0}"|\
50 No resolution is required, this is an informational message|\
51 This message indicates that the configuration of the APP-C component was located \
52 and is being loaded from the specified file.
54 LOADING_DEFAULTS=APPC0004I|\
55 Configuration defaults loaded from resource file "{0}"|\
56 No resolution is required, this is an informational message|\
57 This is a normal indication that the default configuration settings were loaded \
58 from the resource file. The APP-C components load a default configuration first \
59 so that all configuration values have valid default settings. Any user configuation \
60 that may be specified then overrides these defaults.
62 NO_DEFAULTS_FOUND=APPC0005E|\
63 No default property resource "{0}" was found!|\
64 This is an internal error. Contact support.|\
65 This is an internal error that indicates that the default resource property file \
66 could not be located. This is likely a packaging error and is indicative of \
67 a construction problem. Refer this to development or level 3 support for assistance.
69 PROPERTY_VALUE=APPC0006I|\
70 Property "{0}" ="{1}"|\
71 No resolution is required, this is an informational message|\
72 This message is issued to show the value of configuration properties and is used to \
73 debug start up of the component.
75 NO_OVERRIDE_PROPERTY_FILE_LOADED=APPC0007E|\
76 No configuration file named [{0}] was found on the configuration search path [{1}]. \
77 If a configuration file should have been loaded, check the file name and search \
78 path specified. APPC will proceed using the default values and command-line \
80 If a configuration file was expected, verify the file name and that it exists on \
81 the search path for the configuration properties. The search path defaults to \
82 <em>${user.home},/opt/app/appc/etc,etc,../etc,/etc,.</em> and can be overridden \
83 by specification of the property <em>org.openecomp.appc.bootstrap.path</em>. The \
84 property file name defaults to <em>appc.properties</em> and can also be \
85 overridden by the <em>org.openecomp.appc.bootstrap.file</em> property.|\
86 This message indicates that the bootstrap path was searched for the bootstrap \
87 property file (a file that can be supplied to configure APPC) and that no file \
88 with the specified name was found on any of the path elements of the path.
90 SEARCHING_CONFIGURATION_OVERRIDES=APPC0008I|\
91 Searching path "{0}" for configuration settings "{1}"|\
92 No resolution is required|\
93 This message indicates that the specified path is being examined for a configuration \
94 file of the indicated name. The configuration file defaults to <em>appc.properties</em> \
95 but can be overridden by specification of the <em>org.openecomp.appc.bootstrap.file</em> \
96 property (using a command-line override, for example). This message is intended to \
97 assist in the debugging and analysis of configuration issues where the indicated \
98 file may not be processed or found. The path that is searched is a comma-delimited \
99 list of directories and defaults to <em>${user.home},/opt/app/appc/etc,etc,../etc,/etc,.</em> \
100 but can also be overridden by specification of the <em>org.openecomp.appc.bootstrap.path</em> \
103 LOADING_APPLICATION_OVERRIDES=APPC0009I|\
104 Loading application-specific override properties|\
105 No resolution required|\
106 This message indicates that the APPC component was invoked as an embedded component \
107 and that the caller has supplied an override property object.
109 NO_APPLICATION_OVERRIDES=APPC0010I|\
110 No application-specific override properties were provided!|\
111 No resolution required|\
112 This message indicates that the APPC component was invoked as an embedded component \
113 and that the caller has supplied an override property object, but that object was \
116 MERGING_SYSTEM_PROPERTIES=APPC0011I|\
117 Merging system properties into configuration|\
118 No resolution is required|\
119 This message indicates that the java virtual machine system properties are being \
120 examined and merged into the APP-C component configuration. This allows for command \
121 line specification of any APP-C configuration property as a standard java define \
122 JVM option (ex: -Dproperty=value).
124 SETTING_SPECIAL_PROPERTY=APPC0012I|\
125 Setting property "{0}={1}" in system properties|\
126 No resolution required.|\
127 This message indicates that the specified property loaded from defaults, property \
128 file overrides, application overrides, or command-line overrides is being placed \
129 in the system (java virtual machine) properties object. Some libraries that may \
130 be integrated with APP-C (for example, DME2 or AFT libraries) may only look for \
131 their properties in the system properties object. This allows those components \
132 to be configured from the APP-C configuration.
134 LOADING_RESOURCE_BUNDLE=APPC0013I|\
135 Loading resource bundle "{0}"|\
136 No resolution required|\
137 This message indicates that the specified resource bundle is being loaded.
139 LOGGING_ALREADY_INITIALIZED=APPC0014W|\
140 Logging has already been initialized, check the container logging definitions to ensure \
141 they represent your desired logging configuration.|\
142 If logging is configured incorrectly, move the definitions to the container or component \
143 that first initialized logging. If they are ok, no resolution is required.|\
144 This message indicates that the logging environment already exists and has been configured.
146 SEARCHING_LOG_CONFIGURATION=APPC0015I|\
147 Searching path "{0}" for log configuration file "{1}"|\
148 No resolution is required|\
149 This message indicates that the APP-C component configuration file specified a logging \
150 configuration file and/or search path and the path is being searched. This is used to \
151 assist in debugging the configuration process.
153 LOADING_DEFAULT_LOG_CONFIGURATION=APPC0016I|\
154 Loading default logging configuration from system resource file "{0}"|\
155 No resolution is required|\
156 A default logging configuration for the component is loaded from system resources to \
157 ensure that a valid logging environment exists. This is a normal message, and will \
158 be followed by APPC0019I if a user-specified logging configuration overrides the \
161 NO_LOG_CONFIGURATION=APPC0017E|\
162 No log configuration could be found or defaulted!|\
163 A valid logging configuration cannot be found, and no default configuration resource \
164 was loaded. This is likely a packaging issue and should be referred to development \
165 or level 3 support for assistance.|\
166 This is an internal error.
168 UNSUPPORTED_LOGGING_FRAMEWORK=APPC0018E|\
169 An unsupported logging framework is bound to SLF4J. Only Logback or Log4J are supported.|\
170 This is a compatibility error with logging frameworks used in the application environment \
171 and should be referred to development or level 3 support for assistance.|\
172 This is an internal error.
174 LOADING_LOG_CONFIGURATION=APPC0019I|\
175 Loading logging configuration from file "{0}"|\
176 No resolution is required|\
177 The specified logging configuration is being loaded.
179 UNKNOWN_PROVIDER=APPC0020E|\
180 Provider {0} cannot be found or cannot be resolved to one of the known providers, [{1}].|\
181 Specify the name of a valid provider. The IAAS adapter contains a set of providers \
182 that are defined. Each of these providers is assigned a logical name. The call \
183 to the IAAS adapter must specify the name of the provider that is desired. This \
184 could be the result of an incorrect call, or the IAAS adapter configuration is \
186 The APP-C IAAS adapter is being called to request a service on a specific provider, but \
187 the name of the provider cannot be found in the list of defined providers. This may \
188 be an error in the directed graph that contains the call to the IAAS adapter, or it \
189 may be an error in the request, or the configuration of the IAAS adapter may need \
192 SERVER_STATE_CHANGE_TIMEOUT=APPC0021E|\
193 Server name "{0}" with id "{1}" in tenant "{2}" and region "{3}" did not change state \
194 within the alloted time. Current state is "{4}" and the desired state(s) are "{5}"|\
195 This is likely a provider issue. If the provider is OpenStack, check the virtual \
196 machine on the horizon dashboard. If the machine is in an invalid state, you may \
197 need to contact Openstack support. The exact mechanisms for recovery of a machine \
198 in an invalid state are varied and will be different from provider to provider.|\
199 This message indicates that the IAAS adapter has performed some requested action \
200 on the specified server (virtual machine) but the server did not enter a valid \
201 state (running, stopped, etc) within the timeout period. The last state (current state) \
202 is shown, as well as the state that was expected. The servers name, UUID, containing \
203 tenant, and region are shown so that the correct provider can be examined.
205 SERVER_DELETED=APPC0022E|\
206 Server name "{0}" with id "{1}" in tenant "{2}" has a state of deleted and cannot be {3}.|\
207 The specified server has been deleted on the provider. This is likely an incorrect \
208 request. Make sure that you are specifying the correct server ID/name, provider, \
209 and region. If the self-link URL is used, make sure that the correct server resource \
210 is specified. If the machine was correct, recreate or rebuild the machine to make \
211 it usable. Correct the request.|\
212 This message indicates that the server specified was found to have been deleted in the \
213 target provider and that the requested action cannot be performed. This may be caused \
216 <li>The UUID of the server is wrong and specifies a machine that no longer exists</li>\
217 <li>The machine was deleted by a different process or request</li>\
218 <li>The wrong provider was requested</li>\
219 <li>The request was out-of-order</li>\
222 UNKNOWN_SERVER_STATE=APPC0023E|\
223 Server name "{0}" with id "{1}" in tenant "{2}" has an unknown state of "{3}".|\
224 Check the machine to determine the state of the machine. Correct that state to a valid \
225 state if possible. This may also be caused by an internal error in the PAL (Provider \
226 Abstraction Layer) used by the IAAS if a new state definition has been added to the \
227 provider (such as a new version or the installation of an unknown or unsupported \
228 extension). If the machine's state is valid, refer this error to development or \
229 level 3 support for assistance.|\
230 This message indicates that a request was made to the IAAS adapter to take some action \
231 on the specified virtual machine, but the machine was found to be in a state that \
232 prevents that action from being performed.
234 COMPONENT_INITIALIZING=APPC0024I|\
235 {0} component {1} is being initialized...|\
236 No resolution needed|\
237 The IAAS adapter is being initialized
239 COMPONENT_INITIALIZED=APPC0025I|\
240 {0} component {1} has completed initialization|\
241 No resolution needed|\
242 The IAAS adapter has been initialized
244 COMPONENT_TERMINATING=APPC0026I|\
245 {0} component {1} is terminating...|\
246 No resolution needed|\
247 The IAAS adapter is being terminated
249 COMPONENT_TERMINATED=APPC0027I|\
250 {0} component {1} has terminated|\
251 No resolution needed|\
252 The IAAS adapter has been terminated
254 IAAS_ADAPTER_UNSUPPORTED_OPERATION=APPC0028E|\
255 Operation {0} is not supported or implemented at this time.|\
256 Change the request to a supported operation|\
257 The IAAS adapter has been requested to perform some operation that it cannot \
258 perform at this time.
260 IAAS_ADAPTER_RPC_CALLED=APPC0029I|\
261 Operation [{0}] called. Input document:\n{1}|\
262 No resolution required|\
263 The IAAS adapter operation indicated was called with the requested input \
266 NO_SERVICE_FOUND=APPC0030E|\
267 Unable to locate the [{0}] service in the OSGi container|\
268 Ensure that the feature containing that service is installed and running|\
269 This indicates that the required feature could not be located
271 CONTEXT_PARAMETERS_DISPLAY=APPC0031I|\
272 Dump of context parameters for module [{0}], RPC [{1}], and version [{2}]|\
273 No resolution required|\
274 The specified RPC is being called and the context properties are being \
275 displayed. This is a debugging message and preceeds the display of \
276 each context property.
278 RESPONSE_PARAMETERS_DISPLAY=APPC0032I|\
279 Response properties from execution of module [{0}], RPC [{1}], and version [{2}] are:|\
280 No resolution required|\
281 The service logic directed graph has been executed and returned the response properties. \
282 This message preceeds the dump of the response properties. It is used for debugging \
283 of service logic and execution problems.
285 NULL_OR_INVALID_ARGUMENT=APPC0033E|\
286 Service {0}:{1} was provided a null (empty) or invalid argument, [{2}] = [{3}]|\
287 This is likely an internal error, refer to support for assistance|\
288 The indicated service was called, but the specified parameter or argument was either \
289 null or empty, or it was invalid. If it has a value, the value is shown. If the \
290 value is null, the value is shown as 'null'.
292 PROCESSING_REQUEST=APPC0034I|\
293 Service {0}:{1} is processing service [{2}] with request id [{3}]|\
294 No resolution required|\
295 The indicated application and RPC is processing the specified service request.
297 INVALID_SERVICE_REQUEST=APPC0035E|\
298 Service {0}:{1} received request for service [{2}] but that service is invalid or unknown.|\
299 Correct the service request, likely a directed graph issue|\
300 The RPC was invoked to process a service request, but the service is not valid.
302 REGISTERING_SERVICE=APPC0036I|\
303 {0} registering service {1} using class {2}|\
304 No resolution required|\
305 The indicated application service is registering itself with the OSGi container using the \
306 indicated java class name.
308 UNREGISTERING_SERVICE=APPC0037I|\
309 {0} unregistering service {1}|\
310 No resolution required|\
311 The application service is being unregistered from the OSGi container services list.
313 LOADING_PROVIDER_DEFINITIONS=APPC0038I|\
314 {0} IAAS Adapter initializing provider {1} as {2}|\
315 No resolution is required|\
316 The IAAS adapter is loading the definition of the specified provider from its \
319 RESTARTING_SERVER=APPC0039I|\
320 {0} IAAS Adapter restart of server requested|\
321 No resolution required|\
322 A graph has invoked the IAAS adapter and has requested the restart of a server. The \
323 properties that govern the request are echoed immediately following this message.
325 REBUILDING_SERVER=APPC0040I|\
326 {0} IAAS Adapter rebuild of server requested|\
327 No resolution required|\
328 A graph has invoked the IAAS adapter and has requested the rebuilding of a server. The \
329 properties that govern the request are echoed immediately following this message.
331 INVALID_SELF_LINK_URL=APPC0041E|\
332 {0} IAAS Adapter cannot perform requested service, VM url [{1}] is invalid|\
333 Correct the call to the adapter with a valid self-link URL|\
334 The IAAS adapter has been called to perform some operation on a virtual machine \
335 but the vm_id of the virtual machine is not valid.
337 SERVER_FOUND=APPC0042I|\
338 Located server {0} on tenant [{1}] and in state [{2}]|\
339 No resolution required|\
340 This message indicates that a service request was made to perform some action on the server \
341 and the indicated server was located on the specified tenant.\
344 STACK_FOUND=APPC0042I|\
345 Located stack {0} on tenant [{1}] and in state [{2}]|\
346 No resolution required|\
347 This message indicates that a service request was made to perform some action on the server \
348 and the indicated server was located on the specified tenant.
352 SERVER_NOT_FOUND=APPC0043E|\
353 No server found in provider with self-link URL [{0}]|\
354 Correct the server URL|\
355 The requested server, identified by its self link URL, could not be found in the provider
357 SERVER_OPERATION_EXCEPTION=APPC0044E|\
358 Exception {0} was caught attempting {1} of server [{2}] on tenant [{3}]|\
359 Contact support for assistance|\
360 An exception was caught while trying to perform the indicated operation on the server. The \
361 exception may yield more information about the cause of the error. This may be because \
362 of access security, or the server is in an invalid state, or any number of reasons. This \
363 message should be referred to support for assistance.
366 STACK_NOT_FOUND=APPC0043E|\
367 No stack found in provider with self-link URL [{0}]|\
368 Correct the server URL|\
369 The requested stack, identified by its self link URL, could not be found in the provider
371 STACK_OPERATION_EXCEPTION=APPC0044E|\
372 Exception {0} was caught attempting {1} of server [{2}] on tenant [{3}]|\
373 Contact support for assistance|\
374 An exception was caught while trying to perform the indicated operation on the stack. The \
375 exception may yield more information about the cause of the error. This may be because \
376 of access security, or the stack is in an invalid state, or any number of reasons. This \
377 message should be referred to support for assistance.
379 MISSING_REQUIRED_PROPERTIES=APPC0045E|\
380 One or more properties for [{0}] are missing, null, or empty. They are:|\
381 A request to execute the adapter indicated was made from a directed graph, but the properties \
382 of the request that are required by the adapter are missing or do not have a value. Correct \
383 the directed graph to supply the missing properties.|\
384 The specified properties for the indicated adapter operation are invalid or missing.
386 SERVER_ERROR_STATE=APPC0046E|\
387 The server [{0}] (id={1}) in tenant {2} is in error state, {3} is not allowed|\
388 Destroy and recreate the instance|\
389 A request to restart or rebuild a server in an error state was received, but those operations \
390 are not allowed on a server in this state. OpenStack only allows a deletion of a server \
391 that is in the error state.
393 IMAGE_NOT_FOUND=APPC0047E|\
394 The image {0} could not be located for {1}.|\
395 The image indicated could not be found. If the operation being requested is a rebuild of \
396 a server, then there is no action that can be taken other than to destroy the server and \
397 rebuild it using an image that exists.|\
398 This is likely caused by an image being deleted after it was used to build a server. If the \
399 request is for a server rebuild, then the image used to create the server was later deleted \
400 and no longer exists. The server cannot be rebuilt, because the image doesnt exist. \
401 The server must be deleted and reconstructed using a valid, existing image.
403 STATE_CHANGE_TIMEOUT=APPC0048E|\
404 Time out waiting for {0} with name {1} (and id {2}) to reach one of {3} states, current state is {4}|\
405 Recover the resource in whatever means is appropriate|\
406 The resource indicated (by name and id) was expected to change it's state (status) to one of the \
407 indicated expected states within a specified timeout but the resource did not complete the \
408 state change. It's current state is also shown. This can be caused by any number of factors \
409 but is normally a problem or conflict within the IaaS provider (OpenStack).
411 STATE_CHANGE_EXCEPTION=APPC0049E|\
412 Exception {0} waiting for {1} with name {2} (and id {3}) to reach one of {4} states, current state is {5}\n\
414 Recover the resource in whatever means is appropriate|\
415 The resource indicated (by name and id) was expected to change it's state (status) to one of the \
416 indicated expected states within a specified timeout but the resource did not complete the \
417 state change. It's current state is also shown. This can be caused by any number of factors \
418 but is normally a problem or conflict within the IaaS provider (OpenStack).
420 STOP_SERVER=APPC0050I|\
421 Server {0} is being stopped...|\
422 No recovery required|\
423 The processing being performed by APPC requires that the indicated server be stopped.
425 START_SERVER=APPC0051I|\
426 Server {0} is being started...|\
427 No recovery required|\
428 The processing being performed by APPC requires that the indicated server be started.
430 RESUME_SERVER=APPC0052I|\
431 Server {0} is being resumed...|\
432 No recovery required|\
433 The processing being performed by APPC requires that the indicated server be resumed from a suspended state.
435 UNPAUSE_SERVER=APPC0053I|\
436 Server {0} is being unpaused...|\
437 No recovery required|\
438 The processing being performed by APPC requires that the indicated server be unpaused from a paused state.
440 CONNECTION_FAILED_RETRY=APPC0054E|\
441 Connection to provider {0} at identity {1} using tenant name {2} (id {3}) failed, reason={4}, \
442 retrying in {5} seconds, attempt {6} of {7}.|\
443 The connection to the provider could not be obtained for the indicated reason. The application \
444 controller will retry the attempt to connect to the provider a maximum number of times. The \
445 message contains the amount of time the system will wait to retry the connection, and the \
446 current attempt and the maximum number of attempts.|\
447 Correct the cause of the connection failure as indicated by the reason.
449 CONNECTION_FAILED=APPC0055E|\
450 Connection to provider {0} at service {1} failed after all retry attempts.|\
451 The connection to the named provider at the indicated service URL cannot be opened. All \
452 retries have been exhausted. The application controller is giving up on the connection and will \
454 Correct the cause of the connection failure as indicated by the reason(s) in previous APPC0054E \
457 STOPPING_SERVER=APPC0056I|\
458 {0} IAAS Adapter stop server requested|\
459 No resolution required|\
460 A graph has invoked the IAAS adapter and has requested the server to be stopped. The \
461 properties that govern the request are echoed immediately following this message.
463 REBUILD_SERVER_FAILED=APPC0057E|\
464 Server {0} (id {1}) failed to rebuild, reason {2}|\
465 The server rebuild failed for the indicated reason. Correct the cause of the failure and \
466 rerun, if applicable.|\
467 The adapter has attempted to rebuild the indicated server but the rebuild request has \
468 been failed by the provider for some reason. The reason returned by the provider is \
469 included in the message.
471 PARAMETER_IS_MISSING=APPC0058E|\
472 Application {0} graph {1} response did not set the {2} parameter. This parameter is \
473 required for synchronization with the controller. Absence of this parameter is assumed \
474 to be a failure. Please correct the DG.|\
475 The indicated directed graph was called from the application controller but when the \
476 graph returned the indicated property was not defined in the return parameters. The \
477 controller requires that property to be defined and set to a value that is used to \
478 inform the controller of the outcome of operations in the graph. Failure to set \
479 the required parameter is assumed to be a failure regardless if the graph actually \
481 Correct the DG to set the specified parameter to a value that is expected and understood \
484 PARAMETER_NOT_NUMERIC=APPC0059E|\
485 Application {0} graph {1} did not set parameter {2} to a valid numeric value ({3}). \
486 Please correct the DG.|\
487 The indicated directed graph was called by the application controller and the graph \
488 did set the specified property, however the property is not a valid numeric \
489 value. The parameter is used to convey a numeric quantity and the controller \
490 cannot convert the value specified to a number. |\
493 DG_FAILED_RESPONSE=APPC0060E|\
494 Application {0} graph {1} completed with failure: error code = {2}, message = {3}|\
495 The directed graph indicated was called by the application controller and when \
496 the graph returned, an error code was set indicating that the graph failed. This \
497 is a message that echoes the results of the graph, and shows the returned error \
499 Correct the cause of the error.
501 EXCEPTION_CALLING_DG=APPC0061E|\
502 Application {0} received exception {1} attempting to call graph {2}, exception \
504 The application controller attempted to call the service logic interpreter (SLI) \
505 to execute the indicated graph, but an exception was caught. The class of the \
506 exception is shown, as is the message associated with the exception. An \
507 abbreviated stack trace is also displayed to provide information as to the \
508 state of the thread at the time of the exception.|\
509 Correct the cause of the exception and rerun.
511 GRAPH_NOT_FOUND=APPC0062E|\
512 Application {0} was unable to locate graph {1}|\
513 The application controller attempted to call the service logic interpreter (SLI) \
514 to execute the specified graph but the graph does not exist in the SLI database.|\
515 Correct the database and install the correct graph.
517 DEBUG_GRAPH_RESPONSE_HEADER=APPC0063D|\
518 Application {0} graph {1} responded with {2} properties|\
519 This is a debugging message that is output immediately after the call to the \
520 directed graph and before any processing is performed to determine the success \
521 or failure of that call. The heading is output prior to dumping all the parameters \
522 that were returned by the graph.|\
523 No recovery action is required.
525 DEBUG_GRAPH_RESPONSE_DETAIL=APPC0064D|\
526 {0}:{1} - {2} = {3}|\
527 This is a debugging message that is output immediately after the call to the \
528 directed graph and before any processing is performed to determine the success \
529 or failure of that call. This message is repeated for each parameter that \
530 exists in the return context from the graph.|\
531 No recovery action is required.
533 INVALID_REQUIRED_PROPERTY=APPC0065E|\
534 Application {0} request "{1}" was supplied a property "{2}" with the value "{3}" \
535 that does not meet the required form(s):|\
536 This message indicates that the specified requested operation was passed the \
537 specific property named and the property value did not meet the expected \
538 format requirements. For example, if the property is expected to be a \
539 numeric quantity and it contains alphabetic characters, or if it is expected \
540 to be a URL and it is not valid. The message also contains a list of one \
541 or more regular expressions that were used to validate the input, and which \
542 supply the syntax required for the property.|\
543 Correct the property and retry.
545 MIGRATING_SERVER=APPC066I|\
546 {0} IAAS Adapter migrate of server requested|\
547 No resolution required|\
548 A graph has invoked the IAAS adapter and has requested the migration of a server. The \
549 properties that govern the request are echoed immediately following this message.
551 EVACUATING_SERVER=APPC0067I|\
552 {0} IAAS Adapter evacuate of server requested|\
553 No resolution required|\
554 A graph has invoked the IAAS adapter and has requested the evacuation of a server. The \
555 properties that govern the request are echoed immediately following this message.
557 MIGRATE_SERVER_FAILED=APPC0068E|\
558 Server {0} (id {1}) failed to migrate during {2} phase, reason {3}|\
559 The server migration failed for the indicated reason. Correct the cause of the failure and \
560 rerun, if applicable.|\
561 The adapter has attempted to migrate the indicated server but the migration request has \
562 been failed by the provider for some reason. The reason returned by the provider is \
563 included in the message.
565 EVACUATE_SERVER_FAILED=APPC0069E|\
566 Server {0} (id {1}) failed to evacuate, reason {2}|\
567 The server evacuation failed for the indicated reason. Correct the cause of the failure and \
568 rerun, if applicable.|\
569 The adapter has attempted to evacuate the indicated server but the evacuation request has \
570 been failed by the provider for some reason. The reason returned by the provider is \
571 included in the message.
573 APPC_TOO_BUSY=APPC0080E|\
574 APP-C instance is too busy|\
575 The APP-C instance handles too many requests and cannot accept new ones as its internal \
576 execution queue is full. The problem can appear when the APP-C instance gets more requests \
577 than it can handle simultaneously.|\
578 Check the server KPIs for possible performance issues (e.g. insufficient memory, \
579 high network latency, slow responsiveness of southbound systems and so on) which can affect \
580 the system throughput.
582 VF_SERVER_BUSY=APPC0081E|\
583 Concurrent access to server "{0}"|\
584 APP-C currently executes a command on the specified server and cannot accept yet another request \
586 Try to resubmit the request at later time.
588 VF_ILLEGAL_COMMAND=APPC0082E|\
589 Server "{0}" does not support command "{1}" in the current state "{2}"|\
590 APP-C cannot perform the requested command on the server in the current state as no state transition \
591 is defined for that.|\
592 Contact support for assistance.
594 VF_UNDEFINED_STATE=APPC0083E|\
595 Server "{0}" cannot handle command "{1}" because of its doubtful state|\
596 The resource has undefined working state as result of abnormal termination of a previous command.|\
597 Recover the resource in whatever means is appropriate.
599 APPC_NO_RESOURCE_FOUND=APPC0084E|\
600 No resource found with ID "{0}" in A&AI system.|\
601 APP-C is unable to resolve the VF details given the instance ID.|\
602 Check whether the resource has been deleted (terminated) before.
604 APPC_EXPIRED_REQUEST=APPC0085E|\
605 The request "{0}" for server "{1}" has exceeded its TTL limit of "{2}" seconds|\
606 The received expired event won't be handled by APP-C instance. Normally the problem might be \
607 related to asynchronous requests arriving to APP-C instance via DMaaP channel.|\
608 Try to submit a new request if still relevant.
610 APPC_WORKFLOW_NOT_FOUND=APPC0086E|\
611 Workflow for vnfType = "{0}" and command = "{1}" not found.|\
612 Unable to retrive Workflow related to mention VNF type and command.|\
613 Check provided VNF and Command details are correct.
615 APPC_INVALID_INPUT=APPC0087E|\
616 Null vnfId and command provided|\
617 Request contains Null vnfId and command|\
618 Provided non-null VNF and Command details.
620 APPC_AUDIT_MSG=APPC0090A|\
621 Operation "{0}" for VNF type "{1}" from Source "{2}" with RequestID "{3}" \
622 was started at "{4}" and ended at "{5}" with status code "{6}"|\
626 AAI_CONNECTION_FAILED=APPC0106E|\
627 APP-C is unable to communicate with A&AI|\
628 Connection to A&AI at service {0} failed after all retry attempts.|\
629 The connection to the A&AI at the indicated service URL cannot be opened. \
630 All retries have been exhausted. APP-C is giving up on the connection and will \
631 reject the operation request.|\
634 AAI_UPDATE_FAILED=APPC0107E|\
635 APP-C is unable to update COMPONENT_ID {0} to {1} for reason {2}|\
636 The update at the end of the operation wasn't performed as a result of \
637 A&AI communication failure or its internal error.|\
640 AAI_GET_DATA_FAILED=APPC0108E|\
641 APP-C is unable to retrieve VF/VFC {0} data for Transaction ID {1} as a \
642 result of A&AI communication failure or its internal error.|\
643 Operation request will be rejected by APP-C|\
646 AAI_CONNECTION_FAILED_RETRY=APPC0105W|\
647 A&AI at identity {0} using VNF_ID {1} failed, reason={2}, retrying in {3} seconds, attempt {4} of {5}.|\
648 The connection to the A&AI could not be obtained for the indicated reason. APP-C will retry to connect \
649 to the A&AI. The message contains the retry delay, the current attempt and the maximum number of attempts.|\
650 Correct the cause of the connection failure as indicated by the reason.
652 AAI_DELETE_FAILED=APPC0114E|\
653 APP-C is unable to delete COMPONENT_ID {0} for reason {1}|\
654 The deletion at the end of the operation wasn't performed as a result of \
655 A&AI communication failure or its internal error.|\
658 AAI_QUERY_FAILED=APPC0115E|\
659 Error Querying AAI with vnfID = {0}|\
660 Querying AAI for the given vnf id returns failure to APPC|\
663 VNF_CONFIGURED=APPC0118I|\
664 VNF {0} is configured|\
665 No resolution is required, this is an informational message|\
666 The VNF configuration has been completed.
668 VNF_CONFIGURATION_STARTED=APPC0116I|\
669 VNF {0} is being configured|\
670 No resolution is required, this is an informational message|\
671 The VNF configuration has been started
673 VNF_CONFIGURATION_FAILED=APPC0119E|\
674 VNF {0} configuration failed for reason {1}|\
675 The configuration operation wasn't performed as a result of VNF communication failure or its internal error.|\
678 VNF_TEST_STARTED=APPC0120I|\
679 VNF {0} is being tested|\
680 No resolution is required, this is an informational message|\
681 The VNF test has been started
683 VNF_TESTED=APPC0121I|\
685 No resolution is required, this is an informational message|\
686 The VNF test has been completed
688 VNF_TEST_FAILED=APPC0122E|\
689 VNF {0} test failed for reason {1}|\
690 The test operation wasn't performed as a result of VNF communication failure or its internal error.|\
693 VNF_NOT_FOUND=APPC0123E|\
694 VNF not found with vnf_id {0}|\
695 The VNF wasn't found for the given vnf-id.|\
698 VNF_HEALTHCECK_FAILED=APPC0124E|\
699 VNF {0} Healthcheck operation failed, reason {1}|\
700 The health check operation wasn't performed as a result of VNF communication failure or its internal error.|\
703 VM_HEALTHCECK_FAILED=APPC0125E|\
704 VM {0} Healthcheck operation failed, reason {1}|\
705 The health check operation wasn't performed as a result of VNF communication failure or its internal error.|\
708 STOP_SERVER_FAILED=APPC0112E|\
709 Server {0} (id {1}) failed to stop during {2} phase, reason {3}|\
710 The server stop failed for the indicated reason. Correct the cause of the failure and \
711 rerun, if applicable.|\
712 The adapter has attempted to stop the indicated server but the stop request has \
713 been failed by the provider for some reason. The reason returned by the provider is \
714 included in the message.
716 TERMINATE_SERVER_FAILED=APPC0113E|\
717 Server {0} (id {1}) failed to terminate during {2} phase, reason {3}|\
718 The server termination failed for the indicated reason. Correct the cause of the failure and \
719 rerun, if applicable.|\
720 The adapter has attempted to terminate the indicated server but the migration request has \
721 been failed by the provider for some reason. The reason returned by the provider is \
722 included in the message.
724 TERMINATE_STACK_FAILED=APPC0113E|\
725 Server {0} (id {1}) failed to terminate during {2} phase, reason {3}|\
726 The server termination failed for the indicated reason. Correct the cause of the failure and \
727 rerun, if applicable.|\
728 The adapter has attempted to terminate the indicated server but the migration request has \
729 been failed by the provider for some reason. The reason returned by the provider is \
730 included in the message.
732 TERMINATING_SERVER=APPC0114I|\
733 {0} IAAS Adapter terminate server requested|\
734 No resolution required|\
735 A graph has invoked the IAAS adapter and has requested the server to be terminated. The \
736 properties that govern the request are echoed immediately following this message.
739 TERMINATING_STACK=APPC0115I|\
740 {0} IAAS Adapter terminate stack requested|\
741 No resolution required|\
742 A graph has invoked the IAAS adapter and has requested the server to be terminated. The \
743 properties that govern the request are echoed immediately following this message.
745 TERMINATE_SERVER=APPC0116I|\
746 Server {0} is being terminated...|\
747 No recovery required|\
748 The processing being performed by APPC requires that the indicated server be terminated.
750 TERMINATE_STACK=APPC0117I|\
751 Stack {0} is being terminated...|\
752 No recovery required|\
753 The processing being performed by APPC requires that the indicated server be terminated.
755 MIGRATE_COMPLETE=APPC0118I|\
756 Migrate {0} finished with status {1}. Start Time: {2}. End Time: {3}. Request ID: {4}. Reason:{5}...|\
757 No resolution is required, this is an informational message|\
758 APP-C Migrate Operation has completed.
760 RESTART_COMPLETE=APPC0119I|\
761 Restart {0} finished with status {1}. Start Time: {2}. End Time: {3}. Request ID: {4}. Reason:{5}...|\
762 No resolution is required, this is an informational message|\
763 APP-C Restart Operation has completed.
765 REBUILD_COMPLETE=APPC0120I|\
766 Rebuild {0} finished with status {1}. Start Time: {2}. End Time: {3}. Request ID: {4}. Reason:{5}...|\
767 No resolution is required, this is an informational message|\
768 APP-C Rebuild Operation has completed.
770 CLOSE_CONTEXT_FAILED=APPC0121E|\
771 Exception {0} was caught attempting to close provider context for {1}.|\
772 Contact support for assistance|\
773 An exception was caught while trying to close the provider context. The \
774 exception may yield more information about the cause of the error. This may be because \
775 of access security, or the server is in an invalid state, or any number of reasons. This \
776 message should be referred to support for assistance.
778 SNAPSHOTING_STACK=APPC0122I|\
779 Stack {0} is being snapshoted...|\
780 No resolution is required|\
783 STACK_SNAPSHOTED==APPC0123I|\
784 Stack {0} snapshoted, snapshot ID = [{1}].|\
785 No resolution is required|\
786 Stack snapshoted successfully.
789 RESTORING_STACK=APPC0124I|\
790 Stack {0} is being restored to snapshot {1}...|\
791 No resolution is required|\
794 STACK_RESTORED=APPC0125I|\
795 Stack {0} is restored to snapshot {1}.|\
796 No resolution is required|\
797 Stack restored successfully.
799 MISSING_PARAMETER_IN_REQUEST=APPC0126E|\
800 Parameter {0} is missing in svc request of {1}.|\
801 Check DG node definition to pass missing parameter's value.|\
802 Node definition in DG missing indicated parameter value or value is incorrect, \
803 check the graph definition.
805 CANNOT_ESTABLISH_CONNECTION=APPC0127E|\
806 Cannot establish connection to server {0} port {1} with user {2}.|\
807 Check server IP, port and user credentials.|\
808 Wrong data sent in request's payload.
811 APPC_METRIC_MSG=APPC0128I|\
812 Operation "{0}" for VNF type "{1}" from Source "{2}" with RequestID "{3}" on "{4}" with action "{5}" \
813 ended in {6} ms with result "{7}"|\
814 No resolution is required, this is an informational message|\
815 This message indicates that the APPC logged some operation to metric
817 SNAPSHOTING_SERVER=APPC0129I|\
818 {0} IAAS Adapter create snapshot of server requested|\
819 No resolution is required, this is an informational message|\
820 This message indicates that a IAAS Adapter create snapshot of server was requested.
822 INPUT_PAYLOAD_PARSING_FAILED = APPC0130E|\
823 Failed to parsing the input payload: {0}|\
824 Please provide correct input string for parsing.|\
827 APPC_EXCEPTION = APPC0132E|\
828 Error occurred for VNF type : {0}, reason {1}|\
829 Runtime exception thrown by APPC.|\
832 SSH_DATA_EXCEPTION = APPC0133E|\
833 SSH Data Exception occurred, reason {0}|\
834 SSH Data exception occurred.|\
837 JSON_PROCESSING_EXCEPTION = APPC0134E|\
838 Json processing exception occurred, reason {0}|\
839 Json processing Exception|\
842 SUCCESS_EVENT_MESSAGE = APPC0136I|\
843 Operation {0} succeed for {1}|\
846 DEPENDENCY_MODEL_NOT_FOUND = APPC0137E|\
847 Dependency model not found for VNF type {0}, reason {1}|\
848 Please provide dependency model|\
851 INVALID_DEPENDENCY_MODEL = APPC0138E|\
852 Invalid Dependency model for VNF Type {0}, reason {1}|\
853 Invalid dependency model found |\
857 FAILURE_RETRIEVE_VNFC_DG = APPC0139E|\
858 Failed to retrieve DG for VNFC Type: {0}|\
859 Failed to retrieve VNFC DG |\
863 SERVER_NETWORK_ERROR=APPC0140E|\
864 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|\
865 Please ensure they are UP and running before requested operation|\
866 It is critical that the VM Server is reachable by the Provider(ex: OpenStack) in order to be able to perform \
867 the requested operation on it.
870 REBUILD_SERVER=APPC0140I|\
871 Server {0} is being rebuilt...|\
872 No recovery required|\
873 The processing being performed by APPC requires that the indicated server be rebuilt.
875 HYPERVISOR_DOWN_ERROR=APPC0141E|\
876 Hypervisor {0} for the Server {1} is either NOT ENABLED, or its status is DOWN or UNKNOWN|\
877 Please ensure the Hypervisor is UP and running before proceeding with the requested operation|\
878 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 \
879 the requested operation on it.
882 HYPERVISOR_STATUS_UKNOWN=APPC0158E|\
883 Unable to determine the status of the Hypervisor for the Server {0} |\
884 Please ensure the userid has privileges enabled to query for the Hypervisor status. |\
885 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.
888 HYPERVISOR_NETWORK_ERROR=APPC0142E|\
889 Hypervisor {0} for the Server {1} is NOT Reachable by APPC for initiating the requested operation|\
890 Please ensure the Hypervisor is connected to the network before proceeding with the requested operation|\
891 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 \
892 the requested operation on it.
894 EVACUATE_SERVER_REBUILD_FAILED=APPC0143E|\
895 Server {0} evacuate from host {1} to host {2} failed during the rebuild on host {2}, reason {3}|\
896 The server rebuild after evacuation failed for the indicated reason. Correct the cause of the failure and \
897 run a rebuild, if applicable.|\
898 The adapter has attempted to rebuild after evacuating the indicated server but the rebuild request has \
899 been failed by the provider for some reason. The reason returned by the provider is \
900 included in the message.
902 RESTART_APPLICATION=APPC0144I|\
903 Application on server {0} is being restarted...|\
904 No recovery required|\
905 The processing being performed by APPC requires that the application on the indicated server be restarted.
907 START_APPLICATION=APPC0145I|\
908 Application on server {0} is being started...|\
909 No recovery required|\
910 The processing being performed by APPC requires that the application on the indicated server be started.
912 APPLICATION_RESTART_FAILED=APPC0146E|\
913 Restart application operation failed on server : {0}, reason {1}|\
914 Restart application operation failure.|\
915 Correct the cause of the failure as indicated by the reason.
917 APPLICATION_START_FAILED=APPC0147E|\
918 Start application operation failed on server : {0}, reason {1}|\
919 Start application operation failure.|\
920 Correct the cause of the failure as indicated by the reason.
922 LOOKING_SERVER_UP=APPC0148I|\
923 {0} IAAS Adapter looking up for the server requested|\
924 No resolution is required, this is an informational message|\
925 This message indicates that a IAAS Adapter lookup of server was requested.
927 EVACUATE_SERVER_REBUILD_FAILED=APPC0149E|\
928 Server {0} evacuate from host {1} to host {2} failed during the rebuild on host {2}, reason {3}|\
929 The server rebuild after evacuation failed for the indicated reason. Correct the cause of the failure and \
930 run a rebuild, if applicable.|\
931 The adapter has attempted to rebuild after evacuating the indicated server but the rebuild request has \
932 been failed by the provider for some reason. The reason returned by the provider is \
933 included in the message.
935 APPLICATION_STOP_FAILED=APPC0150E|\
936 Stop application operation failed on server : {0}, reason {1}|\
937 Stop application operation failure.|\
938 Correct the cause of the failure as indicated by the reason.
940 STOP_APPLICATION=APPC0151I|\
941 Application on server {0} is being stopped...|\
942 No recovery required|\
943 The processing being performed by APPC requires that the application on the indicated server be stopped.
945 LCM_OPERATIONS_DISABLED=APPC0152E|\
946 APPC LCM operations have been administratively disabled|\
947 No recovery required|\
948 This is a indication that the APPC LCM operations are disabled.
950 OAM_OPERATION_EXCEPTION=APPC0153E|\
951 Application {0} received exception {1} while attempting to execute oam operation {2}, exception message = {3}|\
952 The application controller attempted to perform an OAM operation \
953 but an exception was caught. The class of the \
954 exception is shown, as is the message associated with the exception. An \
955 abbreviated stack trace is also displayed to provide information as to the \
956 state of the thread at the time of the exception.|\
957 Correct the cause of the exception and rerun.
959 OAM_OPERATION_STOPPING=APPC0154W|\
960 Application {0} is stopping... |\
961 No recovery required|\
962 The APPC will no longer accept new LCM requests. Previously accepted LCM requests will be allowed to complete.
964 OAM_OPERATION_STOPPED=APPC0155W|\
965 Application {0} is stopped|\
966 No recovery required|\
967 The APPC is not accepting new LCM requests and all previously accepted LCM requests have completed.
969 OAM_OPERATION_STARTING=APPC0156I|\
970 Application {0} is starting...|\
971 No recovery required|\
972 The APPC has initiated its startup procedure. Its internal components are coming online. Once completed it will start accepting LCM requests. \
974 OAM_OPERATION_STARTED=APPC0157I|\
975 Application {0} is started|\
976 No recovery required|\
977 The APPC will now accept new LCM requests for processing.