C.1 CNC Console Validation-hook Error Codes

A preinstall hook named Validation-hook is introduced for validating M-CNCC Core and A-CNCC Core helm configurations.

Validation hook pod is auto deleted if validation succeeds. In case of failure, pod status is displayed as" Error.

In case of Validation-hook errors, refer to the following error codes:

Table -6 Validation-hook Error Codes

Error Code Error Message Format Error Scenarios Sample Error Messages
1001 Invalid value. Resource: <Configuration Name>, ID: <ID>, Attribute: <Attribute>. <More Info>
  • Port should be Numeric
  • Scheme should be either HTTP/HTTPS
  • IDs should follow the alphanumeric pattern
  • Max Limit should be satisfied for M-CNCC IAM, A-CNCC and Instance
  • Max Length for Instance Id
  • Max Length for Self Cncc Id
  • CS instance must have one of these CS subtypes <grafana, kibana, jaeger, prometheus, alertmanager>
  • DD instances must have one of these subtypes <ocnadd, ocnaddapi>
  • NWDAF instances must have one of these subtypes <ocnwdaf, ocnwdafapi>
  • Both ip and fqdn cannot be provided.
  • InvalidConfig
  • multicluster flag should be false in case of single-cluster deployment
    • cncc-iam, mcncc-core, acncc-core flags should be set to true
  • multicluster flag should be true in case of multi-cluster deployment
    • Multi Cluster(manager only) - cncc-iam, mcncc-cncc should be set to true and acncc-core should be set to false
    • Multi Cluster(managing local NF's) - cncc-iam, mcncc-cncc and acncc-core should be set to true.
    • Multi cluster(agent only) - cncc-iam, mcncc-cncc should be set to false and acncc-core should be set to true
  • multicluster flag should be false in case of single-cluster deployment
  • multicluster flag should be true in case of multi-cluster deployment
  • there must be 2 DD instances with same instance id (one with type DD-UI and the other with DD-API)
  • there must be 2 NWDAF instances with same instance id (one with type NWDAF-UI and the other with NWDAF-API)
  • NF type should be present along with cnDBTier instance
  • Each NF can have a maximum of 2 instances with same instance ID, one of which must have type cnDBTier

Invalid value. Resource: mCnccIam, ID: Cluster1, Attribute: Port. It should be numeric value.

Invalid value. Resource: instance, ID: Cluster3-instance1, Attribute: Scheme. Allowed values are: [http, https].

Invalid value. Resource: instance, ID: Cluster1-grafana##$$%, Attribute: id. Ids should be alphanumeric with hyphen allowed as special character.

The count of mCnccIam exceeded max limit. Allowed Value:x. Actual Value: y

Max limit exceeded. Allowed Value:x. Actual Value: y

Invalid value. Resource: aCncc, ID: Cluster3, Attribute: N/A. Both ip and fqdn cannot be provided.

Invalid value. Resource: isMultiClusterEnabled, ID:,Attribute: False.

isMultiClusterEnabled is set as false, only single cluster configuration is allowed. Verify cncc-iam, mcncc-core, acncc-core configuration values

Invalid value. Resource: isMultiClusterEnabled, ID:,Attribute: True.

isMultiClusterEnabled is set as true, only multi cluster configuration is allowed. Verify cncc-iam, mcncc-core, acncc-core configuration values

Invalid value. Resource: isMultiClusterEnabled, ID:,Attribute: False.

isMultiClusterEnabled is set as false, only single cluster configuration is allowed.

Invalid value. Resource: isMultiClusterEnabled, ID:,Attribute: True.

isMultiClusterEnabled is set as true, only multi cluster configuration is allowed.

Invalid value. Resource: DD, ID: Cluster1-dd-instance1, Attribute: N/A. More than one DD instance with same id and type is not allowed

Invalid value. Resource: instance, ID: Cluster1-dd-instance1, Attribute: apiPrefix. For type DD valid Api Prefixes: [/ocnadd, /ocnaddapi]

Invalid value. Resource: NF, ID: Cluster1-instance1, Attribute: N/A. NF type should be present along with cnDBTier instance
1002 Duplicate value. Resource: <Configuration Name>, ID: <ID>, Attribute: <Attribute>. <More Info>
  • All A-CNCC IDs must be unique
  • API prefix must be unique for all instances
  • Owner(Cluster) must have unique CS/DD/NWDAF subtype
  • Duplicate value(s). Resource: aCncc, ID: [Cluster3], Attribute: id.
  • Duplicate value(s). Resource: instance, ID: N/A, Attribute: apiPrefix. Duplicate Attribute values: [/occne12-ip-cluster/ocnadd] for owner: Kolkata
1003 Invalid Reference. Resource: <Configuration Name>, ID: <ID>, Attribute: <Attribute>. <More Info>
  • All the Instance owners must be referenced in M-CNCC IAM IDs or A-CNCC IDs
  • M-CNCC IAM IDs and M-CNCC Core IDs must be same
  • Invalid Reference. Resource: instance, ID: Cluster5, Attribute: Owner. Not present in mCncc ids or aCncc ids.
  • Invalid Reference. Resource: instance, ID: N/A, Attribute: N/A. M-Cncc Iam ids and M-Cncc Core ids do not match.
1004 Missing value. Resource: <Configuration Name>, ID: <ID>, Attribute: <Attribute>. <More Info>
  • Missing apiPrefix parameter for type CS, DD-UI, DD-API, NWDAF-UI, or NWDAF-API
  • Either of IP/FQDN should be present(Manager)
  • SelfCnccId should be present
  • Missing value. Resource: instance, ID: Cluster4-grafana, Attribute: apiPrefix.
  • Missing value. Resource: instance, ID: Cluster3-PolicyInstance, Attribute: N/A. Either ip or fqdn is required.