Created attachment 675538 [details] logs Description of problem: engine-setup fails to setup http port when selinux is disabled. [root@vm-17-135 yum.repos.d]# engine-setup Welcome to oVirt Engine setup utility In order to proceed the installer must stop the ovirt-engine service Would you like to stop the ovirt-engine service? (yes|no): yes 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] : Error: failed adding port 80 to http_port_t because it is already preallocated in selinux. Please choose a different port. HTTP Port [80] : 8080 Error: failed adding port 8080 to http_port_t because it is already preallocated in selinux. Please choose a different port. HTTP Port [80] : 9999 Error: failed adding port 9999 to http_port_t because it is already preallocated in selinux. Please choose a different port. HTTP Port [80] : 5678 Error: failed adding port 5678 to http_port_t because it is already preallocated in selinux. Please choose a different port. Version-Release number of selected component (if applicable): ovirt-engine-3.2.0-1.20130109.gitd1d2442.fc18.noarch How reproducible: Always Steps to Reproduce: 1. Disable selinux and run setup. 2. 3. Actual results: Fails to setup ports Expected results: Need to print nice error message to a user - that selinux is disabled. Additional info:
I'd like to confirm that as today,with a clean install and the system fully updated, the problem remains.
I also get the same issue with ovirt 3.1 and selinux disabled.
patch uploaded for review: http://gerrit.ovirt.org/#/c/11345/
Patch merged to upstream: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=12a18b8abc8b2fb4572d13818649bf01e7065de9
Today I was able to reproduce the (I thought patched) bug with the most current software of Fedora 18 and Ovirt 3.2. Is there any other solution (workaround)?
(In reply to comment #11) > Today I was able to reproduce the (I thought patched) bug with the most > current software of Fedora 18 and Ovirt 3.2. > Is there any other solution (workaround)? Dennis - most recent as 'nightly', or 3.2 GA?
Sorry, I used 3.2 GA. I thought the patch is included, since it was finished before the 3.2 release.
as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this)
closing as this should be in 3.3 (doing so in bulk, so may be incorrect)