Created attachment 706215 [details]
log information

log engine-setup_2013_03_06_14_30_51.log

it is not necessary to enter the IP and HOSTNAME in / etc / hosts for my DNS Servers already do this job, did insertion.

[root@firelap ~]# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
172.16.255.43   firelap   firelap.usc.unirede.net


After entering this information in /etc/hosts, run it:

[root@firelap ~]# engine-cleanup

and after:

[root@firelap ~]# engine-setup

Returning the following error(attached new full log):

2013-03-06 17:35:15::ERROR::engine-setup::2369::root:: Traceback (most recent call last):
  File "/bin/engine-setup", line 2363, in <module>
    main(confFile)
  File "/bin/engine-setup", line 2146, in main
    runSequences()
  File "/bin/engine-setup", line 2068, in runSequences
    controller.runAllSequences()
  File "/usr/share/ovirt-engine/scripts/setup_controller.py", line 54, in runAllSequences
    sequence.run()
  File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line 154, in run
    step.run()
  File "/usr/share/ovirt-engine/scripts/setup_sequences.py", line 60, in run
    function()
  File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py", line 338, in addStorageDomain
    raise Exception(ERROR_ADD_LOCAL_DOMAIN)
Exception: Error: could not add local storage domain

Created attachment 706712 [details]
new log information

new log information from new action.

Hi Marcelo, can you reproduce the issue with ovirt-engine-3.2.1 ?
If you can reproduce the issue with the new version, can you verify you aren't getting any locale errors such as LANG and such not being found or set and that the locale is correctly set in /etc/locale.conf ?

hi sandro,

   thank you for feedback, i'm try instalation for ovirt-all-in-one, but not sucess. Reports(in attached logs):  

[root@firelap ~]# engine-setup 
Welcome to oVirt Engine setup utility
oVirt Engine uses httpd to proxy requests to the application server.
It looks like the httpd installed locally is being actively used.
The installer can override current configuration .
Alternatively you can use JBoss directly (on ports higher than 1024)
Do you wish to override current httpd configuration and restart the service? ['yes'| 'no']  [yes] : 
HTTP Port  [80] : 
HTTPS Port  [443] : 
Host fully qualified domain name. Note: this name should be fully resolvable  [firelap.local] : 
firelap.local did not resolve into an IP address
User input failed validation, do you still wish to use it? (yes|no): yes
Enter a password for an internal oVirt Engine administrator user (admin@internal) :
Warning: Weak Password.
Confirm password :
Organization Name for the Certificate  [local] : firelap
The engine can be configured to present the UI in three different application modes. virt [Manage virtualization only], gluster [Manage gluster storage only], and both [Manage virtualization as well as gluster storage] ['virt'| 'gluster'| 'both']  [both] : 
The default storage type you will be using  ['NFS'| 'FC'| 'ISCSI'| 'POSIXFS']  [NFS] : 
Enter DB type for installation ['remote'| 'local']  [local] : 
Enter a password for a local oVirt Engine DB admin user (engine) :
Warning: Weak Password.
Confirm password :
Local ISO domain path  [/var/lib/exports/iso] : /firebackup/ovirt/iso
Firewall ports need to be opened.
The installer can configure firewall automatically overriding the current configuration. The old configuration will be backed up.
Alternately you can configure the firewall later using an example file. 
Which firewall do you wish to configure? ['None'| 'Firewalld'| 'IPTables']: IPTables
Configure VDSM on this host? ['yes'| 'no']  [yes] : 
Local storage domain path  [/var/lib/images] : /firebackup/ovirt/vms
Confirm root password :

oVirt Engine will be installed using the following configuration:
=================================================================
override-httpd-config:         yes
http-port:                     80
https-port:                    443
host-fqdn:                     firelap.local
auth-pass:                     ********
org-name:                      firelap
application-mode:              both
default-dc-type:               NFS
db-remote-install:             local
db-local-pass:                 ********
nfs-mp:                        /firebackup/ovirt/iso
override-firewall:             IPTables
config-allinone:               yes
storage-path:                  /firebackup/ovirt/vms
superuser-pass:                ********
Proceed with the configuration listed above? (yes|no): yes

