SPK CWC Log Message List¶

Log Message Reference for None

ID Number	Description
06170000	Error listing configMap in namespace
06170001	Error listing configMap in namespace
06170002	failed to list ConfigMaps
06170003	Failed updating configMap in namespace
06170004	Failed to fetch incluster config
06170005	Error in creating clientset
06170006	Error in creating gateway clientset
06170007	Error in creating f5clientset
06170008	Failed to fetch clientset
06170009	Failed to fetch context
0617000a	Started running ClusterInfoDump command
0617000b	Failed at running ClusterInfoDump command
0617000c	failed to create helm version data file in
0617000d	Cluster info is dumped
0617000e	helm.sh is not present in the deployment
0617000f	deployments in the namespace '%s', do not have helm version information.
06170010	error marshalling helmVersiondata: %v
06170011	failed to write helm version data to file %v
06170012	Error getting tmm pod list
06170013	Started describing
06170014	Failed to match version in kube config flags
06170015	Failed to describe
06170016	Completed describing kind with name
06170017	Failed to fech namespace
06170018	Failed to get list of namespaces
06170019	Started running APIresources command
0617001a	Failed at running APIresources command
0617001b	Creating the secret
0617001c	Creating the secret
0617001d	Updating the secret
0617001e	Error in creating/updating secret with given name
0617001f	Error in reading secret
06170020	Failed to get pods in namespace
06170021	product version is present in pod
06170022	Start PodIP and ipFamilyPolicyPreferIPV6 is:
06170023	Prefered PodIP is:
06170024	Failed to create AMQP
06170025	Successfully connected to rabbitmq
06170026	Failed to Setup CPCL
06170027	Failed to get status
06170028	Registering device failed
06170029	Failed to update configmap
0617002a	Failed to activate JWT
0617002b	Received ignorable error in activating JWT
0617002c	failed to get status
0617002d	error in unmarshaling
0617002e	Failed to get status
0617002f	Failed to get status
06170030	Failed to send telemetry report
06170031	Received ignorable error in handling configreport
06170032	Failed to get status
06170033	Failed to activate license
06170034	Received ignorable error in ack verification
06170035	Failed to activate licnese
06170036	Received ignorable error in ack verification
06170037	Failed to get status
06170038	Failed to send telemetry report
06170039	Received ignorable error in handling configreport
0617003a	Failed to get status
0617003b	Failed to verify telemetry report
0617003c	Received ignorable error in handling configreport
0617003d	Pod deleted in middle of telemetry generation. Generating Report again
0617003e	Pod deleted in middle of updating current report. Updating current report
0617003f	Pod deleted in middle of updating telemetry status. Updating telemetry status
06170040	Pod deleted in middle of setting telemetry ready state. Setting ready state
06170041	Pod deleted in middle of re-initializing next report. Re-initializing now
06170042	Telemetry is not yet initialized
06170043	Telemetry initialization done
06170044	Pod was deleted on random day within month before report generation
06170045	Pod was deleted on month end before report generation
06170046	Pod was deleted on month end after report generation
06170047	On startup, state, context, current periodic telemetry are as follows
06170048	Registering device failed
06170049	Received device registration complete state
0617004a	Config Report is ready to download
0617004b	Verification Successful
0617004c	Failed to Inform SPK Controllers on License Status.
0617004d	Nothing to do for now!!
0617004e	Received license expiry notification
0617004f	Failed to Inform SPK Controllers on License Status.
06170050	Received public key expiry notification
06170051	failed to collect telemetry report
06170052	failed to store observation start and end times in secret
06170053	failed to collect telemetry report
06170054	failed to send telemetry report
06170055	Received license expiring notification
06170056	Received certificate expiring notification
06170057	[Mock] Unable to parse licenseExpiryDate
06170058	[Mock] Using license expiry date for mock notifications
06170059	[Mock] Failed to parse license expiry date
0617005a	[Mock] Expiring soon triggers in
0617005b	[Mock] Triggering 'expiring soon' notification now
0617005c	[Mock] Expiring today triggers in
0617005d	[Mock] Triggering 'expiring today' notification now
0617005e	[Mock] Expired triggers in
0617005f	[Mock] Triggering 'expired' notification now
06170060	State is being changed
06170061	Failed to marshall context to string
06170062	Storing context
06170063	Read context
06170064	Error in getting telemetry string
06170065	Storing license status to secret
06170066	Failed to store license status to secret
06170067	Failed to read license status secret store. Context %s, error %s
06170068	Failed to unmarshal license status secret store. Context %s, error %s
06170069	Error in marshling telemetry status
0617006a	Storing telemetry status to secret
0617006b	Failed to store telemetry status to secret
0617006c	Failed to read telemetry status secret store.
0617006d	Failed to unmarshal telemetry status secret store
0617006e	Failed to store license status.
0617006f	License Status read during setup.
06170070	Failed to store license status.
06170071	Failed to store license status.
06170072	Failed to store license status.
06170073	Failed to parse license status date.
06170074	Failed to parse entitlement expiry date.
06170075	License expiry date is extended update the license status.
06170076	Failed to store license status with updated expiry date.
06170077	License expiry date is sucessfully updated post subscription renewal.
06170078	Failed to store license status.
06170079	Failed to store license status.
0617007a	Failed to store telemetry status
0617007b	Telemetry Status read during setup. state %s, errCode %s, errString %s, action %s
0617007c	Failed to store telemetry status
0617007d	Failed to store telemetry status
0617007e	Failed to store telemetry status
0617007f	Failed to store telemetry status
06170080	Failed to store telemetry status
06170081	Failed to store telemetry status
06170082	Failed to store telemetry status
06170083	Failed to store telemetry status
06170084	Failed to read context.
06170085	Failed to store context
06170086	Status copied to ContextNone
06170087	Error in getting telemetry string
06170088	Changing the context
06170089	Changing the error
0617008a	Changing error message
0617008b	failed to delete CPCL config map
0617008c	failed to delete CWC state config map
0617008d	failed to delete CWC QKview config map
0617008e	failed to delete CWC QKview config map
0617008f	The license will expire soon. If it is already renewed, pls ignore this message.
06170090	License is expiring today. If it is already renewed, pls ignore this message.
06170091	License expired. If renewal is done, please upload the telemetry report.
06170092	Report is ready to download.
06170093	Please upload an acknowledgement for the telemetry report.
06170094	Timer fired, calling updateTelemetry
06170095	Skipping the telemetry due to current context
06170096	Error storing reports in secret
06170097	failed to collect telemetry report
06170098	Failed to read configuration
06170099	Failed to build config
0617009a	Failed to create new license server
0617009b	SendReport is no longer supported for InitialRegistration and SwitchLicense
0617009c	failed to download config report
0617009d	failed to download telemetry report
0617009e	failed to update configmap
0617009f	Re-Registering device failed
061700a0	failed to update configmap
061700a1	Error in reading ConfigMap
061700a2	Read info
061700a3	Read info
061700a4	TEEM Cert URL
061700a5	TEEM Entitlement URL
061700a6	TEEM Initial Config URL
061700a7	Mode is configured
061700a8	LicenseServer Root CA Refer Location
061700a9	LicenseServer Root CA Refer Location
061700aa	LicenseServer Root CA
061700ab	Failed to activate
061700ac	Received ignorable error in initial activation callback
061700ad	Activation successful
061700ae	failed to update configmap
061700af	Config Report prepared by CPCL, ready to download
061700b0	Failed to send telemetry report
061700b1	Received ignorable error in initial config report callback
061700b2	Failed to send telemetry report
061700b3	Received ignorable error in initial config report callback
061700b4	Config Report prepared by CPCL, ready to download
061700b5	Failed to verify signature
061700b6	Received ignorable error in verify signature callback
061700b7	Failed to verify signature
061700b8	Received ignorable error in verify signature callback
061700b9	Signature verification successful
061700ba	failed to read configmap.
061700bb	failed to update configmap
061700bc	Failed to start telemetry
061700bd	Received license expiring notification
061700be	Received certificate expiring notification
061700bf	message
061700c0	message
061700c1	message
061700c2	message
061700c3	Rotating Cert Chain
061700c4	Failed to update config map
061700c5	Error creating new jobId
061700c6	Failed to Create Request Payload for Debug API request message
061700c7	Error publishing Debug API request message
061700c8	Published Debug API request message
061700c9	DEBUG: Timeout/Purge ticker is already running
061700ca	DEBUG: Failed to get list of tmm pod IDs
061700cb	DEBUG: Failed to get tmm pod id list, setting ExpectedRespCnt as ErrTmmPodCnt
061700cc	DEBUG: Starting the ticker for job timeout/purge
061700cd	DEBUG: Stopping the ticker of job timeout/purge
061700ce	Nothing to do for now!!
061700cf	No debug jobs currently to check for purge
061700d0	DEBUG: Setting OperationStop for job timeout/purge ticker to stop with no debug util jobs in the queue
061700d1	DEBUG: error while parsing payload to JobDataDebugUtil
061700d2	DEBUG: Request with the job ID has timed out
061700d3	DEBUG: Request with job ID has expired
061700d4	DEBUG: Setting OperationStop for job timeout/purge ticker to stop with no debug util jobs in the queue
061700d5	Adding new job
061700d6	DEBUG: Setting OperationStart for job timeout/purge ticker to start with current number of debug jobs in the queue 1
061700d7	DEBUG: error while parsing debug util job data
061700d8	Response received from tmmId after the request timeout
061700d9	DEBUG: Updating job
061700da	DEBUG: Adding new tmm response
061700db	DEBUG: Job Completes!
061700dc	ParseJobDataDebugUtil unmarshall error
061700dd	DEBUG: Succeeded in getting tmm pod id list, setting ExpectedRespCnt
061700de	Deleting the job data from the job queue
061700df	Deleted the job data from the job queue
061700e0	Deleting the qkview job from the job queue
061700e1	Deleting the qkview jobs started
061700e2	Deleted the qkview jobs
061700e3	Reset ConfigMap to empty state
061700e4	Failed to marshal log levels to YAML
061700e5	logAction
061700e6	msg
061700e7	msg
061700e8	msg
061700e9	fluentbitEnabled: %s
061700ea	Error listening on connection
061700eb	Listening on
061700ec	probe: Signal received to stop probe server for readiness probe
061700ed	probe: error in accepting connection
061700ee	probe: server accepted connection
061700ef	probe: Monitoring probe health
061700f0	probe: stopping probe server
061700f1	probe: server stopped successfully.
061700f2	probe: probe server already running.
061700f3	probe: Checking Rabbit MQ connection status
061700f4	probe: Rabbit MQ connection is nil
061700f5	probe: Rabbit MQ Queue is nil
061700f6	probe: Connection and Queue object are not nil
061700f7	probe: TCP server is stopped
061700f8	probe: TCP server is running
061700f9	Failed to copy directory
061700fa	Failed to copy file
061700fb	File removed successfully
061700fc	message
061700fd	message
061700fe	File/dir removed successfully
061700ff	Handling dssm services
06170100	Failed to run cat cmd
06170101	Container Linux flavour detected
06170102	Found DSSM service in Pod env variables
06170103	DSSM service data will be collected: %s
06170104	Error in dssm handle
06170105	describing output of %s in %s is successful\n
06170106	Error in getting api resources from given namespace
06170107	Getting details of api resource is successful
06170108	collecting kind
06170109	Failed in getting api resources list for given namespace
0617010a	No resources found in given namespace
0617010b	Error getting details of api resources from given namespace
0617010c	Getting details of api resource is successful
0617010d	collecting mrfdb output for %v via %v/%v\n
0617010e	Error during collecting DSSM data %v via %v/%v\n
0617010f	collecting cluster info
06170110	Failed to dump cluster info
06170111	Copying file from folder
06170112	Failed to copy file
06170113	Failed in handling container folders
06170114	collecting pod in namespace
06170115	collecting pod in namespace is done
06170116	collecting namespace
06170117	No pods found in given namespace
06170118	Pods found
06170119	Error in Handling pod
0617011a	Container logs were written to path
0617011b	Collecting objects per namespace
0617011c	Error in collecting objects per namespace
0617011d	Collecting namespace is done
0617011e	Started creating file
0617011f	Started handling namespace
06170120	Creating a directory to store cluster level objects
06170121	Collecting objects per cluster level
06170122	Error in DumpClusterInfo
06170123	Creating directory
06170124	Creating file
06170125	error in creating file
06170126	ParseJobDataQkview unmarshall error
06170127	ParseJobDataQkview: JobDataQkview that is being unmarshalled input.FileLocation
06170128	DEBUG: Error accessing shared location
06170129	Adding new job
0617012a	Error while getting info about containers
0617012b	Container details to collect qkview
0617012c	failed creating cluster-info tar.gz
0617012d	Qkview create request failed
0617012e	Completed POST Qkview request
0617012f	Error creating new jobId
06170130	DEBUG: this is non ideal and never should enter in to this scenario as only one qkview job should be in progress at a given instant
06170131	error occured during the job details update in configmap
06170132	Updated the qkview details in configmap
06170133	deleting the qkview tar folder for the job
06170134	deleting the qkview tar folder from path
06170135	Error: qkview tar folder deletion failed for the job
06170136	deleting the tar folders for the qkview jobs
06170137	deleting the qkview tar folder from path
06170138	errMsg
06170139	v1 qkview API returning http error response
0617013a	failed to read metadata header from download stream
0617013b	missing filename metadata in download stream
0617013c	missing file size metadata in download stream
0617013d	failed to receive data from download stream
0617013e	failed to write response to response writer
0617013f	Error closing gw
06170140	Error closing tw
06170141	crawling
06170142	CreateMessage: Message that is being marshalled
06170143	ParseMessage unmarshall error
06170144	ParseMessage: Message that is being unmarshalled
06170145	Initializing AMQP ...
06170146	bind keys
06170147	bind keys
06170148	bind keys
06170149	bind keys
0617014a	exchange name
0617014b	failed to setup exchange
0617014c	exchange name
0617014d	Failed to Parse Public key response msg
0617014e	Retreived latest public key version
0617014f	Failed to create Public key response msg
06170150	Failed to parse the Public Key request
06170151	Received Public Key request for version
06170152	Latest public key sent
06170153	Failed to publish the Public Key response
06170154	CreatePubKeyResponseMessage key
06170155	ParseAndVerifyPubKeyResponseMessage Output public Key and version
06170156	ParsePubKeyResponseMessage Output public Key and version
06170157	HandlePubKeyResponse: Signed Version and Version Stored Locally
06170158	mismatch of sign version expected and response received signed with public key version
06170159	Failed to parse the Public Key response
0617015a	Received invalid PubKey response message
0617015b	ResponsePubKeyLatestKey failed ParseRsaPublicKeyFromPemStr
0617015c	New Public Key version saved
0617015d	CreatePubKeyEventMessage key version and signVersion
0617015e	CreatePubKeyEventMessage for Public key version
0617015f	Curr Public Key version saved
06170160	ParseAndVerifyPubKeyEventMessage
06170161	Curr Public Key version saved
06170162	ParsePubKeyEventMessage
06170163	HandlePubKeyEvent: Signed Version: and Version Stored Locally
06170164	mismatch of sign version expected and received signed with public key version
06170165	Failed to parse the Public Key event message
06170166	Received invalid PubKey Event message
06170167	EventPubKeyLatestKey failed ParseRsaPublicKeyFromPemStr
06170168	New Public Key version saved
06170169	sendLatestPublicKeyRequests
0617016a	failed to create Public Key request
0617016b	failed to publish Public Key request
0617016c	Initialize AMQP
0617016d	Failed to load client cert and key
0617016e	Failed to establish connection to rabbitmq server
0617016f	error: failed to open connection
06170170	error: failed to open channel
06170171	DEBUG: bindingKeys
06170172	error: failed to declare exchange
06170173	error: failed to declare queue
06170174	publishing exchange with binding key
06170175	Key rotate timeout
06170176	Rotating Keypair - Parsing private key PEM failed
06170177	rotateAndNotifyPubKey version
06170178	Failed to Create Event Payload for Notifying Public Key.
06170179	Publishing Public Key event message to SPK Controllers
0617017a	Failed to publish the message
0617017b	GetKeySignature: received private key as nil
0617017c	writing msgHash failed
0617017d	SignPSS failed
0617017e	VerifySignature: received public key as nil
0617017f	writing msgHash failed
06170180	VerifyPSS failed
06170181	Creating CM20 Response
06170182	Creating CM20 Response
06170183	Failed to publish the entitlement response
06170184	GetEntitlementRequest received with a pub key version different to that of latest private key with CWC. Signing with latest private key
06170185	ParseCM20ResponseMessage: Received Invalid request
06170186	HandleCM20Response: Signed Version and Version Stored Locally
06170187	mismatch of request, response CM20 version
06170188	HandleCM20Event: Signed Version and Version Stored Locally
06170189	mismatch of request, response CM20 version
0617018a	failed to create Public CM20 request
0617018b	Failed to publish message
0617018c	Failed to Create Event Payload for License Verification
0617018d	Publishing event message to SPK Controllers
0617018e	Failed to publish the message
0617018f	Failed to Create Event Payload for Heartbeat
06170190	Error publishing heartbeat message
06170191	====> Published heartbeat message
06170192	recevied error while parsing msg body
06170193	Received ServiceTypeCM20 Request message
06170194	Received ServiceTypePubKey Request message
06170195	Received ServiceTypeDebug Respons message
06170196	Received Invalid messages with
06170197	Failed to create AMQP.
06170198	Successfully Created and Initialised AMQP
06170199	Failed to create channel
0617019a	Failed to consume the message
0617019b	Connection to RabbitMQ lost, Reconnecting ...
0617019c	Failed to acknowledge the message
0617019d	A handler is called with an method that is not supported, only POST is supported
0617019e	DEBUG: received params
0617019f	Final command to run
061701a0	failure occured
061701a1	POST call completed
061701a2	qkview job is already running
061701a3	PV storage is full
061701a4	warningStr
061701a5	POST call completed
061701a6	A handler is called with an method that is not supported, only GET is supported
061701a7	DEBUG: Please try the endpoint /debug/home for debug-api help...
061701a8	Error getting jobdata
061701a9	Error: job id does not exist
061701aa	DEBUG: error while parsing debug util job data
061701ab	GET call completed
061701ac	GET call completed
061701ad	Unsupported command
061701ae	IPv4 Address is valid
061701af	IPv4 Address is invalid.
061701b0	IPv6 Address is valid.
061701b1	IPv6 Address is invalid.
061701b2	Tcpdump Params are valid.
061701b3	Tcpdump Params are invalid.
061701b4	Configview Params are Valid.
061701b5	Configview Params are Invalid.
061701b6	Lsndb Params are Valid.
061701b7	Lsndb Params are Invalid.
061701b8	Bdtcli Params are Valid.
061701b9	bdtcli Params are Invalid.
061701ba	Mrfdb Params are Valid.
061701bb	Mrfdb Params are Invalid.
061701bc	Setloglevel Params are valid.
061701bd	Setloglevel Params are Invalid.
061701be	A handler is called with an method that is not supported, only GET is supported
061701bf	failed to retrieve CWC state for the response
061701c0	GET %v completed
061701c1	handler is supported only in disconnected mode
061701c2	A handler is called with an method that is not supported, only GET is supported
061701c3	failure occured in report
061701c4	GET call completed
061701c5	handler is supported only in disconnected mode
061701c6	A handler is called with an method that is not supported, only POST is supported
061701c7	failure occured in receipt handler
061701c8	POST call completed
061701c9	A handler is called with an method that is not supported, only POST is supported
061701ca	failure occured in reactivate
061701cb	POST call completed
061701cc	A handler is called with an unsupported method
061701cd	handler getting jobId from URI
061701ce	Handler is called with invalid parameter.
061701cf	GET call completed
061701d0	Unable to get the file path
061701d1	Unable to download the file from the path
061701d2	Qkview job has failed
061701d3	no job found with the filters
061701d4	Qkview job deletion failed at jobQueue for job Id
061701d5	Qkview job deletion failed at configmap for job Id
061701d6	Qkview job not found with Id
061701d7	Qkview tar file deletion failed for job Id
061701d8	Qkview deletion completed for jobId
061701d9	Qkview jobs deletion started
061701da	Qkview job deletion failed at configmap for job Id
061701db	Qkview jobs deletion is not successful from configmap
061701dc	Qkview jobs deletion completed
061701dd	filters passed
061701de	job for the filters
061701df	no job found with the filters
061701e0	Finding latest qkview job
061701e1	latest job details
061701e2	Starting mTLS Rest API Server on port 38081
061701e3	Rest API Server stopped
061701e4	Error while fetching deployment list. Error %s
061701e5	Error while fetching daemonset list. Error %s
061701e6	TMM is created as deployment
061701e7	TMM is created as daemonset
061701e8	Error in fetching deployment details from cluster
061701e9	Watch namespaces in the cluster are
061701ea	Error in fetching CRs from watch namespaces
061701eb	Watch namespace have CRs
061701ec	No CRs configured in watch namespace
061701ed	error in fetching pods
061701ee	Error in fetching k8s version
061701f0	Fetching deployment environment variables from containers
061701f1	watch namespace fetched from deployment
061701f2	Error in fetching node list, ignore if not applicable.
061701f3	Failed to create telemetryreports secret
061701f4	Telemetry reports not equal on field name '%v:%v' (%v != %v)
061701f5	Telemetry reports not equal on field name '%v' (%v != %v)
061701f6	Telemetry reports not equal on field name '%v ReplicaCount:%v' (%v != %v)
061701f7	Telemetry reports not equal on field name '%v ThreadCount:%v' (%v != %v)
061701f8	ERROR in unmarshalling json
061701f9	ERROR in unmarshalling CPU metric data in bytes
061701fa	ERROR in marshalling CRD metric data to bytes
061701fb	ERROR in unmarshalling CRD metric data in bytes
061701fc	ERROR in marshalling TMM metric data to bytes
061701fd	ERROR in unmarshalling TMM metric data in bytes
061701fe	ERROR in marshalling DPU metric data to bytes
061701ff	ERROR in unmarshalling DPU metric data in bytes
06170200	Error reading configmap
06170201	Error marshalling DPU details
06170202	ERROR in getting report
06170203	Error in storing to secret
06170204	ERROR in storing reports in secret
06170205	Failed to read telemetryreports secret store
06170206	Failed to unmarshal telemetry status secret store
06170207	ERROR in Marshling telemetry reports
06170208	Storing telemetry reports to secret
06170209	Failed to store telemetry reports to secret
0617020a	ERROR in storing reports in secret
0617020b	Error in storing reports in secret
0617020c	Error in storing reports in secret
0617020d	Error in fetching cluster nodes
0617020e	Error fetching specific node
0617020f	Successfully fetched allowed nodes
06170210	Fetching specific nodes from allowed nodes
06170211	Duplicate node in ALLOWED_NODES_CSV skipped

