Back to Meshery

Error Code Reference

docs/static/v0.5/reference/error-codes/index.html

1.0.18129.8 KB
Original Source

Error Code Reference

Error Codes and Troubleshooting

Meshery and it’s components use a common framework (defined within MeshKit) to generate and document an error with a unique identifier - an error code. Each error code identifies the source component for the error and a standard set of information to describe the error and provide helpful details for troubleshooting the situation surrounding the specific error.

Error Code Categories by Component

Component TypeComponent Name
componentmeshery-server
adaptermeshery-linkerd
adaptermeshery-consul
adaptermeshery-kuma
adaptermeshery-osm
adaptermeshery-istio
clientmesheryctl
adaptermeshery-nginx-sm
adapternsm
librarymeshkit
adaptermeshery-traefik-mesh
adaptercilium
librarymeshery-adapter-library

Meshery Server

Error Name Error CodeSeverityShort Description
ErrInvalidRequestCode 1000
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNilClientCode 1001AlertKubernetes client not initialized
_ Probable Cause: _
Kubernetes config is not accessible to meshery or not valid
_ Suggested Remediation: _
Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized
_ Long Description: _
Kubernetes config is not initialized with Meshery
ErrCreateDataCode 1002
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrQueryCode 1003AlertError while querying data
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Invalid Query performed in Meshery Database
ErrMeshsyncSubscriptionCode 1004AlertMeshSync Subscription failed
_ Probable Cause: _
Could be a network issue
_ Suggested Remediation: _
Check if meshery server is reachable from the browser
_ Long Description: _
GraphQL subscription for MeshSync stopped
ErrOperatorSubscriptionCode 1005
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrAddonSubscriptionCode 1006
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrControlPlaneSubscriptionCode 1007
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrMesheryClientCode 1008
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrSubscribeChannelCode 1009AlertUnable to subscribe to channel
_ Probable Cause: _
Could be a network issue Meshery Broker could have crashed
_ Suggested Remediation: _
Check if Meshery Broker is reachable from Meshery Server Check if Meshery Broker is up and running inside the configured cluster
_ Long Description: _
Unable to create a broker subscription
ErrPublishBrokerCode 1010AlertUnable to publish to broker
_ Probable Cause: _
Could be a network issue Meshery Broker could have crashed
_ Suggested Remediation: _
Check if Meshery Broker is reachable from Meshery Server Check if Meshery Broker is up and running inside the configured cluster
_ Long Description: _
Unable to create a broker publisher
ErrNoMeshSyncCode 1011AlertDatabase handler not initialized
_ Probable Cause: _
Meshery Database is crashed or not reachable
_ Suggested Remediation: _
Restart Meshery Server Please check if Meshery server is accessible to the Database
_ Long Description: _
Meshery Database handler is not accessible to perform operations
ErrNoExternalEndpointCode 1012
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDataPlaneSubscriptionCode 1013AlertData Plane Subscription failed
_ Probable Cause: _
Could be a network issue
_ Suggested Remediation: _
Check if meshery server is reachable from the browser
_ Long Description: _
GraphQL subscription for Data Plane stopped
ErrGettingNamespaceCode 1014AlertCannot get available namespaces
_ Probable Cause: _
The table in the database might not exist
_ Suggested Remediation: _
_ Long Description: _
ErrFetchingPatternsCode 1015AlertCannot fetch patterns
_ Probable Cause: _
There might be something wrong with the Meshery or Meshery Cloud
_ Suggested Remediation: _
Try again, if still exist, please post an issue on Meshery repository
_ Long Description: _
ErrInvalidK8SConfigCode 2000
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNilClientCode 2001AlertKubernetes client not initialized
_ Probable Cause: _
Kubernetes config is not accessible to meshery or not valid
_ Suggested Remediation: _
Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized
_ Long Description: _
Kubernetes config is not initialized with Meshery
ErrPrometheusScanCode 2002AlertUnable to connect to prometheus
_ Probable Cause: _
Prometheus endpoint might not be reachable from meshery Prometheus endpoint is incorrect
_ Suggested Remediation: _
Check if your Prometheus and Grafana Endpoint are correct Connect to Prometheus and Grafana from the settings page in the UI
_ Long Description: _
ErrGrafanaScanCode 2003AlertUnable to connect to grafana
_ Probable Cause: _
Grafana endpoint might not be reachable from meshery Grafana endpoint is incorrect
_ Suggested Remediation: _
Check if your Grafana Endpoint is correct Connect to Grafana from the settings page in the UI
_ Long Description: _
ErrRecordPreferencesCode 2004Alertunable to save user config data
_ Probable Cause: _
User token might be invalid db might be corrupted
_ Suggested Remediation: _
Relogin to Meshery
_ Long Description: _
ErrGrafanaConfigCode 2005AlertGrafana endpoint not configured
_ Probable Cause: _
Grafana endpoint might not be reachable from meshery
_ Suggested Remediation: _
Setup your Grafana Endpoint via the settings dashboard
_ Long Description: _
Cannot find valid grafana endpoint in user pref
ErrPrometheusConfigCode 2006AlertPrometheus endpoint not configured
_ Probable Cause: _
Prometheus endpoint might not be reachable from meshery
_ Suggested Remediation: _
Setup your Prometheus Endpoint via the settings dashboard
_ Long Description: _
Cannot find valid Prometheus endpoint in user pref
ErrGrafanaQueryCode 2007AlertUnable to query grafana
_ Probable Cause: _
Grafana query did not get executed from meshery Grafana query is invalid
_ Suggested Remediation: _
Check if your Grafana query is correct Connect to Grafana from the settings page in the UI
_ Long Description: _
ErrPrometheusQueryCode 2008AlertUnable to query prometheus
_ Probable Cause: _
Prometheus query did not get executed from meshery Prometheus query is invalid
_ Suggested Remediation: _
Check if your Prometheus query is correct Connect to Prometheus and Grafana from the settings page in the UI
_ Long Description: _
ErrGrafanaBoardsCode 2009
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrPrometheusBoardsCode 2010
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrStaticBoardsCode 2011Alertunable to get static board
_ Probable Cause: _
No boards could be available in grafana
_ Suggested Remediation: _
_ Long Description: _
unable to get static board
ErrRequestBodyCode 2012
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrMarshalCode 2013
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrUnmarshalCode 2014
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrEncodingCode 2015
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParseBoolCode 2016Alertunable to parse :
_ Probable Cause: _
Failed due to invalid value of :
_ Suggested Remediation: _
please provide a valid value for :
_ Long Description: _
ErrStreamEventsCode 2017AlertThere was an error connecting to the backend to get events
_ Probable Cause: _
Websocket is blocked in the network Meshery UI is not able to reach the Meshery server
_ Suggested Remediation: _
Ensure Meshery UI is able to reach the Meshery server
_ Long Description: _
ErrStreamClientCode 2018AlertEvent streaming ended
_ Probable Cause: _
Websocket is blocked in the network Meshery UI is not able to reach the Meshery server
_ Suggested Remediation: _
Ensure Meshery UI is able to reach the Meshery server
_ Long Description: _
ErrUnmarshalEventCode 2019
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrPublishSmiResultsCode 2020AlertError publishing SMI results
_ Probable Cause: _
Meshery Cloud is not functional or reachable
_ Suggested Remediation: _
Make sure meshery cloud is up and reachable
_ Long Description: _
ErrMarshalEventCode 2021
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrPluginOpenCode 2022AlertError opening the plugin
_ Probable Cause: _
Plugin is not available in the location plugin does not match with meshery version
_ Suggested Remediation: _
Make sure the plugin is compatible with Meshery server
_ Long Description: _
ErrPluginLookupCode 2023AlertError performing a plugin lookup
_ Probable Cause: _
Plugin is not available in the location
_ Suggested Remediation: _
Make sure the plugin is compatible with Meshery server
_ Long Description: _
ErrPluginRunCode 2024AlertError running meshery plugin
_ Probable Cause: _
plugin does not match with meshery version
_ Suggested Remediation: _
Make sure the plugin is compatible with Meshery server
_ Long Description: _
ErrParseFormCode 2025Alertunable to parse form
_ Probable Cause: _
The data provided could be invalid
_ Suggested Remediation: _
Make sure to enter valid parameters in the form
_ Long Description: _
ErrQueryGetCode 2026Alertunable to get:
_ Probable Cause: _
Query parameter is not a part of the request
_ Suggested Remediation: _
Make sure to pass the query paramater in the request
_ Long Description: _
ErrGetResultCode 2027Alertunable to get result
_ Probable Cause: _
Result Identifier provided is not valid Result did not persist in the database
_ Suggested Remediation: _
Make sure to provide the correct identifier for the result
_ Long Description: _
ErrConvertToSpecCode 2028Alertunable to convert to spec
_ Probable Cause: _
The performance spec format is invalid
_ Suggested Remediation: _
Make sure to provide the correct spec
_ Long Description: _
ErrFetchSMIResultsCode 2029Alertunable to fetch SMI results
_ Probable Cause: _
SMI results did not get persisted Result identifier is invalid
_ Suggested Remediation: _
Make sure to provide the correct identifier for the result
_ Long Description: _
ErrFormFileCode 2030Alerterror getting k8s file
_ Probable Cause: _
The kubeconfig file does not exist in the location
_ Suggested Remediation: _
Make sure to upload the correct kubeconfig file
_ Long Description: _
ErrReadConfigCode 2031Alerterror reading config
_ Probable Cause: _
The kubeconfig file is empty or not valid
_ Suggested Remediation: _
Make sure to upload the correct kubeconfig file
_ Long Description: _
ErrLoadConfigCode 2032Alertunable to load kubernetes config
_ Probable Cause: _
The kubeconfig file is empty or not valid
_ Suggested Remediation: _
Make sure to upload the correct kubeconfig file
_ Long Description: _
ErrOpenFileCode 2033Alertunable to open file:
_ Probable Cause: _
The file does not exist in the location
_ Suggested Remediation: _
Make sure to upload the correct file
_ Long Description: _
ErrKubeVersionCode 2034Alertunable to get kubernetes version
_ Probable Cause: _
Kubernetes might not be reachable from meshery
_ Suggested Remediation: _
Make sure meshery has connectivity to kubernetes
_ Long Description: _
ErrAddAdapterCode 2035AlertmeshLocationURL is empty
_ Probable Cause: _
meshLocationURL cannot be empty to add an adapter
_ Suggested Remediation: _
please provide the meshLocationURL
_ Long Description: _
meshLocationURL is empty to add an adapter
ErrRetrieveDataCode 2036AlertUnable to retrieve the requested data
_ Probable Cause: _
Adapter operation invalid
_ Suggested Remediation: _
Make sure adapter is reachable and running
_ Long Description: _
ErrValidAdapterCode 2037AlertUnable to find valid Adapter URL
_ Probable Cause: _
Given adapter URL is not valid
_ Suggested Remediation: _
Please provide a valid Adapter URL
_ Long Description: _
unable to find a valid adapter for the given adapter URL
ErrOperationIDCode 2038AlertError generating the operation Id
_ Probable Cause: _
Adapter operation invalid
_ Suggested Remediation: _
Make sure adapter is reachable and running
_ Long Description: _
ErrMeshClientCode 2039AlertError creating a mesh client Error pinging the mesh adapter
_ Probable Cause: _
Adapter could not be pinged
_ Suggested Remediation: _
Unable to connect to the Mesh adapter using the given config, please try again
_ Long Description: _
Unable to create a mesh client Unable to ping the mesh adapter
ErrApplyChangeCode 2040AlertError applying the change
_ Probable Cause: _
Adapter operation invalid
_ Suggested Remediation: _
Make sure adapter is reachable and running
_ Long Description: _
ErrRetrieveMeshDataCode 2041AlertError getting operations for the mesh Error getting service mesh name
_ Probable Cause: _
unable to retrieve the requested data
_ Suggested Remediation: _
Make sure adapter is reachable and running
_ Long Description: _
ErrApplicationFailureCode 2042Alertfailed to the application
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDecodingCode 2043AlertError decoding the :
_ Probable Cause: _
Object is not a valid json object
_ Suggested Remediation: _
Make sure if the object passed is a valid json
_ Long Description: _
ErrRetrieveUserTokenCode 2044AlertFailed to get the user token
_ Probable Cause: _
User token could be expired
_ Suggested Remediation: _
Re-initiate login
_ Long Description: _
ErrFailToSaveCode 2045AlertFailed to Save:
_ Probable Cause: _
Meshery Database could be down or not reachable
_ Suggested Remediation: _
Restart Meshery instance and make sure database is up and reachable
_ Long Description: _
ErrFailToDeleteCode 2046AlertFailed to Delete:
_ Probable Cause: _
Meshery Database could be down or not reachable
_ Suggested Remediation: _
Restart Meshery instance and make sure database is up and reachable
_ Long Description: _
ErrErrNewDynamicClientGeneratorCode 2048AlertUnable to generate the dynamic client generator
_ Probable Cause: _
Kubernetes config is not accessible to meshery or not valid
_ Suggested Remediation: _
Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized
_ Long Description: _
ErrInvalidK8SConfigCode 2049
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrClientConfigCode 2050
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrFetchKubernetesNodesCode 2051AlertUnable to fetch kubernetes nodes
_ Probable Cause: _
Kubernetes API server might not be reachable from the Meshery server
_ Suggested Remediation: _
Make sure kubernetes API server is reachable from meshery server
_ Long Description: _
ErrInvalidLTURLCode 2053Alertinvalid loadtest url:
_ Probable Cause: _
URL for load test could be invalid
_ Suggested Remediation: _
please refer to: https://docs.meshery.io/guides/mesheryctl#performance-management
_ Long Description: _
ErrGrafanaClientCode 2073AlertUnable to initialize Grafana Client
_ Probable Cause: _
Invalid Grafana Endpoint or API-Key
_ Suggested Remediation: _
Update your Grafana URL and API-Key from the settings page in the UI
_ Long Description: _
Unable to initializes client for interacting with an instance of Grafana server
ErrPageSizeCode 2074AlertUnable to prase the Page Size
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrPageNumberCode 2075AlertUnable to prase the Page Numer
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrResultIDCode 2076AlertGiven resultID is not valid
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Given resultID is nil
ErrPerfIDCode 2077AlertInvalid peformance profile ID
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrMarshalCode 2078
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrUnmarshalCode 2079
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGenerateUUIDCode 2080AlertUnable to generate a new UUID
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrLocalProviderSupportCode 2081AlertMethod not supported by local provider
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGrafanaOrgCode 2082AlertFailed to get Org data from Grafana
_ Probable Cause: _
Invalid URL Invalid API-Key
_ Suggested Remediation: _
_ Long Description: _
ErrGrafanaBoardsCode 2083
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGrafanaDashboardCode 2084AlertError getting grafana dashboard from UID
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGrafanaDataSourceCode 2085AlertError getting Grafana Board's Datasource
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNilQueryCode 2086AlertQuery data passed is nil
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGrafanaDataCode 2087AlertError getting data from Grafana API
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrApplicationFileNameCode 2088AlertInvalid Applicationfile
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Name field is either not present or is not valid
ErrFilterFileNameCode 2089AlertInvalid Filterfile
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Name field is either not present or is not valid
ErrPatternFileNameCode 2090AlertInvalid Patternfile
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Name field is either not present or is not valid
ErrMakeDirCode 2091AlertUnable to create directory/folder
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrFolderStatCode 2092AlertUnable to find (os.stat) the folder
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrUserIDCode 2093AlertUser ID is empty
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDBConnectionCode 2094AlertConnection to DataBase does not exist
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNilConfigDataCode 2095AlertGiven config data is nil
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDBOpenCode 2096AlertUnable to open the database
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDBRLockCode 2097AlertUnable to obtain read lock from bitcask store
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDBLockCode 2098AlertUnable to obtain write lock from bitcask store
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDBReadCode 2099AlertUnable to read data from bitcast store
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDBDeleteCode 2100AlertUnable to delete config data for the user
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCopyCode 2101AlertError occurred while copying
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDBPutCode 2102AlertUnable to Persist config data.
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrPrometheusGetNodesCode 2103AlertPrometheus Client unable to get all nodes
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrPrometheusLabelSeriesCode 2104AlertUnable to get the label set series
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrPrometheusQueryRangeCode 2105AlertUnable to fetch data for the query
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrPrometheusStaticBoardCode 2106AlertUnbale to get Static Boards
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrTokenRefreshCode 2107AlertError occurred while Refresing the token
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetTokenCode 2108AlertError occurred while getting token from the Browser Cookie
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDataReadCode 2109AlertEeror occurred while reading from the Reader
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrTokenDecodeCode 2110AlertError occurred while Decoding Token Data
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNilJWKsCode 2111AlertInvalid JWks
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Value of JWKs is nil
ErrNilKeysCode 2112AlertKey not found
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
JWK not found for the given KeyID
ErrTokenExpiredCode 2113AlertToken has expired
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Token is invalid, it has expired
ErrTokenClaimsCode 2114AlertError occurred while prasing claims
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrTokenClientCheckCode 2115AlertError occurred while performing token check HTTP request
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrTokenPraseCode 2116AlertError occurred while Prasing and validating the token
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrJWKsKeysCode 2117AlertUnable to fetch JWKs keys from the remote provider
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDecodeBase64Code 2118AlertError occurred while decoding base65 string
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrMarshalPKIXCode 2119AlertError occurred while marshaling PKIX
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrEncodingPEMCode 2120AlertError occurred while encoding jwk to pem
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrPraseUnverifiedCode 2121AlertError occurred while prasing tokens (unverified)
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrEncodingCode 2122
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrFetchCode 2123AlertUnable to fetch data from the Provider
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrPostCode 2124AlertUnable to post data to the Provider
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDeleteCode 2125AlertUnable to delete data from the Provider
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInvalidCapabilityCode 2126AlertCapablity is not supported by your Provider
_ Probable Cause: _
Not logged in to the vaild remote Provider
_ Suggested Remediation: _
Connect to the vaild remote Provider Ask the Provider Adim for access
_ Long Description: _
You dont have access to the capability
ErrResultDataCode 2127Alertgiven result data is nil
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrUnableToPersistsResultCode 2128Alertunable to persists the result data
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrValidURLCode 2129AlertEnter valid URLs
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrTestEndpointCode 2130Alertminimum one test endpoint needs to be specified
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrLoadgeneratorCode 2131Alertspecify valid Loadgenerator
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrProtocolCode 2132Alertspecify the Protocol for all clients
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrTestClientCode 2133Alertminimum one test client needs to be specified
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParsingTestCode 2134Alerterror parsing test duration, please refer to: https://docs.meshery.io/guides/mesheryctl#performance-management
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrFieldCode 2135AlertError: name field is blank
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrSaveSessionCode 2136Alertunable to save session
_ Probable Cause: _
User session could be expired
_ Suggested Remediation: _
Re-initiate login
_ Long Description: _
ErrDataSendCode 2137
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrVersionCompareCode 2138
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrKubeClientCode 2139AlertFailed to Create Kube Client
_ Probable Cause: _
Check Kubernetes
_ Suggested Remediation: _
Check your kubeconfig if valid Ensure meshery is able to reach the kubernetes cluster
_ Long Description: _
ErrWorkloadDefinitionCode 2140AlertFailed to load Workload Definition
_ Probable Cause: _
Workload Definition is invalid or unable to process
_ Suggested Remediation: _
Check Workload Definition
_ Long Description: _
ErrTraitDefinitionCode 2141AlertFailed to Encode Trait Definition
_ Probable Cause: _
Trait Definition is invalid or unable to process
_ Suggested Remediation: _
Check Trait Definition
_ Long Description: _
ErrScopeDefinitionCode 2142AlertFailed to Encode Scope Definition
_ Probable Cause: _
Trait Definition is invalid or unable to process
_ Suggested Remediation: _
Check Trait Definition
_ Long Description: _
ErrPatternFileCode 2143AlertFailed to Parse Pattern File
_ Probable Cause: _
Trait Definition is invalid or unable to process
_ Suggested Remediation: _
Check Trait Definition
_ Long Description: _
ErrExecutionPlanCode 2144AlertFailed to Create Execution Plan
_ Probable Cause: _
Trait Definition is invalid or unable to process
_ Suggested Remediation: _
Check Trait Definition
_ Long Description: _
ErrInvalidPatternCode 2145AlertInvalid Pattern, execution is infeasible
_ Probable Cause: _
Trait Definition is invalid or unable to process
_ Suggested Remediation: _
Check Trait Definition
_ Long Description: _
ErrCompConfigPairsCode 2146
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrFetchDataCode 2147Alertunable to fetch result data
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrIndexOutOfRangeCode 2148AlertError: index out of range
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrSessionCopyCode 2149AlertError: session copy error
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCreateDirCode 2150
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInvalidRequestObjectCode 2151
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrChangeK8sContextCode 2152
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrApplyHelmChartCode 2155AlertError occurred while applying Helm Chart
_ Probable Cause: _
Kubernetes cluster might not be connected Leftover resources from partial install
_ Suggested Remediation: _
Try reinstalling Try reconnecting your kubernetes cluster Clean up artifacts from preinstalled helm release manually
_ Long Description: _
ErrGetFilterCode 2156AlertError failed to get filter
_ Probable Cause: _
Cannot get the filter with the given Filter ID
_ Suggested Remediation: _
Check if the given Filter ID is correct
_ Long Description: _
ErrSaveFilterCode 2157AlertError failed to save filter
_ Probable Cause: _
Cannot save the Filter due to wrong path or URL
_ Suggested Remediation: _
Check if the given path or URL of the filter is correct
_ Long Description: _
ErrDecodeFilterCode 2158AlertError failed to decode filters data into go slice
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrEncodeFilterCode 2159AlertError failed to encode filter
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrImportFilterCode 2160AlertError failed to import filter
_ Probable Cause: _
Cannot save the Filter due to wrong path or URL
_ Suggested Remediation: _
Check if the given path or URL of the Filter is correct
_ Long Description: _
ErrFetchFilterCode 2161AlertError failed to fetch filter
_ Probable Cause: _
Failed to retrieve the list of all the Filters
_ Suggested Remediation: _
_ Long Description: _
ErrDeleteFilterCode 2162AlertError failed to delete filter
_ Probable Cause: _
Failed to delete Filter with the given ID
_ Suggested Remediation: _
Check if the Filter ID is correct
_ Long Description: _
ErrSavePatternCode 2163AlertError failed to save pattern
_ Probable Cause: _
Cannot save the Pattern due to wrong path or URL
_ Suggested Remediation: _
Check if the given path or URL of the Pattern is correct
_ Long Description: _
ErrGetPatternCode 2164AlertError failed to get pattern
_ Probable Cause: _
Cannot get the Pattern with the given Pattern ID
_ Suggested Remediation: _
Check if the given Pattern ID is correct
_ Long Description: _
ErrDeletePatternCode 2165AlertError failed to delete pattern
_ Probable Cause: _
Failed to delete Pattern with the given ID
_ Suggested Remediation: _
Check if the Pattern ID is correct
_ Long Description: _
ErrFetchPatternCode 2166AlertError failed to fetch pattern
_ Probable Cause: _
Failed to retrieve the list of all the Patterns
_ Suggested Remediation: _
_ Long Description: _
ErrImportPatternCode 2167AlertError failed to import pattern
_ Probable Cause: _
Cannot save the Pattern due to wrong path or URL
_ Suggested Remediation: _
Check if the given path or URL of the Pattern is correct
_ Long Description: _
ErrEncodePatternCode 2168AlertError failed to encode pattern
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDecodePatternCode 2169AlertError failed to decode patterns data into go slice
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParsePatternCode 2170AlertError failed to parse pattern file
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrConvertPatternCode 2171AlertError failed to convert PatternFile to Cytoscape object
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrSavingUserPreferenceCode 2172AlertError saving user preference.
_ Probable Cause: _
Invalid data passed Unable to connect with provider
_ Suggested Remediation: _
Pass valid values for preferences Make sure provider supports saving user preferences Make sure you're connected with provider Make sure extension provides these preferences
_ Long Description: _
ErrMesheryInstanceIDCode 2173
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInvalidKubeConfigCode 2174AlertInvalid Kube Config
_ Probable Cause: _
Meshery handler failed to find a valid kubernetes config for the deployment
_ Suggested Remediation: _
Try uploading a new kubeconfig and also ensure that meshery can reach kubernetes API server
_ Long Description: _
ErrInvalidKubeHandlerCode 2175AlertInvalid Kube Handler
_ Probable Cause: _
Meshery handler failed to find a valid kubernetes handler for the deployment
_ Suggested Remediation: _
Try uploading a new kubeconfig and also ensure that meshery can reach kubernetes API server
_ Long Description: _
ErrInvalidKubeContextCode 2176AlertInvalid Kube Context
_ Probable Cause: _
Meshery handler failed to find a valid kubernetes context for the deployment
_ Suggested Remediation: _
Try uploading a new kubeconfig and also ensure that meshery can reach kubernetes API server
_ Long Description: _
ErrCreatingKubernetesComponentsCode 2177Alert
_ Probable Cause: _
component generation was canceled due to deletion or reload of K8s context Invalid kubeconfig Filters passed incorrectly in config Could not fetch API resources from Kubernetes server
_ Suggested Remediation: _
If there is the log "Starting to register ..." for the same contextID after this error means that for some reason the context was reloaded which caused this run to abort. In that case, this error can be ignored. Make sure that the configuration filters passed are in accordance with output from /openapi/v2
_ Long Description: _
ErrInvalidOAMTypeCode 2178
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrKubectlDescribeCode 2179
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrEmptyCurrentK8sContextCode 2180AlertCurrent kubernetes context is empty
_ Probable Cause: _
Meshery is crashed or not reachable
_ Suggested Remediation: _
Restart Meshery Server Please check if Meshery server is accessible to the Database
_ Long Description: _
Meshery is not able to get the current kubernetes context
ErrFetchNodesCode 2181AlertUnable to get the list of nodes
_ Probable Cause: _
Kubernetes API server might not be reachable from the Meshery server
_ Suggested Remediation: _
Make sure kubernetes API server is reachable from meshery server
_ Long Description: _
ErrFetchKubernetesVersionCode 2182AlertUnable to fetch kubernetes version
_ Probable Cause: _
Kubernetes API server might not be reachable from the Meshery server
_ Suggested Remediation: _
Make sure kubernetes API server is reachable from meshery server
_ Long Description: _
ErrScanKubernetesCode 2183AlertUnable to scan kubernetes
_ Probable Cause: _
Kubernetes API server might not be reachable from the Meshery server
_ Suggested Remediation: _
Make sure kubernetes API server is reachable from meshery server
_ Long Description: _
ErrRetrievePodListCode 2184AlertUnable to retrieve pod list
_ Probable Cause: _
Kubernetes API server might not be reachable from the Meshery server Requested resource might not be available
_ Suggested Remediation: _
Make sure kubernetes API server is reachable from meshery server Make sure you are requesting for a valid resource
_ Long Description: _
ErrDetectServiceForDeploymentImageCode 2185AlertUnable to detect service for deployment image
_ Probable Cause: _
Kubernetes API server might not be reachable from the Meshery server Requested resource might not be available
_ Suggested Remediation: _
Make sure kubernetes API server is reachable from meshery server Make sure you are requesting for a valid resource
_ Long Description: _
ErrRetrieveNamespacesListCode 2186AlertUnable to get the list of namespaces
_ Probable Cause: _
Kubernetes API server might not be reachable from the Meshery server Requested resource might not be available
_ Suggested Remediation: _
Make sure kubernetes API server is reachable from meshery server Make sure you are requesting for a valid resource
_ Long Description: _
ErrGetNamespaceDeploymentsCode 2187AlertUnable to get deployments in the namespace
_ Probable Cause: _
Kubernetes API server might not be reachable from the Meshery server Requested resource might not be available
_ Suggested Remediation: _
Make sure kubernetes API server is reachable from meshery server Make sure you are requesting for a valid resource
_ Long Description: _
ErrDetectServiceWithNameCode 2188AlertUnable to get services from the cluster with the name given in names parameter
_ Probable Cause: _
Kubernetes API server might not be reachable from the Meshery server Requested resource might not reachable from Meshery server
_ Suggested Remediation: _
Make sure kubernetes API server is reachable from meshery server Make sure the network connectivity is up between meshery server and the service endpoint
_ Long Description: _
ErrGeneratingLoadTestCode 2189AlertUnable to generate load test
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrRunningTestCode 2190AlertUnable to run test
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrConvertingResultToMapCode 2191AlertUnable to convert from the result to map
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrUnmarshalCode 2192
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGrpcSupportCode 2193Alertdoes not support gRPC load testing
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrStartingNighthawkServerCode 2194AlertUnable to start the nighthawk server
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrTransformingDataCode 2195AlertError while transforming data
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrRunningNighthawkServerCode 2196AlertError while running nighthawk server
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrAddAndValidateExtraHeaderCode 2197AlertUnable to add and validate extra header
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInClusterConfigCode 2198AlertUnable to load in-cluster kubeconfig
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNewKubeClientGeneratorCode 2199AlertUnable to generate new kube dynamic client
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrRestConfigFromKubeConfigCode 2200AlertUnable to create rest config from kube congif
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNewKubeClientCode 2201AlertUnable to create new kube client
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrWriteResponseCode 2202AlertError writing response
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrTestConfigsCode 2203AlertError fetching test configs
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInvalidGenValueCode 2204AlertInvalid value for gen
_ Probable Cause: _
_ Suggested Remediation: _
please provide a valid value for gen (load generator)
_ Long Description: _
ErrFailToLoadExtensionsCode 2205AlertFailed to Load Extensions from Package
_ Probable Cause: _
Plugin is not available in the location plugin does not match with meshery version
_ Suggested Remediation: _
Make sure the plugin is compatible with Meshery server
_ Long Description: _
ErrConversionCode 2206Alertunable to convert YAML to JSON
_ Probable Cause: _
Yaml provided is not valid
_ Suggested Remediation: _
Make sure the yaml is valid and has the right parameters
_ Long Description: _
ErrParseDurationCode 2207Alerterror parsing test duration
_ Probable Cause: _
The format of the duration passed could be incorrect
_ Suggested Remediation: _
please refer to: https://docs.meshery.io/guides/mesheryctl#performance-management
_ Long Description: _
ErrLoadTestCode 2208
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrFetchKubernetesCode 2209
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrPanicRecoveryCode 2210AlertRecovered from panic
_ Probable Cause: _
Meshery crashes
_ Suggested Remediation: _
Restart Meshery
_ Long Description: _
ErrBlankNameCode 2211AlertError: name field is blank
_ Probable Cause: _
Load test name empty or not valid
_ Suggested Remediation: _
Provide a name for the test
_ Long Description: _
ErrGetK8sComponentsCode 2212AlertCould not get K8s components for registration
_ Probable Cause: _
Invalid kubeconfig Filters passed incorrectly in config Could not fetch API resources from Kubernetes server
_ Suggested Remediation: _
Make sure that the configuration filters passed are in accordance with output from /openapi/v2
_ Long Description: _
ErrParseK8sManifestCode 2213
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCreatePatternServiceCode 2214
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrSavingSeededComponentsCode 2215AlertError while saving sample
_ Probable Cause: _
User doesn't have permission to save content.\nDatabase unreachable.\nDatabase locked or corrupt.\nContent unsupported.
_ Suggested Remediation: _
Retry fetching content\nRetry sigining in\nLogin with correct user account\nRetry after deleting '~/.meshery/config'.
_ Long Description: _
ErrGettingSeededComponentsCode 2216AlertError while getting from sample content
_ Probable Cause: _
Sample content does not exist.\nContent file format not supported.\nUser doesn't have permission to read sample content.\nContent file corrupt.
_ Suggested Remediation: _
Try restarting Meshery.\nTry fetching content again.
_ Long Description: _
ErrDownloadingSeededComponentsCode 2217Alert
_ Probable Cause: _
The content is not present at the specified url endpoint HTTP requests failed
_ Suggested Remediation: _
Make sure the content is available at the endpoints Make sure that Github is reachable and the http requests are not failing
_ Long Description: _
ErrContextIDCode 2218AlertError: Context ID is empty
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrMesheryInstanceIDCode 2219
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrMesheryNotInClusterCode 2220AlertError: Meshery is not running inside a cluster
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrBrokerNotConnectedCode 2221AlertBroker not connected
_ Probable Cause: _
Meshery Broker is crashed or not reachable
_ Suggested Remediation: _
Restart Meshery Server Please check if Meshery server has access to the Broker
_ Long Description: _
Meshery Broker is not connected to Meshery Server
ErrResolverInvalidRequestCode 2222AlertInvalid query, please check syntax
_ Probable Cause: _
_ Suggested Remediation: _
Check the query parameters and syntax of the query being run
_ Long Description: _
The Graphql query requested is invalid
ErrResolverNilClientCode 2223AlertKubernetes client not initialized
_ Probable Cause: _
_ Suggested Remediation: _
Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized
_ Long Description: _
Kubernetes config is not initialized with Meshery
ErrResolverCreateDataCode 2224
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrResolverQueryCode 2225
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrResolverMeshsyncSubscriptionCode 2226AlertMeshSync Subscription failed
_ Probable Cause: _
Could be a network issue
_ Suggested Remediation: _
Check if meshery server is reachable from the browser
_ Long Description: _
GraphQL subscription for MeshSync stopped
ErrResolverOperatorSubscriptionCode 2227AlertOperator Subscription failed
_ Probable Cause: _
Could be a network issue
_ Suggested Remediation: _
Check if meshery server is reachable from the browser
_ Long Description: _
GraphQL subscription for Operator stopped
ErrResolverAddonSubscriptionCode 2228
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrResolverControlPlaneSubscriptionCode 2229AlertControl Plane Subscription failed
_ Probable Cause: _
Could be a network issue
_ Suggested Remediation: _
Confirm that Meshery Server is reachable from your browser.
_ Long Description: _
GraphQL subscription for Control Plane stopped
ErrResolverMesheryClientCode 2230
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrResolverSubscribeChannelCode 2231
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrResolverPublishBrokerCode 2232AlertUnable to publish to broker
_ Probable Cause: _
Could be a network issue Meshery Broker could have crashed
_ Suggested Remediation: _
Check if Meshery Broker is reachable from Meshery Server Check if Meshery Broker is up and running inside the configured cluster
_ Long Description: _
Unable to create a broker publisher
ErrResolverNoMeshSyncCode 2233
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrResolverNoExternalEndpointCode 2234
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrBrokerNotFoundCode 2235AlertMeshery broker not found
_ Probable Cause: _
Invalid Grafana Endpoint or API-Key
_ Suggested Remediation: _
Update your Grafana URL and API-Key from the settings page in the UI
_ Long Description: _
Unable to find meshery broker in the cluster
ErrCreateOperatorDeploymentConfigCode 2236AlertOperator deployment configuration could not be created.
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrRequestMeshsyncStoreCode 2237AlertMeshsync store request could not be issued
_ Probable Cause: _
_ Suggested Remediation: _
Make sure meshery broker is healthy
_ Long Description: _
ErrBrokerSubscriptionCode 2238AlertCould not subscribe to the broker subject
_ Probable Cause: _
_ Suggested Remediation: _
Make sure meshery broker is healthy
_ Long Description: _
ErrMesheryControllersStatusSubscriptionCode 2239AlertCould not create meshery controllers status subcription
_ Probable Cause: _
_ Suggested Remediation: _
Make sure the controllers are deployed and their handlers are configured
_ Long Description: _
Meshery controller handlers may not be available
ErrMeshSyncEventsSubscriptionCode 2240AlertCould not create MeshSync events subcription
_ Probable Cause: _
_ Suggested Remediation: _
Make sure the controllers are deployed and their handlers are configured
_ Long Description: _
Meshery controller handlers may not be available
ErrListenAndServeCode 2248FatalListenAndServe Error
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ListenAndServe Error:
ErrCleaningUpLocalProviderCode 2249AlertError cleaning up local provider
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Error cleaning up local provider:
ErrClosingDatabaseInstanceCode 2250AlertError closing database instance
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Error closing database instance:
ErrCreatingUUIDInstanceCode 2251FatalUnable to create UUID instance
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Unable to create UUID instance:

