Bug 1306822 - --test-connection option shall not give connection failure message if the client is successfully registered to RHI service via sat 6.
--test-connection option shall not give connection failure message if the cli...
Status: CLOSED CURRENTRELEASE
Product: Red Hat Satellite 6
Classification: Red Hat
Component: rubygem-foreman-redhat_access (Show other bugs)
Unspecified
Unspecified Unspecified
unspecified Severity unspecified (vote)
: Unspecified
: --
Assigned To: Katello Bug Bin
Katello QA List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-11 14:24 EST by Anisha Narang
Modified: 2016-03-21 14:45 EDT (History)
1 user (show)

See Also:
Fixed In Version: tfm-rubygem-foreman-redhat_access-1.0.1-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-03-21 14:45:10 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Anisha Narang 2016-02-11 14:24:29 EST
Description of problem:
When a client is registered to RHI via sat6 and executes 'redhat-access-insights --test-connection', the result shows 'Connection failure' though the connection is established successfully.
If the system is registered successfully to the RHI service, there should be no connectivity errors listed.

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


How reproducible:


Steps to Reproduce:
1. Register a client machine(via sat6) to RHI service using 'redhat-access-insights --register'.
2. Make sure that the system appears on Sat6 dashboard > RHI> Systems.
3. From the client machine, execute "redhat-access-insights --test-connection'

Actual results:
$redhat-access-insights --test-connection
Successfully registered 59478992.lab.eng.rdu2.redhat.com

Starting to collect Insights data
Uploading Insights data, this may take a few minutes
Upload completed successfully!

2016-02-11 17:30:58 - robottelo.ssh - DEBUG - >>> [10.8.30.250] redhat-access-insights --test-connection
2016-02-11 17:30:58 - robottelo.ssh - INFO - Instantiated Paramiko client 0x38ae690
2016-02-11 17:30:59 - robottelo.ssh - INFO - Destroying Paramiko client 0x38ae690
2016-02-11 17:30:59 - robottelo.ssh - INFO - Destroyed Paramiko client 0x38ae690
2016-02-11 17:30:59 - robottelo.ssh - DEBUG - <<< stdout
Connection test config:
Proxy config: None
Certificate Verification: /etc/rhsm/ca/katello-server-ca.pem
=== Begin Certificate Chain Test ===
depth=1
verify error:num=0
verify return:1
depth=0
verify error:num=0
verify return:1
---
Certificate chain
0 s :/C=US/ST=North Carolina/O=Katello/OU=SomeOrgUnit/CN=sat6-rhai-ci.rhaitest.cee.redhat.com
  i :/C=US/ST=North Carolina/L=Raleigh/O=Katello/OU=SomeOrgUnit/CN=sat6-rhai-ci.rhaitest.cee.redhat.com
