Bug 1384700

Summary:	Collect /etc/profile.d files during foreman-debug run
Product:	Red Hat Satellite	Reporter:	Mike McCune <mmccune>
Component:	Foreman Debug	Assignee:	Chris Roberts <chrobert>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.0	CC:	bbuckingham, chrobert, dlobatog, jcallaha, mmccune, zhunting
Target Milestone:	Unspecified	Keywords:	EasyFix, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/17950
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 16:49:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mike McCune 2016-10-13 22:40:22 UTC

There was a customer situation where they could not properly install Satellite 6 due to a proxy configuration defined in:

/etc/profile.d/proxy.sh

lets collect all the profile files in /etc/profile.d and ensure we have the proper diagnostic information to diagnose this.

Comment 1 Lukas Zapletal 2016-10-14 12:10:13 UTC

I verified this is not collected by sos, but I am afraid including this directory won't help much. I'd rather print all environment variables which are relevant. What ENV variables are we looking for? We can easily print all of them which are defined for a root shell.

Comment 3 Zach Huntington-Meath 2016-12-19 20:07:25 UTC

Created redmine issue http://projects.theforeman.org/issues/17772 from this bug

Comment 4 Chris Roberts 2017-01-05 22:54:34 UTC

Created redmine issue:

http://projects.theforeman.org/issues/17950

Comment 6 Daniel Lobato Garcia 2017-08-09 10:50:40 UTC

Verified 

Tested on:

satellite-6.3.0-16.0.beta.el7sat.noarch
foreman-debug-1.15.2-1.el7sat.noarch


All files matching:
   /etc/profile.d/**/*

were added to the debug tar.

Comment 7 Satellite Program 2018-02-21 16:49:54 UTC

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.

https://access.redhat.com/errata/RHSA-2018:0336