Top


Meshery Adapter for meshery-linkerd

Error Name Error CodeSeverityShort Description
ErrEmptyConfigCode 1000AlertConfig is empty
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetLatestReleasesCode 1001Alertunable to fetch release info
_ Probable Cause: _
Checkout https://docs.github.com/en/rest/reference/repos#releases for more info
_ Suggested Remediation: _
_ Long Description: _
Unable to get the latest release info from the GithubAPI
ErrGetLatestReleaseNamesCode 1002Alertfailed to extract release names
_ Probable Cause: _
Invalid release format
_ Suggested Remediation: _
_ Long Description: _
ErrInstallLinkerdCode 1003AlertError with Linkerd operation:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrMeshConfigCode 1004AlertError configuration mesh:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrFetchManifestCode 1005AlertError fetching mesh manifest: %s
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDownloadBinaryCode 1006AlertError downloading Linkerd binary:
_ Probable Cause: _
Checkout https://docs.github.com/en/rest/reference/repos#releases for more details
_ Suggested Remediation: _
_ Long Description: _
ErrInstallBinaryCode 1007AlertError installing Linkerd binary:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrClientConfigCode 1008AlertError setting client config:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrClientSetCode 1009AlertError setting clientset:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrSampleAppCode 1011AlertError with sample app operation
_ Probable Cause: _
Invalid kubeclient config Invalid manifest
_ Suggested Remediation: _
Reconnect your adapter to meshery server to refresh the kubeclient
_ Long Description: _
Error occurred while trying to install a sample application using manifests
ErrCustomOperationCode 1012AlertError with custom operation
_ Probable Cause: _
Invalid kubeclient config Invalid manifest
_ Suggested Remediation: _
Make sure to apply a valid Kubernetes manifest
_ Long Description: _
Error occurred while applying custom manifest to the cluster
ErrOpInvalidCode 1013AlertInvalid operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInvalidOAMComponentTypeCode 1014Alertinvalid OAM component name:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrLinkerdCoreComponentFailCode 1015Alerterror in linkerd core component
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrProcessOAMCode 1016Alerterror performing OAM operations
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParseLinkerdCoreComponentCode 1017Alertlinkerd core component manifest parsing failing
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParseOAMComponentCode 1018Alerterror parsing the component
_ Probable Cause: _
Could not unmarshall configuration component received via ProcessOAM gRPC call into a valid Component struct
_ Suggested Remediation: _
Check if Meshery Server is creating valid component for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also check if Meshery Server and adapters are referring to same component struct provided in MeshKit.
_ Long Description: _
Error occurred while parsing application component in the OAM request made by Meshery server
ErrParseOAMConfigCode 1019Alerterror parsing the configuration
_ Probable Cause: _
Could not unmarshall OAM config received via ProcessOAM gRPC call into a valid Config struct
_ Suggested Remediation: _
Check if Meshery Server is creating valid config for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also, confirm that Meshery Server and Adapters are referring to same config struct provided in MeshKit
_ Long Description: _
Error occurred while parsing configuration in the request made by Meshery Server
ErrApplyHelmChartCode 1020Alerterror applying helm chart
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNilClientCode 1021AlertKubernetes client not initialized
_ Probable Cause: _
Kubernetes client not initialized
_ Suggested Remediation: _
Reconnect the Meshery Adapter to Meshery Server
_ Long Description: _
Kubernetes client is nil
ErrAddonFromHelmCode 1022AlertError with addon install operation by helm chart
_ Probable Cause: _
The helm chart URL in additional properties of addon operation might be incorrect Could not apply service patch file for the given addon
_ Suggested Remediation: _
_ Long Description: _
ErrInvalidVersionForMeshInstallationCode 1023AlertInvalid version passed for helm based installation
_ Probable Cause: _
Version might not be prefixed with "stable-" or "edge-\
_ Suggested Remediation: _
Version should be prefixed with "stable-" or "edge-\ Version might be empty
_ Long Description: _
Version passed is invalid
ErrAnnotatingNamespaceCode 1024AlertError with annotating namespace
_ Probable Cause: _
Could not get the namespace in cluster Could not update namespace in cluster
_ Suggested Remediation: _
Make sure the cluster is reachable
_ Long Description: _
ErrCertEncodeCode 1101FatalFailed to encode:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrEncodeCertificatesPEMCode 1102FatalFailed to encode certificate PEM:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrEncodePrivateKeyPEMCode 1103FatalFailed to encode private key PEM:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCreateRootCACode 1104AlertFailed to create Root CA:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGeneratePKCode 1105AlertFailed to create Private Key:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGenerateDefaultRootCACode 1106AlertFailed to create default Root CA:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetFileNamesCode 1107Alertfailed to get filenames for dynamic component generation
_ Probable Cause: _
The repository could not be cloned or reached The repository url is invalid Could not reach the remote git repository
_ Suggested Remediation: _
Make sure the owner, repo and path is correct for fetching crd names
_ Long Description: _