1 s :/C=US/ST=North Carolina/L=Raleigh/O=Katello/OU=SomeOrgUnit/CN=sat6-rhai-ci.rhaitest.cee.redhat.com
  i :/C=US/ST=North Carolina/L=Raleigh/O=Katello/OU=SomeOrgUnit/CN=sat6-rhai-ci.rhaitest.cee.redhat.com
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIFLjCCBBagAwIBAgIJAPXL3RmCF4OsMA0GCSqGSIb3DQEBBQUAMIGPMQswCQYD
VQQGEwJVUzEXMBUGA1UECBMOTm9ydGggQ2Fyb2xpbmExEDAOBgNVBAcTB1JhbGVp
Z2gxEDAOBgNVBAoTB0thdGVsbG8xFDASBgNVBAsTC1NvbWVPcmdVbml0MS0wKwYD
VQQDEyRzYXQ2LXJoYWktY2kucmhhaXRlc3QuY2VlLnJlZGhhdC5jb20wHhcNMTUx
MjEwMTQzNjA1WhcNMzUxMjEyMTQzNjA1WjB9MQswCQYDVQQGEwJVUzEXMBUGA1UE
CBMOTm9ydGggQ2Fyb2xpbmExEDAOBgNVBAoTB0thdGVsbG8xFDASBgNVBAsTC1Nv
bWVPcmdVbml0MS0wKwYDVQQDEyRzYXQ2LXJoYWktY2kucmhhaXRlc3QuY2VlLnJl
ZGhhdC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDWUta/PvdJ
f2ITNuRlmV6z3miYLyFfr2p4LCsM6EBkeEFEz/LY1yzoI7Fp0gbkpT5MsDxF8Dys
8MhTNI8nNV1KfC5B2K8tAr9l2UWbloApvDue6L+lNjie3zDqxZedvREZsKkNadZZ
alD/SHYDSRgCAzbBxPcj1GtncUyN/lrdi1NnkP+X6HnNAl5UXsb7Qx7zAed8nIBs
w9sPk2p2lKGVyCBzGLCj9aTqZ+wEEqD+qU0a7AR+Eijs9H7QnExwtihlMz609zzi
F59/Z7nx+/z41ei2HXNu9G8HbaLBGbwiDZZ/AVobkqmE+uX2iqWE7lN3z+TBfnvR
asThUNjFDeypAgMBAAGjggGcMIIBmDAJBgNVHRMEAjAAMAsGA1UdDwQEAwIFoDAd
BgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwEQYJYIZIAYb4QgEBBAQDAgZA
MDUGCWCGSAGG+EIBDQQoFiZLYXRlbGxvIFNTTCBUb29sIEdlbmVyYXRlZCBDZXJ0
aWZpY2F0ZTAdBgNVHQ4EFgQUH8LYGzVyu3FcGdTImXoYAF7RJmQwgcQGA1UdIwSB
vDCBuYAUCEtLMaMMtd7tK7VeE93SnVY/NsyhgZWkgZIwgY8xCzAJBgNVBAYTAlVT
MRcwFQYDVQQIEw5Ob3J0aCBDYXJvbGluYTEQMA4GA1UEBxMHUmFsZWlnaDEQMA4G
A1UEChMHS2F0ZWxsbzEUMBIGA1UECxMLU29tZU9yZ1VuaXQxLTArBgNVBAMTJHNh
dDYtcmhhaS1jaS5yaGFpdGVzdC5jZWUucmVkaGF0LmNvbYIJAPXL3RmCF4OnMC8G
A1UdEQQoMCaCJHNhdDYtcmhhaS1jaS5yaGFpdGVzdC5jZWUucmVkaGF0LmNvbTAN
BgkqhkiG9w0BAQUFAAOCAQEALiwedL6G+VsdeGk/X/W246m6SKEJNW+W+Uu0hoiy
E/gkARRJMDN/FRCizyizFHuJqnEiJPBafJI+NlSKKTiLlsHiZnrhMW38lhh6iFzP
O3j1ZxdujrHXaxjhPePTF/oswOaq5jOnfqxa5CXguDiM8ewSoHRP3cR8xIoKV7o0
xN+JYrB3cIkm/shmg4xLkw+FWbTdH8NTfuJGPu4OV2gTba8ek/fRSboX4+dO/G3C
ROk7nBzGh7e5xMaFkC1Vz+QVZa5286a9rEcbW7SUtdgezBCpF4Wb24rytlrIDIIl
LWQg8jZKSjl7cytrGzzARN4fxjEAl5fvk3Or52Hlk2FQCQ==
-----END CERTIFICATE-----

subject=/C=US/ST=North Carolina/O=Katello/OU=SomeOrgUnit/CN=sat6-rhai-ci.rhaitest.cee.redhat.com
issuer=/C=US/ST=North Carolina/L=Raleigh/O=Katello/OU=SomeOrgUnit/CN=sat6-rhai-ci.rhaitest.cee.redhat.com
---
=== End Certificate Chain Test: SUCCESS ===

=== Begin Upload URL Connection Test ===
Testing: https://sat6-rhai-ci.rhaitest.cee.redhat.com:443/redhat_access/r/insights/uploads/
HTTP Status Code: 400
HTTP Status Text: Bad Request
Connection failed
=== End Upload URL Connection Test: FAILURE ===

=== Begin API URL Connection Test ===
Testing: https://sat6-rhai-ci.rhaitest.cee.redhat.com:443/redhat_access/r/insights/
HTTP Status Code: 401
HTTP Status Text: Unauthorized
Connection failed
=== End API URL Connection Test: FAILURE ===


Connectivity tests completed with some errors

Expected results:
As the system was registered successfully to the RHI service, there should be no connectivity errors listed.

Additional info:
Comment 1 Keith Robertson 2016-03-21 14:45:10 EDT
Fixed in tfm-rubygem-foreman-redhat_access-1.0.1-1

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