Persistent Groups - Snapins added to host but not deployed
-
This is the output for mysql - After inserting that file, restarting the apache server, uninstalling and reinstalling the plugin
-
@georgebells it appears that the file hasn’t been replaced on the server for some reason.
When you view the
/var/www/fog/lib/plugins/persistentgroups/class/directory does persistentgroupsmanager.class.php have a different date than the rest of the files? -
-
@georgebells Well once that file is updated you need to uninstall and reinstall the plugin. When you uninstall that plugin it will drop that trigger from mysql. When you add the plugin back in via the web ui it will recreate that trigger. The updated file from the google drive has the changes made to the create trigger command. You don’t reinstall FOG because it will overwrite the patched file I sent you.
-
Makes sense - Edited my previous response because I immediately realised this is likely the case, just to clarify incase I did word it wrong, I had been reinstalling just the plugin through the UI, not fog itself.
-
@georgebells well the plugin file has the right number of bytes to the size so I think its the same as the file on my production server.
-
Interesting…
I’ve been going to the fog web management > plugins > installed plugins and uninstalling persistent groups…
I have then gone into install plugins, and reinstalled it.
I have also tried going to install plugins, deleting it, back to activate plugins, activating it and installing. -
Do you have any other advice on this? Haven’t had much chance to play around with it lately but hoping to revisit it soon
-
@george1421 Hey. Finally got around to looking at this again. Is it possible you have made any updates to the plugin since?
-
Hello,
I am using fog to manage a data center deployment consisting of over 1000 servers.
I am replying here as the UX feedback provided by @GeorgeBells here perfectly sums up issues I’ve been having as well.
If a feature request / ‘fix’ per details referenced above is NOT possible or planned, then I sincerely urge the dev team to consider allowing users to assign Snapins directly to images.
All of my equipment is of a similar spec, and the image I flash to them contains pre-configured FOG client as well as auto-setup scripts to configure UUID-based values on first boot.
All of my “snapins” are entirely image-specific by design.I would like to quick register all new equipment, immediately flash the same specific image, and then deploy the same snapin every time.