Top


Meshery Adapter for meshery-consul

Error Name Error CodeSeverityShort Description
ErrApplyOperationCode 1000AlertError applying operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParseOAMComponentCode 1001Alerterror parsing the component
_ Probable Cause: _
Could not unmarshall configuration component received via ProcessOAM gRPC call into a valid Component struct
_ Suggested Remediation: _
Check if Meshery Server is creating valid component for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also, check if Meshery Server and adapters are referring to same component struct provided in MeshKit.
_ Long Description: _
Error occurred while parsing application component in the OAM request made by Meshery Server
ErrParseOAMConfigCode 1002Alerterror parsing the configuration
_ Probable Cause: _
Could not unmarshall OAM config received via ProcessOAM gRPC call into a valid Config struct
_ Suggested Remediation: _
Check if Meshery Server is creating valid config for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also, confirm that Meshery Server and Adapters are referring to same config struct provided in MeshKit
_ Long Description: _
Error occurred while parsing configuration in the request made by Meshery Server
ErrProcessOAMCode 1003Alerterror performing OAM operations
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrApplyHelmChartCode 1004AlertError applying helm chart
_ Probable Cause: _
Chart could be invalid
_ Suggested Remediation: _
Use helm verify and helm lint to verify chart path and validity
_ Long Description: _
ErrMeshConfigCode 1005AlertError configuration mesh
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Error getting MeshSpecKey config from in-memory configuration
ErrConsulCoreComponentFailCode 1006Alerterror in Consul core component
_ Probable Cause: _
API version or Kind passed is empty
_ Suggested Remediation: _
Make sure API version and Kind are not empty
_ Long Description: _
ErrParseConsulCoreComponentCode 1007AlertConsul core component manifest parsing failing
_ Probable Cause: _
Could not marshall generated component to YAML
_ Suggested Remediation: _
_ Long Description: _
ErrGetLatestReleasesCode 1008AlertUnable to fetch release info
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetManifestNamesCode 1009AlertUnable to fetch manifest names from github
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrEmptyConfigCode 1010AlertConfig is empty
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrLoadingPathsetCode 1011AlertCould not create a pathset for static component generation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _

