Just as an update, as I am not sure what the hitch here is.
In an attempt to quarantine the issue, these are the steps being used.
- Starting from a blank Ubuntu 14.04.5 Server LVM installation
- Skipping internal bootstrap
- Create /opt/fog directory
sudo apt-get install git
sudo git clone https://github.com/FOGProject/fogproject.git /opt/fog/dist
- Copy .fogsettings from configuration server
sudo ./installfog.sh -y
installfog.sh successfully completes - as denoted by the * Setup Complete prompt during FOG installation - I then try to access the fog database, using
mysql -u root -D fog. At this point, I am prompted the following, “ERROR 1049 (42000): Unknown database ‘fog’.”
I am unsure what is causing this, but it simply appears, to me, that commons/schema.php isn’t being applied. I have attempted a handful of things, as well as begun digging through the repository in an attempt to better understand this. Unfortunately, I have not figured out a manual way to install the database, nor a way to identify what may be occurring that would cause this.
Further, if there is another variable I can cut down on, please let me know. I am trying to replicate the issue with as few of our own variables mixed in as possible. At this stage, we have not bootstrapped the system, and have only installed the necessary package. I have also tried running
sudo apt-get update && apt-get upgrade -y --force-yes before proceeding as well, to no success. This is also using the git HEAD, so there should be no concern about our git mirror of the FOG Project intervening either.
No matter what I do with the latest RC, I cannot get the ‘fog’ database to install - outside of manually running the create+insert script myself.
Is there a way to manually install the database (read, not relying on foginstall.sh) just to validate that everything works. I suppose that’s moot, as I shouldn’t be in control of creating the schema anyway and the installer should always handle it. Just in this current state, I am curious if everything would work if I could install the database. If the -y switch is working as designed, I guess I am curious where this region of logic is handled so that I may further diagnose what the issue might be. My hope in manually doing it was that it would validate whether there was another issue at hand. That said, if there were another issue at hand, you would think the installer would fail.
I feel a little lost with this one, given that RC15 worked without a hitch, and that everything is “installed” successfully with RC21. Yet, when I go to query the ‘fog’ database, am told it doesn’t exist. Thus, indicating to me that some action wasn’t triggered/routed correctly, or that something error’d out and was silently handled.
I will be back on this tomorrow morning - I have to go vote for now.