update from RIFT as of 696b75d2fe9fb046261b08c616f1bcf6c0b54a9b third try
[osm/UI.git] / skyquake / framework / widgets / skyquake_notification / netConfErrors.js
1 const NETCONF_ERRORS = {
2 'in-use' : {
3 description: 'The request requires a resource that already is in use.'
4 },
5 'invalid-value' : {
6 description: 'The request specifies an unacceptable value for one or more parameters.'
7 },
8 'too-big' : {
9 description: 'The request or response (that would be generated) is too large for the implementation to handle.'
10 },
11 'missing-attribute' : {
12 description: 'An expected attribute is missing.'
13 },
14 'bad-attribute' : {
15 description: 'An attribute value is not correct; e.g., wrong type, out of range, pattern mismatch.'
16 },
17 'unknown-attribute' : {
18 description: 'An unexpected attribute is present.'
19 },
20 'missing-element' : {
21 description: 'An expected element is missing.'
22 },
23 'bad-element' : {
24 description: 'An element value is not correct; e.g., wrong type, out of range, pattern mismatch.'
25 },
26 'unknown-element' : {
27 description: 'An unexpected element is present.'
28 },
29 'unknown-namespace' : {
30 description: 'An unexpected namespace is present.'
31 },
32 'access-denied' : {
33 description: 'Access to the requested protocol operation or data model is denied because authorization failed.'
34 },
35 'lock-denied' : {
36 description: 'Access to the requested lock is denied because the lock is currently held by another entity.'
37 },
38 'resource-denied' : {
39 description: 'Request could not be completed because of insufficient resources.'
40 },
41 'rollback-failed' : {
42 description: 'Request to roll back some configuration change (via rollback-on-error or <discard-changes> operations) was not completed for some reason.'
43 },
44 'data-exists' : {
45 description: 'Request could not be completed because the relevant data model content already exists. For example, a "create" operation was attempted on data that already exists.'
46 },
47 'data-missing' : {
48 description: 'Request could not be completed because the relevant data model content does not exist. For example, a "delete" operation was attempted on data that does not exist.'
49 },
50 'operation-not-supported' : {
51 description: 'Request could not be completed because the requested operation is not supported by this implementation.'
52 },
53 'operation-failed' : {
54 description: 'Request could not be completed because the requested operation failed for some reason not covered by any other error condition.'
55 }
56 }
57
58 export default NETCONF_ERRORS;