Top


Meshery Adapter for meshery-kuma

Error Name Error CodeSeverityShort Description
ErrGetLatestReleasesCode 1000Alertunable to fetch release info
_ Probable Cause: _
Checkout https://docs.github.com/en/rest/reference/repos#releases for more info
_ Suggested Remediation: _
_ Long Description: _
Unable to get the latest release info from the GithubAPI
ErrGetLatestReleaseNamesCode 1001Alertfailed to extract release names
_ Probable Cause: _
Invalid release format
_ Suggested Remediation: _
_ Long Description: _
ErrOpInvalidCode 1002AlertInvalid operation
_ Probable Cause: _
The operation is not supported by the adapter Invalid operation name
_ Suggested Remediation: _
Check if the operation name is valid and supported by the adapter
_ Long Description: _
Kuma adapter recived an invalid operation from the meshey server
ErrInstallKumaCode 1003AlertError with kuma operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Error occured while installing kuma mesh through kumactl
ErrMeshConfigCode 1004AlertError configuration mesh
_ Probable Cause: _
_ Suggested Remediation: _
Reconnect the adapter to the Meshery Server
_ Long Description: _
Error getting MeshSpecKey config from in-memory configuration
ErrFetchManifestCode 1005AlertError occured while fetching the mainfest
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrClientConfigCode 1006AlertError occured while setting client config
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrClientSetCode 1007AlertError occured while setting clientset
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrStreamEventCode 1008AlertError occured while streaming events
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrSampleAppCode 1009AlertError with sample app operation
_ Probable Cause: _
Invalid kubeclient config Invalid manifest
_ Suggested Remediation: _
Reconnect your adapter to Meshery Server to refresh the kubeclient
_ Long Description: _
Error occured while trying to install a sample application using manifests
ErrGetKumactlCode 1010AlertError getting kumactl comamndline
_ Probable Cause: _
https://download.konghq.com/mesh-alpine/kuma-\<release>-<platform>-<arch>.tar.gz might be deprecated
_ Suggested Remediation: _
_ Long Description: _
Error occured while downloadingkumactl and moving it to .meshery/bin]
ErrDownloadBinaryCode 1011AlertError downloading kuma binary
_ Probable Cause: _
Checkout https://download.konghq.com/mesh-alpine/kuma-\<release>-<platform>-<arch>.tar.gz for more details
_ Suggested Remediation: _
_ Long Description: _
Error occured while download kuma binary from its release url
ErrInstallBinaryCode 1012AlertError installing kumactl
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Error occured while installing kuma mesh through kumactl
ErrUntarCode 1013AlertError while extracting file
_ Probable Cause: _
The gzip might be corrupt
_ Suggested Remediation: _
Retry the operation
_ Long Description: _
ErrUntarDefaultCode 1014AlertError untaring opeartion default
_ Probable Cause: _
The compressed file might be corrupted
_ Suggested Remediation: _
Clear the cache and retry the operation
_ Long Description: _
Error occured in the process of untaring a compressed file
ErrMoveBinaryCode 1015AlertError occured while moving the kumactl binary
_ Probable Cause: _
Meshery adapter might not have write access
_ Suggested Remediation: _
_ Long Description: _
ErrCustomOperationCode 1016AlertError with custom operation
_ Probable Cause: _
Invalid kubeclient config Invalid manifest
_ Suggested Remediation: _
Reupload the kubconfig in the Meshery Server and reconnect the adapter
_ Long Description: _
Error occured while applying custom manifest to the cluster
ErrNilClientCode 1017AlertKubernetes client not initialized
_ Probable Cause: _
Kubernetes client not initialized
_ Suggested Remediation: _
Reconnect the adapter to Meshery Server
_ Long Description: _
Kubernetes client is nil
ErrApplyHelmChartCode 1018AlertError with helm chart operation
_ Probable Cause: _
_ Suggested Remediation: _
Invalid helm chart configuration
_ Long Description: _
Error occured while applying Helm Chart
ErrGetLatestReleaseCode 1019AlertCould not get latest version
_ Probable Cause: _
Latest version could not be found at the specified url
_ Suggested Remediation: _
_ Long Description: _
ErrInvalidOAMComponentTypeCode 1021Alertinvalid OAM component name:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrKumaCoreComponentFailCode 1022Alerterror in kuma core component
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrProcessOAMCode 1023Alerterror performing OAM operations
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParseKumaCoreComponentCode 1024Alertkuma core component manifest parsing failing
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParseOAMComponentCode 1025Alerterror parsing the component
_ Probable Cause: _
Could not unmarshall configuration component received via ProcessOAM gRPC call into a valid Component struct
_ Suggested Remediation: _
Check if Meshery Server is creating valid component for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also check if Meshery Server and adapters are referring to same component struct provided in MeshKit.
_ Long Description: _
Error occurred while parsing application component in the OAM request made by Meshery server
ErrParseOAMConfigCode 1026Alerterror parsing the configuration
_ Probable Cause: _
Could not unmarshall OAM config recieved via ProcessOAM gRPC call into a valid Config struct
_ Suggested Remediation: _
Check if Meshery Server is creating valid config for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also, confirm that Meshery Server and Adapters are referring to same config struct provided in MeshKit
_ Long Description: _
Error occured while parsing configuration in the request made by Meshery Server
ErrEmptyConfigCode 1027AlertConfig is empty
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrLoadNamespaceCode 1028AlertError occured while applying namespace
_ Probable Cause: _
Trying to access a namespace which is not available
_ Suggested Remediation: _
Verify presence of namespace. Confirm Meshery ServiceAccount permissions
_ Long Description: _

