Fog Installer - Distro check

[Wayne Workman]

@developers @moderators There were a ton of failures last night. Not sure why. When I get home this evening I’ll check it out.

[Wayne Workman]

@developers @moderators I’ve determined most of these failures are due to the remi repository being broken somehow. Some errors from CentOS 7:

package remi-release-7 is not installed
curl: (22) The requested URL returned error: 503 Service Temporarily Unavailable
error: skipping http://rpms.remirepo.net/enterprise/remi-release-7.rpm - transfer failed
Retrieving http://rpms.remirepo.net/enterprise/remi-release-7.rpm
curl: (22) The requested URL returned error: 503 Service Temporarily Unavailable
error: http://rpms.remirepo.net/RPM-GPG-KEY-remi: import read failed(2).
../lib/common/functions.sh: line 580: yum-config-manager: command not found
../lib/common/functions.sh: line 581: yum-config-manager: command not found

I checked on the Fedora ones, similar errors.

However, I’ve tried to reproduce the errors manually and I cannot.

I have to conclude that there was in fact a problem of some kind with the Remi repository, and that it now appears to be fixed. As far as Arch Linux goes, I really don’t have any idea. Everyone’s welcome to look at the logs though.

[Sebastian Roth]

@Wayne-Workman Thanks for looking into this. I maybe found what’s wrong on Arch. MariaDB says:

Installation of system tables failed! Examine the logs in /var/lib/mysql for more information.

DB seems to be not up. Possibly just a rename of the init file in Arch as I saw errors about that too.

[Wayne Workman]

@sebastian-roth Everything is back to the way it was this morning, with no effort from me.

So, we no longer have much of a tie going on. Debian 8, Debian 9, and Ubuntu 16 are now tied for FOG stability. CentOS didn’t fail out because of anything CentOS did, but rather because of the dependency on the remi repo to get certain PHP packages that FOG needs. I’m confident that if CentOS didn’t need the remi repo for FOG, it’d still be tied for leader. But it is what it is I guess.

It would be nice if we could in the future not require external repositories beyond what the OS ships with (like epel and remi and others).

[Sebastian Roth]

@Wayne-Workman Yes, good point. We should look into what is still needed. I think a lot of it came in when PHP7 was still new…

[Sebastian Roth]

Repos are still needed… I spoke too soon: https://github.com/FOGProject/fogproject/issues/224

[Wayne Workman]

@sebastian-roth Well thanks for looking into it.

[Wayne Workman]

Last night, all Ubuntu 17 failed. Looks like a problem with one of their repo mirrors. us.archive.ubuntu.com/ubuntu zesty/main

[Wayne Workman]

Ubuntu 17 still failing.

[Sebastian Roth]

@Wayne-Workman Well I think the issue with Ubuntu is that Zesty (17.04) is history since 13th of January 2018! Seems like it’s gone from the official mirrors now too.
See here: https://wiki.ubuntu.com/ZestyZapus/ReleaseNotes and https://wiki.ubuntu.com/Releases

Ubuntu 17.04 will be supported for 9 months until January 2018. If you need Long Term Support, it is recommended you use Ubuntu 16.04 LTS instead.

[Wayne Workman]

@sebastian-roth Ah you are right. I’ll get that out of there then and setup 17.10

[Sebastian Roth]

@wayne-workman said in Fog Installer - Distro check:

I’ll get that out of there then and setup 17.10

But be aware that 17.10 will be gone in July 2018… really short cycles. And 18.04 is just around the corner!

[Wayne Workman]

@sebastian-roth that’s fine. the whole idea is to follow the distros. This way - if the Ubuntu people do something crazy again, we will know about it immediately.

[Tom Elliott]

Please don’t forget we typically only use Ubuntu LTS versions less the most current version. This is because of the ondrej release cycle. I cannot remember if 16 and higher in fog installer requires the ondrej repo though.

[Wayne Workman]

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

Please don’t forget we typically only use Ubuntu LTS versions less the most current version.

Right. Everyone that is active only recommends ubuntu 16.04 - but I usually advise to use Debian or CentOS.

Also, looks like I messed up the tests real good over the weekend trying to add Ubuntu 17.10.

[Wayne Workman]

Got the tests working again, but the streak counts are from an older backup. Going to try to finagle them back to what they were before sometime soon.

[Wayne Workman]

There might be a problem with Ubuntu 14.04 clean installation. There was a failure last night, this was the problem:
php7.1-gd : Depends: libgd3 (>= 2.1.1) but it is not going to be installed
Might just be a hiccup - if it fails the same way tomorrow morning I’ll look into it more.

[Sebastian Roth]

@Wayne-Workman Looks like a hickup. I just did a quick test on a fresh ubuntu VM I had at hand. Installing php7.1-gd with libgd3 as dependency worked great!

...
Get: 9 http://ppa.launchpad.net/ondrej/php/ubuntu/ trusty/main libgd3 amd64 2.2.5-4+ubuntu14.04.1+deb.sury.org+2 [131 kB]
...
Selecting previously unselected package libgd3:amd64.
Preparing to unpack .../libgd3_2.2.5-4+ubuntu14.04.1+deb.sury.org+2_amd64.deb ...
Unpacking libgd3:amd64 (2.2.5-4+ubuntu14.04.1+deb.sury.org+2) ...
...

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