Troubleshooting

In this section, instructions are summarized that help to trouble shoot known issues that may occur when using keptn.

Service does not receive event, even though it has been sent

Expand instructions

Investigation:

  1. Check the logs of the event-broker using the keptn’s log and looking for the current keptnContext, e.g., keptnContext: 6177178624927956405
  2. The event-broker was not able to send an event to a channel, if the log shows: {"keptnContext":"6177178624927956405","message":"Error while sending request: Error: Request failed with status code 500","keptnService":"eventbroker","logLevel":"ERROR"}

Reason:

Internal knative problem, seen with knative 0.4

Solution:

  1. Re-apply the channel, which should have received the event, e.g., the problem channel. The manifest is provided by the event-broker:

    kubectl apply -f ./keptn/core/eventbroker/config/problem-channel.yaml
    
  2. Re-apply the services that have a subscription to this channel, e.g., for the problem channel it is the servicenow-service:

    kubectl apply -f keptn/install/scripts/keptn-services/servicenow-service/config/servicenow-service.yaml
    
  3. (optional) Delete all pods in the knative-eventing namespace:

    kubectl delete pods --all -n knative-eventing
    

Installation on Azure aborting

Expand instructions

Investigation:

The keptn installation is aborting with the following error:

Cannot obtain the cluster/pod IP CIDR

Reason:

The root cause of this issue is that kubenet is not used in your AKS cluster. However, it is needed to retrieve the podCidr according to the official docs: https://docs.microsoft.com/en-us/rest/api/aks/managedclusters/createorupdate#containerservicenetworkprofile

Solution:

Please select the Kubenet network plugin (basic) when setting up your AKS cluster, instead of Azure network plugin (advanced) and retry the installation. You can find more information here: https://docs.microsoft.com/en-us/azure/aks/configure-kubenet