@Clebboii This is probably true. We learned about a security issue and worked to solve that problem. I’m seeing what i can do to recover this feature, but it may take some time.

This feature is working on the working-1.6 branch if you’re willing to be a little on the bleeding edge (testing would be good for this branch. I’m pretty sure it’ll work for 99% of your needs without much issue, but without enough testers testing this, it’s a slow process.)

My testing shows with the security issue that was fixed, I’m still able to see the log viewer.

It’s difficult to simulate between the different 1.5.x and 1.6 for me.

I’m seeing if I can build a VM that would do the 1.5 side of things, but I’m not putting all my focus into that version of things any more. We are close to 1.6 finally, just need more people letting us know of anything they see.

If you’re unable to test that I understand, and I’m going to try to fix what I can if I can figure it out, but it’s not a top priority for me at least.

This feature is useful, but not a make or break thing for FOG’s operationality in my eyes. I hope that makes sense.

I’m having the exact same behavior.
Was working on the 27, 28 and 29.

Stopped working start of this week (2 september)
Added 3 storage nodes in between.
1a07ba58-be68-4007-a60c-5532e6c42e41-image.png

@Fog_Newb probaly just typoed it and i went with it too lol.

@Tom-Elliott the device is showing in pending devices now, thank you!

It doesn’t work with 6.6.49 too and 6.6.34.

Update to fog 1.6 fixed problem

@Tom-Elliott updated and working - thanks for fixing!

Great, thanks. Bug resolved!

@Tom-Elliott said in 1.6.0-alpha.1377 not showing available images on host:

Now, we have heard occasionally people have UI loading slowdowns when they’re suing FOG Client in their environment and the number of machines and check in times are just too frequent for the FOG Server to keep up and respond to all of them.

Sounds about right, I’ve turned it to 5 minutes but maybe I’ll try it at 30 and see what happens. We have about 1300 host entries (although they’re probably not all active now) but most should be off during the summer holidays. Thanks

@oelked I’m not sure I understand.

What is Persistent Groups plugin not doing that you’re hoping for?

Don’t get me wrong, a plugin building is a good time, as it helps you learn how to hook and event things in the FOG UI as well as potential interactions with other elements as possible. Just I don’t understand the scope of the problem you’re having that Persistent Groups couldn’t address.

Hello, no problem, I’ll try to describe it in more detail
Steps to reproduce

Create location

Set location name

-Storage Group
Establish

Storage Node
Omit because Node is not yet created or exists

Set Storage Node Protocol HTTP

Use inits and kernels from this node True

Add

no error occurs

Location is created.

When you create another location using the same procedure, the previous one will be overwritten
no new location will be created.

This behavior only occurs if no storage node is stored.

I noticed this behavior because I wanted to create my location structure in the master before I created all the storage nodes.

@Outer2211 Why is this a bug?

If the timezone isn’t defined (in the FOG Settings) it should default to the UTC time as it wouldn’t know what timezone your system is in.

@Tauric From the pictures we see that FOG recognized the filesystem as NTFS and should be able to resize it. It’s still strange the size was larger. Good you got this fixed by reinstalling the master to capture from. No idea what could have been wrong with the other one.

@Sebastian-Roth Thanks for the update! Again, this feature for us is more of a “nice to have” than an essential, so no immediate rush. I know all of y’all are busy!

@mronh I had a bit of time today and started looking at it. This is a bigger issue, code security involved and I wasn’t able to fix this in the time given.

I have got it on my list of things to fix when I find some more time.

@mosi This issue is fixed in the latest dev-branch version. Please update.

@AlexPDX This “bug” appears on new installs as well as on upgrades from any previous version.

This is just a minor thing because if things were right it would show the node’s kernel version instead of “Unauthorized”. It’s just not able to pull the kernel version information. Will be fixed when we find the time but this is not a show stopper.