Hide Forgot
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