Installing:
AIO: Validating CPU Compatibility...                              [ DONE ]
AIO: Adding firewall rules...                                     [ DONE ]
Configuring oVirt Engine...                                       [ DONE ]
Configuring JVM...                                                [ DONE ]
Creating CA...                                                    [ DONE ]
Updating ovirt-engine service...                                  [ DONE ]
Setting Database Configuration...                                 [ DONE ]
Setting Database Security...                                      [ DONE ]
Creating Database...                                              [ DONE ]
Updating the Default Data Center Storage Type...                  [ DONE ]
Editing oVirt Engine Configuration...                             [ DONE ]
Editing Postgresql Configuration...                               [ DONE ]
Configuring the Default ISO Domain...                             [ DONE ]
Configuring Firewall...                                           [ DONE ]
Starting ovirt-engine Service...                                  [ DONE ]
Configuring HTTPD...                                              [ DONE ]
AIO: Creating storage directory...                                [ DONE ]
AIO: Adding Local Datacenter and cluster...                       [ DONE ]
AIO: Adding Local host (This may take several minutes)...         [ DONE ]
AIO: Adding Local storage (This may take several minutes)...   [ ERROR ]
Error: could not add local storage domain
Please check log file /var/log/ovirt-engine/engine-setup_2013_04_04_23_30_40.log for more information
[root@firelap ~]# 

   Other error(SELinux):

SELinux is preventing /usr/bin/lsblk from search access on the directory mount.

*****  Plugin catchall (100. confidence) suggests  ***************************

If you believe that lsblk should be allowed search access on the mount directory by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep lsblk /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:tuned_t:s0
Target Context                system_u:object_r:mount_var_run_t:s0
Target Objects                mount [ dir ]
Source                        lsblk
Source Path                   /usr/bin/lsblk
Port                          <Unknown>
Host                          firelap.local
Source RPM Packages           util-linux-2.22.2-6.fc18.x86_64
Target RPM Packages           
Policy RPM                    selinux-policy-3.11.1-86.fc18.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     firelap.local
Platform                      Linux firelap.local 3.8.5-201.fc18.x86_64 #1 SMP
                              Thu Mar 28 21:01:19 UTC 2013 x86_64 x86_64
Alert Count                   1
First Seen                    2013-04-04 23:37:20 BRT
Last Seen                     2013-04-04 23:37:20 BRT
Local ID                      3c8d7111-afee-4284-ae60-4bef107f86ee

Raw Audit Messages
type=AVC msg=audit(1365129440.394:586): avc:  denied  { search } for  pid=10758 comm="lsblk" name="mount" dev="tmpfs" ino=8296 scontext=system_u:system_r:tuned_t:s0 tcontext=system_u:object_r:mount_var_run_t:s0 tclass=dir


type=SYSCALL msg=audit(1365129440.394:586): arch=x86_64 syscall=open success=no exit=EACCES a0=394cc2ddd9 a1=0 a2=1b6 a3=238 items=0 ppid=10744 pid=10758 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=lsblk exe=/usr/bin/lsblk subj=system_u:system_r:tuned_t:s0 key=(null)

Hash: lsblk,tuned_t,mount_var_run_t,dir,search

audit2allow

#============= tuned_t ==============
allow tuned_t mount_var_run_t:dir search;

audit2allow -R

   My rpm's versions:

