Bug 134072 – validate-sat-cert honors http_proxy, not rhn.conf

Bug 134072 - validate-sat-cert honors http_proxy, not rhn.conf

Summary:	validate-sat-cert honors http_proxy, not rhn.conf

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Satellite 5
Classification:	Red Hat
Component:	Server (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Chip Turner
QA Contact:	Red Hat Satellite QA List
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-09-29 08:40 EDT by Matt Domsch
Modified:	2007-07-31 15:09 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-09-29 13:37:07 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Matt Domsch 2004-09-29 08:40:53 EDT

Description of problem:
As essentially a standalone program, validate-sat-cert uses the
http_proxy and https_proxy environment variables for its --send
option, where I would have expected it to use /etc/rhn/rhn.conf for my
authenticating proxy settings found there.  The use of http_proxy does
not allow it to use an authenticating proxy, which my environment
requires.


Version-Release number of selected component (if applicable):
rhn-satellite-admin-3.4.0-2

How reproducible:
always

Steps to Reproduce:
1. set http_proxy and https_proxy
2. validate-sat-cert --send fails
3.

Comment 1 Chip Turner 2004-09-29 13:37:07 EDT

--send is depracated in satellite 3.4 and isn't listed in the man
page.  instead you should update your sat cert in the hosted
environment and run 'satellite-sync' to pull the change down.  --send
was present in older releases and is honored as a depracated option
but shouldn't be used (for largely the issue you point up -- less than
robust handling of proxies)

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