Latest FOG 0.33b
-
My guess is some of the problems you’re reporting (not specific to snapins) are related to the fog/images/init.gz fog/kernel/bzImage you’re reporting.
1.) The no such file or directory issue: fog/kernel/bzImage fog/images/init.gz etc… are because I modified the kernel and image stuff to obtain from the GUI which auto sets based on the values in config.php when you FIRST install fog. I fixed the “fresh” install so all should work properly.
If you already had it installed and performed an update it wouldn’t have changed your database values. So to fix, go to FOG Configuration Page->FOG Settings and change the fog/memtest/memtest, fog/kernel/bzImage, and fog/images/init.gz to memtest, bzImage, init.gz respectively and all should work properly for you.
2.) Probably related to Item number one.
3.) Will look into that, I only fixed the Snapin issues on the Host side. While the Host side still creates the “image” package, I probably missed something and will look into that.
4.) Haven’t added that component yet. Just trying to get the “individual” stuff working absolutely before making the rest of the changes. The other issue I foresee with it is that detecting which snapins are equally associated across the group can be painful. So have to try to figure out the stats on that and how to get them working across the board.
5.) Snapins are a fickle little thing. You actually have to log in to the system for the snapin to truly deploy as it requires user rights to install.
6.) Understood, I’ll take a look at that today when I get home.
7.) What do you mean one deployed right away, while the other just sat there? You mean you setup two systems to deploy a single snapin and one deployed right away, while the other just sat there? Was the one that deployed “right away” logged in and the other no user logged in?
8.) Probably the method of checking isn’t verifying the host. Will look into when I get home.
The last item’s I’ll take a look into as well.
Warning: Invalid argument supplied for foreach() in /var/www/fog/lib/pages/GroupManagementPage.class.php on line 239
Fatal error: Call to a member function get() on a non-object in /var/www/fog/lib/pages/GroupManagementPage.class.php on line 252 -
as further info, I’m also getting the same 2 error messages when trying to just about anything to a newly created (empty) group, on r1249.
PHP Warning: Invalid argument supplied for foreach() in /var/www/fog/lib/pages/GroupManagementPage.class.php on line 239, referer: [url]http://localhost/fog/management/index.php?node=group&sub=delete&groupid=1[/url]
PHP Fatal error: Call to a member function get() on a non-object in /var/www/fog/lib/pages/GroupManagementPage.class.php on line 252, referer: [url]http://localhost/fog/management/index.php?node=group&sub=delete&groupid=1[/url]Rgds
-
[quote=“Tom Elliott, post: 23476, member: 7271”]
7.) What do you mean one deployed right away, while the other just sat there? You mean you setup two systems to deploy a single snapin and one deployed right away, while the other just sat there? Was the one that deployed “right away” logged in and the other no user logged in?
[/quote]I see what you are saying about a user being logged in. And yes two separate computers, same plugin, one deployed right away the other didn’t. I believe that there was a user logged in at the time that I tried to deploy the snapin. There was at the beginning of my testing. When I check the log on the computer itself it shows that a user was logged on when I initially set it up. That user logged out about 20 min after that then another user logged in for about a hour.
-
Fixed the deploy issue where it was overwriting another set tasking.
-
Fixed the group, it never had the associations. Haven’t fixed it to find the matching associations on the hosts, but working on it.
-
r1254 should fix many of the issues reported.
Specifically:
3, 6 and the error thrown. it’s based on Location. I forgot to add checking if the plugin was enabled or not. If it is, it actually matches the location if all hosts in the group match. -
Items 1 and 2 weren’t necessarily an issue, just an oversight that’s relatively simple to fix.
Haven’t fixed #4 yet is it’s more complex logic, so I just added all snapins in the system. If they aren’t associated with the host, they won’t deploy to the host.
Item number 5 is more of an issue due to the login, nothing that I can fix right now. Item number 7 once again just the same as item number 5.
Haven’t worked on 8 yet, will work now.
-
r1255 released.
Fixes item #8, please let me know if there’s any more issues. Thank you for the detailed report.
-
r1256 released.
Fixes an issue in the TaskManagementPage.class.php where The taskType wasn’t returning properly.
Fixes the Wakeup icon to show up properly. Still needs edit’s though.
-
r1257 released.
Fixes the TaskManagementPage scheduled tasks stuff. Can delete scheduled tasks now, and they display more appropriate.
-
Tom, have updated to 1257 and now I am unable to deploy or register new hosts
-
Can you provide error logs by chance?
I just tested registration and deployment and all works well on my end.
-
client screen says, during host reg: Fatal: INT18: BOOT FAILURE
and deploy says unable to find fog/kernel/bzimage
-
I will uninstall fog and I will reinstall
-
AHHH NO
-
Change the fog settings
It can’t find service/ipxe/fog/kernel/bzImage
-
You have to change the kernel, memtest, and bzimage in the fog settings to only point to memtest, init.gz, memtest, not fog/memtest/memtest, fog/images/init.gz, fog/kernel/bzImage
-
This post is deleted! -
all sorted
-
I was doing some more testing on snapins this AM and noticed a few things.
I am still having an issue with group deploy of all snapins. It states Snapins Are already deployed to this host. If I deploy the snapin another way successfully then try it again it creates the task.
I tried to do a quick deploy of snapins to a group and it didn’t create the snapin task. The single snapin didn’t have an option to select which one.
A quick deploy of all snapins for a host worked fine, but the quick deploy of single snapin did all snapins.
I tried group single deploy and it had the drop down which successfully worked.
I cancelled single deploy and all deploy active task for both host and group deploy which also removed the snapin task. It wasn’t working before. Also was able to cancel a single snapin from a deploy all snapins with out issue.
