kbrwn
commented
7 years ago @go4875 Can you try again after following this guide to add this proxy to docker.service?
https://gist.github.com/alekssaul/59a87b5be86f77cc4638083250d90568
Open go4875 opened 7 years ago
kbrwn
commented
7 years ago @go4875 Can you try again after following this guide to add this proxy to docker.service?
https://gist.github.com/alekssaul/59a87b5be86f77cc4638083250d90568
go4875
commented
7 years ago Hello kbrwn i did try that. if you look at my assets.zip file. the proxy to the docker service is included in the ignition files. i also included that entry in my initial post. I have a couple of questions
go4875
commented
7 years ago Hello for some reason the bootstrap is not finishing. It's the same error that I am encountering in the original post the docker0 is not starting. any help would be appreciated
go4875
commented
7 years ago @kbrwn . anyway i can get some more support on this issue? still same bootstrap hanging. seems like etcd is not starting correctly, hence the apiserver is also not available. please let me know. On another ?, is there any limitation to the free 10 node license, e.g. you can only deploy 1 master node with this free 10 node license?? Thanks.
kbrwn
commented
7 years ago @go4875 This is the place to get help if you are a Tectonic trial customer. TBH I think that you should perhaps abandon your installation in favor of the Tectonic Sandbox project. Baremetal/VM installation is a complex process that may not be worth going through just for a trial cluster.
The Tectonic Sandbox is a vagrant based cluster that is meant to show off the features of Tectonic/k8s. https://coreos.com/tectonic/sandbox
journalctl.wrkr-node003.txt
Issue Report Template
Tectonic Version
1.6.2 tectonic 1
Environment
VM installation for test What hardware/cloud provider/hypervisor is being used with Tectonic? Using KVM hypervisor
Expected Behavior
Actual Behavior
assets_081117.zip
Reproduction Steps
My test landscape info 3 nodes - Master 4 nodes - Worker
I have configured our DNS to have hostname and then the alias name. The alias name is what I am using for the node in the GUI installer I have configured one alias for the Controller info ( I tried round robin for the controller nodes, but I get the same error) I have configured a round-robin for the Worker cluster from reading the previous posts and forums, https://github.com/coreos/tectonic-forum/issues/13 seems like api server can't be contacted, even though the api server is pingable from all nodes. Also another weird issue, is that my docker0 is down I am a little lost at this point as to what the issue is currently, but my install won't finish. I followed the suggestion on the other post my results of the the curl checks root@lvpalkvm71:/setup/matchbox-v0.6.1-linux-amd64/scripts/tls# curl http://10.48.220.245:10255/healthz okroot@lvpalkvm71:/setup/matchbox-v0.6.1-linux-amd64/scripts/tls# curl http://mstr-node002:10255/healthz okroot@lvpalkvm71:/setup/matchbox-v0.6.1-linux-amd64/scripts/tls# curl http://10.48.220.248:10255/healthz okroot@lvpalkvm71:/setup/matchbox-v0.6.1-linux-amd64/scripts/tls# We are behind a proxy. I have configured my worker templ yaml and controller temp yaml files to have the below:
path: /etc/environment filesystem: root mode: 0644 contents: inline: | http_proxy=http://172.16.1.11:3128 https_proxy=http://172.16.1.11:3128 no_proxy=127.0.0.1,$BOOTCFGSERVER,$TECTONICCONTROLLER
name: docker.service enable: true dropins:
I have attached my assets file and some journalctl output of controller and worker node.
Other Information
Feature Request
enable proxy configuration on graphical installer journalctl.mstr-node002.txt
Environment
What hardware/cloud provider/hypervisor is being used with Tectonic?
Desired Feature
Other Information
let me know if other information is needed. Would appreciate your help in getting this cluster up and running.