Fog Installer - Distro check

[Wayne Workman]

December 6th, 2016
FOG Version 1.3.0 RC-29
Git Commit 3d79051166f0a735902925c861e1e6d078158f74

Below, I installed FOG as a Storage Node on each of the below systems, and defined a pre-existing FOG 1.3.0 RC-29 server as the database server. Below are the results.

• Arch Linux 2016.10.01 fully updated - Installed without issues.

• Fedora 24 fully updated - Installed without issues per wiki instructions.

• Fedora 25 fully updated - Installed without issues per wiki instructions.

• CentOS 7 fully updated - Installed without issues per wiki instructions.

• Debian 8 fully updated - Installed without issues.

• Ubuntu 16.04 fully updated - Installed without issues.

[Wayne Workman]

December 18th, 2016
Branch: working-1.3.0
Git Commit 3e69bbb5f5ea0b573dad81581665fd15f95eda72

• Arch Linux 2016.10.01 fully updated - Installed without issues.

• Fedora 24 fully updated - Installed without issues per wiki instructions.

• Fedora 25 fully updated - Installed without issues per wiki instructions.

• CentOS 7 fully updated - Installed without issues per wiki instructions.

• Debian 8 fully updated - Installed without issues.

• Ubuntu 16.04 fully updated - Installed without issues.

[Tom Elliott]

@Wayne-Workman
December 19th 2016
Branch: working-1.3.0
Git Commit 7c1778971265813fa214318bd661574ff221635a and e436d8a4a6820956cfee6dabe6a0641b89291b74

CentOS 6 fully updated - Installed without issues per wiki instructions. (Only pertaining to iptables off and selinux in permissive mode.)

[Quazz]

@Tom-Elliott So the PHP thingy is fully resolved on Centos 6? (sorry if it has been for ages, just want to be sure)

[Tom Elliott]

@Quazz Yes. Under the working-1.3.0 branch of course.

[Wayne Workman]

December 30th, 2016
Branch: master
Git Commit f23fb06ace4df6e9e69f974244baa032d1be4e04
Release Version: FOG 1.3.0

There is a minor hiccup in the FOG 1.3.0 installer that causes problems with detecting the router address on Arch, Fedora 24, Fedora 25, CentOS 7, Debian 8, and Ubuntu 16.04. While using the -y argument of the installer, most of these distributions will go into an infinite loop on a fresh installation. They will install without the -y argument but you will need to answer n for setting a router address or type in the actual router address when it asks. Ubuntu doesn’t seem to loop for me but still the router address is wrong in the settings.

There is a workaround for all of the distributions for using the -y argument. You would simply fill the routeraddress variable manually while you start the installer. My router address is 10.0.0.1 thus the answer is:

routeraddress=10.0.0.1 ./installfog.sh -y

You can use this method for a successful unattended installation.

Other than that, everything appears to be fine.

[Wayne Workman]

Janurary 31st, 2017
Branch: master
Git Commit: 7bde5a208dc9b681a22946c3788c5f8242da9f3a
Release Version: FOG 1.3.4

Debian 8.7 - fully updated - installed without issues.
Ubuntu 14.04 - fully updated - installed without issues
Ubuntu 16.04 - fully updated - installed without issues
CentOS 7 - fully updated - installed without issues per wiki instructions

Fedora 25 - fully updated - failed
@Tom-Elliott

* Setting up and starting RPCBind.............................Failed!

Below is the error log.
0_1485920319584_fog_error_1.3.4.log

This is what shows in journalctl -xe after I run systemctl restart rpcbind

