Bug 758444 - client.conf incorrectly specifies /katello
Summary: client.conf incorrectly specifies /katello
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Subscription Asset Manager
Classification: Retired
Component: katello
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Tom McKay
QA Contact: SAM QE List
URL:
Whiteboard:
Depends On:
Blocks: 703617
TreeView+ depends on / blocked
 
Reported: 2011-11-29 20:10 UTC by Eric Sammons
Modified: 2012-04-27 00:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
katello-cli-headpin-0.1.12-1.el6.noarch
Last Closed: 2012-04-27 00:22:36 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 760189 0 high CLOSED headpin CLI fails with <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> 2021-02-22 00:41:40 UTC

Internal Links: 760189

Description Eric Sammons 2011-11-29 20:10:08 UTC
Description of problem:
/etc/headpin/client.conf when installed incorrectly has /katello as the value for path.  This should be changed to be /headpin to avoid user post installation action.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 6.2 
katello-cli-headpin-0.1.12-1.el6.noarch

Comment 1 Tom McKay 2011-12-05 17:19:55 UTC
commit 2703a1b8b1dcc977a2fd3da97a5652458b2b5a1b
Author: Tom McKay <thomasmckay>
Date:   Mon Dec 5 10:58:08 2011 -0500

    + Bug 760189 - headpin CLI fails with <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
      https://bugzilla.redhat.com/show_bug.cgi?id=760189
      Changed client.conf now references /headpin instead of /katello

Comment 2 Eric Sammons 2012-01-12 18:44:20 UTC
cat /etc/headpin/client.conf

[server]
host = localhost.localdomain
port = 443
scheme = https
path = /headpin

[interface]
grep_friendly = false

[shell]
nohistory = false
prompt = headpin>

VERIFIED:

# rpm -qf /etc/headpin/client.conf 
katello-cli-headpin-0.1.13-2.el6.noarch


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