Log Message Details

06170000 : Error listing configMap in namespace

sev: Error

Type: Application

args:

error
configMap
namespace

cause: Cannot retrieve ConfigMap from specified namespace

workaround: Verify ConfigMap exists and pod has read permissions

06170001 : Error listing configMap in namespace

sev: Error

Type: Application

args:

error
configMap
namespace

cause: Error listing ConfigMap in specific namespace

workaround: Check namespace exists and verify RBAC permissions

06170002 : failed to list ConfigMaps

sev: Error

Type: Application

args:

error

cause: Failed to list ConfigMaps with label selector

workaround: Verify label selector syntax and RBAC permissions

06170003 : Failed updating configMap in namespace

sev: Error

Type: Application

args:

error
configMap
namespace

cause: Failed to update ConfigMap in namespace

workaround: Check write permissions and ConfigMap conflicts

06170004 : Failed to fetch incluster config

sev: Error

Type: Application

args:

error

cause: Failed to get in-cluster Kubernetes configuration

workaround: Ensure pod has proper RBAC permissions and service account and that the process is running in a Kubernetes environment.

06170005 : Error in creating clientset

sev: Error

Type: Application

args:

error

cause: Failed to create Kubernetes clientset from config

workaround: Verify cluster connection and authentication credentials

06170006 : Error in creating gateway clientset