[root@firelap marcelo.barbosa]# rpm -qa | grep ovirt
ovirt-engine-webadmin-portal-3.2.1-1.fc18.noarch
ovirt-engine-restapi-3.2.1-1.fc18.noarch
ovirt-engine-tools-3.2.1-1.fc18.noarch
ovirt-iso-uploader-3.2.1-1.fc18.noarch
ovirt-host-deploy-java-1.0.1-1.fc18.noarch
ovirt-engine-backend-3.2.1-1.fc18.noarch
ovirt-engine-3.2.1-1.fc18.noarch
ovirt-log-collector-3.2.1-1.fc18.noarch
ovirt-engine-sdk-3.2.0.10-1.fc18.noarch
ovirt-engine-setup-3.2.1-1.fc18.noarch
ovirt-engine-genericapi-3.2.1-1.fc18.noarch
ovirt-host-deploy-1.0.1-1.fc18.noarch
ovirt-host-deploy-offline-1.0.1-1.fc18.noarch
ovirt-engine-dbscripts-3.2.1-1.fc18.noarch
ovirt-image-uploader-3.2.1-1.fc18.noarch
ovirt-engine-userportal-3.2.1-1.fc18.noarch
ovirt-engine-setup-plugin-allinone-3.2.1-1.fc18.noarch
ovirt-engine-cli-3.2.0.11-1.fc18.noarch
ovirt-release-fedora-5-3.1.noarch

Created attachment 731817 [details]
Log runing in 04/04/2013

