Fog Installer - Distro check

[Sebastian Roth]

@Wayne-Workman Something else I noticed in the logs… You might want to run apt-get autoremove to remove old kernels on that system as well. Not an issue, just making the logs a little smaller and easier to read.

[Wayne Workman]

@sebastian-roth I do normally when I update my ‘clean’ snapshots. Thanks for the suggestion though. Little suggestions like this is honestly what helped me get into Linux and make sense of it all.

Also, Fedora 27 workstation on working branch appears to be having problems now.

[Sebastian Roth]

@Wayne-Workman Had a quick look but couldn’t figure what’s going wrong yet… Something seems wrong with DB (backup?).

[Wayne Workman]

@developers since the 1.5 release, all Ubuntu 16.04 tests are failing. Looks like the notorious alter user SQL problem.

[Tom Elliott]

@wayne-workman We’ve only had one day of releases. The working and dev-branches code for alter user have not changed for a bit, and working was merged into dev-branch, and dev-branch was merged into master. Since the installer worked on 16 just yesterday, this leads me to think there’s a problem with the configuration layout?

Just thinking out loud here, that or between yesterday and today Ubuntu 16 has changed something causing this to break.

[Tom Elliott]

Just for everyone’s viewing pleasure:
Yesterday’s Run:

CentOS7 successfully updated OS.
Debian8 successfully updated OS.
Debian9 successfully updated OS.
Fedora25 successfully updated OS.
Fedora26 successfully updated OS.
Fedora27Workstation successfully updated OS.
Ubuntu17.10 successfully updated OS.
Ubuntu16 successfully updated OS.
Ubuntu14 successfully updated OS.
Arch success with "working"
CentOS7 success with "working"
Debian8 success with "working"
Debian9 success with "working"
Fedora25 success with "working"
Fedora26 success with "working"
Fedora27Workstation success with "working"
Ubuntu17.10 success with "working"
Ubuntu16 success with "working"
Ubuntu14 success with "working"
Arch success with "dev-branch"
CentOS7 success with "dev-branch"
Debian8 success with "dev-branch"
Debian9 success with "dev-branch"
Fedora25 success with "dev-branch"
Fedora26 success with "dev-branch"
Fedora27Workstation success with "dev-branch"
Ubuntu17.10 success with "dev-branch"
Ubuntu16 success with "dev-branch"
Ubuntu14 failure with "dev-branch", failed installation
Fog log: http://theworkmans.us:20080/fog_distro_check/Ubuntu14/fog/2018-02-26_05-02_fog.log
No apache log could be retrieved from Ubuntu14
Arch failure with "master", failed installation
Fog log: http://theworkmans.us:20080/fog_distro_check/Arch/fog/2018-02-26_05-16_fog.log
Apache log: http://theworkmans.us:20080/fog_distro_check/Arch/fog/2018-02-26_05-16_apache.log
CentOS7 success with "master"
Debian8 success with "master"
Debian9 success with "master"
Fedora25 success with "master"
Fedora26 success with "master"
Fedora27Workstation success with "master"
Ubuntu17.10 success with "master"
Ubuntu16 success with "master"
Ubuntu14 success with "master"
Full Report: http://theworkmans.us:20080/fog_distro_check/reports/2018-02-26_06-35_install.log

Todays run:

CentOS7 successfully updated OS.
Debian8 successfully updated OS.
Debian9 successfully updated OS.
Fedora25 successfully updated OS.
Fedora26 successfully updated OS.
Fedora27Workstation successfully updated OS.
Ubuntu17.10 successfully updated OS.
Ubuntu16 successfully updated OS.
Ubuntu14 successfully updated OS.
Arch success with "working"
CentOS7 success with "working"
Debian8 success with "working"
Debian9 success with "working"
Fedora25 success with "working"
Fedora26 success with "working"
Fedora27Workstation success with "working"
Ubuntu17.10 success with "working"
Ubuntu16 failure with "working", returned no exit code
Fog log: http://theworkmans.us:20080/fog_distro_check/Ubuntu16/fog/2018-02-27_03-52_fog.log
Apache log: http://theworkmans.us:20080/fog_distro_check/Ubuntu16/fog/2018-02-27_03-52_apache.log
Ubuntu14 success with "working"
Arch success with "master"
CentOS7 success with "master"
Debian8 success with "master"
Debian9 success with "master"
Fedora25 success with "master"
Fedora26 success with "master"
Fedora27Workstation success with "master"
Ubuntu17.10 success with "master"
Ubuntu16 failure with "master", returned no exit code
Fog log: http://theworkmans.us:20080/fog_distro_check/Ubuntu16/fog/2018-02-27_06-08_fog.log
Apache log: http://theworkmans.us:20080/fog_distro_check/Ubuntu16/fog/2018-02-27_06-08_apache.log
Ubuntu14 success with "master"
Arch success with "dev-branch"
CentOS7 success with "dev-branch"
Debian8 success with "dev-branch"
Debian9 success with "dev-branch"
Fedora25 success with "dev-branch"
Fedora26 success with "dev-branch"
Fedora27Workstation success with "dev-branch"
Ubuntu17.10 success with "dev-branch"
Ubuntu16 failure with "dev-branch", returned no exit code
Fog log: http://theworkmans.us:20080/fog_distro_check/Ubuntu16/fog/2018-02-27_08-23_fog.log
Apache log: http://theworkmans.us:20080/fog_distro_check/Ubuntu16/fog/2018-02-27_08-23_apache.log
Ubuntu14 success with "dev-branch"
Full Report: http://theworkmans.us:20080/fog_distro_check/reports/2018-02-27_08-44_install.log

Message Input

Message #distro_check

No changes to the installer code that handles this between working yesterday, and release. So working worked on Ubuntu 16 yesterday. This leads me to think something Ubuntu did. I don’t know what I can do to fix it.

[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.