Bug 947242

Created attachment 648822 [details]
2 of stage 2

Created attachment 648824 [details]
Yast 2 logs

I'm looking into this in conjunction with bug 947229.

(In reply to Scott Couston from comment #0)
> Installed from Yast>Software Management>Pattern Group XEN/KVM which installs
> without conflict and then using menu as in title creates Massive conflicts
> that solver tries to resolve with great difficulty rendering the whole of
> Virtualisation and useless

Can you provide some additional details here?  I just installed a new openSUSE 13.2 machine (with the update channels enabled during installation). After the machine was up, I installed the Xen and KVM patterns (using Software Management). As you indicated, there were no errors or conflicts. After that process finished, I used the "Install Hypervisor and Tools" module to reinstall and setup the tools. In my environment, I did not see any issues.

The problem could be due to the repos you have enabled. I'll look into that next.

Created attachment 648989 [details]
conflicts.txt

conflicts file provided in bug 947229.

(In reply to Scott Couston from comment #2)
> Created attachment 648824 [details]
> Yast 2 logs

After searching through these log files at length, I found the root of the problem. You have a custom installation repo defined as follows:

--------------------------------------
 - alias       : 13-2
 - name        : 13-2
 - enabled     : 1
 - autorefresh : 1
 - url         : dir:///space/common/operating_system
 - path        : /
 - type        : yast2
 - priority    : 10
 - gpgcheck    : D(Y) repoD(Y) sig? pkgD(Y)
 - keeppackages: 0

Assuming this is a copy of the installation media, the repo itself is not a problem. However, You have the priority of this repo set to 10 - which is a higher priority than the update channel. When the Xen and/or KVM patterns are installed, the virtualization components are installed from this source - which include libvirt version 1.2.9-1.3. This is much older than the 1.2.9-23.1 version included in the update repo.

The Xen and KVM patterns do not install the LXC components. However, the "Install Hypervisor and Tools" YaST Module will install the LXC components if that option is selected. When that option is used, the libvirt-daemon-lxc package is attempted to be installed. This package only contains a README file, but it was not included in the 13.2 media. The end result is that the tool attempts to install the 1.2.9-23.1 version of this package, but that requires 1.2.9-23.1 versions of all libvirt package. Due to the higher priority of the installation media, the version from the update channel cannot be installed.

Marking as resolved as the resolution to this issue is to ensure the priority of the original media is equal to or lower than the priority of the update channel.

Yes Mike, indeed I have a copy of the O/S DVD in a local directory with a higher priority that the http Source. I do this to cut down on installing a new package that can come from the DVD source rather than be downloaded.

The reason my fresh install of KDE and hypervision from the menu worked without issue is exactly that...I had not yet defined a local repo containing the DVD o/s.

We have both learned something valuable, however I would have thought that the dependency issue with this file should alert the user.

I'm not sure if the install of hypervision is able to check for a dependency issue

Can you enlighten me here please...bug closed as worksforme and accepted by reporter....placed on needinfo re the above dependency issue.

(In reply to Scott Couston from comment #8)
> Yes Mike, indeed I have a copy of the O/S DVD in a local directory with a
> higher priority that the http Source. I do this to cut down on installing a
> new package that can come from the DVD source rather than be downloaded.
> 
> The reason my fresh install of KDE and hypervision from the menu worked
> without issue is exactly that...I had not yet defined a local repo
> containing the DVD o/s.

Thanks for the confirmation!

> We have both learned something valuable, however I would have thought that
> the dependency issue with this file should alert the user.
> 
> I'm not sure if the install of hypervision is able to check for a dependency
> issue

The problem is really at the package level, but is partially related to libvirt-daemon-lxc and our installation module. This package is installed by the "Install Hypervisor and Tools" YaST module if the LXC component is selected. However, this package was not included on the openSUSE 13.2 media (which seems to be a mistake). When you attempted to install the LXC components, libvirt-daemon-lxc was pulled from the update channel - which was a newer version and conflicted with the higher priority packages from your original media.

I'll contact the release managers and make sure the libvirt-daemon-lxc package is included in the next versions of Tumbleweed and Leap 42.1. This will ensure the problem does not happen again.

This is an autogenerated message for OBS integration:
This bug (947242) was mentioned in
https://build.opensuse.org/request/show/339172 Leap:42.1 / patterns-openSUSE

Altered reason code appropriately 
Resolved in Leap 42.1