Bug 1258299
Summary: | Many cases fail when run libvirt-cim test with sblim-sfcb server | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Shanzhi Yu <shyu> |
Component: | libvirt-cim | Assignee: | John Ferlan <jferlan> |
Status: | CLOSED WONTFIX | QA Contact: | Jingjing Shao <jishao> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7.2 | CC: | dyuan, jferlan, jsuchane, mzhan, vcrhonek, xuzhang, yalzhang |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-03-25 13:27:19 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Shanzhi Yu
2015-08-31 02:41:32 UTC
As I pointed out in email: > > I don't have an sblim-sfcb config available. I think I've had other > problems with it in the past attempting to configure. I do have a faint > recollection that in there were changes in the tog-pegasus installation > with respect to where the provider was installed/advertised. Ah yes, see > the following upstream commit: > > http://libvirt.org/git/?p=libvirt-cim.git;a=commit;h=a8cfd7dc6a4f173c764f02688ff0c8aec00ecec2 > > Given the "age" of sblim-sfcb-1.3, it could be that there's some sort of > configuration issue with the older sblim-sfcb which hasn't kept up. > Since I saw "7_0" in the rpm name, it made me wonder exactly what that > meant... If I Google sblim-sfcb, I find references that indicate 1.3 is > in maintenance, but there is a 1.4. I have no idea what the differences > are since I don't keep "up to date" on CIM servers. The last time I > touched libvirt-cim code was over a year ago. But if I had to guess, > 1.3 doesn't use "root/interop". > > You could generate a libvirt bz, but it should be a low/zero priority, > and be on the RHEL-7.3 list. Although, I think the real solution is to > find whomever owns the sblim-sfcb package and find out why it hasn't > been updated. Certainly the pegasus-2.14 is beyond the 2.12-5 mentioned > in the commit message of my libvirt-cim change. FWIW, this was one of > the reasons I think I pushed for an update to libvirt-cim. > Move to consideration for 7.4 No sense dragging this out any longer. There's been no libvirt-cim activity and so just closing as WONTFIX. |