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.
A feature in ovirt-node is neededto enable/disable firewall. This request is needed as ovirt-node will be adding libvirt-cim into the RHEV-H package list.
This bug is lacking a little specificity. It's supposed to be for specifically enabling/disabling the firewall port for the CIM server which is port 5989/tcp (wbem-https)
Changing $subject to be more accurate
For now let's just open the port in the default firewall rules.
We'll have discussion upstream about how to handle switching controlling management framework while keeping others usable in read-only mode and in the meantime RHEV-H 6.2 core image RHEV will be main management, libvirtcim optional in read-only mode.
(In reply to comment #5)
> For now let's just open the port in the default firewall rules.
>
> We'll have discussion upstream about how to handle switching controlling
> management framework while keeping others usable in read-only mode and in the
> meantime RHEV-H 6.2 core image RHEV will be main management, libvirtcim
> optional in read-only mode.
The port is open but is the service running by default?
(In reply to comment #7)
> No, the service is not currently running by default
I was mistaken, the service is currently configured to run by default. It doesn't run successfully currently, but it tries to (bug 727532)