Bug 608811
| Summary: | Provisioning Xen paravirt lacks virt bridge | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Community] Spacewalk | Reporter: | Matt Carey <cvstealth2000> | ||||||
| Component: | Installation | Assignee: | Justin Sherrill <jsherril> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Satellite QA List <satqe-list> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 1.0 | CC: | ianforde, jsherril | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-08-19 08:24:56 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: | |||||||||
| Bug Blocks: | 585232 | ||||||||
| Attachments: |
|
||||||||
Created attachment 427468 [details]
Xen guest cobbler modification to allow system to Kickstart
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. fixed in: 298542194ddb81730343307acae524f57b9bb6a5 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. Spacewalk 1.1 has been released. |
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: spacewalk-base-1.0.3-1.el5 spacewalk-oracle-1.0.1-1.el5 cobbler-2.0.3.1-3.el5 Xen host: rhn-virtualization-host-5.4.11-1.el5 rhn-virtualization-common-5.4.11-1.el5 spacewalk-koan-0.2.5-1.el5 koan-1.6.6-1 xen-3.0.3-94.el5 kernel-xen-2.6.18-164.el5 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.