Bugs in FOG 0.33

Tom Elliott

Alright, I’m not going to upload with the group attachment. The reason being that I can’t, for the life of me, figure out how it’s adding/modifying groups. I’ll look further and post when I’ve finally figured it out.

Tom Elliott

Alrighty then,

I finally got groups, sort of, working.

So it’s just like the old method for now where when you’re looking at the list of hosts, you can create your group and add systems to a group.

I can also add, under the group management icon, a link to create a new host directly from there. I haven’t, however (sorry guys) figured out how to add a host to a group from within the group management system. Though, if patient enough, I might be able to figure out a way to do so.

The Groups listing doesn’t display naturally. Simple fix, edit the css file. Open up:

{fogwebdir}/management/css/fog.css

Search for the line: action-box, there are 3 of them.

In the first line of action-box, there is a place that say’s, display: none

Set it to :

display: hidden

Then you’ll be good to go for creating and adding systems to groups the method we’re all used to.

I’ll update my fog package, but also post the changed file here as well. It’ll be a few for the tarball to be updated.

Inventory:

{fogwebdir}/management/css/fog.css
{fogwebdir}/lib/pages/GroupManagementPage.class.php

The GroupManagement part is fully working, but I wanted to give some semblance of operation in this. The membership options current work which didn’t even after I updated my fog.css file.

EDIT:
Tarball is up and running. I may need some help getting the Associative parts of Groups to work: e.g
Image
Snapins Add and Remove
Service Settings
AD
and Printers.

OS Association is there, but there really isn’t a need as we don’t need it for the hosts anymore. I’ll look into what else uses it and remove it as needed.

[url=“/_imported_xf_attachments/0/380_GroupManagementPage.class.php?:”]GroupManagementPage.class.php[/url][url=“/_imported_xf_attachments/0/381_fog.css?:”]fog.css[/url]

Tom Elliott

I’ve got a new kernel based on the core config for 3.10.7

I don’t have a lot of hardware to test on, so please test.

It can be downloaded from:

[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]
OR
wget --no-check-certificate [url]http://mastacontrola.com/fogboot/kernel/bzImage[/url]

Tom Elliott

I figured out the image association but I will not post the update until I work out the other sections a little bit. I think I’m getting to the point, that the only reason I have the includes folder is to reference these for the class building.

I hope you guys don’t mind the time as I am, as the true developers, working a full time job with all of this.

Tom Elliott

Ok,

For now I’ve removed the OS Association Field, and create new group menu from the submenu.include.php file, and for ease of use I moved submenu.include.php from:
{fogwebdir}/management/include/submenu.include.php
TO:
{fogwebdir}/commons/submenu.php

I’ll post this file and the updated:
{fogwebdir}/management/index.php

Also, I’ll post the GroupManagementPage.class.php file.

I’ll update my tarball as well with these changes so far.
Inventory of simple changes:

{fogwebdir}/management/index.php (just changed reference of submenu.include.php to submenu.php}
{fogwebdir}/commons/submenu.php (this file has OS Association removed from Group menu. Moved file from management/includes)
{fogwebdir}/lib/pages/GroupManagementPage.class.php (removed OS Association area, included parts for Image Association, and Removing hosts from membership field. Membership area, host names are links to edit host directly if needed.)

[url=“/_imported_xf_attachments/0/382_GroupManagementPage.class.php?:”]GroupManagementPage.class.php[/url][url=“/_imported_xf_attachments/0/383_submenu.php?:”]submenu.php[/url][url=“/_imported_xf_attachments/0/384_index.php?:”]index.php[/url]

falko

[quote=“Tom Elliott, post: 14297, member: 7271”]I’ve got a new kernel based on the core config for 3.10.7

I don’t have a lot of hardware to test on, so please test.

It can be downloaded from:

[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]
OR
wget --no-check-certificate [url]http://mastacontrola.com/fogboot/kernel/bzImage[/url][/quote]

I can test this monday, thanks

Tom Elliott

I was looking into the init.gz system, but I haven’t been able to figure which parts happen in which order. There’s kind of a lack of comments. So this will be one of the long winded projects, where I try to break the system to figure out exactly what’s happening and when. Hopefully we’ll see partclone working here shortly. I’m actually looking to figuring out how to build partclone into the initrd filesystem and maybe figure out how I can use it.

