@Wayne-Workman Yeah sorry I thought I had mentioned that earlier. They were fine.

@Tom-Elliott Thanks as always. You ever end up in Bloomington, IN I owe you a beer or twelve.

@Wayne-Workman That seemed to make it happy, thanks.

@Tom-Elliott I read your post earlier, then I went and dealt with some other crap for a few hours, came back to my desk and deleted the contents of the file and then tried again. I re-read your post after I got home and realized that I did something stupid. Deleted the file, pushed an image, and it completed successfully.

@Quazz I changed to the master branch, which is the 1.4.0 release, and we just installed it. @CBT is going to poke around it and he’ll get back with you.

@george1421 That file doesn’t exist.

@george1421 I work with @CBT and can help you out here.
I can’t get you exact versions, but I can give you commits from the git log:
We were on 1.3 RC-11 commit 2718a13d2bd11d4d9ccd4be7f2f005a67000da3e and not experiencing the issue. We were on this one for quite a while, and were at a point where we needed functionality, so we stopped pulling new changes from Github.
2-3 weeks ago I updated to the 1.4 RC, commit ae137758eba57b3c8cbbe316142a628020231045 and began experiencing the issue CBT mentioned.
Last Friday, at CBTs request, I pulled again, commit 56c296e9ae2af0e0ba34b12a04b0b8db0a2dc423, which did not resolve the issue.

@Wayne-Workman I’ve got 150 workstations to rename today and I need this fixed: https://forums.fogproject.org/topic/8558/reboot-host-on-hostname-changes-and-ad-changes-even-if-users-are-logged-in-button-not-saving

I was going to just make the change that Tom suggested but I can’t find what he wants us to change.

Edit: I’m on RC-11 now, issue seems to be resolved, or so I am being told by a guy on my team.

@Quazz I’d think if I pulled it down then I’d be able to install it.

Server

• FOG Version: 1.3 RC-10
• OS: Ubuntu 14.04

Client

• Service Version: N/A
• OS: N/A

Description

When running the installation script, it says I need to install/update the database schema, but when you open the FOG console it doesn’t prompt you to do anything. The banner at the top says I am still on RC-10. I also noticed that the top of the installation script says I am installing RC-10, but I assumed that was just something that was missed, as a “git pull” shows that I’m on “working-RC-11.”

Once I’m done, it still says

Running Version: 1.3.0-RC-10

  Your verson of FOG is up to date.

If it wasn’t for git telling me I’m on the current RC-11 I would think that I wasn’t. My only thought is that perhaps the sql update portion is failing for some reason, but I can’t find anything in the error log that would indicate why.

@Wayne-Workman +1 for lazy.

@Wayne-Workman That is good to hear! Thanks

Here’s a fun thought:
I approve all of these pending “new” hosts, now there they are, virgin entries in the database, with no Active Directory configuration. FOG suddenly finds all of these new hosts are joined to a domain, but shouldn’t be, and starts removing all of them from the domain.

@Wayne-Workman Sorry, I believe there is a misunderstanding here.

On July 19 I took a snapshot, and updated to RC1. After a few days of no noticeable problems, I deleted the snapshot. That is the snapshot I would have needed to revert to. The snapshot I took today was of a broken RC1, before I updated to RC8.

Also, while I found a backup of the code in /home, I see that I haven’t had a database backup since April, so that is sad. I’ll probably poke around in the database and see if I can figure something out, otherwise we’ll just start re-associating hosts with images and snapins.