FOG 1.6 Testing Needed - Help would be greatly appreciated as needed

[lebrun78]

Hello,
I try to upgrade my test server to 1.6 version.
But I have a problem with git:
When I try tu update the directory I get : “fatal: ‘working-1.6’ does not appear to be a git repository”

[root@cosinus fogproject]# git checkout working-1.6
Already on 'working-1.6'
[root@cosinus fogproject]# git pull working-1.6
fatal: 'working-1.6' does not appear to be a git repository
fatal: The remote end hung up unexpectedly
[root@cosinus fogproject]# git reset --hard
HEAD is now at d1ea5e5 Fix api for slack return information
[root@cosinus fogproject]# git pull working-1.6
fatal: 'working-1.6' does not appear to be a git repository
fatal: The remote end hung up unexpectedly

Arnaud

[Quazz]

@lebrun78 Do just git pull first to update your branch info.

[lebrun78]

[root@cosinus fogproject]# git pull 
Already up-to-date.

But when I execute installfog.sh I have Version: 1.5.4.562 Installer/Updater

[Quazz]

@lebrun78 Does the WebUI look different now after running installfog.sh?

[Matthieu Jacquart]

@lebrun78 It’s the new web interface 1.6 (don’t care about 1.5.4.562)

[Tom Elliott]

The steps, typically, would be:

git pull
git fetch --all
git checkout working-1.6

The fetch is probably the more important as it will pull in any new branches and tags. It will not clean older branches though.

[Joe Gill]

@Tom-Elliott

I like the new look! Where can we post requests / bugs?

Thanks!

[lebrun78]

@joe-gill
https://forums.fogproject.org/category/11/feature-request

[THEMCV]

Wooooooow it looks great! I’ll poke around and hunt for some bugs.

[Zer0Cool]

@tom-elliott said in FOG 1.6 Testing Needed - Help would be greatly appreciated as needed:

I know you all have been hearing about our work on 1.6 and maybe even our “kind of” roadmap with 1.7, 1.8, 1.9, and 2.0.

Is there any specific place we can check this info out? I would be interested to read about future plans. Thanks

[Tom Elliott]

@zer0cool just where I wrote it already. Right now Joe is very very limited in his ability to help with the project so it really is just me at this point. We have our other people but they are very busy as well.

[Joe Gill]

This post is deleted!

[INF3]

Hey, testing with 1.6 I have found that I’m having trouble creating tasks for hosts. When trying to create any task you get a toast notification in the top right saying ‘Internal Server Error.’

I saw a number of other posts advising to check the apache logs however it doesn’t appear to create an entry when the task creation fails.

Is there other log files I could check for more information?

Im running Centos 7.5 with mysql Ver 15.1 Distrib 5.5.60-MariaDB.

[jms]

Having some trouble on CentOS 7.5 (with all updates). Everything seems to go fine and I can log into the web console and then just get to a blank page. Happens on both Safari and Firefox (latest versions).

Here are my steps … CentOS 7.5 VM – fresh install, freshly updated and rebooted.

#> cd /opt
#> git clone https://github.com/FOGProject/fogproject.git
#> cd fogproject

#> git pull
#> git fetch --all
#> git checkout working-1.6

#> cd bin
#> ./installfog.sh

Set up as Fog server with DHCP and gateway, but not DNS. Then updated firewall …

#> for service in http https tftp ftp mysql nfs mountd rpc-bind proxy-dhcp; do firewall-cmd --permanent --zone=public --add-service=$service; done
#> firewall-cmd --permanent --add-port=49152-65532/udp
#> firewall-cmd --permanent --direct --add-rule ipv4 filter INPUT 0 -p igmp -j ACCEPT
#> systemctl restart firewalld

Next completed the database install via the GUI and completed the text based installer with no issues. But as I’ve said I get sent to the following URL which is just a blank page in both browsers I tried …

https://XXX.XXX.XXX.35/fog/management/index.php?node=home

I have attached the full text output of the installation process.

Sorry - I’m sure I’ve missed something simple and obvious – but can anyone spare a few minutes to take a look and provide some guidance? Thank you !!
0_1540930468007_Fog Installation Log.txt

[Sebastian Roth]

@jms Sounds like you are on the right track here. Can you please take a look at the apache error logs (see my signature). This is where we usually find evidence for why a blank page is shown.

[jms]

@Sebastian-Roth … SELinux maybe the culprit? This is the entire contents of /var/log/httpd/error_log

[Tue Oct 30 15:18:54.950152 2018] [core:notice] [pid 18968] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Tue Oct 30 15:18:54.951263 2018] [suexec:notice] [pid 18968] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Oct 30 15:18:55.024509 2018] [auth_digest:notice] [pid 18968] AH01757: generating secret for digest authentication …
[Tue Oct 30 15:18:55.025440 2018] [lbmethod_heartbeat:notice] [pid 18968] AH02282: No slotmem from mod_heartmonitor
[Tue Oct 30 15:18:55.045190 2018] [mpm_prefork:notice] [pid 18968] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.6.38 configured – resuming normal operations
[Tue Oct 30 15:18:55.045219 2018] [core:notice] [pid 18968] AH00094: Command line: ‘/usr/sbin/httpd -D FOREGROUND’
[Tue Oct 30 16:02:57.220914 2018] [mpm_prefork:notice] [pid 18968] AH00170: caught SIGWINCH, shutting down gracefully
[Tue Oct 30 16:03:13.796605 2018] [core:notice] [pid 1099] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Tue Oct 30 16:03:13.799657 2018] [suexec:notice] [pid 1099] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Oct 30 16:03:13.873692 2018] [auth_digest:notice] [pid 1099] AH01757: generating secret for digest authentication …
[Tue Oct 30 16:03:13.874639 2018] [lbmethod_heartbeat:notice] [pid 1099] AH02282: No slotmem from mod_heartmonitor
[Tue Oct 30 16:03:13.928936 2018] [mpm_prefork:notice] [pid 1099] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.6.38 configured – resuming normal operations
[Tue Oct 30 16:03:13.928975 2018] [core:notice] [pid 1099] AH00094: Command line: ‘/usr/sbin/httpd -D FOREGROUND’

[Sebastian Roth]

@jms Those messages are fine I think. Check for SElinux with this command just to make sure: getenforce (should say permissive)

[jms]

@Sebastian-Roth I set SElinux to permissive and rebooted and now have full access to the web application. Are there any tips/tricks to get this to work in a more secure environment? My customer will require it.

[Sebastian Roth]

@jms Are you sure you wanna use the current 1.6 testing branch of FOG? From what you write it doesn’t sound like it. Please let us know what exactly are you aiming for.

We have a wiki article on CentOS that you might find interesting: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

About SELinux… first search result in the forums is: https://forums.fogproject.org/topic/6154/selinux-policy

[Tom Elliott]

I know it’s been a while since I posted this announcement, but I’ve been kind of keeping up with @Sebastian-Roth with his code changes with 1.5.5 and how they apply to 1.6 as well.

Remember, for the most part, the backend side of FOG is staying the same with as minimal of changes as I can. What this means, is many of things in terms of overall performance and functionality that has been going into 1.5.5 can be relatively simple to apply to 1.6.

There are some caveats to this though. But I think things are looking much better than they had from the initial posting of this.

I know it’s the holiday season and I hope everybody enjoys it. I think this is all the more reason to apply the post so it can be viewed a little more readily.

Thank you all.