I did eventually figure out the issue: I mis-understood the question about "cloud-init" as "engine-init", once I answered yes to cloud-init, I was allowed to set a root password and run engine-setup.

I am curious about some of your questions too, actually.

I was following the instructions from here:
http://www.ovirt.org/blog/2016/08/up-and-running-with-ovirt-4-0-and-gluster-storage/

In that, he said that in order to enable the gluster support in the engine, one has to do it manually.  It seemed odd, or perhaps a misunderstanding of the procedure.

My understanding was that after deploying my three hosts and gluster, I had to deploy the hosted-appliance manually on host 1 so that after the initial deploy, but before it was taken over by HA, I could go in and set the gluster service to on, then finish the setup with the reboot, etc.  

The other thing I was wondering about was setting up the additional hosts.  The instructions say to ssh to each host and deploy the engine there through the ssh command line.  The tool itself says that I shouldn't be doing it, I should be running through the website.  However, when I did that, I had a number of issues that I wasn't able to correct, and when I did it through ssh, I had the best functioning ovirt build yet.

One of the issues I had was when I tried to create a private network for gluster sync'ing, the web interface saw the gluster IPs for hosts 2 and 3 (although host 1 was added with its ovirt/real management IP, and the two networks were not routed).  The web itnerface host add ended up adding hosts 2 and 3 with the gluster IP, and thus things broke a lot.  I had no means of overriding those settings that I saw through the web interface.  When adding through SSH, I had a lot more control over adding the hosts, and was able to add them "correctly".

I suspect this means the overall procedure was in error, and I'd like to learn the "better" way to do it.

--Jim

On Mon, Jan 2, 2017 at 3:38 AM, Simone Tiraboschi <stirabos@redhat.com> wrote:


On Mon, Jan 2, 2017 at 9:39 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:


On Fri, Dec 30, 2016 at 7:31 PM, Jim Kusznir <jim@palousetech.com> wrote:
Hi all:

I'm trying to set up a new ovirt cluster.  I got it "mostly working" earlier, but wanted to change some physical networking stuff, and so I thought I'd blow away my machines and rebuild.  I followed the same recipe to build it all, but now I'm failing at a point that previously worked.

I've built a 3 node cluster with glusterfs backing (3 brick replica), and all that is good and well.  I run the engine-setup --deploy, and it does its stuff, asks me (among other things) the admin password, I type in the password I want it to use (just like last time), then it says to log into the new VM and run engine-setup.  Here's the problem: I try to ssh in as root, and it will NOT accept my password.  It worked a couple days ago, doing it the exact same way, but it will not work now.

Hi Jim,
sorry but why do you need to manually run engine-setup in the engine VM?
If you are deploying with the ovirt-engine-appliance, hosted-engine-setup will run it for you with the right parameters.
 
I've destroyed and re-deployed several times, I've even done a low level wipe of all three nodes and rebuild everything, and again, it doesn't work.

My only guess is that one of the packages the gdeploy script changed, and it has a bug or "new feature" that breaks this for some reason.  Unfortunately, I do not have the package versions that worked or the current list to compare to, so I cannot support this.

In any case, I'm completely stuck here...I can't log in to run engine-deploy, and I don't know enough of the console/low level stuff to try and hack my way into the VM (eg, to manually mount the disk image and replace the password or put my SSH key in).

Suggestions?  Can anyone else replicate this?

Can you please provide logs?

 

--Jim

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users




--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users