(In reply to comment #5)

Hi Marcelo, thanks for the test.
 
> SELinux is preventing /usr/bin/lsblk from search access on the directory
> mount.
> 
> *****  Plugin catchall (100. confidence) suggests 
> ***************************
> 
> If you believe that lsblk should be allowed search access on the mount
> directory by default.
> Then you should report this as a bug.
> You can generate a local policy module to allow this access.
> Do
> allow this access for now by executing:
> # grep lsblk /var/log/audit/audit.log | audit2allow -M mypol
> # semodule -i mypol.pp
> 
> Additional Information:
> Source Context                system_u:system_r:tuned_t:s0
> Target Context                system_u:object_r:mount_var_run_t:s0
> Target Objects                mount [ dir ]
> Source                        lsblk
> Source Path                   /usr/bin/lsblk
> Port                          <Unknown>
> Host                          firelap.local
> Source RPM Packages           util-linux-2.22.2-6.fc18.x86_64
> Target RPM Packages           
> Policy RPM                    selinux-policy-3.11.1-86.fc18.noarch
> Selinux Enabled               True
> Policy Type                   targeted
> Enforcing Mode                Enforcing
> Host Name                     firelap.local
> Platform                      Linux firelap.local 3.8.5-201.fc18.x86_64 #1
> SMP
>                               Thu Mar 28 21:01:19 UTC 2013 x86_64 x86_64
> Alert Count                   1
> First Seen                    2013-04-04 23:37:20 BRT
> Last Seen                     2013-04-04 23:37:20 BRT
> Local ID                      3c8d7111-afee-4284-ae60-4bef107f86ee
> 
> Raw Audit Messages
> type=AVC msg=audit(1365129440.394:586): avc:  denied  { search } for 
> pid=10758 comm="lsblk" name="mount" dev="tmpfs" ino=8296
> scontext=system_u:system_r:tuned_t:s0
> tcontext=system_u:object_r:mount_var_run_t:s0 tclass=dir
> 
> 
> type=SYSCALL msg=audit(1365129440.394:586): arch=x86_64 syscall=open
> success=no exit=EACCES a0=394cc2ddd9 a1=0 a2=1b6 a3=238 items=0 ppid=10744
> pid=10758 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0
> fsgid=0 ses=4294967295 tty=(none) comm=lsblk exe=/usr/bin/lsblk
> subj=system_u:system_r:tuned_t:s0 key=(null)
> 
> Hash: lsblk,tuned_t,mount_var_run_t,dir,search
> 
> audit2allow
> 
> #============= tuned_t ==============
> allow tuned_t mount_var_run_t:dir search;
> 
> audit2allow -R


Can you open a separate bug about this selinux error?
While they're solving the selinux error, can you attach the log placed in /var/log/ovirt-engine/host-deploy/ for this engine-setup execution?

After that, can you configure selinux to run in permissive mode and try again running engine-setup?

(In reply to comment #5)

> Host fully qualified domain name. Note: this name should be fully resolvable
> [firelap.local] : 
> firelap.local did not resolve into an IP address
> User input failed validation, do you still wish to use it? (yes|no): yes

This could be the cause of the failure checking if the host is up. If the host can't be resolved it can't be contacted.
Can you attach /etc/hosts and the output of 'nslookup firelap.local' ?

hi Sandro,

    I realized new test with SELINUX is disabled, but error persist, I believe it is the same bug.
    Below my /etc/hosts 

[marcelo.barbosa@firelap /]$ cat /etc/hosts
127.0.0.1		localhost.localdomain localhost
::1		localhost6.localdomain6 localhost6
192.168.0.3	firelap.local	firelap

    Is there any other test I can do to help? more information? I am available.

Thank you.

Hi Marcelo, SELINUX disabled will lead to other known issues. Just leave it enabled in permissive mode.

192.168.0.3 is assigned to an interface that is up and working on the host?
Can you attach ifconfig output?

Hi,

I'm having the same problem with Fedora 18 and oVirt 3.2 allinone installation.

In my case the problem is that the host can not be deployed because the ovirtmgmt network can not be added, it claims that wlan0 is not an unknow nic:

2013-04-14 12:46:49 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.bridge plugin.execute:417 execute-output: ['/usr/share/vdsm/addNetwork', 'ovirtmgmt', '', '', u'wlan0', '
onboot=yes', 'bootproto=dhcp', 'blockingdhcp=true'] stderr:
Traceback (most recent call last):
  File "/usr/share/vdsm/configNetwork.py", line 1454, in <module>
    main()
  File "/usr/share/vdsm/configNetwork.py", line 1423, in main
    addNetwork(bridge, **kwargs)
  File "/usr/share/vdsm/configNetwork.py", line 886, in addNetwork
    bridged=bridged, **options)
  File "/usr/share/vdsm/configNetwork.py", line 834, in _addNetworkValidation
    raise ConfigNetworkError(ne.ERR_BAD_NIC, "unknown nic: %r" % nic)
ConfigNetworkError: (23, "unknown nic: 'wlan0'")

Wlan0 is up and running according to:
[root@ovirt ~]# ip a show wlan0
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 8c:70:5a:88:b4:04 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.37/24 brd 192.168.1.255 scope global wlan0

And that is the ip I used for the setup, and this is my /etc/hosts file:
127.0.0.1 localhost.localdomain localhost 
::1		localhost6.localdomain6 localhost6
192.168.1.37 ovirt.sombrerorojo.com ovirt

If you need any log file just ask.

Created attachment 735566 [details]
ovirt engine setup log

Created attachment 735567 [details]
ovirt host deploy log

Javier thanks for your report, but I think that is a different issue, maybe vdsm or otopi related. 

In Marcelo's case fqdn is not resolved to any local network device.

In your case fqdn is fully resolvable and reverse resolvable.
The address corresponding to your FQDN is resolved to the wireless NIC wlan0.

Please check in bugzilla if you can find a bug similar to the one you're experiencing and open a new bug on vdsm for your issue if you can't find one.

Marcelo, could you please try:
# engine-cleanup
# yum distro-sync
# engine-setup

I'm not able to reproduce the original problem at comment #0 where:
- the given FQDN is fully resolvable
- the ip address corresponding to FQDN is correctly configured on a local interface
- the setup failed because AIO received a response "Host was found in a 'Failed' state. Please check engine and bootstrap installation logs."

I'm not able to reproduce the new problem described at comment #5 where:
- the given FQDN is not fully resolvable but is in /etc/hosts
- the setup failed because of a selinux error

[root@ovirt ~]# engine-cleanup 
WARNING: Executing oVirt Engine cleanup utility.
This utility will wipe all existing data including configuration settings, certificates and database.
In addition, all existing DB connections will be closed.
Would you like to proceed? (yes|no): yes

Stopping ovirt-engine service...                        [ DONE ]
Removing Database...                                    [ DONE ]
Removing CA...                                          [ DONE ]
Stopping engine-notifierd service...                    [ DONE ]

Cleanup finished successfully!
Cleanup log available at /var/log/ovirt-engine/engine-cleanup_2013_04_19_14_40_07.log
DB Backup available at /var/lib/ovirt-engine/backups/tmpNV3jRj.sql

[root@ovirt ~]# engine-setup 
Welcome to oVirt Engine setup utility
oVirt Engine uses httpd to proxy requests to the application server.
It looks like the httpd installed locally is being actively used.
The installer can override current configuration .
Alternatively you can use JBoss directly (on ports higher than 1024)
Do you wish to override current httpd configuration and restart the service? ['yes'| 'no']  [yes] : 
HTTP Port  [80] : 
HTTPS Port  [443] : 
Host fully qualified domain name. Note: this name should be fully resolvable  [ovirt.localhost] : 
The IP (212.48.8.140) which was resolved from the FQDN ovirt.localhost is not configured on any interface on this host
User input failed validation, do you still wish to use it? (yes|no): yes
Enter a password for an internal oVirt Engine administrator user (admin@internal) :
Confirm password :
Organization Name for the Certificate  [localhost] : 
The engine can be configured to present the UI in three different application modes. virt [Manage virtualization only], gluster [Manage gluster storage only], and both [Manage virtualization as well as gluster storage] ['virt'| 'gluster'| 'both']  [both] : 
The default storage type you will be using  ['NFS'| 'FC'| 'ISCSI'| 'POSIXFS']  [NFS] : 
Enter DB type for installation ['remote'| 'local']  [local] : 
Enter a password for a local oVirt Engine DB admin user (engine) :
Confirm password :
Local ISO domain path  [/var/lib/exports/iso_2013_04_19_14_40_16] : 
Firewall ports need to be opened.
The installer can configure firewall automatically overriding the current configuration. The old configuration will be backed up.
Alternately you can configure the firewall later using an example file. 
Which firewall do you wish to configure? ['None'| 'Firewalld'| 'IPTables']: IPTables
Configure VDSM on this host? ['yes'| 'no']  [yes] : 
Local storage domain path  [/var/lib/images_2013_04_19_14_40_16] : 
Confirm root password :

oVirt Engine will be installed using the following configuration:
=================================================================
override-httpd-config:         yes
http-port:                     80
https-port:                    443
host-fqdn:                     ovirt.localhost
auth-pass:                     ********
org-name:                      localhost
application-mode:              both
default-dc-type:               NFS
db-remote-install:             local
db-local-pass:                 ********
nfs-mp:                        /var/lib/exports/iso_2013_04_19_14_40_16
override-firewall:             IPTables
config-allinone:               yes
storage-path:                  /var/lib/images_2013_04_19_14_40_16
superuser-pass:                ********
Proceed with the configuration listed above? (yes|no): yes

Installing:
AIO: Validating CPU Compatibility...                              [ DONE ]
AIO: Adding firewall rules...                                     [ DONE ]
Configuring oVirt Engine...                                       [ DONE ]
Configuring JVM...                                                [ DONE ]
Creating CA...                                                    [ DONE ]
Updating ovirt-engine service...                                  [ DONE ]
Setting Database Configuration...                                 [ DONE ]
Setting Database Security...                                      [ DONE ]
Creating Database...                                              [ DONE ]
Updating the Default Data Center Storage Type...                  [ DONE ]
Editing oVirt Engine Configuration...                             [ DONE ]
Editing Postgresql Configuration...                               [ DONE ]
Configuring the Default ISO Domain...                             [ DONE ]
Configuring Firewall...                                           [ DONE ]
Starting ovirt-engine Service...                                  [ DONE ]
Configuring HTTPD...                                              [ DONE ]
AIO: Creating storage directory...                                [ DONE ]
AIO: Adding Local Datacenter and cluster...                       [ DONE ]
AIO: Adding Local host (This may take several minutes)...         [ DONE ]
AIO: Adding Local storage (This may take several minutes)...      [ DONE ]

 **** Installation completed successfully ******

     (Please allow oVirt Engine a few moments to start up.....)

**** To access oVirt Engine browse to http://ovirt.localhost:80 ****

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: 84:30:0A:64:CC:D3:2E:7B:EA:96:18:9C:C5:5D:46:E8:1D:30:A1:CE
 * SSH Public key fingerprint: 21:86:40:b1:ac:92:cd:81:c8:b1:1d:79:6e:af:07:0d
 * A default ISO share has been created on this host.
   If IP based access restrictions are required, please edit /var/lib/exports/iso_2013_04_19_14_40_16 entry in /etc/exports
 * The firewall has been updated, the old iptables configuration file was saved to /var/lib/ovirt-engine/backups/iptables.backup.144239-04192013_12907
 * The installation log file is available at: /var/log/ovirt-engine/engine-setup_2013_04_19_14_40_16.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


# rpm -qa | grep ovirt
ovirt-engine-cli-3.2.0.11-1.fc18.noarch
ovirt-engine-userportal-3.2.1-1.fc18.noarch
ovirt-release-fedora-5-3.1.noarch
ovirt-engine-3.2.1-1.fc18.noarch
ovirt-log-collector-3.2.2-1.fc18.noarch
ovirt-engine-setup-plugin-allinone-3.2.1-1.fc18.noarch
ovirt-engine-sdk-3.2.0.10-1.fc18.noarch
ovirt-engine-webadmin-portal-3.2.1-1.fc18.noarch
ovirt-host-deploy-offline-1.0.1-1.fc18.noarch
ovirt-iso-uploader-3.2.2-1.fc18.noarch
ovirt-engine-genericapi-3.2.1-1.fc18.noarch
ovirt-image-uploader-3.2.2-1.fc18.noarch
ovirt-engine-tools-3.2.1-1.fc18.noarch
ovirt-host-deploy-1.0.1-1.fc18.noarch
ovirt-engine-backend-3.2.1-1.fc18.noarch
ovirt-engine-dbscripts-3.2.1-1.fc18.noarch
ovirt-engine-setup-3.2.1-1.fc18.noarch
ovirt-host-deploy-java-1.0.1-1.fc18.noarch
ovirt-engine-restapi-3.2.1-1.fc18.noarch

# rpm -qa |grep vdsm
vdsm-cli-4.10.3-10.fc18.noarch
vdsm-xmlrpc-4.10.3-10.fc18.noarch
vdsm-bootstrap-4.10.3-10.fc18.noarch
vdsm-python-4.10.3-10.fc18.x86_64
vdsm-4.10.3-10.fc18.x86_64

# getenforce 
Enforcing

# rpm -qa |grep selinux
libselinux-python-2.1.12-7.3.fc18.x86_64
selinux-policy-3.11.1-90.fc18.noarch
selinux-policy-doc-3.11.1-90.fc18.noarch
selinux-policy-devel-3.11.1-90.fc18.noarch
libselinux-2.1.12-7.3.fc18.x86_64
libselinux-utils-2.1.12-7.3.fc18.x86_64
selinux-policy-targeted-3.11.1-90.fc18.noarch

# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.3.203 ovirt.localhost ovirt.localhost.localdomain

# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master ovirtmgmt state UP qlen 1000
    link/ether 00:1a:4a:24:05:fb brd ff:ff:ff:ff:ff:ff
    inet6 fe80::21a:4aff:fe24:5fb/64 scope link 
       valid_lft forever preferred_lft forever
3: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN 
    link/ether 7a:f6:26:25:51:15 brd ff:ff:ff:ff:ff:ff
4: bond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
5: bond4: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
6: bond1: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
7: bond2: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
8: bond3: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
9: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP 
    link/ether 00:1a:4a:24:05:fb brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.203/24 brd 192.168.3.255 scope global ovirtmgmt
    inet6 fe80::21a:4aff:fe24:5fb/64 scope link 
       valid_lft forever preferred_lft forever

Sandro,

    Sorry delay in my feedback, much work for here.
    I tried again and go successful, after my steps: 

1) Install Fedora 18 in my host.
2) yum update -y (for my host)
3) set repo ovirt:

