HI Alex, yeah - the issue was pre-installed libvirt causing issues. As long as it's standard Ubuntu 1604 - that's all you need. Kindly, Kaspars ________________________________________ From: Alex Arnoldy [alex.arnoldy@suse.com] Sent: Friday, January 18, 2019 12:55 PM To: Roman Gorshunov; airship-discuss@lists.airshipit.org Subject: Re: [Airship-discuss] Airship in a bottle install failure... Thanks. Maybe I'll give that one a shot. It won't shed any light into the previous issues I've had but it's also possible that those problems were related to intermittent keyboard driver problems I've seen in the past. --Alex. Alex Arnoldy Software Defined Infrastructure Solutions Architect SUSE Alex.Arnoldy@SUSE.com (P) +1 (408) 828-9797 -----Original Message----- From: Roman Gorshunov <paye600@gmail.com> Sent: Friday, January 18, 2019 10:36 AM To: airship-discuss@lists.airshipit.org Subject: Re: [Airship-discuss] Airship in a bottle install failure... Hi, `git clone ...; cd airship-in-a-bottle/; vagrant up` mostly works fine. The vagrant box image used works good. Regards, -- Roman Gorshunov On Fri, Jan 18, 2019 at 6:41 PM Alex Arnoldy <alex.arnoldy@suse.com> wrote:
Hi Drew,
Unfortunately not. However, I think I'll have a bit of a breather today so this afternoon I'll give it another shot.
Are there any known gotchas when it comes to the VM or O/S? I noticed someone eluded to not including KVM to the initial install packages helped out.
Best,
--Alex.
Alex Arnoldy Software Defined Infrastructure Solutions Architect SUSE Alex.Arnoldy@SUSE.com (P) +1 (408) 828-9797
-----Original Message----- From: Drew Walters <drewwalters96@gmail.com> Sent: Friday, January 18, 2019 9:38 AM To: Alex Arnoldy <alex.arnoldy@suse.com> Cc: MATT MCEUEN <MM9745@att.com>; airship-discuss@lists.airshipit.org; INI-EAI-INO-MBL Balsiger Daniel <Daniel.Balsiger@swisscom.com> Subject: Re: [Airship-discuss] Airship in a bottle install failure...
On Jan 15, 2019, at 4:57 PM, Alex Arnoldy <alex.arnoldy@suse.com> wrote:
Hi Drew,
I gave it another shot with the latest build. It definitely went better, but it still went into a CrashLoopBackOff on one of the MaaS pods before it could complete. Unfortunately, I was neck deep in something else so I had to shut that VM down before collecting any info.
As a small side note, I did ensure that the hostname of the VM was in /etc/hosts and associated with the IPv4 primary interface.
Sorry that’s not much info to go on,
--Alex.
Alex Arnoldy Software Defined Infrastructure Solutions Architect SUSE Alex.Arnoldy@SUSE.com (P) +1 (408) 828-9797
Hi Alex,
Were you able to return to the VM and obtain the logs of the failing MaaS pod before it was removed? I’m not entirely sure where to proceed from here, but perhaps someone more familiar with MaaS may know some additional things you can try.
Drew _______________________________________________ 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=L2WcX1Ge33cpIHXX6krAgw&m=1QkZWVrNKsc-yvwNebiLcq02zjfbK6RHbjuVQGIR0lU&s=y-pWlk22qanjnSJNO7kZmh2X1A7hN8sfUHBqczBl_AY&e=
_______________________________________________ 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=L2WcX1Ge33cpIHXX6krAgw&m=1QkZWVrNKsc-yvwNebiLcq02zjfbK6RHbjuVQGIR0lU&s=y-pWlk22qanjnSJNO7kZmh2X1A7hN8sfUHBqczBl_AY&e= _______________________________________________ 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=L2WcX1Ge33cpIHXX6krAgw&m=1QkZWVrNKsc-yvwNebiLcq02zjfbK6RHbjuVQGIR0lU&s=y-pWlk22qanjnSJNO7kZmh2X1A7hN8sfUHBqczBl_AY&e=