Bug 985119 - Install fail with firewalld on Fedora 19
Install fail with firewalld on Fedora 19
Status: CLOSED NEXTRELEASE
Product: oVirt
Classification: Community
Component: ovirt-engine-installer (Show other bugs)
3.2
x86_64 Linux
urgent Severity urgent
: ---
: ---
Assigned To: Sandro Bonazzola
integration
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-16 16:46 EDT by Hetz Ben Hamo
Modified: 2013-07-19 02:04 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-07-19 02:04:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
engine-setup log (107.37 KB, text/plain)
2013-07-16 16:46 EDT, Hetz Ben Hamo
no flags Details

  None (edit)
Description Hetz Ben Hamo 2013-07-16 16:46:04 EDT
Created attachment 774481 [details]
engine-setup log

Description of problem:

Fresh install of Fedora 19, just tried to install oVirt 3.2. I run the engine-setup, I select Firewalld and when it's doing the setup, it aborts with the error "ValueError: need more than 1 value to unpack"

How reproducible:
Install Fedora 19, don't set any configuration manually, follow the instructions on the screen when running sudo engine-setup

Steps to Reproduce:
1. intall with yum as appears on ovirt.org
2. run sudo engine-setup
3. Select Firewalld

Actual results:
Getting error ValueError: need more than 1 value to unpack and it halts

Expected results:
To finish setup :)

Additional info:
Log attached
Comment 1 Sandro Bonazzola 2013-07-19 02:02:13 EDT
Hi Hetz, 3.2 is not ready for Fedora 19.
firewalld-cmd has changed it's output on Fedora 19 and 3.2 scripts are not able ro parse it.
Please try using 3.3.0 from nightly with engine-setup-2: it supports Fedora 19 firewalld.
Comment 2 Sandro Bonazzola 2013-07-19 02:04:53 EDT
Moving to closed next release: it is fixed for upcoming 3.3.0.

Note You need to log in before you can comment on or make changes to this bug.