Tom Elliott

This weekend was rather busy for me, but I did take some time to try out a few things. It looks like the init.gz package from the 899 revision already contains the components for partclone. However, I can’t figure out how to get the /bin/fog script to actually use it. I tried editing the file, especially pertaining to Windows 7, and tried getting it to use part clone with the commands:

partclone.ntfs -c -s <hard drive/partition> -o <file to save as>

and

partclone.restore -s <filename> -o <hard drive/partition>

But i kept getting the typical invalid syntax response.

I am going to try, in debug mode, to mount the nfs share and commandline partclone to find out exactly what I need to do to get partclone working.

For right now, I’m just lost in the sauce trying to figure out how to get this to work. My hopes are that partclone will work better for the single disk, resizable than partimage currently does.

One question I have though, hopefully somebody can answer, is How come, during the deploy process for Single Disk, Resizable, there isn’t a method to recreating the first partition? The lines that I find are:

                                elif [ "$win7partcnt" == "2" ]; then 
                                    win7part2start=`parted -s $hd u kB print | sed -e '/^.2/!d' -e 's/^ [0-9]*[ ]*//' -e 's/kB  .*//'`; 
                                    if [ "$win7part2start" == "" ]; then 
                                        handleError "Unable to determine disk start location.";
                                    fi      

                                    adjustedfdsize=`expr $sizefd + $win7part2start`;
    
                                    parted -s $hd u kB rm 2 &>/dev/null;
                                    parted -s $hd u kB mkpart primary ntfs ${win7part2start}kB ${adjustedfdsize}kB  &>/dev/null;

Now I understand that the mbr, supposedly, gets rewritten after the imaging begins, but what I’m finding, is that the partitions aren’t deleted and their not recreated.

Also notice, there’s nothing stating which part is the boot partition either.

I guess I just don’t understand enough of the system, but it would seem to me that we would need somthing like:

                                elif [ "$win7partcnt" == "2" ]; then 
                                    win7part2start=`parted -s $hd u kB print | sed -e '/^.2/!d' -e 's/^ [0-9]*[ ]*//' -e 's/kB  .*//'`; 
                                    if [ "$win7part2start" == "" ]; then 
                                        handleError "Unable to determine disk start location.";
                                    fi      

                                    adjustedfdsize=`expr $sizefd + $win7part2start`;
                                     
                                    parted -s $hd u kB rm 1 &>/dev/null
                                    parted -s $hd u kB mkpart primary ntfs 2048s ${win7part1end}kB &>/dev/null;
                                    parted -s $hd set 1 boot on &>dev/null
                                    parted -s $hd u kB rm 2 &>/dev/null;
                                    parted -s $hd u kB mkpart primary ntfs ${win7part2start}kB ${adjustedfdsize}kB  &>/dev/null;

This would need to happen anytime the system is being written, but maybe not so much on the Multiple partitions as the MBR is directly written which should, theoretically, contain the partitioning of the hard drive so it can continue with no issues.

For Single Disk, resizeable, this doesn’t happen and the partitions, apparently, are removed, but not properly recreated. This causes an issue in that that rec.img.000 gets installed, but because ${hd}2 doesn’t exist, sys.img.000 can’t be written to the 2nd partition, so it just continues on like the deploy has completed.

Tom Elliott

While testing my custom init.gz, I found an issue in the Quick Image system. This, from what I can tell right now, affects all of the PXE options to perform the Quick Image (Full host registration, quick image, etc…) as the function it calls does not exist. I see a function called createImagePackage(…) but the function performed within the files is not relative and it’s not pointing to the class. I’m going to play a bit until I figure this part out, but until then, just wanted to post this issue.

Tom Elliott

I was able to correct for the issue with Quickimage, but it did require me to do two things.

