Closed kwmonroe closed 6 years ago
Seems this probably isn't a problem with conjure-up, but rather juju itself. When I juju deploy ~/.cache/conjure-up/canonical-kubernetes-deployed-20180418.1504.yaml
, it looks like things are gonna go great, with each app on a new machine and graylog on machine 0:
...
- add unit apache2/0 to new machine 1
- add unit easyrsa/0 to new machine 2
- add unit elasticsearch/0 to new machine 3
- add unit etcd/0 to new machine 4
- add unit etcd/1 to new machine 5
- add unit etcd/2 to new machine 6
- add unit graylog/0 to new machine 0
- add unit kubeapi-load-balancer/0 to new machine 7
- add unit kubernetes-master/0 to new machine 8
- add unit kubernetes-worker/0 to new machine 9
- add unit kubernetes-worker/1 to new machine 10
- add unit kubernetes-worker/2 to new machine 11
- add unit mongodb/0 to new machine 12
Deploy of bundle completed.
However, a juju status on this deployment shows the same thing -- graylog and apache2 are smashed on machine 0:
juju status
...
apache2/0* maintenance executing 0 34.238.153.179 (install) installing charm software
easyrsa/0* active executing 1 54.89.174.66 (config-changed) Certificate Authority ready.
elasticsearch/0* maintenance executing 2 52.203.131.75 (config-changed) installing charm software
etcd/0 maintenance executing 3 54.174.144.161 (install) installing charm software
etcd/1 maintenance executing 4 54.89.152.120 (install) installing charm software
etcd/2* maintenance executing 5 34.207.94.127 (install) installing charm software
graylog/0* maintenance executing 0 34.238.153.179 (install) installing charm software
kubeapi-load-balancer/0* maintenance executing 6 174.129.54.106 (install) installing charm software
kubernetes-master/0* maintenance executing 7 34.231.247.252 (install) Installing kubectl snap
kubernetes-worker/0 waiting idle 8 34.234.84.209 Waiting for cluster DNS.
filebeat/1 maintenance executing 34.234.84.209 (install) installing charm software
flannel/1 waiting allocating 34.234.84.209 agent initializing
kubernetes-worker/1 maintenance executing 9 34.201.27.75 (install) Installing kube-proxy snap
kubernetes-worker/2* waiting idle 10 34.207.89.170 Waiting for cluster DNS.
filebeat/0* maintenance executing 34.207.89.170 (install) Installing filebeat
flannel/0* maintenance executing 34.207.89.170 (install) installing charm software
mongodb/0* maintenance executing 11 54.86.240.162 (install) installing charm software
FYI, filed a bug against core with a simpler test case:
I tried to make the graylog fragment put graylog on machine 0 with a given constraint:
https://github.com/conjure-up/spells/commit/bfd94cf3bd3a3d76e77bc9807b662489504613db
Taking advantage of the graylog addon alias, I run conjure-up like this:
This merges my graylog fragment into the following bundle (from
~/.cache/conjure-up/canonical-kubernetes-deployed-20180418.1504.yaml
):That seems fine, but notice that only graylog has a
to:
placement directive. However, when the deployment finishes, something afoul is revealed:Why is
apache2/0
hulk smashed besidegraylog/0
on machine 0?