Top


Meshery Adapter for meshery-osm

Error Name Error CodeSeverityShort Description
ErrInstallOSMCode 1000AlertError with osm operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Error occured while installing osm mesh through osmctl
ErrTarXZFCode 1001AlertError while extracting file
_ Probable Cause: _
The gzip might be corrupt
_ Suggested Remediation: _
Retry the operation
_ Long Description: _
ErrMeshConfigCode 1002AlertError configuration mesh
_ Probable Cause: _
_ Suggested Remediation: _
Reconnect the adaptor to the meshkit server
_ Long Description: _
Error getting MeshSpecKey config from in-memory configuration
ErrRunOsmCtlCmdCode 1003AlertError running istioctl command
_ Probable Cause: _
Corrupted istioctl binary Command might be invalid
_ Suggested Remediation: _
_ Long Description: _
ErrDownloadBinaryCode 1004AlertError downloading osm binary
_ Probable Cause: _
Checkout https://docs.github.com/en/rest/reference/repos#releases for more details
_ Suggested Remediation: _
_ Long Description: _
Error occured while download osm binary from its github release
ErrInstallBinaryCode 1005AlertError installing osm binary
_ Probable Cause: _
Corrupted osm release binary Invalid installation location
_ Suggested Remediation: _
_ Long Description: _
ErrSampleAppCode 1006AlertError with sample app operation
_ Probable Cause: _
Invalid kubeclient config Invalid manifest
_ Suggested Remediation: _
Reconnect your adapter to meshery server to refresh the kubeclient
_ Long Description: _
Error occured while trying to install a sample application using manifests
ErrCustomOperationCode 1007AlertError with custom operation
_ Probable Cause: _
Invalid kubeclient config Invalid manifest
_ Suggested Remediation: _
Reupload the kubconfig in the Meshery Server and reconnect the adapter
_ Long Description: _
Error occured while applying custom manifest to the cluster
ErrCreatingNSCode 1008AlertError creating namespace
_ Probable Cause: _
Invalid kubeclient config Invalid manifest
_ Suggested Remediation: _
Reupload the kubeconfig in the Meshery Server and reconnect the adapter
_ Long Description: _
Error occured while applying manifest to create a namespace
ErrRunExecutableCode 1009AlertError running executable
_ Probable Cause: _
Corrupted binary Invalid operation
_ Suggested Remediation: _
Check if the adaptor is executing a deprecated command
_ Long Description: _
ErrSidecarInjectionCode 1010AlertError occured while injection sidecar
_ Probable Cause: _
Corrupted binary Invalidoperation
_ Suggested Remediation: _
Check if the adaptor is executing a deprecated command
_ Long Description: _
Error occured while injecting sidercar using osm(ctl) osm namespace add/remove \<name\>
ErrOpInvalidCode 1011AlertInvalid operation
_ Probable Cause: _
The operation is not supported by the adapter Invalid operation name
_ Suggested Remediation: _
Check if the operation name is valid and supported by the adapter
_ Long Description: _
Istio adapter recived an invalid operation from the meshey server
ErrApplyHelmChartCode 1012AlertError occured while applying Helm Chart
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNilClientCode 1013Alertkubernetes client not initialized
_ Probable Cause: _
kubernetes client not initialized
_ Suggested Remediation: _
Reconnect the adaptor to Meshery server
_ Long Description: _
Kubernetes client is nil
ErrInvalidOAMComponentTypeCode 1014Alertinvalid OAM component name:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrOSMCoreComponentFailCode 1015Alerterror in osm core component
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrProcessOAMCode 1016Alerterror performing OAM operations
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParseOSMCoreComponentCode 1017Alertosm core component manifest parsing failing
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParseOAMComponentCode 1018Alerterror parsing the component
_ Probable Cause: _
Could not unmarshall configuration component received via ProcessOAM gRPC call into a valid Component struct
_ Suggested Remediation: _
Check if Meshery Server is creating valid component for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also check if Meshery Server and adapters are referring to same component struct provided in MeshKit.
_ Long Description: _
Error occurred while parsing application component in the OAM request made by Meshery server
ErrParseOAMConfigCode 1019Alerterror parsing the configuration
_ Probable Cause: _
Could not unmarshall OAM config recieved via ProcessOAM gRPC call into a valid Config struct
_ Suggested Remediation: _
Check if Meshery Server is creating valid config for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also, confirm that Meshery Server and Adapters are referring to same config struct provided in MeshKit
_ Long Description: _
Error occured while parsing configuration in the request made by Meshery Server
ErrGetLatestReleaseCode 1020AlertCould not get latest version
_ Probable Cause: _
Latest version could not be found at the specified url
_ Suggested Remediation: _
_ Long Description: _
ErrLoadNamespaceCode 1021AlertError occured while applying namespace
_ Probable Cause: _
Trying to access a namespace which is not available
_ Suggested Remediation: _
Verify presence of namespace. Confirm Meshery ServiceAccount permissions
_ Long Description: _
ErrEmptyConfigCode 1022AlertConfig is empty
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetLatestReleasesCode 1023AlertUnable to fetch release info
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetLatestReleaseNamesCode 1024AlertFailed to extract release names
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetManifestNamesCode 1025AlertUnable to fetch manifest names from github
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _

Top


Meshery Adapter for meshery-istio

