Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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
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?)
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.
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.
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