# yum localinstall http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm -y

4) install package all-in-one:

# yum install -y ovirt-engine-setup-plugin-allinone-3.2.1-1.fc18.noarch

see my versions:

ovirt-engine-tools-3.2.1-1.fc18.noarch
ovirt-release-fedora-6-1.noarch
ovirt-engine-setup-3.2.1-1.fc18.noarch
ovirt-host-deploy-offline-1.0.1-1.fc18.noarch
ovirt-engine-userportal-3.2.1-1.fc18.noarch
ovirt-image-uploader-3.2.2-1.fc18.noarch
ovirt-engine-webadmin-portal-3.2.1-1.fc18.noarch
ovirt-engine-cli-3.2.0.11-1.fc18.noarch
ovirt-engine-backend-3.2.1-1.fc18.noarch
ovirt-engine-setup-plugin-allinone-3.2.1-1.fc18.noarch
ovirt-host-deploy-java-1.0.1-1.fc18.noarch
ovirt-engine-genericapi-3.2.1-1.fc18.noarch
ovirt-iso-uploader-3.2.2-1.fc18.noarch
ovirt-engine-restapi-3.2.1-1.fc18.noarch
ovirt-engine-3.2.1-1.fc18.noarch
ovirt-host-deploy-1.0.1-1.fc18.noarch
ovirt-engine-dbscripts-3.2.1-1.fc18.noarch
ovirt-engine-sdk-3.2.0.10-1.fc18.noarch
ovirt-log-collector-3.2.2-1.fc18.noarch

