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

Azure AKS error: Unable to create configMap noticer. #827

Closed
marcello-mirenda opened this issue Feb 21, 2019 · 10 comments
Closed

Azure AKS error: Unable to create configMap noticer. #827

marcello-mirenda opened this issue Feb 21, 2019 · 10 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@marcello-mirenda
Copy link

Expected Behavior

in-memory-channel-dispatcher-5758f86c6c-cbflc status -> running

Actual Behavior

in-memory-channel-dispatcher-5758f86c6c-cbflc status -> Waiting: CrashLoopBackOff

Steps to Reproduce the Problem

  1. Follow the instructions from https://github.com/knative/docs/blob/master/install/Knative-with-AKS.md
  2. Access the dashboard
  3. Goto namespace knative-eventing / pods

Additional Info

Here is the log with the error that blocks the container from starting:
{"level":"fatal","ts":1550757304.3971024,"caller":"fanoutsidecar/main.go:91","msg":"Unable to create configMap noticer.","error":"Get https://mmi-aks-cluster-b7b26957.hcp.westeurope.azmk8s.io:443/api?timeout=32s: EOF","stacktrace":"main.main\n\t/home/argent/go/src/github.com/knative/eventing/cmd/fanoutsidecar/main.go:91\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:201"}

@evankanderson
Copy link
Member

Hello,

Which version of Knative are you running? We just released 0.4.0 a few days ago, so it's not clear if this was the old or the new release. (I'm guessing it was the 0.3.0 release because I see my machine's name in the stack traces, and the 0.4.0 release was mostly built by automation rather than my running tools by hand.)

@marcello-mirenda
Copy link
Author

marcello-mirenda commented Feb 22, 2019

Hello Evan,

this issue is regarding version 0.3.0. I also tried the version 0.4.0 with other problems always related to the AKS hosting.

@marcello-mirenda
Copy link
Author

Hello Evan,
I just saw that you have updated the instructions from https://github.com/knative/docs/blob/master/install/Knative-with-AKS.md to the 0.4.0 version.

I'm going to try this version again.

You can close this issue if you want. In case any other comment coming from me will be about the 0.4.0 version.

Thanks

@lukas-lansky
Copy link

I see this issue with KNative 0.4.0 at AKS, k8s 1.12.5.

C:\Source> kubectl logs in-memory-channel-dispatcher-56d6f99dc6-8ljkb --namespace knative-eventing -c dispatcher
{"level":"fatal","ts":1551885992.0521848,"caller":"fanoutsidecar/main.go:91","msg":"Unable to create configMap noticer.","error":"Get https://onlineorderingcicluster-6b9da14d.hcp.eastus2.azmk8s.io:443/api?timeout=32s: EOF","stacktrace":"main.main\n\t/go/src/github.com/knative/eventing/cmd/fanoutsidecar/main.go:91\nruntime.main\n\t/root/sdk/go1.12rc1/src/runtime/proc.go:200"}

@akashrv
Copy link
Contributor

akashrv commented Mar 20, 2019

/kind bug

@mtnygard
Copy link

mtnygard commented May 9, 2019

I can confirm this issue still happens with release 0.5.0

@akashrv
Copy link
Contributor

akashrv commented May 9, 2019

@mtnygard Could you deploy from master and check once? In 0.6 (to be released next week) we have removed this dependency on configmap for fanoutsidecar.

@mtnygard
Copy link

mtnygard commented May 9, 2019

@akashrv I can give it a try. I'm pretty new to knative so have just been following the "Install on Azure Kubernetes Service (AKS)" guide from knative.dev docs.

To install from master, do I just replace the filenames like https://github.com/knative/serving/releases/download/v0.5.0/serving.yaml with URLs that point into the master tree? Or do I actually need to clone the repo and run a build?

@akashrv
Copy link
Contributor

akashrv commented May 9, 2019

You can get the latest nightly build here: https://console.cloud.google.com/storage/browser/knative-nightly
In your case, you could apply the eventing release yaml. Eventing doesn't depend on istio or serving.

@akashrv
Copy link
Contributor

akashrv commented Jun 20, 2019

/priority awaiting-more-evidence

@knative-prow-robot knative-prow-robot added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Jun 20, 2019
mgencur added a commit to mgencur/eventing that referenced this issue Sep 22, 2020
… (knative#827)

* Modify scripts to be reusable in serverless-operator repo

* remove redundant env variables
* move sourcing upstream e2e-commons out from our e2e-common
* hardcode TEST_IMAGE_TEMPLATE in e2e-tests.sh as this file only runs in
CI
* move selecting TEST_IMAGE_TEMPLATE into e2e-tests-local.sh as this is
where we want to specify custom templates
* use ${variable:-} pattern where possible to prevent errors in
serverless-operator repo where we run with -e and undefined variables
fail the whole build

* Define OLM_NAMESPACE

Co-authored-by: Martin Gencur <mgencur@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

No branches or pull requests

7 participants