Bug 1119651
Summary: | Can not register RHEL5.11-20140625.0 against SAM-1.4.1-RHEL-6-20140714.1 | ||
---|---|---|---|
Product: | [Retired] Subscription Asset Manager | Reporter: | qianzhan |
Component: | candlepin | Assignee: | Katello Bug Bin <katello-bugs> |
Status: | CLOSED WORKSFORME | QA Contact: | SAM QE List <sam-qe-list> |
Severity: | high | Docs Contact: | |
Priority: | urgent | ||
Version: | 1.4 | CC: | dgoodwin, liliu, qianzhan, shihliu |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-07-16 09:03:30 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
qianzhan
2014-07-15 08:39:06 UTC
I have also tried to do registration with my RHEL6.5GA client(10.66.128.9, root/redhat), however, it always failed to register to the new sam 1.4.1 server(10.66.129.28) with the error "certificate verify failed", but it can register to the sam 1.4.0 server(10.66.128.24). Can you confirm that (a) the clocks are in sync, and (b) if you remove completely all candlepin-cert-consumer rpms, then re-install one for the server you intend to register to. I have a suspicion that installing a second one with the previous still installed is not taking effect. Hi Devan, Thanks for your information! I checked the time of the sam server(10.66.129.28), it's really not correct, I then updated it to correct time, and removed the candlepin-cer-consumer again and re-install it, however, my client(10.66.128.9) still failed to register to the sam server. I'm not sure what's going on here, I started logging into systems to try to reproduce, but everything seems fine. In original bug the 5.11 client is 10.66.15.55, on that system I was able to register fine without any changes: [root@dhcp-15-55 ca]# subscription-manager identity system identity: e9f11ac7-5fc7-4199-87dd-3c694c668979 name: dhcp-15-55.nay.redhat.com org name: ACME_Corporation org ID: ACME_Corporation In comment #3 I see another 5.11 client referenced so I tried there too: [root@dhcp-128-9 ca]# subscription-manager register --username=admin --password=admin The system has been registered with ID: 527e0700-9c80-4ea0-8299-122fccac407d So in original bug report, I am quite certain it was caused by clock skew, I can see warnings in rhsm.log on both systems. I can't say why it didn't immediately start working in comment #3 but it's gone now, we have two 5.11 clients talking to SAM 1.4.1, I believe clock skew was to blame here. This bug does not exist in SAM-1.4.1-RHEL-6-20140714.1 server, so close it. |