-- Unit rpcbind.service has begun starting up.
Jan 31 21:39:21 localhost.localdomain rpcbind[10604]: rpcbind: /run/rpcbind/rpcbind.lock: No such file or directory
Jan 31 21:39:21 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='
Jan 31 21:39:21 localhost.localdomain systemd[1]: rpcbind.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 21:39:21 localhost.localdomain systemd[1]: Failed to start RPC Bind.
-- Subject: Unit rpcbind.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit rpcbind.service has failed.
-- 
-- The result is failed.
Jan 31 21:39:21 localhost.localdomain systemd[1]: rpcbind.service: Unit entered failed state.
Jan 31 21:39:21 localhost.localdomain systemd[1]: rpcbind.service: Failed with result 'exit-code'.

Also have tried uninstalling rpcbind, the service still will not restart.

[Wayne Workman]

Just so people are aware, I’m still testing the distributions. I’ve automated this & the results are available daily to the fog team only. I’ll post here with concerns.

Right now - Fedora 25 is broke, it’s a bug in the OS, nothing we can do about it. It’s related to rpcbind.

And it appears that starting last night something is wrong with the fog installation on Ubuntu 16. It’s related to the alter user command in MySQL.

[Wayne Workman]

After re-running the tests, Ubuntu 16 appears fine. Must have been a fluke. Anyone want to donate a server? I’m using an old Poweredge r410.

[Wayne Workman]

Fedora 25 and 26 are not working with the installer right now, something to do with rpcbind.

I’ve not found the time to look at it. The failure logs are here if anyone want’s to take a peek:
http://perpetuum.io:20080/fog_distro_check/Fedora25/fog/2017-07-31_04-14_fog.log
http://perpetuum.io:20080/fog_distro_check/Fedora26/fog/2017-07-31_04-22_fog.log

Of course, I’m still testing the Linux distributions that FOG tries to support, it’s all automated now. You can find daily results in the dashboard link in my signature.

[Sebastian Roth]

Seems like they had several issues with rpcbind over the last year or so: https://bugzilla.redhat.com/show_bug.cgi?id=1401561 and https://bugzilla.redhat.com/show_bug.cgi?id=1415496 (Not sure if those are related or not!)

@Wayne-Workman SElinux is disabled on those machines I suspect?!

[Tom Elliott]

@sebastian-roth I suspect it was my “fixing” code that is now “fixed” but causing a problem with latest updates. Just a guess. My fixing code just made it so fedora could install, and basically all it did was make sure the path it was looking for during startup existed. Now it looks like it’s the reverse, it’s trying to create a file that already exists, hence permission denied… (as it’s likely in use then too).

[Wayne Workman]

@sebastian-roth said in Fog Installer - Distro check:

SElinux is disabled on those machines I suspect?!

I forgot to disable it on those two VMs… that is my bad. I’ll get that fixed.

[Wayne Workman]

The issues appear to have been non-issues in the latest tests. SELinux was not set to permissive (my fault).

[Wayne Workman]

Soon, the fog installer dashboard (see my signature) will have streak counts for each item. There will be a current success streak and a record success streak.

I’ve been wanting to do this for a while, I think it’ll be fun to watch the counts stack up. I’m monitoring the files for a couple days to be sure everything is working right before I put the values into the tables.

[Wayne Workman]

Streak counts are now public.

[george1421]

Very nice job!! After some time we should be able to identify the most stable OS for FOG installs. This will really come in handy when thinking about which OS we might support in the future.

[Wayne Workman]

@george1421 I think I already know which ones will be most stable. I’ll keep quiet though and we’ll see how it goes.

[Wayne Workman]

Arch bombed out this morning on all branches - something to do with NFS. This is typical for Arch - one day it’ll just bomb out hard across the board on the same item, a couple days later it’s fixed. Once it was related to mariadb problems, today it’s NFS.

Not trying to bash Arch here, there is a very small team working on Arch and they overall do a good job when you take into account their team size. Also stuff is going to break occasionally when you’re always making stuff better.

On a side note, the streak counts seem to be working.

[Wayne Workman]

Between 1:40 AM and 2:44 AM CST, the Arch team likes to make changes. I can tell because working branch runs first, and succeeded with Arch, but later dev-branch and master failed with the same error.