sev: Error

Type: Application

args:

error

cause: Failed to create gateway Kubernetes clientset for F5 gateway APIs

workaround: Check pod permissions, cluster connectivity, and restart pod

06170007 : Error in creating f5clientset

sev: Error

Type: Application

args:

error

cause: N/A

workaround: N/A

06170008 : Failed to fetch clientset

sev: Warning

Type: Application

args:

error

cause: N/A

workaround: N/A

06170009 : Failed to fetch context

sev: Warning

Type: Application

args:

error

cause: N/A

workaround: N/A

0617000a : Started running ClusterInfoDump command

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617000b : Failed at running ClusterInfoDump command

sev: Error

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617000c : failed to create helm version data file in

sev: Error

Type: Application

args:

cause: Failed to create helm version data file during cluster info dump

workaround: Check file system permissions and available disk space

0617000d : Cluster info is dumped

sev: Info

Type: Application

args:

dest
output

cause: N/A

workaround: N/A

0617000e : helm.sh is not present in the deployment

sev: Info

Type: Application

args:

deployment name:

cause: N/A

workaround: N/A

0617000f : deployments in the namespace '%s', do not have helm version information.

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170010 : error marshalling helmVersiondata: %v

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170011 : failed to write helm version data to file %v

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170012 : Error getting tmm pod list

sev: Error

Type: Application

args:

error

cause: Cannot get TMM pod list using app=f5-tmm label selector

workaround: Verify TMM pods are running and labeled correctly

06170013 : Started describing

sev: Info

Type: Application

args:

resource

cause: N/A

workaround: N/A

06170014 : Failed to match version in kube config flags

sev: Error

Type: Application

args:

error

cause: Version matching failed in kubectl config flags

workaround: Update kubectl version or adjust configuration flags

06170015 : Failed to describe

sev: Error

Type: Application

args:

error

cause: kubectl describe command execution failed

workaround: Check resource existence and kubectl permissions

06170016 : Completed describing kind with name

sev: Info

Type: Application

args:

kind
name

cause: N/A

workaround: N/A

06170017 : Failed to fech namespace

sev: Error

Type: Application

args:

error

cause: Failed to fetch specific namespace information

workaround: Verify namespace exists and check read permissions

06170018 : Failed to get list of namespaces

sev: Error

Type: Application

args:

error

cause: Cannot list all namespaces in cluster

workaround: Check cluster-level RBAC permissions for namespace listing

06170019 : Started running APIresources command

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617001a : Failed at running APIresources command

sev: Error

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617001b : Creating the secret

sev: Info

Type: Application

args:

secretName

cause: N/A

workaround: N/A

0617001c : Creating the secret

sev: Info

Type: Application

args:

secretName

cause: N/A

workaround: N/A

0617001d : Updating the secret

sev: Info

Type: Application

args:

secretName

cause: N/A

workaround: N/A

0617001e : Error in creating/updating secret with given name

sev: Error

Type: Application

args:

secret
newName
error

cause: Error creating or updating Kubernetes Secret

workaround: Check secret size limits and write permissions

0617001f : Error in reading secret

sev: Error

Type: Application

args:

secretName
error

cause: Cannot read Secret from Kubernetes

workaround: Verify Secret exists and read permissions are granted

06170020 : Failed to get pods in namespace

sev: Error

Type: Application

args:

error

cause: Failed to get pods in specified namespace

workaround: Verify namespace exists and pod listing permissions

06170021 : product version is present in pod

sev: Info

Type: Application

args:

pod name:

cause: N/A

workaround: N/A

06170022 : Start PodIP and ipFamilyPolicyPreferIPV6 is:

sev: Debug

Type: Application

args:

podIP
ipFamilyPolicyPreferIPV6

cause: N/A

workaround: N/A

06170023 : Prefered PodIP is:

sev: Debug

Type: Application

args:

podIP

cause: N/A

workaround: N/A

06170024 : Failed to create AMQP

sev: Error

Type: System

args:

Error

cause: RabbitMQ message broker is unavailable, misconfigured, or experiencing connectivity issues preventing AMQP connection establishment.

workaround: Check RabbitMQ pod status verify service endpoints, restart RabbitMQ service, or check network policies blocking communication.

06170025 : Successfully connected to rabbitmq

sev: Info

Type: System

args:

amqp

cause: N/A

workaround: N/A

06170026 : Failed to Setup CPCL

sev: Error

Type: Application

args:

error

cause: Error in setting up CPCL due to an error in the CPCL handle build config or in the creation of a new license engine.

workaround: Verify CPCL license engine configs.

06170027 : Failed to get status

sev: Error

Type: Application

args:

error

cause: Unable to fetch the license status due to issue with cluster or status data is wrong.

workaround: Check if K8S cluster is working properly, if working fine and the error persists continuously contact the support engineer.

06170028 : Registering device failed

sev: Critical

Type: Application

args:

error

cause: Either installation of CWC component is not done properly or an expired / invalid JWT is being used. In connected license mode, check if there is connectivity to the outside world from the box where it is getting installed.

workaround: Reinstall CWC component, check the JWT and the connectivity

06170029 : Failed to update configmap

sev: Error

Type: System

args:

key
value
error

cause: Failed to update config map during Switch License.

workaround: Trigger switch license operation again.

0617002a : Failed to activate JWT

sev: Critical

Type: Application

args:

status

cause: If the error is during initial setup, then one of the reason can be pre-requisite steps are missed before installing CWC. Or the JWT is not valid. If the error has come during Switch License operation the JWT seems to be incorrect.

workaround: Check the JWT if it's valid. If not apply for a new JWT For initial setup, reinstall CWC with the new, for switch license operation trigger with new JWT.

0617002b : Received ignorable error in activating JWT

sev: Warning

Type: Application

args:

status

cause: N/A

workaround: N/A

0617002c : failed to get status

sev: Error

Type: Application

args:

error

cause: Unable to fetch the license status due to issue with cluster or status data is wrong.

workaround: Check if K8S cluster is working properly, if working fine and the error persists continuously contact the support engineer.

0617002d : error in unmarshaling

sev: Error

Type: Application

args:

error

cause: Unable to fetch the license status due to issue with cluster or status data is wrong.

workaround: Check if K8S cluster is working properly, if working fine and the error persists continuously contact the support engineer.

0617002e : Failed to get status

sev: Error

Type: Application

args:

error

cause: Unable to fetch the license status due to issue with cluster or status data is wrong.

workaround: Check if K8S cluster is working properly, if working fine and the error persists continuously contact the support engineer.

0617002f : Failed to get status

sev: Error

Type: Application

args:

error

cause: Unable to fetch license status from cluster during config report handling.

workaround: Check K8s cluster health.

06170030 : Failed to send telemetry report

sev: Error

Type: Application

args:

status

cause: Telemetry report transmission failed due to network issues or licensing server problems.

workaround: Check connectivity to licensing server and verify telemetry configuration.

06170031 : Received ignorable error in handling configreport

sev: Warning

Type: Application

args:

status

cause: N/A

workaround: N/A

06170032 : Failed to get status

sev: Error

Type: Application

args:

error

cause: Unable to fetch license status from cluster during config report handling

workaround: Check K8s cluster health.

06170033 : Failed to activate license

sev: Error

Type: Application

args:

status

cause: License activation failed during acknowledgment verification for initial registration.

workaround: Check JWT validity and licensing server connectivity.

06170034 : Received ignorable error in ack verification

sev: Warning

Type: Application

args:

status

cause: N/A

workaround: N/A

06170035 : Failed to activate licnese

sev: Error

Type: Application

args:

status

cause: License activation failed during acknowledgment verification for license switching.

workaround: Verify new JWT and retry switch license operation

06170036 : Received ignorable error in ack verification

sev: Warning

Type: Application

args:

status

cause: N/A

workaround: N/A

06170037 : Failed to get status

sev: Error

Type: Application

args:

error

cause: Unable to fetch license status from cluster during config report handling.

workaround: Check K8s cluster health.

06170038 : Failed to send telemetry report

sev: Error

Type: Application

args:

status

cause: Current periodic telemetry report transmission failed

workaround: Verify licensing server connectivity and telemetry service health

06170039 : Received ignorable error in handling configreport

sev: Warning

Type: Application

args:

status

cause: N/A

workaround: N/A

0617003a : Failed to get status

sev: Error

Type: Application

args:

error

cause: Unable to fetch license status from cluster during config report handling.

workaround: Check K8s cluster health.

0617003b : Failed to verify telemetry report

sev: Error

Type: Application

args:

status

cause: Telemetry report verification failed due to invalid acknowledgment or server issues

workaround: Resubmit acknowledgment and verify JWT validity.

0617003c : Received ignorable error in handling configreport

sev: Warning

Type: Application

args:

status

cause: N/A

workaround: N/A

06170047 : On startup, state, context, current periodic telemetry are as follows

sev: Notice

Type: Application

args:

state
telemetry
currentPeriodicTelemetry

cause: N/A

workaround: N/A

06170048 : Registering device failed

sev: Error

Type: Application

args:

error

cause: Device registration failed during pod startup when in CPCL initialized state

workaround: Check JWT validity and licensing server connectivity

06170049 : Received device registration complete state

sev: Notice

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617004a : Config Report is ready to download

sev: Notice

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617004b : Verification Successful

sev: Notice

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617004c : Failed to Inform SPK Controllers on License Status.

sev: Error

Type: Application

args:

error

cause: RabbitMQ communication failed when publishing license verification status

workaround: Check RabbitMQ connectivity and service health

0617004d : Nothing to do for now!!

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617004e : Received license expiry notification

sev: Warning

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617004f : Failed to Inform SPK Controllers on License Status.

sev: Error

Type: Application

args:

error

cause: RabbitMQ communication failed when publishing license expiry notification.

workaround: Verify RabbitMQ service, network connectivity.

06170050 : Received public key expiry notification

sev: Warning

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170051 : failed to collect telemetry report

sev: Error

Type: Application

args:

error

cause: Telemetry data collection failed during initial registration

workaround: Check telemetry service configuration and data sources

06170052 : failed to store observation start and end times in secret

sev: Error

Type: Application

args:

error

cause: Failed to persist telemetry timing data to Kubernetes Secret

workaround: Check Secret write permissions and storage availability

06170053 : failed to collect telemetry report

sev: Error

Type: Application

args:

error

cause: Telemetry collection failed during license switching operation

workaround: Check telemetry service health and retry switch operation

06170054 : failed to send telemetry report

sev: Error

Type: Application

args:

error

cause: Telemetry report transmission failed after collection

workaround: Verify licensing server connectivity and report format

06170055 : Received license expiring notification

sev: Info

Type: Application

args:

notification

cause: N/A

workaround: N/A

06170056 : Received certificate expiring notification

sev: Info

Type: Application

args:

notification

cause: N/A

workaround: N/A

06170057 : [Mock] Unable to parse licenseExpiryDate

sev: Error

Type: Application

args:

error

cause: N/A

workaround: N/A

06170058 : [Mock] Using license expiry date for mock notifications

sev: Info

Type: Application

args:

expiryDate

cause: N/A

workaround: N/A

06170059 : [Mock] Failed to parse license expiry date

sev: Error

Type: Application

args:

error

cause: N/A

workaround: N/A

0617005a : [Mock] Expiring soon triggers in

sev: Info

Type: Application

args:

timeleft
currentTime
expectedTriggerTime

cause: N/A

workaround: N/A

0617005b : [Mock] Triggering 'expiring soon' notification now

sev: Info

Type: Application

args:

actualTime

cause: N/A

workaround: N/A

0617005c : [Mock] Expiring today triggers in

sev: Info

Type: Application

args:

timeleft
currentTime
expectedTriggerTime

cause: N/A

workaround: N/A

0617005d : [Mock] Triggering 'expiring today' notification now

sev: Info

Type: Application

args:

actualTime

