| 2021-11-08 10:14:43 |
Peter Jose De Sousa |
bug |
|
|
added bug |
| 2021-11-08 10:14:43 |
Peter Jose De Sousa |
attachment added |
|
crashdump https://bugs.launchpad.net/bugs/1950139/+attachment/5538791/+files/juju-crashdump-9dcd8aa8-02ae-4ab7-b146-76bae0ae8f36.tar.xz |
|
| 2021-11-08 16:38:59 |
Peter Jose De Sousa |
bug |
|
|
added subscriber Canonical Field Medium |
| 2021-11-08 18:55:34 |
Peter Jose De Sousa |
description |
Hi,
When deploying coredns charm revision 18, offering, consuming and relating CoreDNS the SAAS endpoint on the foreign model goes to "Unknown".
This is repeated on different clouds. Steps to reproduce are:
Prerequisites:
1. A charmed k8s cluster
2. a bootstrapped juju controller on k8s
Steps:
FOREIGN_MODEL=MYCONTROLLER:MYMODEL
1. Add CoreDNS model
2. juju deploy cs:~containers/coredns
3. juju offer coredns:dns-provider
4. juju consume -m $FOREIGN_MODEL coredns-k8s:admin/kube-system-coredns.coredns
5. juju relate -m $FOREIGN_MODEL kubernetes-master coredns
juju --version
2.9.17-ubuntu-amd64
crashdump attached, screendumps in private-fileshare
thank you
Peter |
Hi,
When deploying coredns charm revision 18, offering, consuming and relating CoreDNS the SAAS endpoint on the foreign model goes to "Unknown" and DNS is not accessible on Kubernetes cluster.
This is repeated on different clouds. Steps to reproduce are:
Prerequisites:
1. A charmed k8s cluster
2. a bootstrapped juju controller on k8s
Steps:
FOREIGN_MODEL=MYCONTROLLER:MYMODEL
1. Add CoreDNS model
2. juju deploy cs:~containers/coredns
3. juju offer coredns:dns-provider
4. juju consume -m $FOREIGN_MODEL coredns-k8s:admin/kube-system-coredns.coredns
5. juju relate -m $FOREIGN_MODEL kubernetes-master coredns
juju --version
2.9.17-ubuntu-amd64
crashdump attached, screendumps in private-fileshare
thank you
Peter |
|
| 2021-11-09 11:01:56 |
Peter Jose De Sousa |
description |
Hi,
When deploying coredns charm revision 18, offering, consuming and relating CoreDNS the SAAS endpoint on the foreign model goes to "Unknown" and DNS is not accessible on Kubernetes cluster.
This is repeated on different clouds. Steps to reproduce are:
Prerequisites:
1. A charmed k8s cluster
2. a bootstrapped juju controller on k8s
Steps:
FOREIGN_MODEL=MYCONTROLLER:MYMODEL
1. Add CoreDNS model
2. juju deploy cs:~containers/coredns
3. juju offer coredns:dns-provider
4. juju consume -m $FOREIGN_MODEL coredns-k8s:admin/kube-system-coredns.coredns
5. juju relate -m $FOREIGN_MODEL kubernetes-master coredns
juju --version
2.9.17-ubuntu-amd64
crashdump attached, screendumps in private-fileshare
thank you
Peter |
Hi,
When deploying coredns charm revision 18, offering, consuming and relating CoreDNS the SAAS endpoint on the foreign model goes to "Unknown" and DNS is not accessible on Kubernetes cluster.
This is repeated on different clouds. Steps to reproduce are:
Prerequisites:
1. A charmed k8s cluster
2. a bootstrapped juju controller on k8s
Steps:
FOREIGN_MODEL=MYCONTROLLER:MYMODEL
1. Add CoreDNS model
2. juju deploy cs:~containers/coredns
3. juju offer coredns:dns-provider
4. juju consume -m $FOREIGN_MODEL coredns-k8s:admin/kube-system-coredns.coredns
5. juju relate -m $FOREIGN_MODEL kubernetes-master coredns
juju --version
2.9.17-ubuntu-amd64
crashdump attached, screendumps in private-fileshare
[WORKAROUND]
Add the k8s cloud to the underlying cloud controller. This should send the application into "Active" state and allow you run enable coredns successfully.
thank you
Peter |
|
