Re: [Users] Problem Creating "oVirt Engine" - Stuck on FQDN

Finally got oVirtEngine to install, albeit, "not resetting the HTTPd from its original port to the usual port 80 and/or 443"" (or so I think is the way the "engine-setup" installation process resets the HTTPd) since every time I did agrees to use the "engine-setup" defaults regarding the HTTPd I got an error during the installation. Could it be that I have to "kill" the HTTPd process before running the "engine-setup"…? Anyway, after bypassing any modification by "engine-setup" of the HTTPd parameters, the process was smooth and ended up with the following: **** Installation completed successfully ****** (Please allow oVirt Engine a few moments to start up.....) **** To access oVirt Engine browse to http://ovirt.ct-radiology.local:8700 **** Additional information: * There are less than 4096 MBs of available free memory on this machine. It is recommended to have at least 4096 MBs of available memory to run the oVirt Engine. * oVirt Engine CA SSL Certificate SHA1 fingerprint: 8B:89:5B:07:B6:20:91:4F:2C:48:DF:45:E0:AB:19:F0:C6:2D:4E:0E * SSH Public key fingerprint: 27:0b:5f:b3:8d:65:5b:df:b1:4c:f0:22:3e:d7:aa:e5 * A default ISO share has been created on this host. If IP based access restrictions are required, please edit /var/lib/exports/iso entry in /etc/exports * oVirt Engine requires the following TCP/IP Incoming ports to be opened on the firewall: 22, 8700, 8701 * an example of the required configuration for iptables can be found at: /etc/ovirt-engine/iptables.example * In order to configure firewalld, please execute the following command: firewall-cmd --add-service ovirt * The installation log file is available at: /var/log/ovirt-engine/engine-setup_2013_07_19_18_04_56.log * Please use the user "admin" and password specified in order to login into oVirt Engine * To configure additional users, first configure authentication domains using the 'engine-manage-domains' utility Voilá…. Then came the real test, in the same virtual machine I'm creating to host oVirt Engine, I opened Firefox and copied the URL given by the "Successful Installation message above; that is "http://ovirt.ct-radiology.local:8700" Here I was ecstatic when FireFox showed the initial oVirt screen as shown below; *NOW the NEW PROBLEM I'm inquiring hereafter. After pressing the "User Portal", "Administrator Portal" and "Reports Portal" link, I get the following, respectively;* Hmmm. Why show me the initial page (which uses por 8700) and not the following (which appear to use por 8701)…? Could I need to change something in the firewall…? Is the Apache and/or JBoss services running…? Any suggestions…? Thanks in advanced; RIchie *José E ("Richie") Piovanetti, MD, MS* M: 787-615-4884 | richiepiovanetti(a)healthcareinfopartners.com <mailto:richiepiovanetti@healthcareinfopartners.com> On Jun 9, 2013, at 12:42 PM, Richie@HIP <richiepiovanetti(a)healthcareinfopartners.com <mailto:richiepiovanetti@healthcareinfopartners.com>> wrote: > Thanks to Ryan and Sandro. > > Did the addition to the host file (with variations for the IP range > i'm using and domains), and SELinux Config, and it worked; the oVirt > Engine "create" process ran its course, with one exemption. :-( > > The first time I selected ALL the defaults proposed by "create", > including the one related to changing the HTTPd port from where it was > (in port 1000 or so) to the usual ports ("80" for HTTP and "443" for > HTTPS) and that created an "Error" in the last step of the "create" > process. No worried, I reverted to a prior "snapshot" (since I'm > doing this in a Virtual Machine, and the second time did NOT change > the HTTPd ports as suggested (by typing "no" in that step) and the > "create" routine ran completely, finishing with the URL I should use > to access the oVirtEngine GUI with the browser. > > Thanks to all - thus far… ;-) > > Richie > * > José E ("Richie") Piovanetti, MD, MS* > M: 787-615-4884 | richiepiovanetti(a)healthcareinfopartners.com > <mailto:richiepiovanetti@healthcareinfopartners.com> > > > > > > > On Jun 5, 2013, at 3:09 PM, Ryan Wilkinson <ryanwilk(a)gmail.com > <mailto:ryanwilk@gmail.com>> wrote: > >> Edit your /etc/hosts file and add an entry for the hostname of your >> engine: >> 192.168.0.50 ovirt.domain.local >> >> Also, edit /etc/selinux/config and set >> selinux=permissive >> >> - you'll need to reboot for the selinux config. to take effect. >> >> >> On Wed, Jun 5, 2013 at 11:54 AM, Richie@HIP >> <richiepiovanetti(a)healthcareinfopartners.com >> <mailto:richiepiovanetti@healthcareinfopartners.com>> wrote: >> >> After sending you the previous email, I re-read your reply more >> carefully and another question arose. >> >> Does the FQDN have to resolve to the "oVirt Node" IP..? >> >> Right now, "localhost.localdomain" is resolving to "127.0.0.1" >> which is the host where I'm installing the "oVirt Engine". >> >> What IP is the oVirtEngine expecting…? The engine's own host, or >> the oVirt Nodes…? >> >> Richie >> >> José E ("Richie") Piovanetti, MD, MS >> M: 787-615-4884 <tel:787-615-4884> | >> richiepiovanetti(a)healthcareinfopartners.com >> <mailto:richiepiovanetti@healthcareinfopartners.com> >> >> >> >> >> >> >> On Jun 5, 2013, at 10:47 AM, Sandro Bonazzola >> <sbonazzo(a)redhat.com <mailto:sbonazzo@redhat.com>> wrote: >> >> > Il 05/06/2013 05:10, Richie@HIP ha scritto: >> >> >> >> I follow the prompts that appear after the "Welcome to oVirt >> Engine setup utility" is shown in the terminal window until I get >> to the prompt: >> >> >> >> Host fully qualified domain name. Note: this name should >> be fully resolvable [localhost.localdomain] : >> >> >> >> If I press "Enter", I get…: >> >> >> >> The IP (127.0.0.1) which was resolved from the FQDN >> localhost.localdomain is not configured on any non loopback >> interface on this host >> >> >> >> I figured that in order to define a FQDNm I had to expose my >> "oVirt Engine" VN to the Internet. Since I'm doing all from home >> (where I'm limited to a "Dynamic IP", albeit, which hardly-ever >> changes) I went to DynDns.org <http://dyndns.org/> and created an >> entry so my "FQDN Text-URL" would resolve to the IP where I'm at. >> I also modified my Domain's DNS and entered a "DNS Alias" named >> "dcmanagement", defining this "DNS alias" to resolve into my IP >> by going to DynDNS.org <http://dyndns.org/> to get my "Public >> IP". Hence, the alias "dcmanagement1" resolves by going to >> "healthcareinfopartners.dyndns.org >> <http://healthcareinfopartners.dyndns.org/>" and gets my Public IP. >> >> >> >> NOTE - To test this setup, I do "ping" to either >> "healthcareinfopartners.dyndns.org >> <http://healthcareinfopartners.dyndns.org/>" or >> "dcmanagement1.healthcareinfopartners.dyndns.org >> <http://dcmanagement1.healthcareinfopartners.dyndns.org/>" and I >> get my Dynamic Public IP back. Once the "Text URL" issue was >> returning my IP (as FQDN expect) I repeated the: >> >> >> >> sudo engine-setup >> >> >> >> Upon reaching: >> >> >> >> Host fully qualified domain name. Note: this name should >> be fully resolvable [localhost.localdomain] : >> >> >> >> I entered "dcmanagement1.healthcareinfopartners.com >> <http://dcmanagement1.healthcareinfopartners.com/>" and got my >> Public IP back with the following message: >> >> >> >> The IP (70.45.xxx.xx) which was resolved from the FQDN >> dcmanagement1.healthcareinfopartners.com >> <http://dcmanagement1.healthcareinfopartners.com/> is not >> configured on any non loopback interface on this host >> > >> > You have just to set /etc/hosts with the IP address of the network >> > device you're going to use for creating the bridge with the >> FQDN you're >> > going to use for the host. >> > No need to have a public IP, it could just be defined locally in >> > /etc/hosts or provided by a local DNS server. >> > The important thing is that FQDN resolves to an IP on a local >> network >> > device. >> > >> > >> > -- >> > Sandro Bonazzola >> > Better technology. Faster innovation. Powered by community >> collaboration. >> > See how it works at redhat.com <http://redhat.com/> >> > >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org <mailto:Users@ovirt.org> >> http://lists.ovirt.org/mailman/listinfo/users >> >> > _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users