cause: N/A

workaround: N/A

0617005e : [Mock] Expired triggers in

sev: Info

Type: Application

args:

timeleft
currentTime
expectedTriggerTime

cause: N/A

workaround: N/A

0617005f : [Mock] Triggering 'expired' notification now

sev: Info

Type: Application

args:

actualTime

cause: N/A

workaround: N/A

06170060 : State is being changed

sev: Notice

Type: Application

args:

from
to

cause: N/A

workaround: N/A

06170061 : Failed to marshall context to string

sev: Error

Type: Application

args:

error

cause: JSON marshaling failed when converting CPCL context to string for storage.

workaround: Check context data validity and JSON marshaling dependencies.

06170062 : Storing context

sev: Info

Type: Compliance

args:

context

cause: N/A

workaround: N/A

06170063 : Read context

sev: Info

Type: Application

args:

payload

cause: N/A

workaround: N/A

06170064 : Error in getting telemetry string

sev: Error

Type: Application

args:

error

cause: JSON marshaling failed when converting license status to string for secret storage.

workaround: Verify license status data structure and JSON dependencies.

06170065 : Storing license status to secret

sev: Info

Type: Application

args:

licenseStatusSecret

cause: N/A

workaround: N/A

06170066 : Failed to store license status to secret

sev: Error

Type: Application

args:

licenseStatus
error

cause: Failed to store license status data to Kubernetes Secret.

workaround: Check Secret write permissions and storage capacity.

06170067 : Failed to read license status secret store. Context %s, error %s

sev: Error

Type: System

args: N/A

cause: Cannot read license status from Kubernetes Secret for specific context.

workaround: Verify Secret exists and has read permissions.

06170068 : Failed to unmarshal license status secret store. Context %s, error %s

sev: Error

Type: Application

args: N/A

cause: JSON unmarshaling failed when reading license status from Secret.

workaround: Check Secret data format and JSON structure validity.

06170069 : Error in marshling telemetry status

sev: Error

Type: Application

args:

error

cause: JSON marshaling failed when converting telemetry status to string.

workaround: Verify telemetry status data structure integrity.

0617006a : Storing telemetry status to secret

sev: Info

Type: Application

args:

telemetryStatus

cause: N/A

workaround: N/A

0617006b : Failed to store telemetry status to secret

sev: Error

Type: System

args:

error
status

cause: Failed to store telemetry status data to Kubernetes Secret.

workaround: Check Secret write permissions and available storage.

0617006c : Failed to read telemetry status secret store.

sev: Error

Type: System

args:

error

cause: Cannot read telemetry status from Kubernetes Secret.

workaround: Verify Secret exists and check read permissions.

0617006d : Failed to unmarshal telemetry status secret store

sev: Error

Type: Application

args:

error

cause: JSON unmarshaling failed when reading telemetry status from Secret.

workaround: Check Secret data format and K8s API server connection.

0617006e : Failed to store license status.

sev: Error

Type: Application

args:

error
context

cause: Failed to store license status during setup initialization.

workaround: Check Secret write permissions and retry setup.

0617006f : License Status read during setup.

sev: Info

Type: Application

args:

context
state
errCode
errString
action

cause: N/A

workaround: N/A

06170070 : Failed to store license status.

sev: Error

Type: Application

args:

error
context

cause: Failed to store license status during reset operation.

workaround: Verify Secret write access and storage availability.

06170071 : Failed to store license status.

sev: Error

Type: Application

args:

error
context

cause: Failed to store license status when setting active state.

workaround: Check Secret write permissions and retry activation.

06170072 : Failed to store license status.

sev: Error

Type: Application

args:

error
context

cause: Failed to store license status when updating state.

workaround: Verify Secret write access and storage health.

06170073 : Failed to parse license status date.

sev: Error

Type: Application

args:

error

cause: License status date parsing failed using RFC3339 format.

workaround: Verify license date format and update with valid RFC3339 timestamp.

06170074 : Failed to parse entitlement expiry date.

sev: Error

Type: Application

args:

error

cause: Entitlement expiry date parsing failed using RFC3339 format.

workaround: Check entitlement date format.

06170075 : License expiry date is extended update the license status.

sev: Debug

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170076 : Failed to store license status with updated expiry date.

sev: Error

Type: Application

args:

error
context

cause: License status storage failed when updating expiry date.

workaround: Check Secret write permissions and retry expiry update.

06170077 : License expiry date is sucessfully updated post subscription renewal.

sev: Info

Type: Application

args:

License Expiry date

cause: N/A

workaround: N/A

06170078 : Failed to store license status.

sev: Error

Type: Application

args:

error
context

cause: License status storage failed when setting error state.

workaround: Verify Secret write access and storage capacity.

06170079 : Failed to store license status.

sev: Error

Type: Application

args:

error
context

cause: License status storage failed when updating license details.

workaround: Check Secret write permissions and data validity.

0617007a : Failed to store telemetry status

sev: Error

Type: Application

args:

error

cause: Telemetry status storage failed during setup initialization.

workaround: Check Secret write permissions and retry telemetry setup.

0617007b : Telemetry Status read during setup. state %s, errCode %s, errString %s, action %s

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617007c : Failed to store telemetry status

sev: Error

Type: Application

args:

error

cause: Telemetry status storage failed during reset operation.

workaround: Verify Secret write access and storage health.

0617007d : Failed to store telemetry status

sev: Error

Type: Application

args:

error

cause: Telemetry status storage failed when resetting to initialized state.

workaround: Check Secret write permissions and retry operation.

0617007e : Failed to store telemetry status

sev: Error

Type: Application

args:

error

cause: Telemetry status storage failed when setting report validity.

workaround: Verify Secret write access and data integrity.

0617007f : Failed to store telemetry status

sev: Error

Type: Application

args:

error

cause: Telemetry status storage failed during report copying/aggregation.

workaround: Check Secret write permissions and storage capacity.

06170080 : Failed to store telemetry status

sev: Error

Type: Application

args:

error

cause: Telemetry status storage failed when updating report dates.

workaround: Verify Secret write access and timestamp validity.

06170081 : Failed to store telemetry status

sev: Error

Type: Application

args:

error

cause: Telemetry status storage failed when setting active state.

workaround: Check Secret write permissions and retry activation.

06170082 : Failed to store telemetry status

sev: Error

Type: Application

args:

error

cause: Telemetry status storage failed when updating report state.

workaround: Verify Secret write access and state validity.

06170083 : Failed to store telemetry status

sev: Error

Type: Application

args:

error

cause: Telemetry status storage failed when setting report error state.

workaround: Check Secret write permissions and error data validity.

06170084 : Failed to read context.

sev: Error

Type: Application

args:

error

cause: CPCL context reading failed from Secret during status handler setup.

workaround: Verify context Secret exists and check read permissions.

06170085 : Failed to store context

sev: Error

Type: Application

args:

error

cause: CPCL context storage failed when updating current context.

workaround: Check Secret write permissions and context data validity.

06170086 : Status copied to ContextNone

sev: Info

Type: Application

args:

status
context
src

cause: N/A

workaround: N/A

06170087 : Error in getting telemetry string

sev: Error

Type: Application

args:

error

cause: JSON marshaling failed when converting UserStatus struct to string for CM20 status response.

workaround: Contact F5 support engineer for assistance.

06170088 : Changing the context

sev: Info

Type: Application

args:

to
from

cause: N/A

workaround: N/A

06170089 : Changing the error

sev: Info

Type: Application

args:

to
from

cause: N/A

workaround: N/A

0617008a : Changing error message

sev: Info

Type: Application

args:

to
from

cause: N/A

workaround: N/A

0617008b : failed to delete CPCL config map

sev: Error

Type: System

args:

error

cause: N/A

workaround: N/A

0617008c : failed to delete CWC state config map

sev: Error

Type: System

args:

error

cause: N/A

workaround: N/A

0617008d : failed to delete CWC QKview config map

sev: Error

Type: System

args:

error

cause: N/A

workaround: N/A

0617008e : failed to delete CWC QKview config map

sev: Error

Type: System

args:

error

cause: N/A

workaround: N/A

0617008f : The license will expire soon. If it is already renewed, pls ignore this message.

sev: Notice

Type: Application

args:

daysLeft

cause: N/A

workaround: N/A

06170090 : License is expiring today. If it is already renewed, pls ignore this message.

sev: Notice

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170091 : License expired. If renewal is done, please upload the telemetry report.

sev: Alert

Type: Application

args:

expiredOn

cause: License is expired.

workaround: Contact F5 to renew license.

06170092 : Report is ready to download.

sev: Notice

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170093 : Please upload an acknowledgement for the telemetry report.

sev: Notice

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170094 : Timer fired, calling updateTelemetry

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170095 : Skipping the telemetry due to current context

sev: Info

Type: Application

args:

context

cause: N/A

workaround: N/A

06170096 : Error storing reports in secret

sev: Error

Type: Application

args:

error

cause: Failed to store telemetry report observation start and end times to Kubernetes Secret during license report building.

workaround: Check Secret write permissions and available storage space.

06170097 : failed to collect telemetry report

sev: Error

Type: Application

args:

error

cause: Telemetry data collection failed during license report building due to metrics gathering errors or resource access issues.

workaround: Check telemetry service configuration, verify metric collection permissions, and retry report generation.

06170098 : Failed to read configuration

sev: Alert

Type: Application

args:

error

cause: CPCL configuration reading failed from ConfigMap or configuration source is inaccessible.

workaround: Verify ConfigMap exists and contains valid configuration data.

06170099 : Failed to build config

sev: Alert

Type: Application

args:

error

cause: CPCL configuration reading failed from ConfigMap or configuration source is inaccessible.

workaround: Verify ConfigMap exists and contains valid configuration data.

0617009a : Failed to create new license server

sev: Alert

Type: Application

args:

error

cause: License engine creation failed due to invalid configuration parameters or missing certificates.

workaround: Verify CA certificates, product configuration, and licensing server connectivity.

0617009b : SendReport is no longer supported for InitialRegistration and SwitchLicense

sev: Info

Type: System

args: N/A

cause: N/A

workaround: N/A

0617009c : failed to download config report

sev: Alert

Type: Application

args:

error
report

cause: Config report download failed during initial registration or license switching.

workaround: Check licensing server and licensing engine connectivity and retry download operation.

0617009d : failed to download telemetry report

sev: Alert

Type: Application

args:

error
report

cause: Config report download failed during initial registration or license switching.

workaround: Check licensing server and licensing engine connectivity and retry download operation.

0617009e : failed to update configmap

sev: Alert

Type: System

args:

error
key
value

cause: ConfigMap update failed during device re-registration with new JWT.

workaround: Check ConfigMap write permissions and Kubernetes API connectivity.

0617009f : Re-Registering device failed

sev: Alert

Type: Application

args:

error

cause: Device re-registration failed after JWT update.

workaround: Verify new JWT validity and licensing server connectivity.

061700a0 : failed to update configmap

sev: Alert

Type: System

args:

error
key
value

cause: ConfigMap update failed when storing updated JWT.

workaround: Check ConfigMap write permissions and verify switching JWT format.

061700a1 : Error in reading ConfigMap

sev: Error

Type: System

args:

error
key

cause: ConfigMap read-by-key operation failed.

workaround: Verify ConfigMap exists and is accessible.

061700a2 : Read info

sev: Debug

Type: Application

args:

key
value

cause: N/A

workaround: N/A

061700a3 : Read info

sev: Info

Type: Application

args:

key
value

cause: N/A

workaround: N/A

061700a4 : TEEM Cert URL

sev: Info

Type: Application

args:

cause: N/A

workaround: N/A

061700a5 : TEEM Entitlement URL

sev: Info

Type: Application

args:

cause: N/A

workaround: N/A

061700a6 : TEEM Initial Config URL

sev: Info

Type: Application

args:

cause: N/A

workaround: N/A

061700a7 : Mode is configured

sev: Info

Type: Application

args:

mode

cause: N/A

workaround: N/A

061700a8 : LicenseServer Root CA Refer Location

sev: Info

Type: Application

args:

root_ca_cert_refer_location

