Bug 772796

Summary: Default kickstart snippet spacewalk/post_reactivation_key throws python error
Product: [Community] Spacewalk Reporter: Daniel Jabbour <drj>
Component: ServerAssignee: Jan Pazdziora (Red Hat) <jpazdziora>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.5CC: jpazdziora, slukasik
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-18 09:33:46 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: 765736    
Attachments:
Description Flags
Screen shot of error on console none

Description Daniel Jabbour 2012-01-10 00:55:49 UTC
Created attachment 551735 [details]
Screen shot of error on console

Description of problem:

During installation, on the terminal I noticed a python error. Upon investigation, I learned that the default spacewalk kickstart snippet spacewalk/post_reactivation_key uses python as an interpreter but indents the "try" block in error.

See attached screenshot for an example of the error output

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

Spacewalk 1.5. Uncertain if it persists in 1.6.

How reproducible:
Always.

Steps to Reproduce:
1. Create a kickstart profile using the wizard.

2. Deploy said profile and look at the console.

3. When it tries to grab an activation key from Spacewalk, it will throw python errors.
  
Actual results:

Python errors on console.

Expected results:

No python errors on console.

Additional info:

Comment 1 Jan Pazdziora (Red Hat) 2012-01-18 09:33:46 UTC
This was fixed in Spacewalk 1.6, via bug 730999.

*** This bug has been marked as a duplicate of bug 730999 ***