Hi Julien, sorry for the delay. The "Unable to connect to server" messages are referring to the kubernetes apiserver being unreachable, and from your logs, it looks like the apiserver failed to start up with the error "failed to listen on 0.0.0.0:6444: listen tcp 0.0.0.0:6444: bind: address already in use". Is the issue reproducible, or did you just hit it the one time? If reproducible, can you confirm whether anything is listening on port 6444 prior to running the AIAB script? Thanks, Matt -----Original Message----- From: BERTOZZI, JULIEN Sent: Thursday, July 18, 2019 4:07 AM To: airship-discuss@lists.airshipit.org Subject: [Airship-discuss] AIB install issue *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello, I am trying to setup AIB on a fresh 16.04 install, without a proxy, but I'm getting some errors when running the setup script. Here is the first one that I can see: Unpacking docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Setting up docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Installing new version of config file /etc/init.d/docker ... Installing new version of config file /etc/init/docker.conf ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Unable to connect to the server: EOF Unable to connect to the server: EOF E0627 11:11:38.937690 1 round_trippers.go:169] CancelRequest not implemented Unable to connect to the server: EOF E0627 11:12:09.786160 1 round_trippers.go:169] CancelRequest not implemented E0627 11:12:14.786265 1 round_trippers.go:169] CancelRequest not implemented The logs are quite long, so I organized everything in a repo: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JulienBe_airship-2Din-2Da-2Dbottle-2Dtesting&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=4PFygK135CuVlwdFm5y3c1kN-8p786y6mSWfEpqp6wE&e= Does it ring a bell for anyone ? Thanks for your time, Julien _______________________________________________ Airship-discuss mailing list Airship-discuss@lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=W_MUU5RD5NVllVkZUHLiT5EG-BZvQGizNKrqS4zyCMI&e=

Hello Matt ! Well, as per recommendation on the aiab site, I always wipe between tries. I've had it a few times before posting to the ML. I retried now that I got your message (same image on the same usb key, same machine). Only difference that shouldn't affect anything is that I let it upgrade during install instead of doing it after the install Anyway, it seems to work, I got my k8s env 😊 Helm wasn't working properly though, it didn't created it's files. Doing a new `helm init` didn't fixed. Although it said the files were created, well, they were nowhere to be found Onto the next step Thanks for your time, J -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 12, 2019 4:07 PM To: Bertozzi, Julien <julien.bertozzi@intl.att.com>; 'airship-discuss@lists.airshipit.org' <airship-discuss@lists.airshipit.org> Subject: RE: AIB install issue Hi Julien, just wanted to confirm whether you're still seeing this issue? Thanks Matt -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 5, 2019 1:45 PM To: BERTOZZI, JULIEN <julien.bertozzi@intl.att.com>; airship-discuss@lists.airshipit.org Subject: RE: AIB install issue Hi Julien, sorry for the delay. The "Unable to connect to server" messages are referring to the kubernetes apiserver being unreachable, and from your logs, it looks like the apiserver failed to start up with the error "failed to listen on 0.0.0.0:6444: listen tcp 0.0.0.0:6444: bind: address already in use". Is the issue reproducible, or did you just hit it the one time? If reproducible, can you confirm whether anything is listening on port 6444 prior to running the AIAB script? Thanks, Matt -----Original Message----- From: BERTOZZI, JULIEN Sent: Thursday, July 18, 2019 4:07 AM To: airship-discuss@lists.airshipit.org Subject: [Airship-discuss] AIB install issue *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello, I am trying to setup AIB on a fresh 16.04 install, without a proxy, but I'm getting some errors when running the setup script. Here is the first one that I can see: Unpacking docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Setting up docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Installing new version of config file /etc/init.d/docker ... Installing new version of config file /etc/init/docker.conf ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Unable to connect to the server: EOF Unable to connect to the server: EOF E0627 11:11:38.937690 1 round_trippers.go:169] CancelRequest not implemented Unable to connect to the server: EOF E0627 11:12:09.786160 1 round_trippers.go:169] CancelRequest not implemented E0627 11:12:14.786265 1 round_trippers.go:169] CancelRequest not implemented The logs are quite long, so I organized everything in a repo: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JulienBe_airship-2Din-2Da-2Dbottle-2Dtesting&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=4PFygK135CuVlwdFm5y3c1kN-8p786y6mSWfEpqp6wE&e= Does it ring a bell for anyone ? Thanks for your time, Julien _______________________________________________ Airship-discuss mailing list Airship-discuss@lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=W_MUU5RD5NVllVkZUHLiT5EG-BZvQGizNKrqS4zyCMI&e=

