Bug 1888067
Summary: | rhsm-migrate-classic-to-rhsm fails to prompt me for the destination credentials; instead I get HTTP error (401 - Unauthorized): Invalid user credentials | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | John Sefler <jsefler> |
Component: | subscription-manager | Assignee: | candlepin-bugs |
Status: | CLOSED NOTABUG | QA Contact: | Red Hat subscription-manager QE Team <rhsm-qe> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.3 | CC: | redakkan |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-10-20 13:41:55 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
John Sefler
2020-10-13 22:37:39 UTC
As I think more about this test report and reflect on the original design for rhn-migrate-classic-to-rhsm, I believe this is working as designed and here is why... Since the server that is configured in the rhsm.conf file is a regex match for both hosted entitlement servers (subscription.rhsm(.stage).redhat.com), the assumption is that the user credentials that were used to register the system to the old hosted RHN would be the same credentials as used in the migration to the new RHSM. Therefore, it makes sense that the rhn-migrate-classic-to-rhsm did not prompt me for destination credentials in comment 0 because the assumption is that the migration from the old RHN to the new RHSM would use the same Red Hat account. That is why the rhsm.log file encounters a 401 Unauthorized on request="GET /subscription/users/rhsm-client/owners". In fact, the purpose for the --destination-url argument was intended to specify a non-hosted account, e.g. an onpremise satellite6 server. This explains the behavior in comment 0 and comment 1 and is therefore working as has always been designed. So the question now is... why is this being reported now? The answer is because RHSMQE has test coverage for this scenario that has traditionally been executed as a tier3 test against a local onpremise candlepin whose url is not a match to subscription.rhsm(.stage).redhat.com. Due to recent initiatives by RHSMQE to start executing tier3 tests against stage, this test failure arose. I vote to move this to CLOSED NOTABUG. |