@TBuzaTechnician You would need to run the mysqladmin command first, then do the command.
That should set your mysql password and ensure FOG will install using that now set password.
@Sebastian-Roth if I had to guess it’s lvm setup.
If you run
mysqladm --user root password "newpassword", you should not do it as a part of the installation script (eventually yes, but as of right now no.)
After you set the password, then you can run it with
snmysqlpass='newpassword' ./installfog.sh -y
Eventually, I know we want to create a separate user and password pair for mysql for security reasons, but in the mean time, the above should work.
You are safe to run the install in /opt/fogproject as needed.
When you created the new server, did you copy the original servers /opt/fog folder over to the new server?
@Quazz I don’t know that it’s a bug. Yes, i understand this is unexpected behaviour. But Remember the location plugin is a plugin. It’s not a default element of the core of fog. The Core elements attempt to ping all hosts each iteration. (So this is the expected behavior).
That’s not to say we shouldn’t have this in bug reports and we’ll need to add things to the location plugin to distribute the PING Hosts to enable location specific pinging.
This is not currently coded for or thought of so I imagine this will take a while to work out.
@AdamH From the sounds of things, the storage group item is not set on the image. The GUI tries to correct for this by applying the first storage group to the image, but if there is no actual value set, this message you see will still happen.
I’d suggest updating the image even though it shows as though it is set.
I commented out the “style” info you put, and moved it to push info out to the left instead of the right so that the form field is still accessible when reading the information.