Hey Will, that was surely a bad start and we know about the state of Node.
Please take a look at this email http://lists.ovirt.org/pipermail/node-devel/2014-January/000581.html to see where you can find a draft image which should address some bugs. - fabian Am Donnerstag, den 16.01.2014, 23:08 -0500 schrieb Will Dennis (Live.com): > In any case, I took one of their older servers which was already > running > CentOS 6.5, installed the requisite packages on it, and in short order > had > an engine server up and running (oVirt 3.3.2). That seems to have been > the > easy part :-/ Now came the installation of a hypervisor node. I > downloaded > and burned an ISO of the latest oVirt node installer > (ovirt-node-iso-3.0.3-1.1.vdsm.fc19.iso) and tried to install it on > one of > their target Intel servers. On the 1st try I got to the end of the > setup > TUI, invoked the Install link, and was promptly thrown an error > (sorry, but > forgot what it was, something like "press X for a command prompt, or > Reboot".) No problem, I rebooted, selected booting off the CD again, > waited > until the TUI came up, and when I tried to move past the first screen, > it > threw me out to a login prompt. OK, enough of that (the server takes a > long > time to reboot, and then boot off the CD) - I then thought I would try > it on > a VMware Workstation VM (yes, I get the irony, but VMware wkstn can > handle > nested virt, so it's a great testbed platform for OpenStack, etc.) > because > that would install a heck of a lot faster. That went a lot better - > got the > oVirt node 3.0.3 installed on the first try. > > More pain was soon to follow, however. I logged in and started > configuring > the node. The TUI was easy enough - much like an ESXi node ;) I set > the NIC > to IPv4 static, entered in the correct IP info, registered a DNS name > for > the IP I had assigned, and then tested pinging the engine, all was > good. I > then moved on to the section where you define the engine. I entered in > the > FQDN of the engine, verified the key fingerprint, and clicked the > "Save and > Register" link at the bottom. That seemed to work, so I completed the > rest > of the TUI, and then looked at the oVirt engine web UI. There was my > new > node, ready for authorization. I clicked the link to authorize it, and > after > a while, the UI came back with "Install Failed" status. Hmmm. So I > went back > to the node's TUI, and now some of the screens said that the IP addr > was > unconfigured? I went then to the Network screen, and sure enough, the > NIC at > the bottom showed "Unconfigured". WTF? So I went and entered in the > correct > info back in the IPv4 section, and then arrowed down to the Save link > and > clicked it - and the next screen said something like "No info needing > changes, nothing to do." Whaaaa? Went back to the network setup > screen, NIC > still showing "Unconfigured" even though the IPv4 info still was > there. I > did a ping test at this point from the Ping link on the network setup > page, > and what do you know - I could still ping IP's (the engine, the > default gw, > etc.) But as I moved around the TUI, other screens still said that the > network was unconfigured. Went back to the Web UI of the engine, put > the > host in Maint, then tried to Activate it, still no go - Install > Failed. Even > though I had configured the node to allow remote access and set a > password, > and also verified via nmap that TCP port 22 on the node was indeed > listening, when I tried to SSH into the node as admin, I immediately > got a > "connection closed" message, so that failed as well. Went back to the > node's > network setup page, set the IPv4 to "Disabled", saved it, then went > back and > set it back to "Static" then re-entered the IPv4 info. Clicked the > Save > link, it went thru the setup again, came back with a success, verified > with > ping etc. that networking was working on the node. The engine web UI > still > said that it could not connect to the node however. So I put the node > in > Maint, and then removed it. I went back to the node, went to the > Engine > setup page, and re-did the screen to define the engine on the node. I > notice > that after I did this, however, that the node screens went back to > saying > that the network was unconfigured. Grrrrrr. But the node was back in > the > engine's Web UI, however no joy this time either - "Install failed" > again. > Well, the hell with this, said I - I removed the node again from the > engine, > and went and installed Fedora 19 minimal install on the VM, so I could > use > the directions found in > http://www.ovirt.org/Quick_Start_Guide#Install_Fedora_Host and give > that a > try. (At least I can see what's going on with the node's OS using > F19.)
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