cause: N/A

workaround: N/A

061700a9 : LicenseServer Root CA Refer Location

sev: Info

Type: Application

args:

defaulting to CaCertLocationCode

cause: N/A

workaround: N/A

061700aa : LicenseServer Root CA

sev: Info

Type: Application

args:

licenseserver_root_ca_path

cause: N/A

workaround: N/A

061700ab : Failed to activate

sev: Critical

Type: Application

args:

error

cause: License activation failed.

workaround: Verify JWT validity, check licensing server connectivity, and ensure certificates are properly configured.

061700ac : Received ignorable error in initial activation callback

sev: Info

Type: Application

args:

error

cause: N/A

workaround: N/A

061700ad : Activation successful

sev: Info

Type: Application

args:

status
payload

cause: N/A

workaround: N/A

061700ae : failed to update configmap

sev: Alert

Type: System

args:

error

cause: Failed to update cwc-state-cm ConfigMap during license switching to store previous license report.

workaround: Check ConfigMap write permissions and Kubernetes API connectivity.

061700af : Config Report prepared by CPCL, ready to download

sev: Info

Type: Application

args:

status
payload

cause: N/A

workaround: N/A

061700b0 : Failed to send telemetry report

sev: Alert

Type: Application

args:

error

cause: Telemetry report transmission failed during initial registration or license switching.

workaround: Check licensing server connectivity and network configuration.

061700b1 : Received ignorable error in initial config report callback

sev: Info

Type: Application

args:

error

cause: N/A

workaround: N/A

061700b2 : Failed to send telemetry report

sev: Alert

Type: Application

args:

error

cause: Periodic telemetry report transmission failed.

workaround: Verify licensing server connectivity and telemetry service health.

061700b3 : Received ignorable error in initial config report callback

sev: Info

Type: Application

args:

error

cause: N/A

workaround: N/A

061700b4 : Config Report prepared by CPCL, ready to download

sev: Info

Type: Application

args:

status
payload

cause: N/A

workaround: N/A

061700b5 : Failed to verify signature

sev: Alert

Type: Application

args:

error

cause: Signature verification failed during initial registration or license switching.

workaround: Re-download config report and resubmit, check licensing server connection.

061700b6 : Received ignorable error in verify signature callback

sev: Info

Type: Application

args:

error

cause: N/A

workaround: N/A

061700b7 : Failed to verify signature

sev: Alert

Type: Application

args:

error

cause: Signature verification failed during periodic telemetry reporting.

workaround: Re-download config report and resubmit, check licensing server connection.

061700b8 : Received ignorable error in verify signature callback

sev: Info

Type: Application

args:

error

cause: N/A

workaround: N/A

061700b9 : Signature verification successful

sev: Info

Type: Application

args:

status
payload

cause: N/A

workaround: N/A

061700ba : failed to read configmap.

sev: Alert

Type: System

args:

error
key

cause: Failed to read jwt-switching-to key from cpcl-config-cm during license switching.

workaround: Verify cpcl-config-cm ConfigMap contains jwt-switching-to key.

061700bb : failed to update configmap

sev: Alert

Type: System

args:

error
key
value

cause: Failed to update JWT key in cpcl-config-cm with switching JWT during license verification.

workaround: Check ConfigMap write permissions and JWT format.

061700bc : Failed to start telemetry

sev: Alert

Type: Application

args:

error

cause: Telemetry service startup failed after successful license verification.

workaround: Check telemetry configuration and service dependencies.

061700bd : Received license expiring notification

sev: Info

Type: Application

args:

notification

cause: N/A

workaround: N/A

061700be : Received certificate expiring notification

sev: Info

Type: Application

args:

notification

cause: N/A

workaround: N/A

061700bf : message

sev: Critical

Type: Application

args:

filename
args

cause: N/A

workaround: N/A

061700c0 : message

sev: Error

Type: Application

args:

filename
args

cause: CPCL license engine error logged through callback handler.

workaround: Review specific error details and check license engine health.

061700c1 : message

sev: Debug

Type: Application

args:

filename
args

cause: N/A

workaround: N/A

061700c2 : message

sev: Info

Type: Application

args:

filename
args

cause: N/A

workaround: N/A

061700c3 : Rotating Cert Chain

sev: Info

Type: Application

args:

cert

cause: N/A

workaround: N/A

061700c4 : Failed to update config map

sev: Alert

Type: System

args:

error

cause: Failed to update cpcl-key-cm ConfigMap during certificate chain rotation.

workaround: Check ConfigMap write permissions and Kubernetes API server health.

061700c5 : Error creating new jobId

sev: Error

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700c6 : Failed to Create Request Payload for Debug API request message

sev: Error

Type: Application

args:

message
jobid
error

cause: N/A

workaround: N/A

061700c7 : Error publishing Debug API request message

sev: Error

Type: Application

args:

message
jobid
error

cause: N/A

workaround: N/A

061700c8 : Published Debug API request message

sev: Info

Type: Application

args:

message
jobid

cause: N/A

workaround: N/A

061700d1 : DEBUG: error while parsing payload to JobDataDebugUtil

sev: Error

Type: Application

args:

error

cause: N/A

workaround: N/A

061700d2 : DEBUG: Request with the job ID has timed out

sev: Error

Type: Application

args:

jobid

cause: N/A

workaround: N/A

061700d3 : DEBUG: Request with job ID has expired

sev: Info

Type: Application

args:

jobid

cause: N/A

workaround: N/A

061700d4 : DEBUG: Setting OperationStop for job timeout/purge ticker to stop with no debug util jobs in the queue

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700d5 : Adding new job

sev: Info

Type: Application

args:

jobid

cause: N/A

workaround: N/A

061700d6 : DEBUG: Setting OperationStart for job timeout/purge ticker to start with current number of debug jobs in the queue 1

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700d7 : DEBUG: error while parsing debug util job data

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700d8 : Response received from tmmId after the request timeout

sev: Error

Type: Application

args:

tmmid

cause: N/A

workaround: N/A

061700d9 : DEBUG: Updating job

sev: Info

Type: Application

args:

jobid

cause: N/A

workaround: N/A

061700da : DEBUG: Adding new tmm response

sev: Info

Type: Application

args:

tmmId
currentRespCnt

cause: N/A

workaround: N/A

061700db : DEBUG: Job Completes!

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700dc : ParseJobDataDebugUtil unmarshall error

sev: Info

Type: Application

args:

error

cause: N/A

workaround: N/A

061700dd : DEBUG: Succeeded in getting tmm pod id list, setting ExpectedRespCnt

sev: Info

Type: Application

args:

expectedRespCnt

cause: N/A

workaround: N/A

061700de : Deleting the job data from the job queue

sev: Info

Type: Application

args:

jobid

cause: N/A

workaround: N/A

061700df : Deleted the job data from the job queue

sev: Info

Type: Application

args:

jobid

cause: N/A

workaround: N/A

061700e0 : Deleting the qkview job from the job queue

sev: Info

Type: Application

args:

jobid

cause: N/A

workaround: N/A

061700e1 : Deleting the qkview jobs started

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700e2 : Deleted the qkview jobs

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700e3 : Reset ConfigMap to empty state

sev: Info

Type: Application

args:

name
namespace

cause: N/A

workaround: N/A

061700e4 : Failed to marshal log levels to YAML

sev: Error

Type: Application

args:

error

cause: N/A

workaround: N/A

061700e5 : logAction

sev: Info

Type: Application

args:

name
namespace

cause: N/A

workaround: N/A

061700e6 : msg

sev: Error

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700e7 : msg

sev: Error

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700e8 : msg

sev: Warning

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700e9 : fluentbitEnabled: %s

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700ea : Error listening on connection

sev: Error

Type: Application

args:

error

cause: TCP readiness probe server failed to bind to target port, likely due to port already in use or insufficient permissions.

workaround: Check if port is available and verify pod networking configuration.

061700eb : Listening on

sev: Info

Type: Application

args:

ip
port

cause: N/A

workaround: N/A

061700ec : probe: Signal received to stop probe server for readiness probe

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700ed : probe: error in accepting connection

sev: Error

Type: Application

args:

error

cause: TCP readiness probe server failed to accept incoming connections, likely due to network issues or listener closure.

workaround: Check network connectivity and restart the probe server.

061700ee : probe: server accepted connection

sev: Debug

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700ef : probe: Monitoring probe health

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700f0 : probe: stopping probe server

sev: Info

Type: Application

args:

ip
port

cause: N/A

workaround: N/A

061700f7 : probe: TCP server is stopped

sev: Debug

Type: Application

args:

error

cause: N/A

workaround: N/A

061700f8 : probe: TCP server is running

sev: Debug

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700f9 : Failed to copy directory

sev: Error

Type: System

args:

error

cause: N/A

workaround: N/A

061700fa : Failed to copy file

sev: Error

Type: System

args:

error

cause: N/A

workaround: N/A

061700fb : File removed successfully

sev: Info

Type: Application

args:

filename

cause: N/A

workaround: N/A

061700fc : message

sev: Error

Type: System

args: N/A

cause: N/A

workaround: N/A

061700fd : message

sev: Error

Type: Application

args: N/A

cause: N/A

workaround: N/A

061700fe : File/dir removed successfully

sev: Info

Type: Application

args:

path

cause: N/A

workaround: N/A

061700ff : Handling dssm services

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170100 : Failed to run cat cmd

sev: Error

Type: Application

args:

error

cause: N/A

workaround: N/A

06170101 : Container Linux flavour detected

sev: Info

Type: Application

args:

flavor

cause: N/A

workaround: N/A

06170102 : Found DSSM service in Pod env variables

sev: Info

Type: Application

args:

service

cause: N/A

workaround: N/A

06170103 : DSSM service data will be collected: %s

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170104 : Error in dssm handle

sev: Error

Type: Application

args:

error

cause: N/A

workaround: N/A

06170105 : describing output of %s in %s is successful\n

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170106 : Error in getting api resources from given namespace

sev: Error

Type: Application

args:

output
namespace

cause: N/A

workaround: N/A

06170107 : Getting details of api resource is successful

sev: Info

Type: Application

args:

resource

cause: N/A

workaround: N/A

06170108 : collecting kind

sev: Info

Type: Application

args:

kind

cause: N/A

workaround: N/A

06170109 : Failed in getting api resources list for given namespace

sev: Error

Type: Application

args:

namespace

cause: N/A

workaround: N/A

0617010a : No resources found in given namespace

sev: Warning

Type: Application

args:

namespace
resource

cause: N/A

workaround: N/A

0617010b : Error getting details of api resources from given namespace

sev: Error

Type: Application

args:

namespace
item

cause: N/A

workaround: N/A

0617010c : Getting details of api resource is successful

sev: Info

Type: Application

args:

resource

cause: N/A

workaround: N/A

0617010d : collecting mrfdb output for %v via %v/%v\n

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617010e : Error during collecting DSSM data %v via %v/%v\n

sev: Error

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617010f : collecting cluster info

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170110 : Failed to dump cluster info

sev: Error

Type: Application

args:

error

cause: N/A

workaround: N/A

06170111 : Copying file from folder

sev: Info

Type: Application

args:

from
to

cause: N/A

workaround: N/A

06170112 : Failed to copy file

sev: Error

Type: Application

args:

error

cause: N/A

workaround: N/A

06170113 : Failed in handling container folders

sev: Error

Type: Application

args:

error

cause: N/A

workaround: N/A

06170114 : collecting pod in namespace

sev: Info

Type: Application

args:

pod
namespace

cause: N/A

workaround: N/A

06170115 : collecting pod in namespace is done

sev: Info

Type: Application

args:

pod
namespace

cause: N/A

workaround: N/A

06170116 : collecting namespace

sev: Info

Type: Application

args:

namespace

cause: N/A

workaround: N/A

06170117 : No pods found in given namespace

sev: Warning

Type: Application

args:

namespace

cause: N/A

workaround: N/A

06170118 : Pods found

sev: Info

Type: Application

args:

pods

cause: N/A

workaround: N/A

06170119 : Error in Handling pod

sev: Error

Type: Application

args:

error
pod