Hello Matt ! Clarification: At installed, when asked if it could install upgrades, I said yes this time. I'm not sure that it changed anything but that's the only thing I can think of As for the helm issue, it was a pretty unexpected behavior, none of us encountered this before. Next time I'll see if I can give you access to the vm Thanks for your time ! Julien -----Original Message----- From: MCEUEN, MATT Sent: Tuesday, August 13, 2019 6:00 PM To: Bertozzi, Julien <julien.bertozzi@intl.att.com>; 'airship-discuss@lists.airshipit.org' <airship-discuss@lists.airshipit.org>; PARK, HYON H <hp5419@att.com> Subject: RE: AIB install issue Hey Julien, Happy to hear of progress! Can you please clarify this one: "I let it upgrade during install instead of doing it after the install" -- do you mean that you did some of the steps here [1] in parallel? I learned yesterday that Hyon Park is getting the same error when running AIAB, consistently (just like you were), and I'm not sure what the common thread is yet. He was running in a VM on a public cloud on an Ubuntu 16.04 host. I'm not able to reproduce the issue, but I suspect there may be a common thread between your old environment and his current one. I'm also interested in your new issue. AIAB should be pretty turn-key, installing its own dependencies, etc! [1]: https://opendev.org/airship/treasuremap/src/branch/master/tools/deployment/a... -----Original Message----- From: BERTOZZI, JULIEN <julien.bertozzi@intl.att.com> Sent: Tuesday, August 13, 2019 9:20 AM To: MCEUEN, MATT <MM9745@att.com>; 'airship-discuss@lists.airshipit.org' <airship-discuss@lists.airshipit.org> Subject: RE: AIB install issue Hello Matt ! Well, as per recommendation on the aiab site, I always wipe between tries. I've had it a few times before posting to the ML. I retried now that I got your message (same image on the same usb key, same machine). Only difference that shouldn't affect anything is that I let it upgrade during install instead of doing it after the install Anyway, it seems to work, I got my k8s env 😊 Helm wasn't working properly though, it didn't created it's files. Doing a new `helm init` didn't fixed. Although it said the files were created, well, they were nowhere to be found Onto the next step Thanks for your time, J -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 12, 2019 4:07 PM To: Bertozzi, Julien <julien.bertozzi@intl.att.com>; 'airship-discuss@lists.airshipit.org' <airship-discuss@lists.airshipit.org> Subject: RE: AIB install issue Hi Julien, just wanted to confirm whether you're still seeing this issue? Thanks Matt -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 5, 2019 1:45 PM To: BERTOZZI, JULIEN <julien.bertozzi@intl.att.com>; airship-discuss@lists.airshipit.org Subject: RE: AIB install issue Hi Julien, sorry for the delay. The "Unable to connect to server" messages are referring to the kubernetes apiserver being unreachable, and from your logs, it looks like the apiserver failed to start up with the error "failed to listen on 0.0.0.0:6444: listen tcp 0.0.0.0:6444: bind: address already in use". Is the issue reproducible, or did you just hit it the one time? If reproducible, can you confirm whether anything is listening on port 6444 prior to running the AIAB script? Thanks, Matt -----Original Message----- From: BERTOZZI, JULIEN Sent: Thursday, July 18, 2019 4:07 AM To: airship-discuss@lists.airshipit.org Subject: [Airship-discuss] AIB install issue *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello, I am trying to setup AIB on a fresh 16.04 install, without a proxy, but I'm getting some errors when running the setup script. Here is the first one that I can see: Unpacking docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Setting up docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Installing new version of config file /etc/init.d/docker ... Installing new version of config file /etc/init/docker.conf ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Unable to connect to the server: EOF Unable to connect to the server: EOF E0627 11:11:38.937690 1 round_trippers.go:169] CancelRequest not implemented Unable to connect to the server: EOF E0627 11:12:09.786160 1 round_trippers.go:169] CancelRequest not implemented E0627 11:12:14.786265 1 round_trippers.go:169] CancelRequest not implemented The logs are quite long, so I organized everything in a repo: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JulienBe_airship-2Din-2Da-2Dbottle-2Dtesting&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=4PFygK135CuVlwdFm5y3c1kN-8p786y6mSWfEpqp6wE&e= Does it ring a bell for anyone ? Thanks for your time, Julien _______________________________________________ Airship-discuss mailing list Airship-discuss@lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=W_MUU5RD5NVllVkZUHLiT5EG-BZvQGizNKrqS4zyCMI&e=