Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Fresh deploy in Kubernetes 1.14.1 not working #85

Closed
malozanoff opened this issue Apr 30, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@malozanoff
Copy link

commented Apr 30, 2019

Describe the bug
Installed Slack App in a channel, ran the kubernetes deploy both via kubectl apply and helm (same issue), the bot is in the channel, it sends notifications, it responds to ping but does not respond to any other command.

A look at the logs from the backend pod shows:
INFO[2019-04-30T18:49:54Z] Invalid request. Dumping the response

To Reproduce
Steps to reproduce the behavior:

  1. Follow installation instructions using a Kubernetes 1.14.1 cluster
  2. Try to do a @BotKube get pods

Expected behavior
Expected the bot respond with something.

Screenshots
image

Additional context
Kubernetes 1.14.1 cluster running in bare metal. Private Slack team

@malozanoff malozanoff added the bug label Apr 30, 2019

@PrasadG193

This comment has been minimized.

Copy link
Member

commented May 6, 2019

Hi @malozanoff ,
I tried to reproduce the issue with BotKube v0.7.0 and K8s v1.14.1 on minikube. I didn't find any issue while executing any commands. I am passing --set config.communications.slack.channel=alerts where alerts is a private channel and I have already invited BotKube on that channel. Could you please tell me, what channel name you are using (i.e format of channel name)? Also, could you please send the content of configmap botkube-configmap in botkube namespace?

Thanks.

@PrasadG193

This comment has been minimized.

Copy link
Member

commented May 7, 2019

Turned out to be a configuration problem. Hence closing the issue.

@PrasadG193 PrasadG193 closed this May 7, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.