Bug 725815

Summary: add vios-proxy to comps.xml
Product: Red Hat Enterprise Linux 6 Reporter: Dennis Gregorovic <dgregor>
Component: relengAssignee: Dennis Gregorovic <dgregor>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: high    
Version: 6.2CC: abeekhof, atodorov, borgan, ddumas, dgregor, dmach, matahari-maint, notting, syeghiay, tross
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 721119 Environment:
Last Closed: 2011-12-06 18:52:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 721119    
Bug Blocks:    

Description Dennis Gregorovic 2011-07-26 16:20:10 UTC 
vios-proxy is a new package in 6.2.  No other packages depend on it, so it will need to be added to comps.xml in order to be pulled into the compose.
Comment 2 Bill Nottingham 2011-07-26 16:29:15 UTC 
This also looks like it should be a dependency of a virtualization tool.
Comment 3 Perry Myers 2011-07-26 16:51:32 UTC 
@notting: It's not a strict dependency, that's the issue.

We need vios-proxy for using AMQP over virtio-serial between hosts and KVM guests.

But not all matahari usage will be on virt environments, so we can't put a Requires: vios-proxy on matahari packages.  

Any suggestions for how this should be handled?
Comment 4 Bill Nottingham 2011-07-26 17:15:28 UTC 
Wouldn't it then be a dependency of either libvirt, or the qemu tools?
Comment 5 Perry Myers 2011-07-26 17:23:27 UTC 
No, it's not
Comment 6 Bill Nottingham 2011-08-01 20:01:32 UTC 
OK, so looks like it would be added as an optional package in both the client-mgmt-tools  group, and the virtualization group.
Comment 7 Dennis Gregorovic 2011-08-01 20:29:50 UTC 
comps.xml updated
Comment 12 errata-xmlrpc 2011-12-06 18:52:04 UTC 
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/RHEA-2011-1743.html