Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1339048 - Register to satellite failed in node ng through cockpit
Summary: Register to satellite failed in node ng through cockpit
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit
Version: 7.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: pre-dev-freeze
: 7.2
Assignee: Dominik Perpeet
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: ovirt-node-ng-platform
TreeView+ depends on / blocked
 
Reported: 2016-05-24 03:36 UTC by wanghui
Modified: 2016-09-06 08:31 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-25 04:05:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
sosreport (5.89 MB, application/x-xz)
2016-05-24 03:36 UTC, wanghui
no flags Details

Description wanghui 2016-05-24 03:36:40 UTC
Created attachment 1160872 [details]
sosreport

Description of problem:
Node ng can not register to satellite through cockpit.

Version-Release number of selected component (if applicable):
rhev-hypervisor7-ng-3.6-20160518.0
imgbased-0.6-0.1.el7ev.noarch
cockpit-0.103-1.el7.x86_64
cockpit-ovirt-dashboard-0.9.1-0.0.1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install node ng
2. Install the rpm from satellite to provide CA files.
3. In subscriptions page, file the satellite url in the customer url field. And alos file the username,passowrd.
4. Click register

Actual results:
1. It reports "Unable to reach the server at *****:443/subscription".

Expected results:
1. It should register to satellite succeed.

Additional info:

Comment 2 wanghui 2016-05-26 08:47:34 UTC
(In reply to Stef Walter from comment #1)
> Do you have a test system we can reproduce this bug against?

Hi Stef, 

Which one your need for testing, the node ng or satellite6 server?

Comment 4 wanghui 2016-05-31 04:09:01 UTC
(In reply to Stef Walter from comment #3)
> The satellite6 server would be needed. Thanks.

Hi Stef,

Due to our policy, I can only share you the env through the email. So I send you a email to share you the satellite6 server's info.

Thanks!
huiwa

Comment 7 Dominik Perpeet 2016-07-12 06:37:39 UTC
Other bugs cover activation key, proxy and org support. Also, we have upsteam CI coverage via candlepin starting 0.114.

It is now difficult to tell where this problem came from, or if it even came from Cockpit, and if there are no objections I'll close this bug.

Comment 8 Ying Cui 2016-07-12 06:42:39 UTC
Chen and Wei, could you help on comment 5?

Comment 9 Wei Wang 2016-07-12 09:39:35 UTC
Hi Stef,

After confirming with satellite team, you can try with port 80 for listening instead of port 443.

Comment 10 Wei Wang 2016-08-11 10:12:27 UTC
Test Version
redhat-virtualization-host-4.0-20160810.1.x86_64.liveimg.squashfs
imgbased-0.8.3-0.1.el7ev.noarch

Test steps:
1. Install RHVH with kickstart file in attachment.
2. Install the CA files
3. In node console shell, input the below command:
   #subscription-manager register --serverurl=<satellite server> --username=username --password=passwd
4.Check the result
  
Result:
"Unable to reach the server at satellite61.redhat.com:443/subscription" is displayed on the console.

QE can reproduce this bug with the latest RHVH version.

Comment 11 Fabian Deutsch 2016-08-11 10:36:26 UTC
There is still a chance that this is a bug on the Node side.

Douglas, can you reproduce this bgu with our latest RHVH 4 build?

Comment 12 Douglas Schilling Landgraf 2016-08-11 15:58:46 UTC
(In reply to weiwang from comment #10)
> Test Version
> redhat-virtualization-host-4.0-20160810.1.x86_64.liveimg.squashfs
> imgbased-0.8.3-0.1.el7ev.noarch
> 
> Test steps:
> 1. Install RHVH with kickstart file in attachment.
> 2. Install the CA files
> 3. In node console shell, input the below command:
>    #subscription-manager register --serverurl=<satellite server>
> --username=username --password=passwd
> 4.Check the result
>   
> Result:
> "Unable to reach the server at satellite61.redhat.com:443/subscription" is
> displayed on the console.
> 
> QE can reproduce this bug with the latest RHVH version.

Could you please share the satellite test env and CA files to install with me by email as well? 

Thanks!

Comment 13 Wei Wang 2016-08-12 01:59:08 UTC
(In reply to Douglas Schilling Landgraf from comment #12)
> (In reply to weiwang from comment #10)
> > Test Version
> > redhat-virtualization-host-4.0-20160810.1.x86_64.liveimg.squashfs
> > imgbased-0.8.3-0.1.el7ev.noarch
> > 
> > Test steps:
> > 1. Install RHVH with kickstart file in attachment.
> > 2. Install the CA files
> > 3. In node console shell, input the below command:
> >    #subscription-manager register --serverurl=<satellite server>
> > --username=username --password=passwd
> > 4.Check the result
> >   
> > Result:
> > "Unable to reach the server at satellite61.redhat.com:443/subscription" is
> > displayed on the console.
> > 
> > QE can reproduce this bug with the latest RHVH version.
> 
> Could you please share the satellite test env and CA files to install with
> me by email as well? 
> 
> Thanks!

Ok, no problem! The email has been sent to you, please check!

Comment 14 Dominik Perpeet 2016-08-17 14:17:00 UTC
Is there any progress?

I'm tempted to close this issue, as the case is covered by upstream Cockpit CI.

Being unable to reach a server hints at an underlying issue that isn't related to Cockpit.

Comment 15 Fabian Deutsch 2016-08-19 08:09:14 UTC
In the logs I see:

2016-05-23 03:26:11,256 [ERROR] rhsmcertd-worker:16736 @rhsmcertd-worker:47 - Either the consumer is not registered or the certificates are corrupted. Certificate update using daemon failed.

Could you please try to reproduce this issue on plain RHEL with the exact same steps you used on RHVH?

Comment 16 Wei Wang 2016-08-22 07:14:17 UTC
Test Version:
redhat-release-server-7.2-7.el7.x86_64
cockpit-0.114-2.el7.x86_64
cockpit-ws-0.114-2.el7.x86_64

Test Steps:
1. Install vm with RHEL-7.2-20151015.0-Server-x86_64-dvd1.iso
2. Install cockpit rpm
3. Enable cockpit services
4. Install the CA files
5.a). In node console shell, input the below command:
#subscription-manager register --serverurl=<satellite server> --username=username --password=passwd
6.a). Check the result
5.b-1). Login cockpit website hostIP:9090 with root account
  b-2). In subscriptions page, file the satellite url in the customer url field. And also file the username,passowrd, then click "register"
6.b). Check the display on node screen.