5) run engine-setup

# engine-setup 
Welcome to oVirt Engine setup utility
oVirt Engine uses httpd to proxy requests to the application server.
It looks like the httpd installed locally is being actively used.
The installer can override current configuration .
Alternatively you can use JBoss directly (on ports higher than 1024)
Do you wish to override current httpd configuration and restart the service? ['yes'| 'no']  [yes] : 
HTTP Port  [80] : 
HTTPS Port  [443] : 
Host fully qualified domain name. Note: this name should be fully resolvable  [ovirt.local] : 
ovirt.local did not resolve into an IP address
User input failed validation, do you still wish to use it? (yes|no): yes
Enter a password for an internal oVirt Engine administrator user (admin@internal) :
Error: can't accept an empty answer for param
Enter a password for an internal oVirt Engine administrator user (admin@internal) :
Warning: Weak Password.
Confirm password :
Organization Name for the Certificate  [local] : ovirt
The engine can be configured to present the UI in three different application modes. virt [Manage virtualization only], gluster [Manage gluster storage only], and both [Manage virtualization as well as gluster storage] ['virt'| 'gluster'| 'both']  [both] : 
The default storage type you will be using  ['NFS'| 'FC'| 'ISCSI'| 'POSIXFS']  [NFS] : 
Enter DB type for installation ['remote'| 'local']  [local] : 
Enter a password for a local oVirt Engine DB admin user (engine) :
Warning: Weak Password.
Confirm password :
Local ISO domain path  [/var/lib/exports/iso] : /ovirt/iso
Firewall ports need to be opened.
The installer can configure firewall automatically overriding the current configuration. The old configuration will be backed up.
Alternately you can configure the firewall later using an example file. 
Which firewall do you wish to configure? ['None'| 'Firewalld'| 'IPTables']: IPTables
Configure VDSM on this host? ['yes'| 'no']  [yes] : yes
Local storage domain path  [/var/lib/images] : /ovirt/vms
Confirm root password :