Error Name Error CodeSeverityShort Description
ErrEmptyConfigCode 1000AlertConfig is empty
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetLatestReleasesCode 1001Alertunable to fetch release info
_ Probable Cause: _
Checkout https://docs.github.com/en/rest/reference/repos#releases for more info
_ Suggested Remediation: _
_ Long Description: _
Unable to get the latest release info from the GithubAPI
ErrGetLatestReleaseNamesCode 1002Alertfailed to extract release names
_ Probable Cause: _
Invalid release format
_ Suggested Remediation: _
_ Long Description: _
ErrInstallUsingIstioctlCode 1003AlertError with istio operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Error occured while installing istio mesh through istioctl
ErrUnzipFileCode 1004AlertError while unzipping
_ Probable Cause: _
File might be corrupt
_ Suggested Remediation: _
_ Long Description: _
ErrTarXZFCode 1005AlertError while extracting file
_ Probable Cause: _
/The gzip might be corrupt
_ Suggested Remediation: _
_ Long Description: _
ErrMeshConfigCode 1006AlertError configuration mesh
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Error getting MeshSpecKey config from in-memory configuration
ErrRunIstioCtlCmdCode 1007AlertError running istioctl command
_ Probable Cause: _
Corrupted istioctl binary Command might be invalid
_ Suggested Remediation: _
_ Long Description: _
ErrSampleAppCode 1008AlertError with sample app operation
_ Probable Cause: _
Invalid kubeclient config Invalid manifest
_ Suggested Remediation: _
Reconnect your adapter to meshery server to refresh the kubeclient
_ Long Description: _
Error occured while trying to install a sample application using manifests
ErrEnvoyFilterCode 1009AlertError with envoy filter operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrApplyPolicyCode 1010AlertError with apply policy operation
_ Probable Cause: _
Invalid kubeclient config Invalid manifest
_ Suggested Remediation: _
Reconnect your adapter to meshery server to refresh the kubeclient
_ Long Description: _
Error occured while trying to install a sample application using manifests
ErrCustomOperationCode 1011AlertError with custom operation
_ Probable Cause: _
Invalid kubeclient config Invalid manifest
_ Suggested Remediation: _
_ Long Description: _
Error occured while applying custom manifest to the cluster
ErrAddonFromTemplateCode 1012AlertError with addon install operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInvalidInstallationProfileCode 1013AlertError while installing istio due to wrong profile
_ Probable Cause: _
Invalid profile passed
_ Suggested Remediation: _
Provide one of the profiles: "demo","minimal","default" profiles
_ Long Description: _
ErrCreatingIstioClientCode 1014AlertUnable to create a new istio client
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrIstioVetSyncCode 1015AlertFailed to sync
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrIstioVetCode 1016Alerterror while running Istio vet command
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParseOAMComponentCode 1017Alerterror parsing the component
_ Probable Cause: _
Could not unmarshall configuration component received via ProcessOAM gRPC call into a valid Component struct
_ Suggested Remediation: _
Check if Meshery Server is creating valid component for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also check if Meshery Server and adapters are referring to same component struct provided in MeshKit.
_ Long Description: _
Error occurred while parsing application component in the OAM request made by Meshery server
ErrParseOAMConfigCode 1018Alerterror parsing the configuration
_ Probable Cause: _
Could not unmarshall OAM config recieved via ProcessOAM gRPC call into a valid Config struct
_ Suggested Remediation: _
Check if Meshery Server is creating valid config for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also, confirm that Meshery Server and Adapters are referring to same config struct provided in MeshKit
_ Long Description: _
Error occured while parsing configuration in the request made by Meshery Server
ErrNilClientCode 1019Alertkubernetes client not initialized
_ Probable Cause: _
kubernetes client not initialized
_ Suggested Remediation: _
Reconnect the adaptor to Meshery server
_ Long Description: _
Kubernetes client is nil
ErrParseIstioCoreComponentCode 1020Alertistio core component manifest parsing failing
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInvalidOAMComponentTypeCode 1021Alertinvalid OAM component name:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrOpInvalidCode 1022AlertInvalid operation
_ Probable Cause: _
The operation is not supported by the adapter Invalid operation name
_ Suggested Remediation: _
Check if the operation name is valid and supported by the adapter
_ Long Description: _
Istio adapter recived an invalid operation from the meshey server
ErrIstioCoreComponentFailCode 1023Alerterror in istio core component
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrProcessOAMCode 1024Alerterror performing OAM operations
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrApplyHelmChartCode 1025AlertError occured while applying Helm Chart
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGettingIstioReleaseCode 1026AlertError occured while fetching Istio release artifacts
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrUnsupportedPlatformCode 1027Alertrequested platform is not supported by Istio
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Istio only supports Windows, Linux and Darwin
ErrIstioctlNotFoundCode 1028AlertUnable to find Istioctl
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDownloadingTarCode 1029AlertError occured while downloading Istio tar
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrUnpackingTarCode 1030AlertError occured while unpacking tar
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrMakingBinExecutableCode 1031AlertError while making istioctl an executable
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrLoadNamespaceCode 1032AlertError while labeling namespace:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _

Top


mesheryctl client

Error Name Error CodeSeverityShort Description
ErrResetMeshconfigCode 1004AlertError resetting meshconfig
_ Probable Cause: _
Meshery server config file is not reset to default settings
_ Suggested Remediation: _
Verify Meshery server config file is reset to default settings by executing mesheryctl system context view
_ Long Description: _
ErrApplyManifestCode 1005AlertError applying manifest with update: and delete:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrApplyOperatorManifestCode 1006AlertError applying operator manifests with update: and delete:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCreateDirCode 1007AlertError creating directory
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrUnmarshalCode 1008
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNoAdaptersCode 1010FatalAdapter for required mesh not found
_ Probable Cause: _
_ Suggested Remediation: _
Deploy the proper Meshery Adapter for your service mesh
_ Long Description: _
Adapter for required mesh not found
ErrPromptCode 1011FatalError while reading selected option
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCreatingDeployRequestCode 1012FatalError sending deploy request
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCreatingDeployResponseRequestCode 1013FatalError creating request for deploy response
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrAddingAuthDetailsCode 1014FatalError adding auth details
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCreatingDeployResponseStreamCode 1015
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrTimeoutWaitingForDeployResponseCode 1016FatalTimed out waiting for deploy event
_ Probable Cause: _
_ Suggested Remediation: _
Check your environment and try again
_ Long Description: _
Timed out waiting for deployment
ErrFailedDeployingMeshCode 1017FatalFailed to deploy the service mesh
_ Probable Cause: _
_ Suggested Remediation: _
Check your environment and try again
_ Long Description: _
Failed to deploy the service mesh
ErrCreatingValidateRequestCode 1018FatalError sending Validate request
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCreatingValidateResponseRequestCode 1019FatalError creating request for validate response
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrTimeoutWaitingForValidateResponseCode 1020FatalTimed out waiting for validate response
_ Probable Cause: _
_ Suggested Remediation: _
Check your environment and try again
_ Long Description: _
Timed out waiting for validate response
ErrSMIConformanceTestsFailedCode 1021FatalSMI conformance tests failed
_ Probable Cause: _
_ Suggested Remediation: _
Join https://layer5io.slack.com/archives/C010H0HE2E6
_ Long Description: _
SMI conformance tests failed
ErrRetrievingCurrentContextCode 1022
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrSettingTemporaryContextCode 1023AlertError setting temporary context
_ Probable Cause: _
temporary context is not set properly
_ Suggested Remediation: _
Verify the temporary context is set properly using the -c flag provided
_ Long Description: _
ErrCreateManifestsFolderCode 1024AlertError creating manifest folder
_ Probable Cause: _
system error in creating manifest folder
_ Suggested Remediation: _
Make sure manifest folder (.meshery/manifests) is created properly
_ Long Description: _
ErrProcessingMctlConfigCode 1025AlertError processing config
_ Probable Cause: _
Error due to invalid format of Mesheryctl config
_ Suggested Remediation: _
Make sure Mesheryctl config is in correct format and valid
_ Long Description: _
ErrRestartMesheryCode 1026AlertError restarting Meshery
_ Probable Cause: _
Meshery is not running
_ Suggested Remediation: _
Restart Meshery instance
_ Long Description: _
ErrMesheryConfigCode 1027Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
error processing config
ErrReadFilepathCode 1028Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNoProfileNameCode 1029Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
please enter a profile-name
ErrNoTestURLCode 1030Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
please enter a test URL
ErrNotValidURLCode 1031Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
please enter a valid test URL
ErrFailMarshalCode 1032Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
failed to marshal values
ErrAttachAuthTokenCode 1033
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrFailRequestCode 1034
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrFailReqStatusCode 1035
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrFailUnmarshalCode 1036Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
failed to unmarshal response body
ErrNoProfileFoundCode 1037Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
no profiles found with given name
ErrFailTestRunCode 1038Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
failed to run test
ErrInvalidOutputChoiceCode 1039Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
output-format choice invalid, use [jsonyaml]
ErrUnauthenticatedCode 1040
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrFailRequestCode 1044
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrFailReqStatusCode 1045
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrAttachAuthTokenCode 1046
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInitPortForwardCode 1047
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrRunPortForwardCode 1048FatalFailed to run port-forward
_ Probable Cause: _
Meshery pod is not in running phase mesheryctl can't connect to kubernetes with client-go
_ Suggested Remediation: _
Make sure Meshery pod exists and is in running state Check if mesheryctl is connected to kubernetes with mesheryctl system check
_ Long Description: _
Error running port-forward for Meshery
ErrFailedGetEphemeralPortCode 1049
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrProcessingConfigCode 1050AlertError processing config
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Error processing config
ErrCreatingConfigFileCode 1051AlertUnable to create config file
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Unable to create config file
ErrAddingTokenToConfigCode 1052AlertUnable to add token to config
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Unable to add token to config
ErrAddingContextToConfigCode 1053AlertUnable to add context to config
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Unable to add context to config
ErrUnmarshallingConfigFileCode 1054AlertError unmarshalling config file
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Error unmarshalling config file
ErrGettingRequestContextCode 1055FatalUnable to add token to config
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Unable to add token to config
ErrInvalidAPIResponseCode 1056FatalInvalid API response
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Invalid API response
ErrUnmarshallingAPIDataCode 1057FatalError unmarshalling API data
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Error unmarshalling API data
ErrConnectingToServerCode 1058FatalUnable to communicate with Meshery server
_ Probable Cause: _
_ Suggested Remediation: _
See https://docs.meshery.io for help getting started with Meshery
_ Long Description: _
Unable to communicate with Meshery server See https://docs.meshery.io for help getting started with Meshery
ErrSettingDefaultContextToConfigCode 1059
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _

Top


Meshery Adapter for meshery-nginx-sm

