Bug 818887
Summary: | Unable to unregister a system via SAM GUI | ||
---|---|---|---|
Product: | [Retired] Subscription Asset Manager | Reporter: | Ryoichiro Tsuruno <rtsuruno> |
Component: | candlepin | Assignee: | Jordan OMara <jomara> |
Status: | CLOSED WORKSFORME | QA Contact: | SAM QE List <sam-qe-list> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.0.0 | CC: | athomas, esammons, jomara, mcoggin, tomckay |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-29 13:41:48 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
Ryoichiro Tsuruno
2012-05-04 09:41:58 UTC
Thank you for your bug report. This issue was evaluated for inclusion in the current release of Subscription Asset Manager (SAM). Unfortunately, we are unable to address this request. Because we are in the final stages of development in the current release, only significant, release-blocking issues involving serious regressions and data corruption can be considered. If you believe this issue meets the release blocking criteria as defined and communicated to you by your Red Hat Support representative, please ask your representative to file this issue as a blocker for the current release. Otherwise, ask that it be evaluated for inclusion in the next release of SAM. Thank you for your bug report. This issue was evaluated for inclusion in the current release of Subscription Asset Manager (SAM). Unfortunately, we are unable to address this request. Because we are in the final stages of development in the current release, only significant, release-blocking issues involving serious regressions and data corruption can be considered. If you believe this issue meets the release blocking criteria as defined and communicated to you by your Red Hat Support representative, please ask your representative to file this issue as a blocker for the current release. Otherwise, ask that it be evaluated for inclusion in the next release of SAM. Here is my rhsm.conf file. I am registering against hosted SAM (if that's a correct term). Another strange thing is that when I launch SAM GUI, it reports that the system is registered to hosted RHN even though I have it registered against hosted SAM. [root@rhel6-1 ~]# cat /etc/rhsm/rhsm.conf # Red Hat Subscription Manager Configuration File: # Unified Entitlement Platform Configuration [server] # Server hostname: hostname = subscription.rhn.redhat.com # Server prefix: prefix = /subscription # Server port: port = 443 # Set to 1 to disable certificate validation: insecure = 0 # Set the depth of certs which should be checked # when validating a certificate ssl_verify_depth = 3 # Server CA certificate location: ca_cert_dir = /etc/rhsm/ca/ # an http proxy server to use proxy_hostname = # port for http proxy server proxy_port = # user name for authenticating to an http proxy, if needed proxy_user = # password for basic http proxy auth, if needed proxy_password = [rhsm] # Content base URL: baseurl= https://cdn.redhat.com # Default CA cert to use when generating yum repo configs: repo_ca_cert = %(ca_cert_dir)sredhat-uep.pem # Where the certificates should be stored productCertDir = /etc/pki/product entitlementCertDir = /etc/pki/entitlement consumerCertDir = /etc/pki/consumer [rhsmcertd] # Frequency of certificate refresh (in minutes): certFrequency = 240 # Frequency of autoheal check (1440 min = 1 day): healFrequency = 1440 I wrote a github gist for connecting your local rhsm to SAM. Can you try these settings and try again? (substitute /headpin for your installation, presumably /sam) https://gist.github.com/2645015 Is this still an issue? Is there any more help that is required? Thanks! Tom Closing as working |