cause: N/A

workaround: N/A

0617011a : Container logs were written to path

sev: Info

Type: Application

args:

path

cause: N/A

workaround: N/A

0617011b : Collecting objects per namespace

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617011c : Error in collecting objects per namespace

sev: Error

Type: Application

args:

error
namespace

cause: N/A

workaround: N/A

0617011d : Collecting namespace is done

sev: Info

Type: Application

args:

namespace

cause: N/A

workaround: N/A

0617011e : Started creating file

sev: Info

Type: Application

args:

path

cause: N/A

workaround: N/A

0617011f : Started handling namespace

sev: Info

Type: Application

args:

namespace

cause: N/A

workaround: N/A

06170120 : Creating a directory to store cluster level objects

sev: Info

Type: Application

args:

directory

cause: N/A

workaround: N/A

06170121 : Collecting objects per cluster level

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170122 : Error in DumpClusterInfo

sev: Error

Type: Application

args:

error

cause: N/A

workaround: N/A

06170123 : Creating directory

sev: Info

Type: Application

args:

name

cause: N/A

workaround: N/A

06170124 : Creating file

sev: Info

Type: Application

args:

name

cause: N/A

workaround: N/A

06170125 : error in creating file

sev: Error

Type: Application

args:

error

cause: N/A

workaround: N/A

06170126 : ParseJobDataQkview unmarshall error

sev: Info

Type: Application

args:

error

cause: N/A

workaround: N/A

06170127 : ParseJobDataQkview: JobDataQkview that is being unmarshalled input.FileLocation

sev: Info

Type: Application

args:

filelocation

cause: N/A

workaround: N/A

06170128 : DEBUG: Error accessing shared location

sev: Error

Type: Application

args:

location
error

cause: N/A

workaround: N/A

06170129 : Adding new job

sev: Info

Type: Application

args:

jobid

cause: N/A

workaround: N/A

0617012a : Error while getting info about containers

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617012b : Container details to collect qkview

sev: Info

Type: Application

args:

details

cause: N/A

workaround: N/A

0617012c : failed creating cluster-info tar.gz

sev: Error

Type: Application

args:

error

cause: N/A

workaround: N/A

0617012d : Qkview create request failed

sev: Error

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617012e : Completed POST Qkview request

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

0617012f : Error creating new jobId

sev: Error

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170130 : DEBUG: this is non ideal and never should enter in to this scenario as only one qkview job should be in progress at a given instant

sev: Error

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170131 : error occured during the job details update in configmap

sev: Info

Type: Application

args:

error

cause: N/A

workaround: N/A

06170132 : Updated the qkview details in configmap

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170133 : deleting the qkview tar folder for the job

sev: Info

Type: Application

args:

jobid

cause: N/A

workaround: N/A

06170134 : deleting the qkview tar folder from path

sev: Info

Type: Application

args:

path

cause: N/A

workaround: N/A

06170135 : Error: qkview tar folder deletion failed for the job

sev: Error

Type: Application

args:

error
jobid

cause: N/A

workaround: N/A

06170136 : deleting the tar folders for the qkview jobs

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170137 : deleting the qkview tar folder from path

sev: Info

Type: Application

args:

path

cause: N/A

workaround: N/A

06170138 : errMsg

sev: Error

Type: Application

args: N/A

cause: N/A

workaround: N/A

06170139 : v1 qkview API returning http error response

sev: Debug

Type: Application

args:

url
code
text

error

cause: N/A

workaround: N/A

06170140 : Error closing tw

sev: Error

Type: System

args:

error

cause: N/A

workaround: N/A

06170141 : crawling

sev: Info

Type: Application

args:

path

cause: N/A

workaround: N/A

06170142 : CreateMessage: Message that is being marshalled

sev: Debug

Type: System

args:

msgType
svcType
isSigned
dataType
signv

cause: N/A

workaround: N/A

06170143 : ParseMessage unmarshall error

sev: Info

Type: System

args:

error

cause: N/A

workaround: N/A

06170144 : ParseMessage: Message that is being unmarshalled

sev: Debug

Type: System

args:

input.gType
svcType
isSigned
dataType
signv

cause: N/A

workaround: N/A

06170145 : Initializing AMQP ...

sev: Info

Type: System

args: N/A

cause: N/A

workaround: N/A

06170146 : bind keys

sev: Info

Type: System

args:

keys

cause: N/A

workaround: N/A

06170147 : bind keys

sev: Info

Type: System

args:

keys

cause: N/A

workaround: N/A

06170148 : bind keys

sev: Info

Type: System

args:

keys

cause: N/A

workaround: N/A

06170149 : bind keys

sev: Info

Type: System

args:

keys

cause: N/A

workaround: N/A

0617014a : exchange name

sev: Info

Type: System

args:

name

cause: N/A

workaround: N/A

0617014b : failed to setup exchange

sev: Critical

Type: System

args: N/A

cause: AMQP exchange setup failed during initialization - could be due to exchange declaration, queue creation, or binding operations

workaround: Check RabbitMQ permissions, verify exchange and queue naming, ensure connection is established before setup

0617014c : exchange name

sev: Info

Type: System

args:

name

cause: N/A

workaround: N/A

0617014d : Failed to Parse Public key response msg

sev: Error

Type: System

args:

rspMsg
error

cause: JSON unmarshaling failed when parsing debug response message

workaround: Verify debug response message format and JSON structure

0617014e : Retreived latest public key version

sev: Notice

Type: System

args:

version

cause: N/A

workaround: N/A

0617014f : Failed to create Public key response msg

sev: Error

Type: System

args:

rspMsg
error

cause: Failed to create public key response message during key exchange

workaround: Check RSA key validity and message serialization process

06170150 : Failed to parse the Public Key request

sev: Error

Type: System

args:

to
error

cause: JSON parsing failed for incoming public key request message

workaround: Verify request message format and JSON structure

06170151 : Received Public Key request for version

sev: Notice

Type: System

args:

version

cause: N/A

workaround: N/A

06170152 : Latest public key sent

sev: Info

Type: System

args:

replyTo

cause: N/A

workaround: N/A

06170153 : Failed to publish the Public Key response

sev: Error

Type: System

args:

to
error

cause: Publishing public key response message failed

workaround: Check RabbitMQ connection and replyTo queue configuration

06170154 : CreatePubKeyResponseMessage key

sev: Debug

Type: System

args:

version
signVer

cause: N/A

workaround: N/A

06170155 : ParseAndVerifyPubKeyResponseMessage Output public Key and version

sev: Debug

Type: System

args:

key
version

cause: N/A

workaround: N/A

06170156 : ParsePubKeyResponseMessage Output public Key and version

sev: Debug

Type: System

args:

key
version

cause: N/A

workaround: N/A

06170157 : HandlePubKeyResponse: Signed Version and Version Stored Locally

sev: Info

Type: System

args:

signedVer
localVer

cause: N/A

workaround: N/A

06170158 : mismatch of sign version expected and response received signed with public key version

sev: Critical

Type: System

args:

expSignVer
resSignVer

cause: Critical version mismatch - local RSA key version differs from public key response signature version

workaround: Force public key refresh or restart key synchronization process

06170159 : Failed to parse the Public Key response

sev: Error

Type: System

args:

error

cause: Failed to parse and verify public key response message

workaround: Check message format, signature verification, and RSA key validity

0617015a : Received invalid PubKey response message

sev: Error

Type: System

args: N/A

cause: Received unexpected public key response type - not latest key response

workaround: Check message type handling and response processing logic

0617015b : ResponsePubKeyLatestKey failed ParseRsaPublicKeyFromPemStr

sev: Error

Type: System

args: N/A

cause: RSA public key parsing failed from PEM string in response

workaround: Verify PEM format and RSA key structure

0617015c : New Public Key version saved

sev: Info

Type: System

args:

version

cause: N/A

workaround: N/A

0617015d : CreatePubKeyEventMessage key version and signVersion

sev: Debug

Type: System

args:

keyVer
signVer

cause: N/A

workaround: N/A

0617015e : CreatePubKeyEventMessage for Public key version

sev: Debug

Type: System

args:

version

cause: N/A

workaround: N/A

0617015f : Curr Public Key version saved

sev: Info

Type: System

args:

version

cause: N/A

workaround: N/A

06170160 : ParseAndVerifyPubKeyEventMessage

sev: Info

Type: System

args:

key
version

cause: N/A

workaround: N/A

06170161 : Curr Public Key version saved

sev: Info

Type: System

args:

version

cause: N/A

workaround: N/A

06170162 : ParsePubKeyEventMessage

sev: Info

Type: System

args:

key
version

cause: N/A

workaround: N/A

06170163 : HandlePubKeyEvent: Signed Version: and Version Stored Locally

sev: Info

Type: System

args:

signedVer
localVer

cause: N/A

workaround: N/A

06170164 : mismatch of sign version expected and received signed with public key version

sev: Critical

Type: System

args:

expSignVer
resSignVer

cause: Critical version mismatch in public key event - signature version differs from local version

workaround: Synchronize key versions or restart key management process

06170165 : Failed to parse the Public Key event message

sev: Error

Type: System

args:

error

cause: Failed to parse public key event message

workaround: Check event message format and JSON parsing

06170166 : Received invalid PubKey Event message

sev: Critical

Type: System

args: N/A

cause: Invalid public key event type received - not latest key event

workaround: Check event type handling and message routing

06170167 : EventPubKeyLatestKey failed ParseRsaPublicKeyFromPemStr

sev: Error

Type: System

args: N/A

cause: RSA public key parsing failed from PEM string in event message

workaround: Verify PEM format and key structure in event

06170168 : New Public Key version saved

sev: Info

Type: System

args:

version

cause: N/A

workaround: N/A

06170169 : sendLatestPublicKeyRequests

sev: Debug

Type: System

args:

version

cause: N/A

workaround: N/A

0617016a : failed to create Public Key request

sev: Error

Type: System

args:

error

cause: Failed to create public key request message for latest key

workaround: Check message creation logic and JSON serialization

0617016b : failed to publish Public Key request

sev: Error

Type: System

args:

error

cause: Publishing public key request message failed

workaround: Verify RabbitMQ connection and routing configuration

0617016c : Initialize AMQP

sev: Info

Type: System

args:

namespace
url

cause: N/A

workaround: N/A

0617016d : Failed to load client cert and key

sev: Error

Type: Application

args:

error

cause: Failed to load TLS client certificate and key for RabbitMQ

workaround: Check certificate files exist and are valid

0617016e : Failed to establish connection to rabbitmq server

sev: Error

Type: System

args:

error

cause: Cannot establish connection to RabbitMQ server

workaround: Verify RabbitMQ server is running and network connectivity

0617016f : error: failed to open connection

sev: Error

Type: System

args: N/A

cause: RabbitMQ connection is null when trying to create channel

workaround: Check connection establishment and retry logic

06170170 : error: failed to open channel

sev: Error

Type: System

args: N/A

cause: Failed to open AMQP channel on existing connection

workaround: Check connection health and RabbitMQ resource limits

06170171 : DEBUG: bindingKeys

sev: Debug

Type: System

args:

keys

cause: N/A

workaround: N/A

06170172 : error: failed to declare exchange

sev: Error

Type: System

args: N/A

cause: Cannot declare RabbitMQ exchange

workaround: Verify exchange permissions and RabbitMQ configuration

06170173 : error: failed to declare queue

sev: Error

Type: System

args: N/A

cause: Failed to declare RabbitMQ queue

workaround: Check queue permissions and naming conflicts

06170174 : publishing exchange with binding key

sev: Info

Type: System

args:

exchangeKey
bindingKey

cause: N/A

workaround: N/A

06170175 : Key rotate timeout

sev: Debug

Type: System

args:

time

cause: N/A

workaround: N/A

06170176 : Rotating Keypair - Parsing private key PEM failed

sev: Error

Type: System

args: N/A

cause: RSA private key parsing failed during key rotation

workaround: Check key generation process and PEM format

06170177 : rotateAndNotifyPubKey version

sev: Info

Type: System

args:

version

cause: N/A

workaround: N/A

