Categories

  • 13k Topics
    115k Posts
    Tom ElliottT

    @Strahd At the least I’d suggest downloading an export of your hosts/images:

    From there you can delete the database or rebuidl from scratch by:

    mysql -u root If you have a password on your db I don’t know it but use the -p and you’ll be prompted to enter it.

    DROP DATABASE fog;

    Will delete everything.

    From there, I still highly recommend you delete the /opt/fog/.fogsettings

    Then rerun the installer.

    I’m still going to say use working-1.6 as the testbed.

    I hate that you’re having issues and I assure you I’m unable to replicate the problem you’re currently having which makes trying to fix your specific case impossible of course.

    Hope this helps.

    I’d still (at the least) get a full backup of your DB just in case something goes horribly wrong.

  • Get the latest news on what's happening.
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    2k Topics
    19k Posts
    Tom ElliottT

    @Valer For the Storage Group/Storage Node issue, fog doesn’t delete anything when installing.

    At most it may alter tables or swap data around but I don’t think that’s what happened here.

    I do see it showing 12 storage groups, I don’t see your screen for storage nodes. I’ll see if I can replicate the problem there. Confusing why it shows 12 to 1 of 1 entry? A little strange

    Refind needing being signed, makes sense. The Secureboot stuff we worked on was mostly concerned with the flow from IPXE -> Kernel, I didn’t think about the refind file. I’ll see if I can address that.

    Can you tell me what schema version you’re on?

    MariaDB [fog]> select * from schemaVersion; +-----+--------+ | vID | vValue | +-----+--------+ | 1 | 323 | +-----+--------+ 1 row in set (0.000 sec)

    Is what you should see. 323 is the latest which injects that new Task item, that said if your machine is in legacy boot, (non-uefi) you won’t be presented with the menu.

    If you can give me:

    SELECT vValue FROM schemaVersion; SELECT pxeID, pxeName FROM pxeMenu ORDER BY pxeID;
  • Report bugs, request features, or get the latest progress.
    2k Topics
    21k Posts
    L

    @Tom-Elliott Hi, Yes with the proposed fix, it works now.

96

Online

12.7k

Users

17.6k

Topics

156.9k

Posts