First thing I had to do was edit
{fogwebdir}/service/hostlookupbymac.php
Here’s what I did/changed to this file:
From:
53 $tmp;
54 if( createImagePackage( $conn, $imageMember, “”, $tmp, false ) )
To:
53 $tmp;
54 $Host = new Host($hid);
55 if ( $Host->createImagePackage(1,“AutoRegTask”,true,true,true) )
56 //if( createImagePackage( $conn, $imageMember, “”, $tmp, false ) )
Then in file:
{fogwebdir}/lib/fog/Host.class.php
Go to and comment out Line 528.
Then all worked well. Including the Main GUI.
I don’t like commenting lines within a class that was, for the most part, working already, but I had to for quickimage as it’s trying to assign, for logging purposes I guess, the username to create the task. When it’s quick image, it doesn’t know who the user is so it spits out an error and will not create the task, the PXE File for the host will get created, but no database task gets created.
I’m guessing a similar change will need to be made in the Full Host registration script.

Tom Elliott

I made the required changes to auto.register.php to allow imaging and rather than posting all the individual files, I created the tarball that contains all my changes to the UI. Hopefully it works for everybody.

[url]https://mastacontrola.com/fog_0.33b.tar.bz2[/url]

There are still things in the UI that I’m aware of, but it’s a systematic process and I might be slow, but I will keep people posted.

EDIT: Reposted file, if you downloaded it already, please redownload and replace your auto.register.php file as I made added a class when it wasn’t needed. (SORRY GUYS)

Thanks,

Tom Elliott

Found an issue where imaging tasks aren’t being inserted into the imaging log. So there’s no record of what was imaged or when. I’m looking into what forces it to happen. It looks to be After completion when things get written to Post_Stage3.php, but I don’t know how to track that.

Techie_Wils

I’ll be honest I’m being lazy and haven’t read the whole thread so apologies if this has already being covered.

Some background, I’ve used Fog on a Ubuntu server since 0.27 and love it so thank you. I’ve being having issues uploading an image from a Windows x64 machine with a Samsung SSD 840 drive, but can deploy my original x32 Win 7 image to it. In my attempts to figure it out I upgraded my old 0.32 Fog setup to the 0.33 beta but am still having issues. Any help would be appreciated.