06170178 : Failed to Create Event Payload for Notifying Public Key.

sev: Error

Type: System

args:

error

cause: Failed to create public key notification event payload

workaround: Check event creation logic and message structure

06170179 : Publishing Public Key event message to SPK Controllers

sev: Info

Type: System

args:

signVer

cause: N/A

workaround: N/A

0617017a : Failed to publish the message

sev: Error

Type: System

args:

error

cause: Publishing public key notification to controllers failed

workaround: Check RabbitMQ connection to license exchange

0617017b : GetKeySignature: received private key as nil

sev: Error

Type: System

args: N/A

cause: Private key is null when attempting to sign message

workaround: Ensure RSA key pair generation completed successfully

0617017c : writing msgHash failed

sev: Error

Type: System

args:

error

cause: Failed to write message hash during signing process

workaround: Check cryptographic library and key validity

0617017d : SignPSS failed

sev: Error

Type: System

args:

error

cause: RSA-PSS signature generation failed

workaround: Verify private key format and cryptographic setup

0617017e : VerifySignature: received public key as nil

sev: Error

Type: System

args: N/A

cause: Public key is null during signature verification

workaround: Ensure public key exchange completed successfully

0617017f : writing msgHash failed

sev: Error

Type: System

args:

error

cause: Failed to write message hash during verification

workaround: Check public key validity and cryptographic setup

06170180 : VerifyPSS failed

sev: Error

Type: System

args:

error

cause: RSA-PSS signature verification failed

workaround: Verify public key and signature format compatibility

06170181 : Creating CM20 Response

sev: Info

Type: System

args:

responsetype
entitlement
expiry
uuid
signKeyVer

cause: N/A

workaround: N/A

06170182 : Creating CM20 Response

sev: Info

Type: System

args:

responsetype
entitlement
expiry
uuid
signKeyVer

cause: N/A

workaround: N/A

06170183 : Failed to publish the entitlement response

sev: Critical

Type: System

args:

replyTo
error

cause: Failed to publish CM20 entitlement response message to a queue

workaround: Check if RabbitMQ Pod is up and running. Check CWC Logs to check if connection is established successfully. If not restart RabbitMQ Pod followed by CWC pod.

06170184 : GetEntitlementRequest received with a pub key version different to that of latest private key with CWC. Signing with latest private key

sev: Info

Type: System

args: N/A

cause: N/A

workaround: N/A

06170185 : ParseCM20ResponseMessage: Received Invalid request

sev: Notice

Type: System

args: N/A

cause: N/A

workaround: N/A

06170186 : HandleCM20Response: Signed Version and Version Stored Locally

sev: Info

Type: System

args:

signedVersion
localVersion

cause: N/A

workaround: N/A

06170187 : mismatch of request, response CM20 version

sev: Error

Type: System

args:

reqV
respV

cause: Failed to publish CM20 entitlement response message to the queue

workaround: Check the versions of CWC and CNE-Contollers are they in sync. Restart CWC Pod.

06170188 : HandleCM20Event: Signed Version and Version Stored Locally

sev: Info

Type: System

args:

signedVersion
localVersion

cause: N/A

workaround: N/A

06170189 : mismatch of request, response CM20 version

sev: Error

Type: System

args:

reqV
respV

cause: Version mismatch in CM20 event message - local key version differs from message signature version

workaround: Trigger public key refresh or check key distribution mechanism

0617018a : failed to create Public CM20 request

sev: Error

Type: System

args:

error

cause: Failed to create CM20 entitlement request message payload

workaround: Check message structure, verify RSA key availability and JSON serialization

0617018b : Failed to publish message

sev: Error

Type: System

args:

error

cause: Publishing CM20 entitlement request message to RabbitMQ failed

workaround: Verify RabbitMQ connection, check binding key and exchange configuration

0617018c : Failed to Create Event Payload for License Verification

sev: Error

Type: System

args:

error

cause: Failed to create license verification event payload for CM20

workaround: Check license status data availability and message formatting

0617018d : Publishing event message to SPK Controllers

sev: Info

Type: System

args:

event
entitlement
expiry
uuid

cause: N/A

workaround: N/A

0617018e : Failed to publish the message

sev: Error

Type: System

args:

error

cause: Publishing license verification message to controllers failed

workaround: Check RabbitMQ connection to license exchange, verify routing configuration

0617018f : Failed to Create Event Payload for Heartbeat

sev: Error

Type: System

args:

error

cause: Failed to create heartbeat event payload

workaround: Check heartbeat configuration and message formatting

06170190 : Error publishing heartbeat message

sev: Error

Type: System

args:

error

cause: Error publishing heartbeat message to RabbitMQ

workaround: Verify RabbitMQ connection and exchange configuration

06170191 : ====> Published heartbeat message

sev: Info

Type: System

args:

time

cause: N/A

workaround: N/A

06170192 : recevied error while parsing msg body

sev: Error

Type: System

args:

message

cause: JSON parsing failed when processing incoming RabbitMQ message body

workaround: Check message format, verify JSON structure and encoding

06170193 : Received ServiceTypeCM20 Request message

sev: Info

Type: System

args: N/A

cause: N/A

workaround: N/A

06170194 : Received ServiceTypePubKey Request message

sev: Info

Type: System

args: N/A

cause: N/A

workaround: N/A

06170195 : Received ServiceTypeDebug Respons message

sev: Info

Type: System

args: N/A

cause: N/A

workaround: N/A

06170196 : Received Invalid messages with

sev: Error

Type: System

args:

service
message

cause: Received message with invalid service type or message type combination

workaround: Check message routing configuration and sender message formatting

06170197 : Failed to create AMQP.

sev: Error

Type: System

args:

error

cause: AMQP connection creation and initialization failed during client startup or reconnection

workaround: Check RabbitMQ server availability, network connectivity, and authentication

06170198 : Successfully Created and Initialised AMQP

sev: Info

Type: System

args: N/A

cause: N/A

workaround: N/A

06170199 : Failed to create channel

sev: Error

Type: System

args:

error

cause: Failed to create AMQP channel for message operations

workaround: Check connection health, RabbitMQ channel limits, and resource availability

0617019a : Failed to consume the message

sev: Error

Type: System

args:

error

cause: Failed to start consuming messages from the assigned queue

workaround: Verify queue exists, check consume permissions and connection stability

0617019b : Connection to RabbitMQ lost, Reconnecting ...

sev: Info

Type: System

args:

reason

cause: N/A

workaround: N/A

0617019c : Failed to acknowledge the message

sev: Warning

Type: System

args:

error

cause: N/A

workaround: N/A

0617019d : A handler is called with an method that is not supported, only POST is supported

sev: Debug

Type: User

args:

handler
method

cause: N/A

workaround: N/A

0617019e : DEBUG: received params

sev: Info

Type: User

args:

params

cause: N/A

workaround: N/A

0617019f : Final command to run

sev: Info

Type: User

args:

cause: N/A

workaround: N/A

061701a0 : failure occured

sev: Error

Type: Application

args:

error

cause: General failure in debug handler operation

workaround: Review request parameters and check system resources

061701a1 : POST call completed

sev: Info

Type: Application

args:

cause: N/A

workaround: N/A

061701a2 : qkview job is already running

sev: Error

Type: User

args:

error

cause: QKView job is already running when new request submitted

workaround: Wait for current QKView to complete or cancel it

061701a3 : PV storage is full

sev: Error

Type: System

args:

error

cause: Persistent Volume storage is full

workaround: Clean up old files or increase storage capacity

061701a4 : warningStr

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

061701a5 : POST call completed

sev: Info

Type: Application

args:

cause: N/A

workaround: N/A

061701a6 : A handler is called with an method that is not supported, only GET is supported

sev: Debug

Type: Application

args:

handler
method

cause: N/A

workaround: N/A

061701a7 : DEBUG: Please try the endpoint /debug/home for debug-api help...

sev: Debug

Type: User

args: N/A

cause: N/A

workaround: N/A

061701a8 : Error getting jobdata

sev: Error

Type: Application

args:

error

cause: No active jobs available

workaround: Check job status and database connectivity

061701a9 : Error: job id does not exist

sev: Error

Type: User

args:

error

cause: Requested job ID does not exist in system

workaround: Verify job ID and check job cleanup policies

061701aa : DEBUG: error while parsing debug util job data

sev: Error

Type: Application

args: N/A

cause: Error parsing debug utility job data

workaround: Check data format and job execution logs

061701ab : GET call completed

sev: Info

Type: User

args:

cause: N/A

workaround: N/A

061701ac : GET call completed

sev: Info

Type: User

args:

cause: N/A

workaround: N/A

061701ad : Unsupported command

sev: Info

Type: User

args:

command

cause: N/A

workaround: N/A

061701ae : IPv4 Address is valid

sev: Debug

Type: User

args:

address

cause: N/A

workaround: N/A

061701af : IPv4 Address is invalid.

sev: Debug

Type: User

args:

address

cause: N/A

workaround: N/A

061701b0 : IPv6 Address is valid.

sev: Debug

Type: User

args:

address

cause: N/A

workaround: N/A

061701b1 : IPv6 Address is invalid.

sev: Debug

Type: User

args:

address

cause: N/A

workaround: N/A

061701b2 : Tcpdump Params are valid.

sev: Debug

Type: User

args:

params

cause: N/A

workaround: N/A

061701b3 : Tcpdump Params are invalid.

sev: Debug

Type: User

args:

params

cause: N/A

workaround: N/A

061701b4 : Configview Params are Valid.

sev: Debug

Type: User

args:

params

cause: N/A

workaround: N/A

061701b5 : Configview Params are Invalid.

sev: Debug

Type: User

args:

params

cause: N/A

workaround: N/A

061701b6 : Lsndb Params are Valid.

sev: Debug

Type: User

args:

params

cause: N/A

workaround: N/A

061701b7 : Lsndb Params are Invalid.

sev: Debug

Type: User

args:

params

cause: N/A

workaround: N/A

061701b8 : Bdtcli Params are Valid.

sev: Debug

Type: User

args:

params

cause: N/A

workaround: N/A

061701b9 : bdtcli Params are Invalid.

sev: Debug

Type: User

args:

params

cause: N/A

workaround: N/A

061701ba : Mrfdb Params are Valid.

sev: Debug

Type: User

args:

params

cause: N/A

workaround: N/A

061701bb : Mrfdb Params are Invalid.

sev: Debug

Type: User

args:

params

cause: N/A

workaround: N/A

061701bc : Setloglevel Params are valid.

sev: Debug

Type: User

args:

params

cause: N/A

workaround: N/A

061701bd : Setloglevel Params are Invalid.

sev: Debug

Type: User

args:

params

cause: N/A

workaround: N/A

061701be : A handler is called with an method that is not supported, only GET is supported

sev: Info

Type: User

args:

handler
method

cause: N/A

workaround: N/A

061701bf : failed to retrieve CWC state for the response

sev: Error

Type: Application

args:

error
payloadLen

cause: Failed to retrieve CWC state for API response

workaround: Check CWC service health and configuration

061701c0 : GET %v completed

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

061701c1 : handler is supported only in disconnected mode

sev: Info

Type: User

args:

handler

cause: N/A

workaround: N/A

061701c2 : A handler is called with an method that is not supported, only GET is supported

sev: Info

Type: Application

args:

handler
method

cause: N/A

workaround: N/A

061701c3 : failure occured in report

sev: Error

Type: Application

args:

details

cause: General failure in telemetry report handler

workaround: Review telemetry configuration and connectivity

061701c4 : GET call completed

sev: Info

Type: Application

args:

cause: N/A

workaround: N/A

061701c5 : handler is supported only in disconnected mode

sev: Info

Type: User

args:

handler

cause: N/A

workaround: N/A

061701c6 : A handler is called with an method that is not supported, only POST is supported

sev: Info

Type: User

args:

handler
method

cause: N/A

workaround: N/A

061701c7 : failure occured in receipt handler

sev: Error

Type: Application

args:

details

cause: Error in receipt handler processing

workaround: Check message format and handler configuration

061701c8 : POST call completed

sev: Info

Type: Application

args:

