Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1519707 - current instructions for setting up a RHCERT system prevent operation via proxy
Summary: current instructions for setting up a RHCERT system prevent operation via proxy
Keywords:
Status: NEW
Alias: None
Product: Red Hat Certification Program
Classification: Red Hat
Component: redhat-certification
Version: 1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Greg Nichols
QA Contact: rhcert qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-01 09:07 UTC by Christian Horn
Modified: 2018-01-09 00:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3254901 None None None 2017-12-01 09:09:28 UTC

Description Christian Horn 2017-12-01 09:07:23 UTC
Description of problem:
current instructions for setting up a RHCERT system prevent operation via proxy
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_hardware_certification/1.0/html-single/test_suite_user_guide/#chap-prepare-test-environment
instructs to use a kickstart template, which directly installs the required packages.
When doing this, afterwards following
https://access.redhat.com/documentation/en-us/red_hat_openstack_certification_test_suite/11/html-single/red_hat_openstack_certification_workflow_guide/index#proxy-settings-for-test-server-and-test-client
to configure a proxy, the RHCERT interface can not be used for login.

Version-Release number of selected component (if applicable):
current

How reproducible:
always

Steps to Reproduce:
1. setup a squid proxy, i.e. on rhel7 "yum install squid; systemctl start squid"
2. install a system using this template:
   http://people.redhat.com/gcase/rhcert-2/ks/rhel7-x86_64-rhcert.ks
   (following above instructions)
3. # stop/start rhcert to get a rhcert.xml template
   rhcertd stop
   rhcertd start
4. # configure proxy as per our documentation
   echo 'http_proxy=192.168.4.45:3128' >>/etc/sysconfig/httpd
   echo 'https_proxy=192.168.4.45:3128' >>/etc/sysconfig/httpd
   mv /etc/rhcert.xml /etc/rhcert.xml.org
   head -22 /etc/rhcert.xml.org >/etc/rhcert.xml
   echo '    <proxy-url protocol="http">192.168.4.45:3128</proxy-url>' >>/etc/rhcert.xml
   echo '    <proxy-url protocol="https">192.168.4.45:3128</proxy-url>' >>/etc/rhcert.xml
   tail -6 /etc/rhcert.xml.org >>/etc/rhcert.xml
5. rhcertd start
6. access the ip of the rhcert system

Actual results:
Login not possible, connection refused etc.

Expected results:
Login should be possible

Additional info:
When removing 
  redhat-certification
  redhat-certification-hardware
  redhat-certification-backend 
from the kickstart template and installing them later (before step 3), then login is possible.  I have not looked deeper into this, maybe postscripts are doing strange things while not considering that they are in anaconda.

Comment 1 Christian Horn 2017-12-01 09:09:29 UTC
See also bz1515656 for documentation fixes.

Comment 3 Christian Horn 2018-01-09 00:35:04 UTC
I can not say for sure if bz1524444 is related, I did not understand enough about the rootcause of the issue here to judge that.  Both bz are dealing with proxy though.
If there is a test build which fixes bz1524444 , then one could replicate the issue here (steps ion #c0 ) and then verify if the issue still appears with the test build being used.


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