Skip to content

Commit

Permalink
fix(deployment): added device error code descriptions and actions
Browse files Browse the repository at this point in the history
  • Loading branch information
@smrutisenapati @pallabpain
smrutisenapati authored and pallabpain committed May 9, 2023
1 parent f2599e5 commit af2ecb7
Showing 1 changed file with 157 additions and 9 deletions.
166 changes: 157 additions & 9 deletions riocli/deployment/errors.py
View file
Original file line number Diff line number Diff line change
Expand Up @@ -13,10 +13,43 @@
# limitations under the License.

ERRORS = {
# Device related Error codes
"DEP_E151": {
"description": "Device is either offline or not reachable",
"action": "Ensure that the device is connected to the internet"
},
"DEP_E302": {
"description": "Supervisord related error on device",
"action": ("Ensure supervisord is installed on rapyuta virtual environment and working\n"
"Re-onboard the device, if issue persists report to rapyuta.io support.")
},
"DEP_E161": {
"description": "Docker image not found for executables of components deployed on device",
"action": "Ensure that the docker image path is valid and secrets have privileges"
},
"DEP_E316": {
"description": "Docker image pull failed in device",
"action": "Ensure that the docker image path is valid and secrets have privileges"
},
"DEP_E317": {
"description": "Missing subpath or empty mount path",
"action": ("Ensure the current device has a subpath\n"
"Ensure that the mount path isn’t empty")
},
"DEP_E304": {
"description": "DeviceManager internal error",
"action": "Report to rapyuta.io support"
},
"DEP_E306": {
"description": "DeviceEdge internal error",
"action": "Ensure deviceedge is up and running"
},
"DEP_E307": {
"description": "DeviceEdge bad request",
"action": "Report to rapyuta.io support"
},

# Application related errors.
"DEP_E152": {
"description": "Executables of the component deployed on the device either exited too early or failed",
"action": "Executables of the component deployed on the device either exited too early or failed"
Expand All @@ -38,10 +71,6 @@
"description": "Dependent deployment is in error state",
"action": "Troubleshoot the dependent deployment that is in error state"
},
"DEP_E161": {
"description": "Docker image not found for executables of components deployed on device",
"action": "Ensure that the docker image path is valid"
},
"DEP_E162": {
"description": ("Validation error. Cases include:\nInconsistent values of ROS distro "
"and CPU architecture variables for the device and package being provisioned. "
Expand All @@ -50,9 +79,11 @@
"variables.\nOnboard the device again.")
},
"DEP_E163": {
"description": "Application has stopped and exited unexpectedly, and crashes continuously",
"description": "Application has stopped and exited unexpectedly, and crashes continuously on device",
"action": "Debug the application using the corresponding deployment logs"
},

# CloudBridge related error codes.
"DEP_E171": {
"description": "Cloud bridge encountered duplicate alias on the device",
"action": ("Change the alias name during deployment and ensure that there"
Expand Down Expand Up @@ -84,9 +115,126 @@
"description": "Cloud bridge on the cloud component encountered multiple ROS service origins",
"action": "Re-onboard the device"
},
"DEP_E317": {
"description": "Missing subpath or empty mount path",
"action": ("Ensure the current device has a subpath\n"
"Ensure that the mount path isn’t empty")

# Docker image related Error codes
"DEP_E350": {
"description": "Get http error when pulling image from registry on device",
"action": "Ensure registry is accesible."
},
"DEP_E351": {
"description": "Unable to parse the image name on device",
"action": "Ensure image name is correct and available in registry."
},
"DEP_E352": {
"description": "Unable to inspect image on device",
"action": "Ensure valid image is present"
},
"DEP_E353": {
"description": "Required Image is absent on device and PullPolicy is NeverPullImage",
"action": "Ensure pull policy is not set to never or image is present on device"
},

# Container related error codes
"DEP_E360": {
"description": "Failed to create container config on device",
"action": ("Ensure executable config is mounted correctly\n"
"If issue persists report to rapyuta.io support")
},
"DEP_E361": {
"description": "Runtime failed to start any of pod's container on device",
"action": ("Ensure executable command is valid\n"
"If issue persists report to rapyuta.io support")
},
"DEP_E362": {
"description": "Runtime failed to create container on device",
"action": ("Report to rapyuta.io support")
},
"DEP_E363": {
"description": "Runtime failed to kill any of pod's containers on device",
"action": ("Report to rapyuta.io support")
},
"DEP_E364": {
"description": "Runtime failed to create a sandbox for pod on device",
"action": ("Report to rapyuta.io support")
},
"DEP_E365": {
"description": "Runtime failed to get pod sandbox config from pod on device",
"action": ("Report to rapyuta.io support")
},
"DEP_E366": {
"description": "Runtime failed to stop pod's sandbox on device",
"action": ("Report to rapyuta.io support")
},
"DEP_E399": {
"description": "Deployment failed for some unknown reason on device",
"action": ("Report to rapyuta.io support")
},

# ROS Comm Related Device Errors
"DEP_E303": {
"description": "Cloud Bridge executable not running on device",
"action": ("Troubleshoot Cloud Bridge container on device by analyzing logs")
},
"DEP_E305": {
"description": "Native Network executable not running on device",
"action": ("Troubleshoot native network container on device by analyzing logs")
},
"DEP_E313": {
"description": "ROS Master executable not running on device",
"action": ("Troubleshoot ROS Master container on device by analyzing logs")
},
"DEP_E330": {
"description": "ROS2 Native Network executable not running on device",
"action": ("Troubleshoot ROS2 Routed Network container on device by analyzing logs")
},
"DEP_E331": {
"description": "ROS2 Routed Network executable not running on device",
"action": ("Troubleshoot ROS2 Routed Network container on device by analyzing logs")
},

# Cloud error codes
"DEP_E201": {
"description": "Cloud component deployment pending",
"action": ("Report to rapyuta.io support")
},
"DEP_E202": {
"description": "Cloud component status unknown",
"action": ("Report to rapyuta.io support")
},
"DEP_E203": {
"description": "Cloud Bridge not running on cloud",
"action": "Troubleshoot the failed component by analyzing the deployment logs"
},
"DEP_E204": {
"description": "ROS Master not running on cloud",
"action": "Troubleshoot the failed component by analyzing the deployment logs"
},
"DEP_E205": {
"description": "Cloud Broker not running on cloud",
"action": "Troubleshoot the failed component by analyzing the deployment logs"
},
"DEP_E208": {
"description": "Desired set of replicas not running on cloud",
"action": "Troubleshoot the failed component by analyzing the deployment logs"
},
"DEP_E209": {
"description": "Native Network not running on cloud",
"action": "Troubleshoot the failed component by analyzing the deployment logs"
},
"DEP_E210": {
"description": "Disk Not Running",
"action": ("Ensure disk is running")
},
"DEP_E213": {
"description": "Broker running low on memory",
"action": ("Report to rapyuta.io support")
},
"DEP_E214": {
"description": "ROS2 Native Network not running on cloud",
"action": "Troubleshoot the failed component by analyzing the deployment logs"
},
"DEP_E215": {
"description": "ROS2 Routed Network not running on cloud",
"action": "Troubleshoot the failed component by analyzing the deployment logs"
}
}

0 comments on commit af2ecb7

Please sign in to comment.