Bug 956261 - bootstrap client rpm name change
Summary: bootstrap client rpm name change
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Subscription Asset Manager
Classification: Retired
Component: Documentation
Version: 1.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Deon Ballard
QA Contact: Katello Bug Bin
URL:
Whiteboard:
Depends On: 956256
Blocks: sam20-tracker
TreeView+ depends on / blocked
 
Reported: 2013-04-24 14:29 UTC by Tom McKay
Modified: 2014-05-10 03:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 956256
Environment:
Last Closed: 2014-05-10 03:42:12 UTC
Embargoed:


Attachments (Terms of Use)

Description Tom McKay 2013-04-24 14:29:14 UTC
+++ This bug was initially created as a clone of Bug #956256 +++

All references to installing katello bootstrap cert rpm on client system need name changed.

From candlepin-cert-consumer-$fqdn-1.0-1.noarch.rpm
To   candlepin-cert-consumer.noarch.rpm

Comment 1 Tom McKay 2013-04-25 11:39:41 UTC
@Deon - I am assigning this to myself for the moment. There is discussion as to whether or not this is a good change or not. I will re-assign to you when confirmed. Thanks!

Comment 2 Tom McKay 2013-05-09 12:21:37 UTC
Branch: refs/heads/master
  Home:   https://github.com/Katello/katello-installer
  Commit: 9aebf59a65e02a3feaef798f926ba16b62bb9032
      https://github.com/Katello/katello-installer/commit/9aebf59a65e02a3feaef798f926ba16b62bb9032
  Author: Dmitri Dolguikh <dmitri>
  Date:   2013-05-03 (Fri, 03 May 2013)

For documentation:

Current candlepin cert rpm will remain unchanged. This means existing docs and customer usage is backward compatible.

An additional rpm, however, is now available that does not contain the server's hostname. This new rpm may be used in place of the previous.  The new name is:

candlepin-cert-consumer-latest.noarch.rpm

Comment 3 Deon Ballard 2014-05-10 03:42:12 UTC
Mass closure of bugs modified in 2013. All of these are in the currently-published docs.


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