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.
Description of problem:
Add a switch to libvirt-cim so that it connects to libvirt socket using the read-only socket (i.e. virConnectOpenReadOnly vs. virConnectOpen). In this read-only mode, all libvirt read-only APIs should function normally. If a CIM API is called that requires read-write socket access, a graceful error should be returned to the user connecting to libvirt-cim.
As part of this feature, we need to make sure we update the libvirt-cim test cases to test read-only mode.
libvirt-cim-0.5.13-1.el6 has been built in RHEL-6-candidate and should
provide the functionality. See /etc/libvirt-cim.conf configuration file
and edit it to have
readonly = true;
it should allow only read only operations through libvirt. All others
(i.e. modifying state) should raise an error at the CIM level.
Daniel
------- Comment From sglass.com 2011-11-08 15:49 EDT-------
---Problem Description---
reverse mirror of Red Hat 712257 on libvirt-cim
Contact Information = na
---uname output---
na
Machine Type = na
---Debugger---
A debugger is not configured
---System Management Component Data---
System management type: na
*Additional Instructions for na:
-Attach screen shoot of System Managment Utility
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1587.html