oVirt Engine will be installed using the following configuration:
=================================================================
override-httpd-config:         yes
http-port:                     80
https-port:                    443
host-fqdn:                     ovirt.local
auth-pass:                     ********
org-name:                      ovirt
application-mode:              both
default-dc-type:               NFS
db-remote-install:             local
db-local-pass:                 ********
nfs-mp:                        /ovirt/iso
override-firewall:             IPTables
config-allinone:               yes
storage-path:                  /ovirt/vms
superuser-pass:                ********
Proceed with the configuration listed above? (yes|no): yes

Installing:
AIO: Validating CPU Compatibility...                              [ DONE ]
AIO: Adding firewall rules...                                     [ DONE ]
Configuring oVirt Engine...                                       [ DONE ]
Configuring JVM...                                                [ DONE ]
Creating CA...                                                    [ DONE ]
Updating ovirt-engine service...                                  [ DONE ]
Setting Database Configuration...                                 [ DONE ]
Setting Database Security...                                      [ DONE ]
Creating Database...                                              [ DONE ]
Updating the Default Data Center Storage Type...                  [ DONE ]
Editing oVirt Engine Configuration...                             [ DONE ]
Editing Postgresql Configuration...                               [ DONE ]
Configuring the Default ISO Domain...                             [ DONE ]
Configuring Firewall...                                           [ DONE ]
Starting ovirt-engine Service...                                  [ DONE ]
Configuring HTTPD...                                              [ DONE ]
AIO: Creating storage directory...                                [ DONE ]
AIO: Adding Local Datacenter and cluster...                       [ DONE ]
AIO: Adding Local host (This may take several minutes)...         [ DONE ]
AIO: Adding Local storage (This may take several minutes)...      [ DONE ]

 **** Installation completed successfully ******

     (Please allow oVirt Engine a few moments to start up.....)

