Bug 514288 - Obsolete warning message appears on kickstart Session Status page when kickstarting to RHEL versions < 5
Summary: Obsolete warning message appears on kickstart Session Status page when kickst...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Provisioning
Version: 530
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Martin Korbel
URL:
Whiteboard:
Depends On:
Blocks: sat560-lowbug
TreeView+ depends on / blocked
 
Reported: 2009-07-28 17:41 UTC by Steve Salevan
Modified: 2013-10-01 21:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-01 21:54:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Steve Salevan 2009-07-28 17:41:13 UTC
Description of problem:
If a user attempts to kickstart to an older version of RHEL (< 5), they'll be presented with the following warning when they schedule it:

Warning:
System <client fqdn> is scheduled to be kickstarted to an older version of Red Hat Enterprise Linux, it will require the GPG key for the older release.
Please install this key, example: rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-former

This warning was valid on Satellites <= 520, as the auto-kickstart-* packages used to kickstart a machine to an older version of RHEL were indeed signed with the old key.  Since all >= 530 kickstarts use the koan rpm instead of the auto-kickstart-* packages, which will always be signed with the newest redhat-release key, this warning message is no longer valid.

Version-Release number of selected component (if applicable):
530, 7/24 Stage build

How reproducible:
Always

Steps to Reproduce:
1. Schedule a kickstart to RHEL < 5
2. View the Session Status page
  
Actual results:
Message as above

Expected results:
No warning message produced

Additional info:

Comment 1 Clifford Perry 2009-07-28 17:50:32 UTC
531 - or wait even to post 531 code

Comment 5 Tomas Lestach 2013-05-29 10:34:07 UTC
Removing the warning together with the localized string ...

spacewalk.git: bd92f3bdf04595984f4bb369caf77fd99e204b49

Comment 7 Martin Korbel 2013-09-30 09:51:15 UTC
VERIFIED on spacewalk-java-2.0.2-44.el6sat
REPRODUCED on spacewalk-java-1.2.39-133.el6sat
FIXED on spacewalk-java-1.10.87-1

I have not  a luck with reproduce this bug. I do not able to cause to show the warning. I have success provisioned RHEL4.



I have checked com/redhat/rhn/frontend/strings/java/StringResource_en_US.xml
spacewalk-java-2.0.2-44.el6sat:
<trans-unit id="kickstart.session.user_canceled">
        <source>Kickstart canceled by user: {0}</source>
        <context-group name="ctx">
          <context context-type="sourcefile">/rhn/kickstart/KickstartSessionCancel.do</context>
        </context-group>
      </trans-unit>
      <trans-unit id="kickstart.schedule.success">
        <source>System Kickstart scheduled for {0}</source>
        <context-group name="ctx">
          <context context-type="sourcefile">/rhn/kickstart/ScheduleKickstart.do</context>
        </context-group>
      </trans-unit>




spacewalk-java-1.2.39-133.el6sat:
<trans-unit id="kickstart.session.user_canceled">
        <source>Kickstart canceled by user: {0}</source>
        <context-group name="ctx">
          <context context-type="sourcefile">/rhn/kickstart/KickstartSessionCancel.do</context>
        </context-group>
      </trans-unit>
      <trans-unit id="kickstart.schedule.requires.older.gpgkey">
        <source>System {0} is scheduled to be kickstarted to an older version of Red Hat Enterprise Linux, it will require the GPG key for the older release.  &lt;br/&gt; Please install this key, example: &lt;strong&gt; rpm --import  /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-former &lt;/strong&gt; </source>
        <context-group name="ctx">
          <context context-type="sourcefile">/rhn/kickstart/ScheduleKickstart.do</context>
        </context-group>
      </trans-unit>

Comment 8 Clifford Perry 2013-10-01 21:54:25 UTC
Satellite 5.6 has been released. This bug was tracked under the release.  

This bug was either VERIFIED or RELEASE_PENDING (re-verified prior shortly
before release). 

Moving to CLOSED CURRENT_RELEASE. 

Text from Upgrade Erratum follows:

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-2013-1395.html


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