@AngryScientist It would be interesting to know if the contents of your .fogsettings file is messed up and then upgrading caused the installer to look at bad data again??

My production server is running Centos 7, I think we are on RC34 and that upgraded cleanly.

@Tom-Elliott Thanks i did svn up and then re-installed and it looks like its all good again 🙂

@Tom-Elliott
I can confirm that the issue is resolved now. Thanks a lot for all the good work!

@Tom-Elliott

Problem was fixed in RC-34/35

Thank You

RC 32 should address the problem you are describing.

Of note, this same issue was occurring on snapins as well.

Both elements should now properly work.

@Tom-Elliott thanks Tom, updating now

is RC30 current working branch? Whooops sorry i missed the RC30 post.

@Thiago-Moraes Here’s my advice for you: https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

Joking aside, it looks like you’re on an absolutely ancient version of FOG. I’d recommend you build a new server using the latest FOG 1.3.0 Release Candidate and begin using that.

Confirmed, found, patched, tested fix. Will push shortly.

Confirmed, and republished RC-29.

Unexpected referrer check simply wasn’t sending the right class to operate from.

This should now work as intended.

FYI, it’s working 🙂

alt text

@michael_f @Wayne-Workman @Hanz a patch has been developed and verified for this issue. It will be released with 0.11.6 (along with a few other new features) once release candidate testing finishes for the client.

Cool, thanks. 🙂

https://github.com/FOGProject/fogproject/issues/145

@Wayne-Workman found and confirmed. I was partially aware of there being an issue with this but just kept over thinking how to approach it.

I’ve implemented a solution into working-RC-28 which appears to fix this , among a few others, issue.

I mean following the steps I outlined above is how I got it to finally work. Assume a save and a hard refresh on a separate tab to achieve each = . Considering what I found with the storage group association of images yesterday I figured I’d try toggling some settings, and that included the Search vs List option.

It wasn’t until I performed a Search from the Images page that the LIST option setting began to work as intended.

Again, this is on an absolutely from-the-ground-up installation of CentOS followed by RC26. The only thing introduced other than my standard configuration was the importing of exports.

@Tom-Elliott everything seems to be working fine now using the working-branch, both inventory and the image task, thanks.

@sudburr Of course, but you can change where these are written to (in console).

Each of the services have a default tty (and they should all be different, though it wouldn’t hurt anything to have them on the same).

The idea, I think, is so make users more aware of the services and that they are running and any issues that might be happening. I don’t know how any information printed out by the services would be “sensitive” unless your file names are in such a way it might give out PII or confidential/sensitive information. In that case, though, you can just change the TTY for the services within FOG Configuration -> FOG Settings -> FOG Linux Service TTY Output (I think).

@Tom-Elliott Thanks for the very fast assistance! Awesome work as usual.

My magic is fixing it now.

Will be in for RC-27.