Error Name Error CodeSeverityShort Description
ErrEmptyConfigCode 1000AlertConfig is empty
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInstallBinaryCode 1001AlertFailed to change permission of the binary
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetLatestReleasesCode 1002AlertUnable to fetch release info
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetLatestReleaseNamesCode 1003AlertFailed to extract release names
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrStatusCheckCode 1004AlertError Bad Status
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrUnmarshalCode 1005AlertUnable to unmarshal the :
_ Probable Cause: _
Object is not a valid json object
_ Suggested Remediation: _
Make sure if the object passed is a valid json
_ Long Description: _
ErrCustomOperationCode 1006AlertError with applying custom operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInstallNginxCode 1007AlertError with Nginx installation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrMeshConfigCode 1008AlertError configuration mesh
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrClientConfigCode 1009AlertError setting client config
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrStreamEventCode 1010AlertError streaming events
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrSampleAppCode 1011AlertError with sample app operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrOpInvalidCode 1012AlertInvalid operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNilClientCode 1013Alertkubernetes client not initialized
_ Probable Cause: _
kubernetes client not initialized
_ Suggested Remediation: _
Reconnect the adaptor to Meshery server
_ Long Description: _
Kubernetes client is nil
ErrApplyHelmChartCode 1014AlertError occured while applying Helm Chart
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParseOAMComponentCode 1015Alerterror parsing the component
_ Probable Cause: _
Could not unmarshall configuration component received via ProcessOAM gRPC call into a valid Component struct
_ Suggested Remediation: _
Check if Meshery Server is creating valid component for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also, check if Meshery Server and adapters are referring to same component struct provided in MeshKit.
_ Long Description: _
Error occurred while parsing application component in the OAM request made by Meshery Server
ErrParseOAMConfigCode 1016Alerterror parsing the configuration
_ Probable Cause: _
Could not unmarshall OAM config recieved via ProcessOAM gRPC call into a valid Config struct
_ Suggested Remediation: _
Check if Meshery Server is creating valid config for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also, confirm that Meshery Server and Adapters are referring to same config struct provided in MeshKit
_ Long Description: _
Error occured while parsing configuration in the request made by Meshery Server
ErrProcessOAMCode 1017Alerterror performing OAM operations
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNginxCoreComponentFailCode 1018Alerterror in NGINX Service Mesh core component
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParseNginxCoreComponentCode 1019AlertFailure to parse core component manifest for NGINX Service Mesh
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrLoadNamespaceCode 1020AlertError occured while applying namespace
_ Probable Cause: _
Trying to access a namespace which is not available
_ Suggested Remediation: _
Verify presence of namespace. Confirm Meshery ServiceAccount permissions
_ Long Description: _

Top


Meshery Adapter for nsm

Error Name Error CodeSeverityShort Description
ErrEmptyConfigCode 1000AlertConfig is empty
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetLatestReleasesCode 1001Alertunable to fetch release info:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetLatestReleaseNamesCode 1002Alertfailed to extract release names:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInstallNSMCode 1003AlertError with nsm operation:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCreatingHelmIndexCode 1004AlertError with nsm operation:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrEntryWithAppVersionNotExistsCode 1005AlertEntry: with app version : does not exists
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrHelmRepositoryNotFoundCode 1006AlertEither the repo : does not exists or is corrupt:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDecodeYamlCode 1007AlertError decoding yaml:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrMeshConfigCode 1008AlertError configuration mesh:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrApplyHelmChartCode 1009AlertError applying helm chart:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrConvertingAppVersionToChartVersionCode 1010AlertError converting app version to chart version:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCreatingNSMMeshClientCode 1011AlertUnable to create a new nsm client:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrSampleAppCode 1012AlertError with sample app operation:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCustomOperationCode 1013AlertError with custom operation:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrOpInvalidCode 1014AlertInvalid operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _

Top


meshkit library

Error Name Error CodeSeverityShort Description
ErrGetCrdNamesCode 1001AlertError getting crd names
_ Probable Cause: _
Could not execute kubeopenapi-jsonschema correctly
_ Suggested Remediation: _
Make sure the binary is valid and correct Make sure the filter passed is correct
_ Long Description: _
ErrGetSchemasCode 1002AlertError getting schemas
_ Probable Cause: _
Schemas Json could not be produced from given crd.
_ Suggested Remediation: _
Make sure the filter passed is correct
_ Long Description: _
ErrGetAPIVersionCode 1003AlertError getting api version
_ Probable Cause: _
Api version could not be parsed
_ Suggested Remediation: _
Make sure the filter passed is correct
_ Long Description: _
ErrGetAPIGroupCode 1004AlertError getting api group
_ Probable Cause: _
Api group could not be parsed
_ Suggested Remediation: _
Make sure the filter passed is correct
_ Long Description: _
ErrPopulatingYamlCode 1005AlertError populating yaml
_ Probable Cause: _
Yaml could not be populated with the returned manifests
_ Suggested Remediation: _
_ Long Description: _
ErrAbsentFilterCode 1006AlertError with passed filters
_ Probable Cause: _
ItrFilter or ItrSpecFilter is either not passed or empty
_ Suggested Remediation: _
Pass the correct ItrFilter and ItrSpecFilter
_ Long Description: _
ErrNoneDatabaseCode 11010AlertNo Database selected
_ Probable Cause: _
database name is empty
_ Suggested Remediation: _
Input a name for the database
_ Long Description: _
ErrDatabaseOpenCode 11011AlertUnable to open database
_ Probable Cause: _
Database is unreachable
_ Suggested Remediation: _
Make sure your database is reachable
_ Long Description: _
ErrSQLMapUnmarshalJSONCode 11012Alertfailed to unmarshal json
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrSQLMapUnmarshalTextCode 11013Alertfailed to unmarshal text
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrSQLMapMarshalValueCode 11014Alertfailed to marshal value
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrSQLMapUnmarshalScannedCode 11015
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrSQLMapInvalidScanCode 11016
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrClosingDatabaseConnectionCode 11017Alertfailed to close database connection
_ Probable Cause: _
Invalid database instance passed.
_ Suggested Remediation: _
Make sure the DB handler has a valid database instance.
_ Long Description: _
ErrApplyManifestCode 11021AlertError Applying manifest
_ Probable Cause: _
Manifest could be invalid
_ Suggested Remediation: _
Make sure manifest yaml is valid
_ Long Description: _
ErrServiceDiscoveryCode 11022AlertError Discovering service
_ Probable Cause: _
Network not reachable to the service
_ Suggested Remediation: _
Make sure the endpoint is reachable
_ Long Description: _
ErrApplyHelmChartCode 11023AlertError applying helm chart
_ Probable Cause: _
Chart could be invalid
_ Suggested Remediation: _
Make sure to apply valid chart
_ Long Description: _
ErrNewKubeClientCode 11024AlertError creating kubernetes clientset
_ Probable Cause: _
Kubernetes config is not accessible to meshery or not valid
_ Suggested Remediation: _
Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized
_ Long Description: _
ErrNewDynClientCode 11025AlertError creating dynamic client
_ Probable Cause: _
Kubernetes config is not accessible to meshery or not valid
_ Suggested Remediation: _
Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized
_ Long Description: _
ErrNewDiscoveryCode 11026AlertError creating discovery client
_ Probable Cause: _
Discovery resource is invalid or doesnt exist
_ Suggested Remediation: _
Makes sure the you input valid resource for discovery
_ Long Description: _
ErrNewInformerCode 11027AlertError creating informer client
_ Probable Cause: _
Informer is invalid or doesnt exist
_ Suggested Remediation: _
Makes sure the you input valid resource for the informer
_ Long Description: _
ErrEndpointNotFoundCode 11028AlertUnable to discover an endpoint
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInvalidAPIServerCode 11029AlertInvalid API Server URL
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrLoadConfigCode 11030AlertError loading kubernetes config
_ Probable Cause: _
Kubernetes config is not accessible to meshery or not valid
_ Suggested Remediation: _
Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized
_ Long Description: _
ErrValidateConfigCode 11031AlertValidation failed in the kubernetes config
_ Probable Cause: _
Kubernetes config is not accessible to meshery or not valid
_ Suggested Remediation: _
Upload your kubernetes config via the settings dashboard. If uploaded, wait for a minute for it to get initialized
_ Long Description: _
ErrSelectorBasedMapCode 11036Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrProtocolBasedMapCode 11037Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrLableBasedMapCode 11038Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrPortParsingCode 11039Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGenerateServiceCode 11040Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrConstructingRestHelperCode 11041Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCreatingServiceCode 11042Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrUnmarshalCode 11043AlertUnmarshal unknown error: %s
_ Probable Cause: _
Invalid object format
_ Suggested Remediation: _
Make sure to input a valid JSON object
_ Long Description: _
ErrUnmarshalInvalidCode 11044AlertUnmarshal invalid error for type:
_ Probable Cause: _
Invalid object format
_ Suggested Remediation: _
Make sure to input a valid JSON object
_ Long Description: _
ErrUnmarshalSyntaxCode 11045AlertUnmarshal syntax error at offest:
_ Probable Cause: _
Invalid object format
_ Suggested Remediation: _
Make sure to input a valid JSON object
_ Long Description: _
ErrUnmarshalTypeCode 11046AlertUnmarshal type error at key: %s. Error: %s
_ Probable Cause: _
Invalid object format
_ Suggested Remediation: _
Make sure to input a valid JSON object
_ Long Description: _
ErrUnmarshalUnsupportedTypeCode 11047AlertUnmarshal unsupported type error at key:
_ Probable Cause: _
Invalid object format
_ Suggested Remediation: _
Make sure to input a valid JSON object
_ Long Description: _
ErrUnmarshalUnsupportedValueCode 11048AlertUnmarshal unsupported value error at key:
_ Probable Cause: _
Invalid object format
_ Suggested Remediation: _
Make sure to input a valid JSON object
_ Long Description: _
ErrMarshalCode 11049AlertMarshal error, Description: %s
_ Probable Cause: _
Invalid object format
_ Suggested Remediation: _
Make sure to input a valid JSON object
_ Long Description: _
ErrGetBoolCode 11050AlertError while getting Boolean value for key: %s, error: %s
_ Probable Cause: _
Not a valid boolean
_ Suggested Remediation: _
Make sure it is a boolean
_ Long Description: _
ErrInvalidProtocolCode 11051Alertinvalid protocol: only http, https and file are valid protocols
_ Probable Cause: _
Network protocol is incorrect
_ Suggested Remediation: _
Make sure to specify the right network protocol
_ Long Description: _
ErrRemoteFileNotFoundCode 11052Alertremote file not found at
_ Probable Cause: _
File doesnt exist in the location File name is incorrect
_ Suggested Remediation: _
Make sure to input the right file name and location
_ Long Description: _
ErrReadingRemoteFileCode 11053Alerterror reading remote file
_ Probable Cause: _
File doesnt exist in the location File name is incorrect
_ Suggested Remediation: _
Make sure to input the right file name and location
_ Long Description: _
ErrReadingLocalFileCode 11054Alerterror reading local file
_ Probable Cause: _
File doesnt exist in the location File name is incorrect
_ Suggested Remediation: _
Make sure to input the right file name and location
_ Long Description: _
ErrViperCode 11056FatalViper configuration initialization failed
_ Probable Cause: _
Viper is crashing
_ Suggested Remediation: _
Make sure viper is configured properly
_ Long Description: _
ErrInMemCode 11057FatalInMem configuration initialization failed
_ Probable Cause: _
In memory map is crashing
_ Suggested Remediation: _
Make sure map is configured properly
_ Long Description: _
ErrPodHasNoLabelsCode 11058Alertthe pod has no labels and cannot be exposed
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrServiceHasNoSelectorsCode 11059Alertthe service has no pod selector set
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInvalidDeploymentNoSelectorsLabelsCode 11060Alertthe deployment has no labels or selectors and cannot be exposed
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInvalidDeploymentNoSelectorsCode 11061Alertinvalid deployment: no selectors, therefore cannot be exposed
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInvalidReplicaNoSelectorsLabelsCode 11062Alertthe replica set has no labels or selectors and cannot be exposed
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInvalidReplicaSetNoSelectorsCode 11063Alertinvalid replicaset: no selectors, therefore cannot be exposed
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNoPortsFoundForHeadlessResourceCode 11064Alertno ports found for the non headless resource
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrUnknownSessionAffinityErrCode 11065Alertunknown session affinity:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrMatchExpressionsConvertionErrCode 11066Alertcouldn't convert expressions - to map-based selector format
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrFailedToExtractPodSelectorErrCode 11067Alertcannot extract pod selector from
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrFailedToExtractPortsCode 11068Alertcannot extract ports from
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrFailedToExtractProtocolsErrCode 11069Alertcannot extract protocols from
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCannotExposeObjectErrCode 11070Alertcannot expose a
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrControllerCode 11071Alert
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInvalidSizeFileCode 11072Alert
_ Probable Cause: _
Given file size is either 0 or exceeds the limit of 50 MB
_ Suggested Remediation: _
_ Long Description: _
Could not read the file while walking the repo
ErrCloningRepoCode 11073Alertcould not clone the repo
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _

