Upgrade to Trunk version

[kjohnson]

Hello,
I upgraded to the Trunk version and now I do not see any hosts or images that were created before the upgrade when I log into Fog.
I do see the images in the /images directory.
How do I go about getting the Trunk version to recognize that there are images in the Image directory?
The /image path is already in the Image Path Storage Management settings.

Ken

[Joe Schmitt]

What version are you on? (Look at the cloud in the upper left). Also, did you use git or svn?

[Wayne Workman]

What version were you on before?

[kjohnson]

Hello, here are the details:

In the cloud logo, it says 4406. There is a box below the login box and it says version 1.2.0.
I used the git method.
Installed on Ubuntu Trusty 14.04.
It was working before the upgrade.

[Joe Schmitt]

What version did you upgrade from?

[SKasai]

As the guys are asking, do you recall when you installed FOG prior to the upgrade to the Trunk version.

Another thing I know is… There is a warning message about ‘Did you back up your Database, as this will do a database schema change…’

Lastly, when you set up your FOG server the first time, did you set it up as the IP it is on? I know I had mine built on a different IP and moved it to another one, that the original config settings are saved and read by the installer so that might muck some things up.

[kjohnson]

Hello,
Actually I was running is version 1.2.0.
Then one day last week, my client image size said 0. I read somewhere in the forum where installing the Trunk version will fix it.
Before the 0 size error, I had been using for for the past year with no problems.

Ken

[Wayne Workman]

@kjohnson Did you complete the installation? There should have been a point where you needed to open the browser, update the DB schema, then go back to the installer and press [ENTER].

[SKasai]

@kjohnson Yea, I am also curious if you did the DB Schema update.

Do you recall when you went to the FOG Web UI and log into it, did it pester you about the fact that you need to do a DB Schema upgrade… And that you should make sure you back up your Database…

Cause from the sound of it, you might not have completed the upgrade and maybe the reason you are having some issues…

[kjohnson]

Hello,
No it did not prompt me to update the schema.
Do I need to run the install again to see if I get the prompt?

Ken

[SKasai]

@kjohnson said:

Hello,
No it did not prompt me to update the schema.
Do I need to run the install again to see if I get the prompt?

Ken

I think probably… Not sure. I think one of the devs will need to pipe in on this for sure, but might be the source of your issues with missing information.

[Wayne Workman]

@kjohnson

instead of the plain old ./installfog.sh

You can now tell fog to assume defaults, use all previous settings, and update the DB for you if you install using:

./installfog.sh -y

It’s called the “Auto Accept” argument.

[SKasai]

@Wayne-Workman Huh… Didn’t know that… I just saw the db update when you run the management console…

[Cire3]

You stated this …

Then one day last week, my client image size said 0. I read somewhere in the forum where installing the Trunk version will fix it.

So this issue was present before the upgrade ? Just trying to see if the problem is not the upgrade itself.

[Wayne Workman]

@SKasai said:

@Wayne-Workman Huh… Didn’t know that… I just saw the db update when you run the management console…

if that’s what you thought the upgrade process was, you likely never finished the installation… Can you try upgrading using the command I provided?

[SKasai]

@Wayne-Workman Not to worried about it now… I am pretty sure even on the 4425 trunk version, the web ui did prompt me to do this and I let it go. In some ways, it was good it did it this way as I inadvertantly revved the production server and had to back track.