While trying to get this machine to upload I have found a few bugs so apologies if this has already being covered:
[LIST]
[]on the update kernel page when selecting a new kernel the following is displayed: FOG DEBUG: FOGPageManager: Class: FOGConfigurationPage, Method: kernel, Error: Method not found in class, defaulting to index()
[]When upgrading from 0.32 with a database full of clients, the images tab displays an error as you can now state the OS ID in the image and not the host (believe it has already being covered and I sorted that my self)
[]Just a note I had configured a proxy and port on 0.32, when upgrading it lost these setting. You can simple reinput them but its just something I noticed.
[]Again when upgrading, all my clients had the join active directory tick box ticked, after the upgrade this tick was removed. Again clicking the tick box solves this but just a note.
[]The disk usage graph is no longer working on the dashboard and says failed to connect to defaultmember, clicking this link displays this error: FOG DEBUG: FOGPageManager: Failed to Render Page: Node: hwinfo, Error: No FOGPage Class found for this node. You should try the old “includes” style management code [U][COLOR=#0066cc]found here[/COLOR][/U]
[]On an upgrade from 0.32 all my groups and their member ships have being deleted during the upgrade.
[/LIST]
If I find anything else I will gladly update the thread and test any new builds. If any could help with my problem at the top I’d be grateful.

Cheers

Tom Elliott

Download and install my version of fog.

[url]https://mastacontrola.com/fog_0.33b.tar.bz2[/url]

It has all the classes for the kernel update and many more.

Also, the Host Table does not contain the hostOS field anymore, so if you’re importing all your old, make sure the file doesn’t contain a reference to hostOS. It may even be a part of the fog 33 files, but I haven’t looked that far yet.

The graph does work, but you have to have a pointer to /images from what I can tell. Make sure storage management is properly setup as well. Also the link in my build for the server information works.

Sorry Edited for the correct link, missed the b after 33.

Techie_Wils

[quote=“Tom Elliott, post: 15535, member: 7271”]Download and install my version of fog.

[url]https://mastacontrola.com/fog_0.33b.tar.bz2[/url]

It has all the classes for the kernel update and many more.

Also, the Host Table does not contain the hostOS field anymore, so if you’re importing all your old, make sure the file doesn’t contain a reference to hostOS. It may even be a part of the fog 33 files, but I haven’t looked that far yet.

The graph does work, but you have to have a pointer to /images from what I can tell. Make sure storage management is properly setup as well. Also the link in my build for the server information works.

Sorry Edited for the correct link, missed the b after 33.[/quote]

Thanks for this I’ll definitely update my FOG. Found a few more bits, not sure if its already being brought up:
[LIST]
[]Cant make groups of hosts any more (no links in groups menu)
[]Host registration from the PXE boot menu does not work, it gets stuck in a loop of sending inventory
[*]when adding a host from the web interface, clicking the tick box for AD integration does not pull the information through and when you go back in to the host the information is not there. If you click the AD tick box here it does work. (hope that made sense)
[/LIST]
I’ll download your link now and see what’s what.

Thanks

-Edit-

I downloaded your version of fog and still have no luck imaging this drive, I checked and it is a advanced format 4k drive. It did fix the group issue though. Not had chance to check the rest of it yet.

Tom Elliott

To my knowledge, support for 4k drives is in the works, but not yet implemented. I’ll take a look at kernel configurations, but as I don’t have any 4k drives to test with, I’m afraid I’d just be shooting blind. Even if I can get the system to read the disk, I doubt I’d be able to implement, right away, enough changes quickly enough to actually support recreating the disk partitioning properly for deployment.

I’m not saying I won’t try, but I need to learn more about it.

Tom Elliott

[quote=“Bill Arlofski, post: 10849, member: 1799”]Hi everyone. THANK YOU FOR FOG! Seriously.

Now that I realized there is a 0.33beta avail for testing, I am jumping in head-first.

Hope this is the correct place to report bugs or bug-like issues. If not, please direct me to the correct place.

I just grabbed 0.33beta today like so:

svn co [url]https://freeghost.svn.sourceforge.net/svnroot/freeghost/trunk[/url] freeghost

And ran the install script.

When the web UI updater ran on first logon I got the following errors:
[ATTACH]248[/ATTACH]

As I went through the menus, I cam across the following related errors:
[ATTACH]249[/ATTACH]

And on a host’s page:
[ATTACH]250[/ATTACH]

Google was of no help, and I also found nothing similar when searching the forums here.

Any help fixing this? Would love to get to putting 0.33beta through

Thanks! And thanks again for FOG!

edit: I have nightly dumps of the db, so I can easily restore a 0.32 fog db and run any tests requested if necessary.[/quote]

While I’m sure you’ve by and gone figured this out by now,

The reason you were seeing the OS field issue on the Image management page is because of the change From 0.32 to 0.33,

The OS type field is now assigned to the Image rather than per each host as was in the past. You’re seeing the error’s because the OS field on your images hasn’t been set. To fix the error’s, all you need to do is click on the image and assign the proper OS for it.

Tom Elliott

All,

I was able to get printerAssoc to load from the group fields. However, that being said, the printer’s don’t load to the hosts. This is a bug I’m currently looking into. Hopefully I’ll be able to report back soon.

Tom Elliott

I figured out the problem and was able to tidy up my code to be way more inline with Blackout’s original. I’m still working on the default printer part, so when I figure that out I’ll push the updates, everything else, for now, is working.

Tom Elliott

I’m going to push updates for HostManagementPage, GroupManagementPage, PrinterManagementPage, SnapinManagementPage, and Host.class.php and Printer.class.php and fog.host.edit.js

Edited fog.host.edit.js to allow the checkbox for default printer function similar to radio button. I just think a checkbox is more appropriate as we’re choosing which printer is default.

Though the field is there, as a checkmark, the default value is not set yet.

Found the issue with adding a printer in Printer.class.php that affected Host.class.php in that Printer was requiring name, port, id, and model, which isn’t true when the printer is of network type, it only requires name and id, and if it’s iPrint, it only requires name, port, and id. This allows the addPrinter() function to work properly.

Also corrected the snapin and printer portions of Host.class.php to only insert one instance of a printer. You shouldn’t be able to put 4 of the same printer on a system, and now you can’t on the management system.

Will post in a few minutes.

EDIT: r914 is up (913 updated fine, but I had an unintentional edit on another file)

Bugs in FOG 0.33

246

11.6k

17.1k

154.6k