Bug 747521

Summary: [vds_bootstrap] Firewall cannot be set on RHEL 5 host
Product: Red Hat Enterprise Linux 6 Reporter: Jakub Libosvar <jlibosva>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED WONTFIX QA Contact: Jakub Libosvar <jlibosva>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2CC: abaron, bazulay, iheim, ykaul
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
When adding a new host to RHEV-M 3.0, there is a new checkbox for setting iptables rules. Do not tick this checkbox if you are adding a RHEL-5 node to RHEV-M. If you do that, host installation would fail.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-20 15:01:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Bootstrap log none

Description Jakub Libosvar 2011-10-20 06:41:37 UTC 
Created attachment 529199 [details]
Bootstrap log

Description of problem:
When installing RHEL 5 to RHEV-M and checkbox for setting iptables rules, this installation fails with following error
Thu, 20 Oct 2011 08:30:07 DEBUG    <BSTRAP component='Firewall' status='FAIL' message='NamedTemporaryFile() got an unexpected keyword argument ~delete~'/>

Version-Release number of selected component (if applicable):
ic145.1

How reproducible:
Always

Steps to Reproduce:
1. Start installation of RHEL 5 host with checked 'Configure iptables rules' checkbox
  
Actual results:
Installation fails

Expected results:
Installation succeeds and iptables rules are set

Additional info:
Attaching log
Comment 2 Itamar Heim 2011-10-20 11:45:01 UTC 
to set expectations, we shoul dbe fine with an expected results are a warning back to rhev-m that "Cannot configure iptables on RHEL 6" or something like that.
so sounds like we should just know to not fail on this step for RHEL 5?
(or since rhel 5 isn't interseting enough, release note to not try to set iptables on it?)
Comment 3 Dan Kenigsberg 2011-10-20 15:01:50 UTC 
Doh! I always forget that we have to keep supporting RHEL-5 hosts. Luckily, the penalty this time is not too harsh, so I suggest release noting this fact.

I'll take it as another proof that late features such as bug 736114 are risky.
Comment 4 Dan Kenigsberg 2011-10-20 15:01:50 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When adding a new host to RHEV-M 3.0, there is a new checkbox for setting iptables rules. Do not tick this checkbox if you are adding a RHEL-5 node to RHEV-M. If you do that, host installation would fail.