Bug 608811 - Provisioning Xen paravirt lacks virt bridge
Summary: Provisioning Xen paravirt lacks virt bridge
Alias: None
Product: Spacewalk
Classification: Community
Component: Installation (Show other bugs)
(Show other bugs)
Version: 1.0
Hardware: All Linux
Target Milestone: ---
Assignee: Justin Sherrill
QA Contact: Red Hat Satellite QA List
Depends On:
Blocks: space11
TreeView+ depends on / blocked
Reported: 2010-06-28 17:38 UTC by Matt Carey
Modified: 2010-08-19 08:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-19 08:24:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Xen guest lacking vif (3.37 KB, text/plain)
2010-06-28 17:38 UTC, Matt Carey
no flags Details
Xen guest cobbler modification to allow system to Kickstart (2.63 KB, text/plain)
2010-06-28 17:39 UTC, Matt Carey
no flags Details

Description Matt Carey 2010-06-28 17:38:48 UTC
Created attachment 427467 [details]
Xen guest lacking vif

Description of problem: When trying to provision a Xen paravirt guest on a host it fails to create the virtual NIC interface with the guest. The Kickstart profile has the "Virtual Bridge" set to xenbr0, however that value is not getting pushed down to Cobbler when reporting the system profile leading to the Kickstart to fail due to lack of network communication to the Spacewalk server.

Version-Release number of selected component (if applicable):
Spacewalk host:

Xen host:

How reproducible:
This bug is reproducible with every attempt to provision a Xen paravirt guest.

Steps to Reproduce:
1. Create a Kickstart profile with the following attributes:  
  Virtualization Type = Xen Para-Virtualized Guest
  Virtual Bridge: xenbr0
2. In the Systems view in the WebUI select a host that is running Xen with Provisioning/Virtualization entitlements, then navigate to Virtualization->Provisioning
3. Enter a Guest Name and choose the option to Schedule Kickstart and Finish
Actual results:
The Xen configuration file under /etc/xen/<Guest Name> on the Xen host contains no line with vif = [ XXXXX ] when xenbr0 is specified in the Kickstart profile.

Expected results:
The Xen para-virt guest should have a virtual NIC in the configuration file when provisioning it through Spacewalk. 

Additional info:  Attached to the bug are the configurations when provisioning the guest and a quick hack to the Cobbler system profile to get the guest functional to be Kickstarted.

Comment 1 Matt Carey 2010-06-28 17:39:40 UTC
Created attachment 427468 [details]
Xen guest cobbler modification to allow system to Kickstart

Comment 2 Ian Forde 2010-07-02 22:17:44 UTC
FYI, as discussed on the spacewalk list, this also affects KVM provisioning from Spacewalk, so it's not just an issue seen when using Xen.  The workaround works for KVM provisioning too.

Comment 3 Justin Sherrill 2010-07-06 19:02:47 UTC
fixed in:

Cobbler apparently at some point broke api compatibility by making the modify-interface not work (instead modify_interface should be used).

Gonna see about backporting to 1.0.

Comment 4 Milan Zázrivec 2010-08-19 08:24:56 UTC
Spacewalk 1.1 has been released.

Note You need to log in before you can comment on or make changes to this bug.