Top


Meshery Adapter for meshery-traefik-mesh

Error Name Error CodeSeverityShort Description
ErrApplyHelmChartCode 1012AlertError occured while applying Helm Chart
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNilClientCode 1013Alertkubernetes client not initialized
_ Probable Cause: _
kubernetes client not initialized
_ Suggested Remediation: _
Reconnect the adapter to Meshery server
_ Long Description: _
Kubernetes client is nil
ErrInvalidOAMComponentTypeCode 1014Alertinvalid OAM component name:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrTraefikCoreComponentFailCode 1015Alerterror in Traefik core component
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrProcessOAMCode 1016Alerterror performing OAM operations
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParseTraefikCoreComponentCode 1017AlertTraefik core component manifest parsing failing
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParseOAMComponentCode 1018Alerterror parsing the component
_ Probable Cause: _
Could not unmarshall configuration component received via ProcessOAM gRPC call into a valid Component struct
_ Suggested Remediation: _
Check if Meshery Server is creating valid component for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also, check if Meshery Server and adapters are referring to same component struct provided in MeshKit.
_ Long Description: _
Error occurred while parsing application component in the OAM request made by Meshery Server
ErrParseOAMConfigCode 1019Alerterror parsing the configuration
_ Probable Cause: _
Could not unmarshall OAM config received via ProcessOAM gRPC call into a valid Config struct
_ Suggested Remediation: _
Check if Meshery Server is creating valid config for ProcessOAM gRPC call. This error should never happen and can be reported as a bug in Meshery Server. Also, confirm that Meshery Server and Adapters are referring to same config struct provided in MeshKit
_ Long Description: _
Error occurred while parsing configuration in the request made by Meshery Server
ErrGetLatestReleaseCode 1020AlertCould not get latest version
_ Probable Cause: _
Latest version could not be found at the specified url
_ Suggested Remediation: _
_ Long Description: _
ErrEmptyConfigCode 1029AlertConfig is empty
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetLatestReleasesCode 1030AlertUnable to fetch release info
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetLatestReleaseNamesCode 1031AlertFailed to extract release names
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrInstallTraefikCode 1032AlertError with traefik operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCreatingHelmIndexCode 1033AlertError while creating Helm Index
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrEntryWithAppVersionNotExistsCode 1034AlertEntry for the app version does not exist
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrHelmRepositoryNotFoundCode 1035AlertHelm repo not found
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrDecodeYamlCode 1036AlertError occured while decoding YAML
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrMeshConfigCode 1037AlertError configuration mesh
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrConvertingAppVersionToChartVersionCode 1038AlertError occured while converting app version to chart version
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCreatingTraefikMeshClientCode 1039AlertUnable to create a new NSM client
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrSampleAppCode 1040AlertError with sample app operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCustomOperationCode 1041AlertError with custom operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrOpInvalidCode 1042AlertInvalid operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _

Top


Meshery Adapter for cilium

Error Name Error CodeSeverityShort Description
ErrInstallCiliumCode 1000AlertError with Cilium operation
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
Error occured while installing Cilium mesh through Cilium
ErrTarXZFCode 1001AlertError while extracting file
_ Probable Cause: _
The gzip might be corrupt
_ Suggested Remediation: _
Retry the operation
_ Long Description: _
ErrMeshConfigCode 1002AlertError configuration mesh
_ Probable Cause: _
_ Suggested Remediation: _
Reconnect the adaptor to the meshkit server
_ Long Description: _
Error getting MeshSpecKey config from in-memory configuration
ErrRunCiliumCmdCode 1003AlertError running cilium command
_ Probable Cause: _
Corrupted cilium binary Command might be invalid
_ Suggested Remediation: _
_ Long Description: _
ErrDownloadBinaryCode 1004AlertError downloading Cilium binary
_ Probable Cause: _
Checkout https://docs.github.com/en/rest/reference/repos#releases for more details
_ Suggested Remediation: _
_ Long Description: _
Error occured while download Cilium binary from its github release
ErrInstallBinaryCode 1005AlertError installing Cilium binary
_ Probable Cause: _
Corrupted Cilium release binary Invalid installation location
_ Suggested Remediation: _
_ Long Description: _
ErrSampleAppCode 1006AlertError with sample app operation
_ Probable Cause: _
Invalid kubeclient config Invalid manifest
_ Suggested Remediation: _
Reconnect your adapter to Meshery Server to refresh the kubeclient
_ Long Description: _
Error occured while trying to install a sample application using manifests
ErrCustomOperationCode 1007AlertError with custom operation
_ Probable Cause: _
Invalid kubeclient config Invalid manifest
_ Suggested Remediation: _
Upload the kubconfig in the Meshery Server and reconnect the adapter
_ Long Description: _
Error occured while applying custom manifest to the cluster
ErrCreatingNSCode 1008AlertError creating namespace
_ Probable Cause: _
Invalid kubeclient config Invalid manifest
_ Suggested Remediation: _
Upload the kubeconfig in the Meshery Server and reconnect the adapter
_ Long Description: _
Error occured while applying manifest to create a namespace
ErrRunExecutableCode 1009AlertError running executable
_ Probable Cause: _
Corrupted binary Invalid operation
_ Suggested Remediation: _
Check if the adaptor is executing a deprecated command
_ Long Description: _
ErrSidecarInjectionCode 1010
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrOpInvalidCode 1011AlertInvalid operation
_ Probable Cause: _
The operation is not supported by the adapter Invalid operation name
_ Suggested Remediation: _
Check if the operation name is valid and supported by the adapter
_ Long Description: _
Cilium adapter recived an invalid operation from the meshey server
ErrApplyHelmChartCode 1012AlertError occured while applying Helm Chart
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNilClientCode 1013Alertkubernetes client not initialized
_ Probable Cause: _
kubernetes client not initialized
_ Suggested Remediation: _
Reconnect the adaptor to Meshery server
_ Long Description: _
Kubernetes client is nil
ErrInvalidOAMComponentTypeCode 1014Alertinvalid OAM component name:
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCiliumCoreComponentFailCode 1015Alerterror in Cilium core component
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrProcessOAMCode 1016Alerterror performing OAM operations
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParseCiliumCoreComponentCode 1017AlertCilium core component manifest parsing failing
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrParseOAMComponentCode 1018Alerterror parsing the component
_ Probable Cause: _
Invalid OAM component passed in OAM request
_ Suggested Remediation: _
Check if your request has vaild OAM components
_ Long Description: _
Error occured while prasing application component in the OAM request made
ErrParseOAMConfigCode 1019Alerterror parsing the configuration
_ Probable Cause: _
Invalid OAM config passed in OAM request
_ Suggested Remediation: _
Check if your request has vaild OAM config
_ Long Description: _
Error occured while prasing component config in the OAM request made
ErrGetLatestReleaseCode 1020AlertCould not get latest version
_ Probable Cause: _
Latest version could not be found at the specified url
_ Suggested Remediation: _
_ Long Description: _
ErrEmptyConfigCode 1021AlertConfig is empty
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetLatestReleasesCode 1022AlertUnable to fetch release info
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetLatestReleaseNamesCode 1023AlertFailed to extract release names
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrGetManifestNamesCode 1024AlertUnable to fetch manifest names from github
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrMakingBinExecutableCode 1025AlertError while making cilium cli an executable
_ Probable Cause: _
Download might be corrupted.
_ Suggested Remediation: _
Please retry operation.
_ Long Description: _
ErrLoadNamespaceCode 1026AlertError occured while applying namespace
_ Probable Cause: _
Trying to access a namespace which is not available
_ Suggested Remediation: _
Verify presence of namespace. Confirm Meshery ServiceAccount permissions
_ Long Description: _
ErrUnpackingTarCode 1027AlertError occured while unpacking tar
_ Probable Cause: _
The gzip might be corrupt
_ Suggested Remediation: _
Please retry operation.
_ Long Description: _
ErrUnzipFileCode 1028AlertError while unzipping
_ Probable Cause: _
File might be corrupt
_ Suggested Remediation: _
Please retry operation.
_ Long Description: _
ErrDownloadingTarCode 1029AlertError occured while downloading Cilium tar
_ Probable Cause: _
Error occured while download cilium tar from its release url
_ Suggested Remediation: _
Checkout https://github.com/cilium/cilium-cli/releases/download//cilium--.tar.gz for more details
_ Long Description: _
ErrGettingReleaseCode 1030AlertCould not get latest version
_ Probable Cause: _
Latest version could not be found at the specified url
_ Suggested Remediation: _
Verify network connectivity. Ensure github.com is reachable. Try retrying the operation.
_ Long Description: _

Top


meshery-adapter-library library

Error Name Error CodeSeverityShort Description
ErrGetNameCode 1000
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrCreateInstanceCode 1001
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrMeshConfigCode 1002
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrValidateKubeconfigCode 1003
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrClientConfigCode 1004
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrClientSetCode 1005
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrStreamEventCode 1006
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrOpInvalidCode 1007
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrApplyOperationCode 1008
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrListOperationsCode 1009
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrNewSmiCode 1010
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _
ErrRunSmiCode 1011
_ Probable Cause: _
_ Suggested Remediation: _
_ Long Description: _

Top