Nope - this looks ok: When a cluster is created, then it creates a private network for you (in your case 10.0.0.0/24), connecting this network via a router to your public network. Floating ip is the assigned to your machine accordingly. So - if now your part-011 runs ok, do you have also now all the Etcd certificates/keys in your /etc/kubernetes/certs
Am 02.02.2019 um 17:55 schrieb Alfredo De Luca <alfredo.deluca@gmail.com>:
part-011 run succesfully.... + set -o errexit + set -o nounset + set -o pipefail + '[' True == True ']' + exit 0
But what I think it's wrong is the floating IP . It's not the IP that goes on internet which is the eth0 on my machine that has 10.1.8.113... anyway here is the network image
<image.png>
On Sat, Feb 2, 2019 at 5:47 PM Clemens <clemens.hardewig@crandale.de <mailto:clemens.hardewig@crandale.de>> wrote: One after the other: First of all part-011 needs to run successfully: Did your certificates create successfully? What is in /etc/kubernetes/certs ? Or did you run part-011 already successfully?
Am 02.02.2019 um 17:36 schrieb Alfredo De Luca <alfredo.deluca@gmail.com <mailto:alfredo.deluca@gmail.com>>:
Failed to start heat-container-agent.service: Unit heat-container-agent.service not found.
-- Alfredo