Bug 474475 - Operating System column blank in Errata Alert and Status Report emails
Operating System column blank in Errata Alert and Status Report emails
Status: CLOSED WORKSFORME
Product: Spacewalk
Classification: Community
Component: Server (Show other bugs)
0.3
All Linux
low Severity medium
: ---
: ---
Assigned To: Jeff Ortel
Red Hat Satellite QA List
:
Depends On:
Blocks: space04
  Show dependency treegraph
 
Reported: 2008-12-03 17:44 EST by Jeff Ortel
Modified: 2009-01-22 11:42 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-01-22 11:42:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jeff Ortel 2008-12-03 17:44:20 EST
Description of problem:
On Satellite v5.1.0 - In errata notifications sent out from Sat 5.1, the
'Operating System' field is not being populated for the affected systems. It
remains blank.

Sample email attached.

How reproducible:
Always

Steps to Reproduce:
When new errata are released execute satellite-sync -cChannelName.
Once sync is completed satellite would send our alert emails with details
regarding that errata.

Actual results:
>>
Under the errata email ::

Operating System is blank.

System                          Operating System
------------------------------- ---------------------------------------------
desktop.sample.com
lab1.test.com

Expected results:

>>
System                          Operating System
------------------------------- ---------------------------------------------
desktop.sample.com  < Respective Operating System >
lab1.test.com  < Respective Operating System >
Comment 1 Jeff Ortel 2008-12-03 17:47:55 EST
Fixed so email affected servers is listed as:

Release    Arch       Profile Name
---------- ---------- ---------------------------------------------
5Server    i686       lab0
5Server    i686       lab1
5Server    i686       lab3
5Server    i686       lab5
5Server    i686       lab7
5Server    i686       lab9

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