**** To access oVirt Engine browse to http://ovirt.local:80 ****

Additional information:
 * oVirt Engine CA SSL Certificate SHA1 fingerprint: 7D:85:0D:62:88:52:14:C6:90:3D:70:C5:62:48:27:C5:42:EC:CF:7A
 * SSH Public key fingerprint: 80:71:aa:03:51:d4:71:d9:7b:cd:6e:d8:34:7a:c2:bb
 * A default ISO share has been created on this host.
   If IP based access restrictions are required, please edit /ovirt/iso entry in /etc/exports
 * The installation log file is available at: /var/log/ovirt-engine/engine-setup_2013_05_15_23_32_18.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


successful !!!

great work !!! thank you.

Marcelo Barbosa
Fedora Project Ambassador
firemanxbr

Sandro,

    I suggest for attached storage "iso" and "export" use this documentation:

http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues

    In my instalation some services is not activates:

# systemctl enable nfs-server.service
# systemctl enable nfs-lock.service
# systemctl start nfs-server.service
# systemctl start nfs-lock.service

    This documentation how-to create storages and more.

Marcelo Barbosa
Fedora Project Ambassador
firemanxbr

(In reply to comment #17)
> Sandro,
> 
>     I suggest for attached storage "iso" and "export" use this documentation:
> 
> http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues
> 
>     In my instalation some services is not activates:
> 
> # systemctl enable nfs-server.service
> # systemctl enable nfs-lock.service
> # systemctl start nfs-server.service
> # systemctl start nfs-lock.service
> 
>     This documentation how-to create storages and more.
> 
> Marcelo Barbosa
> Fedora Project Ambassador
> firemanxbr

can you open a separate bug for this issue? I'm closing this one.

Sandro,

   Okay, no problem, i go open newest suggestion, great work.

Regards.

Marcelo Barbosa
Fedora Project Ambassador
firemanxbr