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:
Provided a error description about the api of getSecurityModel in libvirt-python. Actually, the getSecurityModel returns the security model of a hypervisor, not the securify model of the host.
Version-Release number of selected component (if applicable):
libvirt-1.2.8-16.el7_1.1.x86_64
libvirt-python-1.2.8-7.el7_1.1.x86_64
How reproducible:
100%
Steps:
1. In libvirt-python.
[root@localhost ~]# rpm -ql libvirt-python
/usr/lib64/python2.7/site-packages/libvirt.py
...
[root@localhost ~]# vim /usr/lib64/python2.7/site-packages/libvirt.py
...
def getSecurityModel(self):
"""Extract information about the host security model """
...
2. In libvirt-docs.
[root@localhost ~]# firefox /usr/share/doc/libvirt-docs-1.2.8/html/html/libvirt-libvirt.html
...
int virNodeGetSecurityModel (virConnectPtr conn,
virSecurityModelPtr secmodel)
Extract the security model of a hypervisor. The 'model' field in the @secmodel argument may be initialized to the empty string if the driver has not activated a security model.
...
Actual results :
As description.
Expected results :
Improve the description in libvirt-python.
Additional info:
[root@localhost ~]# vim /etc/libvirt/qemu.conf
...
# The default security driver is SELinux. If SELinux is disabled
# on the host, then the security driver will automatically disable
# itself. If you wish to disable QEMU SELinux security driver while
# leaving SELinux enabled for the host in general, then set this
# to 'none' instead.
...
commit 713ed9d570df92b3ba029b4cbb3cd7a4c45bf1de
Author: Ján Tomko <jtomko>
CommitDate: 2015-03-05 16:08:51 +0100
Clarify description for virNodeGetSecurityModel
s/host/hypervisor/ to match the wording used by the C binding.
https://bugzilla.redhat.com/show_bug.cgi?id=1198518
git describe: v1.2.13-1-g713ed9d
Verify it as follows. The result is expected. Move its status to VERIFIED.
# rpm -q libvirt-python
libvirt-python-1.2.15-1.el7.x86_64
# vim /usr/lib64/python2.7/site-packages/libvirt.py
3809 def getSecurityModel(self):
3810 """Extract information about the hypervisor security model """
3811 ret = libvirtmod.virNodeGetSecurityModel(self._o)
3812 if ret is None: raise libvirtError ('virNodeGetSecurityModel() failed', conn=self)
3813 return ret
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.
https://rhn.redhat.com/errata/RHBA-2015-2203.html
Description of problem: Provided a error description about the api of getSecurityModel in libvirt-python. Actually, the getSecurityModel returns the security model of a hypervisor, not the securify model of the host. Version-Release number of selected component (if applicable): libvirt-1.2.8-16.el7_1.1.x86_64 libvirt-python-1.2.8-7.el7_1.1.x86_64 How reproducible: 100% Steps: 1. In libvirt-python. [root@localhost ~]# rpm -ql libvirt-python /usr/lib64/python2.7/site-packages/libvirt.py ... [root@localhost ~]# vim /usr/lib64/python2.7/site-packages/libvirt.py ... def getSecurityModel(self): """Extract information about the host security model """ ... 2. In libvirt-docs. [root@localhost ~]# firefox /usr/share/doc/libvirt-docs-1.2.8/html/html/libvirt-libvirt.html ... int virNodeGetSecurityModel (virConnectPtr conn, virSecurityModelPtr secmodel) Extract the security model of a hypervisor. The 'model' field in the @secmodel argument may be initialized to the empty string if the driver has not activated a security model. ... Actual results : As description. Expected results : Improve the description in libvirt-python. Additional info: [root@localhost ~]# vim /etc/libvirt/qemu.conf ... # The default security driver is SELinux. If SELinux is disabled # on the host, then the security driver will automatically disable # itself. If you wish to disable QEMU SELinux security driver while # leaving SELinux enabled for the host in general, then set this # to 'none' instead. ...