Result:
"Unable to reach the server at satellite61.redhat.com:443/subscription" is displayed on screen.

More info:
I also test with satellite 6.2 server, the result is the same.

Comment 17 Stef Walter 2016-08-22 07:20:58 UTC
Dominik is away. The problem is that I see this:

$ nslookup satellite61.redhat.com
Server:		10.38.5.26
Address:	10.38.5.26#53

** server can't find satellite61.redhat.com: NXDOMAIN

Is there a server against which we can reproduce this bug?

Comment 18 Douglas Schilling Landgraf 2016-08-22 19:33:54 UTC
I have tried to reproduce the report and got the same error from Stef in comment#17.

weiwang, do you have any advise? 

Thanks!

Comment 19 Wei Wang 2016-08-24 06:28:20 UTC
(In reply to Douglas Schilling Landgraf from comment #18)
> I have tried to reproduce the report and got the same error from Stef in
> comment#17.
> 
> weiwang, do you have any advise? 
> 
> Thanks!

We are doubt about the satellite server have some problem, RHEL7 and RHVH4.0 cannot register satellite 6.2 successful, so we now debug this. I will update the info later.

Comment 20 Wei Wang 2016-08-25 03:28:54 UTC
After retry and research this bug again, we can register to satellite from cockpit webUI and CLI successful.

The correct point is the server Url need to be <satellite hostname>/rhsm.

I have retest with satellite6.2+RHEL7.2 using cockpit webUI and CLI, the bug cannot be reproduced.

Comment 21 Stef Walter 2016-08-25 07:22:58 UTC
Dominik, should we add /rhsm automatically to a satellite URL without a path?

Comment 22 Dominik Perpeet 2016-09-06 08:31:54 UTC
Technically we don't know it's a satellite system, upstream we support candlepin. The suffix is entirely up to the server's configuration. We can discuss trying the suffix automatically if we can't connect using just the hostname.


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