cause: N/A

workaround: N/A

061701c9 : A handler is called with an method that is not supported, only POST is supported

sev: Info

Type: User

args:

handler
method

cause: N/A

workaround: N/A

061701ca : failure occured in reactivate

sev: Error

Type: Application

args:

error

cause: Failure in reactivate operation

workaround: Check license status and configuration validity

061701cb : POST call completed

sev: Info

Type: Application

args:

cause: N/A

workaround: N/A

061701cc : A handler is called with an unsupported method

sev: Info

Type: User

args:

handler
methodCalled
supportedMethod

cause: N/A

workaround: N/A

061701cd : handler getting jobId from URI

sev: Info

Type: Application

args:

handler

cause: N/A

workaround: N/A

061701ce : Handler is called with invalid parameter.

sev: Info

Type: User

args:

handler
error

cause: N/A

workaround: N/A

061701cf : GET call completed

sev: Info

Type: Application

args:

cause: N/A

workaround: N/A

061701d0 : Unable to get the file path

sev: Error

Type: System

args:

url
path
error

cause: Unable to get file path for QKView download

workaround: Check file system permissions and path configuration

061701d1 : Unable to download the file from the path

sev: Error

Type: System

args:

url
path
error

cause: Cannot download file from specified path

workaround: Verify file exists and check network connectivity

061701d2 : Qkview job has failed

sev: Error

Type: Application

args:

jobid
error

cause: QKView job execution failed

workaround: Check system resources and retry operation

061701d3 : no job found with the filters

sev: Info

Type: User

args:

filters

cause: N/A

workaround: N/A

061701d4 : Qkview job deletion failed at jobQueue for job Id

sev: Error

Type: Application

args:

jobid
error

cause: QKView job deletion failed at job queue level

workaround: Manual cleanup may be required, check queue status

061701d5 : Qkview job deletion failed at configmap for job Id

sev: Error

Type: System

args:

jobid
error

cause: QKView job deletion failed in ConfigMap storage

workaround: Check ConfigMap permissions and manually clean up

061701d6 : Qkview job not found with Id

sev: Info

Type: User

args:

jobid

cause: N/A

workaround: N/A

061701d7 : Qkview tar file deletion failed for job Id

sev: Error

Type: System

args:

jobid
error

cause: QKView tar file deletion failed from file system

workaround: Check file permissions and available disk space

061701d8 : Qkview deletion completed for jobId

sev: Info

Type: Application

args:

jobid

cause: N/A

workaround: N/A

061701d9 : Qkview jobs deletion started

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

061701da : Qkview job deletion failed at configmap for job Id

sev: Error

Type: System

args:

jobid
error

cause: Batch QKView job deletion failed in ConfigMap

workaround: Perform manual ConfigMap cleanup

061701db : Qkview jobs deletion is not successful from configmap

sev: Error

Type: System

args:

error

cause: Bulk QKView jobs deletion unsuccessful from ConfigMap

workaround: Check ConfigMap permissions and perform manual cleanup

061701dc : Qkview jobs deletion completed

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

061701dd : filters passed

sev: Info

Type: User

args:

filters

cause: N/A

workaround: N/A

061701de : job for the filters

sev: Info

Type: User

args:

jobid
filters

cause: N/A

workaround: N/A

061701df : no job found with the filters

sev: Info

Type: User

args:

filters

cause: N/A

workaround: N/A

061701e0 : Finding latest qkview job

sev: Info

Type: Application

args: N/A

cause: N/A

workaround: N/A

061701e1 : latest job details

sev: Info

Type: User

args:

cause: N/A

workaround: N/A

061701e2 : Starting mTLS Rest API Server on port 38081

sev: Info

Type: System

args: N/A

cause: N/A

workaround: N/A

061701e3 : Rest API Server stopped

sev: Critical

Type: System

args:

error

cause: REST API server stopped due to critical error

workaround: Check server logs and restart service

061701e4 : Error while fetching deployment list. Error %s

sev: Error

Type: Application

args: N/A

cause: Kubernetes API server is unreachable or down

workaround: Check Kubernetes API, permissions, namespace, network connectivity

061701e5 : Error while fetching daemonset list. Error %s

sev: Error

Type: Application

args: N/A

cause: Failed to list deployments from Kubernetes API server

workaround: Check Kubernetes API, permissions, cluster health, network connectivity

061701e6 : TMM is created as deployment

sev: Debug

Type: Application

args: N/A

cause: N/A

workaround: N/A

061701e7 : TMM is created as daemonset

sev: Debug

Type: Application

args: N/A

cause: N/A

workaround: N/A

061701e8 : Error in fetching deployment details from cluster

sev: Error

Type: Application

args:

error:

cause: Failed to list deployments from Kubernetes API server

workaround: Check Kubernetes API, permissions, cluster health, network connectivity

061701e9 : Watch namespaces in the cluster are

sev: Debug

Type: Application

args:

namespace(s):

cause: N/A

workaround: N/A

061701ea : Error in fetching CRs from watch namespaces

sev: Error

Type: Application

args:

error:

cause: Failed to fetch custom resources from namespace

workaround: Check Kubernetes API, permissions, CRDs, namespace, network connectivity

061701eb : Watch namespace have CRs

sev: Debug

Type: Application

args: N/A

cause: N/A

workaround: N/A

061701ec : No CRs configured in watch namespace

sev: Debug

Type: Application

args:

cause: N/A

workaround: N/A

061701ed : error in fetching pods

sev: Error

Type: Application

args:

error

cause: Failed to list pods from Kubernetes API

workaround: Check Kubernetes API, permissions, namespace, label selector, network connectivity

061701ee : Error in fetching k8s version

sev: Error

Type: Application

args:

error

cause: Failed to fetch Kubernetes version from API server

workaround: Check API server health, permissions, network connectivity

061701f0 : Fetching deployment environment variables from containers

sev: Debug

Type: Application

args: N/A

cause: N/A

workaround: N/A

061701f1 : watch namespace fetched from deployment

sev: Debug

Type: Application

args:

namespace:

cause: N/A

workaround: N/A

061701f2 : Error in fetching node list, ignore if not applicable.

sev: Error

Type: Application

args:

error

cause: Failed to fetch node list from Kubernetes API

workaround: Check API, permissions, node labels, network connectivity

061701f3 : Failed to create telemetryreports secret

sev: Error

Type: Application

args:

error

cause: Failed to create or update telemetryreports secret.

workaround: Check API, permissions, namespace, secret size/format.

061701f4 : Telemetry reports not equal on field name '%v:%v' (%v != %v)

sev: Error

Type: Application

args: N/A

cause: N/A

workaround: N/A

061701f5 : Telemetry reports not equal on field name '%v' (%v != %v)

sev: Error

Type: Application

args: N/A

cause: N/A

workaround: N/A

061701f6 : Telemetry reports not equal on field name '%v ReplicaCount:%v' (%v != %v)

sev: Error

Type: Application

args: N/A

cause: N/A

workaround: N/A

061701f7 : Telemetry reports not equal on field name '%v ThreadCount:%v' (%v != %v)

sev: Error

Type: Application

args: N/A

cause: N/A

workaround: N/A

061701f8 : ERROR in unmarshalling json

sev: Error

Type: Application

args:

error

cause: N/A

workaround: N/A

061701f9 : ERROR in unmarshalling CPU metric data in bytes

sev: Error

Type: Application

args:

error

cause: Invalid or malformed CPU metric JSON data

workaround: Check CPU metric data format and data source

061701fa : ERROR in marshalling CRD metric data to bytes

sev: Error

Type: Application

args:

error

cause: Failed to marshal CRD metric data to JSON bytes

workaround: Check CRD metric data and content validity

061701fb : ERROR in unmarshalling CRD metric data in bytes

sev: Error

Type: Application

args:

error

cause: Invalid or malformed CRD metric JSON data

workaround: Check CRD metric data format and data source

061701fc : ERROR in marshalling TMM metric data to bytes

sev: Error

Type: Application

args:

error

cause: Failed to marshal TMM usage metric data to JSON bytes

workaround: Check TMM usage data structure and content validity

061701fd : ERROR in unmarshalling TMM metric data in bytes

sev: Error

Type: Application

args:

error

cause: Invalid or malformed TMM usage metric JSON data

workaround: Check TMM usage metric data format and data source

061701fe : ERROR in marshalling DPU metric data to bytes

sev: Error

Type: Application

args:

error

cause: Failed to marshal DPU metric data to JSON bytes

workaround: Check DPU metric data structure and content validity

061701ff : ERROR in unmarshalling DPU metric data in bytes

sev: Error

Type: Application

args:

error

cause: Invalid or malformed DPU metric JSON data

workaround: Check DPU metric data format and data source

06170200 : Error reading configmap

sev: Error

Type: Application

args:

error

cause: Failed to read required ConfigMap from Kubernetes

workaround: Check ConfigMap existence, API access, permissions, and namespace

06170201 : Error marshalling DPU details

sev: Error

Type: Application

args:

error

cause: Failed to marshal DPU metric data to JSON

workaround: Check DPU data structure and content for serialization issues

06170202 : ERROR in getting report

sev: Error

Type: Application

args:

error

cause: Failed to convert environment details to JSON format.

workaround: Check TMM, DPU and CPU metric data format and data source.

06170203 : Error in storing to secret

sev: Error

Type: Application

args:

error

cause: Failed to store telemetry report data in Kubernetes secret

workaround: Check secret permissions, API access, and data format validity

06170204 : ERROR in storing reports in secret

sev: Error

Type: Application

args:

error

cause: Failed to save telemetry reports to the Kubernetes secret.

workaround: Check secret permissions, API access, namespace, and data size.

06170205 : Failed to read telemetryreports secret store

sev: Error

Type: Application

args:

error

cause: Failed to read telemetry report data from Kubernetes.

workaround: Check secret existence, access permissions, and namespace configuration.

06170206 : Failed to unmarshal telemetry status secret store

sev: Error

Type: Application

args:

error

cause: Failed to parse telemetry status data from storage.

workaround: Check data format, integrity, and storage content validity.

06170207 : ERROR in Marshling telemetry reports

sev: Error

Type: Application

args:

error

cause: Failed to convert telemetry reports data to JSON format.

workaround: Check telemetry reports structure and data for serialization issues.

06170208 : Storing telemetry reports to secret

sev: Info

Type: Application

args:

telemetryReport

cause: N/A

workaround: N/A

06170209 : Failed to store telemetry reports to secret

sev: Error

Type: Application

args:

error
telemetryreports

cause: Failed to save telemetry report data to Kubernetes storage.

workaround: Check storage permissions, API access, namespace, and data size limits.

0617020a : ERROR in storing reports in secret

sev: Error

Type: Application

args:

error

cause: Failed to store telemetry report data in Kubernetes storage.

workaround: Check storage permissions, API access, namespace, and data size limits.

0617020b : Error in storing reports in secret

sev: Error

Type: Application

args:

error

cause: Failed to store updated telemetry report data in secure storage.

workaround: Check storage permissions, API access, namespace, and data size limits.

0617020c : Error in storing reports in secret

sev: Error

Type: Application

args:

error

cause: Failed to store current telemetry report data in Kubernetes storage.

workaround: Check storage permissions, API access, namespace, and data size limits.

0617020d : Error in fetching cluster nodes

sev: Error

Type: Application

args:

error

cause: Failed to fetch node list from Kubernetes API

workaround: Check API, permissions, network connectivity, cluster health

0617020e : Error fetching specific node

sev: Error

Type: Application

args:

node
error

cause: Failed to fetch node from Kubernetes API

workaround: Check API, permissions, network connectivity, cluster health

0617020f : Successfully fetched allowed nodes

sev: Debug

Type: Application

args:

requestedCount
foundCount

cause: N/A

workaround: N/A

06170210 : Fetching specific nodes from allowed nodes

sev: Debug

Type: Application

args:

nodeCount

cause: N/A

workaround: N/A

06170211 : Duplicate node in ALLOWED_NODES_CSV skipped

sev: Debug

Type: Application

args:

node

cause: N/A

workaround: N/A

Previous Next