Fog Installer - Distro check

[Wayne Workman]

@tom-elliott said in Fog Installer - Distro check:

This leads me to think something Ubuntu did.

I agree, probably something in Ubuntu has changed since the FOG Code base has not changed.

Typically, it’s normal for there to be a ‘hiccup’ in the testing process occasionally. An example would be yesterday’s failure on ubuntu 14 - just a single failure on a single branch.

Today’s failure was different though, same failure on Ubuntu 16 for all branches. Yet, code base has not changed. This means something with Ubuntu changed.

[Wayne Workman]

My Arch VM is having problems - not getting a DHCP lease for whatever reason. Not sure why, as I have mechanisms to ensure a fresh lease built into the test cycle. Must be patching related.
Looks like Fedora Remi repository had a hiccup last night also, doesn’t look major though.

[Wayne Workman]

Lots of failures last night - over the weekend I did update my VMs so I’m blaming that. Last time I updated the VMs, there were several failures the next day but the day after that, everything started working. So I’m waiting to see tomorrow’s results.

[Wayne Workman]

The failures are infact a problem with Fedora. See this thread for details: https://forums.fogproject.org/topic/11702/upgrading-from-1-5-0-to-1-5-1-fails-at-backup

[Wayne Workman]

As of now, all installer tests are passing with the release of 1.5.2.

[Wayne Workman]

I’m going to try to get Ubuntu 18.04 into the test cycle tonight.

[george1421]

@wayne-workman Do you have a way to do a quality of service check against FOG or are you doing this right now?

What I’m thinking is a http curl call to the vm at the www root and see if the url was redirected to /fog/management or something like that . That would test if the fog UI was actually up and talking with the database.

[Wayne Workman]

@george1421 I could add this in - but as soon as this is in there, we will want to check something else next. There is a project called Selenium that is suited for testing responses to web requests. @developers @moderators does anyone have experience with Selenium that could help put together some tests? If not, I’m fine with writing up a simple python script to do some testing with the Requests library (I have experience with that).

[Sebastian Roth]

@Wayne-Workman Back in 2007 I used twill when doing Web Application Firewall testing for my diploma thesis. But seems like this project hasn’t gone anywhere since then. Just thought I might throw that in, probably not worth anything.

[Wayne Workman]

@sebastian-roth It’s truly dis-heartening to me to be shown awesome libraries from yesteryear that didn’t take off… My heart goes out to Twill. However, Requests has gained substantial community support (not due to any of my doings) and probably has a much longer future than other libraries. I was hoping someone had Selinium experience - but I really do think we can do just fine with Requests.

[Wayne Workman]

A heads up - seems like Ubuntu 18 is having a lot of problems these past few days. I’ve not looked into it yet.

[Wayne Workman]

I’ve added Fedora 28 server to the list.

[Wayne Workman]

Looks like there is a possible issue with php-fpm on Ubuntu 16. I’ll look into it in more detail this evening.

[Wayne Workman]

@developers I’ve looked into the Ubuntu 16.04 problems for the last two hours and have determined the problem is being intermittently caused by a problematic ppa.launchpad.net server: 91.189.95.83. The apt-get update command times out, and because it was not successfully run, lots of packages fail to install. I’ve also looked over all of the commits in the working, dev-branch, and master branch of the fogproject github repository around the days that the Ubuntu 16.04 failures started happening, there are no commits that would cause this.

The workaround: If the installer fails for you, manually run apt-get update until it succeeds. Once it has succeeded, run the installer again and it should work.

[Sebastian Roth]

@Wayne-Workman Thanks heaps for digging into this!

[Wayne Workman]

Just an update,

You will notice that the link in my signature is different, the one there is the new one.
Long story short, I setup an email server for myself, which caused DNS & ssl problems to arrise with the fogtesting dashboard. So - I moved the site to a t2.nano in AWS. The same VM here at my house is still doing 100% of all testing, but when it gets done it does a quick rsync to the aws box to update the website with the new dashboard & files.

[Wayne Workman]

I’ve added Fedora 29 Beta to the daily installation tests. I’ll remove it and add the official release as soon as that’s available. I’ve also updated all of my ‘clean’ snapshots with the latest patches.

[Wayne Workman]

I’ve removed Fedora29-Beta, and setup a Fedora29 minimal server today, from the official release ISO. I’m pretty sure I remembered to do everything this time (like firewalld and selinux). We’ll see how it goes tomorrow morning.

[Wayne Workman]

So the issue with Fedora 29 is the Remi repo, they don’t seem to be caught up with the recent release. Their website still lists the beta version. I tried manually installing the remi repo for fedora 29 beta, doesn’t work. I don’t think there’s anything we can do until Remi Repo gets their end fixed. Most likely, when it’s fixed, everything will just start working because it appears the fog installer is creating the correct commands.

[Wayne Workman]

So as expected, the remi repo removed Fedora 29 beta, and added Fedora 29 release. Dev-branch and master are passing the installation tests, but working is failing which seems strange. Ubuntu 18 on working branch also failed - this test was run immediately after the Fedora 29 working test, so maybe it’s something with my vm host or internet at that time. It’s normal for this test system to have the occasional blip (it is what it is) so we’ll see what the tests say tomorrow.