Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2147371

Summary: rhn-migrate-classic-to-rhsm throws an Error: No module named 'libxml2'
Product: Red Hat Enterprise Linux 8 Reporter: John Sefler <jsefler>
Component: subscription-managerAssignee: candlepin-bugs
Status: CLOSED WONTFIX QA Contact: Red Hat subscription-manager QE Team <rhsm-qe>
Severity: low Docs Contact:
Priority: unspecified    
Version: 8.8Flags: pm-rhel: mirror+
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-05 11:17:32 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 2022-11-23 20:02:26 UTC
Description of problem:

On fresh Beaker installs of RHEL-8.8.0-20221120.2 arches [s390x, aarch64, s390x] but not [x86_64], attempts to run rhn-migrate-classic-to-rhsm fail with exitCode=2 and stdErr=

Unable to find Subscription Manager module.
Error: No module named 'libxml2'


Version-Release number of selected component (if applicable):
RHEL-8.8.0-20221120.2
[root@ampere-mtsnow-altramax-01-vm-03 ~]# rpm -q subscription-manager subscription-manager-migration
subscription-manager-1.28.33-1.el8.aarch64
subscription-manager-migration-1.28.33-1.el8.aarch64


How reproducible:
on [s390x, aarch64, s390x] but not [x86_64]

Steps to Reproduce:
[root@ampere-mtsnow-altramax-01-vm-03 ~]# rhn-migrate-classic-to-rhsm -h
Unable to find Subscription Manager module.
Error: No module named 'libxml2'



However, life is good after installing python3-libxml2
[root@ampere-mtsnow-altramax-01-vm-03 ~]# rpm -q python3-libxml2
package python3-libxml2 is not installed
[root@ampere-mtsnow-altramax-01-vm-03 ~]# yum install python3-libxml2 --quiet --assumeyes

Installed:
  python3-libxml2-2.9.7-15.el8.aarch64                                                                                                                                             

[root@ampere-mtsnow-altramax-01-vm-03 ~]# rpm -q python3-libxml2
python3-libxml2-2.9.7-15.el8.aarch64

[root@ampere-mtsnow-altramax-01-vm-03 ~]# rhn-migrate-classic-to-rhsm -h
usage: rhn-migrate-classic-to-rhsm [OPTIONS]

optional arguments:
  -h, --help            show this help message and exit
  -n, --no-auto         don't execute the auto-attach option while registering
                        with subscription manager
  -s SERVICE_LEVEL, --servicelevel SERVICE_LEVEL
                        service level to follow when attaching subscriptions,
                        for no service level use --servicelevel=""
  --remove-rhn-packages
                        remove legacy packages
  --no-proxy            don't use legacy proxy settings with destination
                        server
  --org ORG             organization to register to
  --environment ENVIRONMENT
                        environment to register to
  -f, --force           ignore channels not available on destination server
  --activation-key ACTIVATION_KEYS
                        activation key to use for registration (can be
                        specified more than once)
  --keep                leave system registered in legacy environment
  --legacy-user LEGACY_USER
                        specify the user name on the legacy server
  --legacy-password LEGACY_PASSWORD
                        specify the password on the legacy server
  --destination-url DESTINATION_URL
                        specify the subscription management server to migrate
                        to
  --destination-user DESTINATION_USER
                        specify the user name on the destination server
  --destination-password DESTINATION_PASSWORD
                        specify the password on the destination server


Actual results:
  Error: No module named 'libxml2'  (when package python3-libxml2 is not installed)

Expected results:
  

Additional info:

[root@ampere-mtsnow-altramax-01-vm-03 ~]# rpm -q subscription-manager-migration --requires
/usr/libexec/platform-python
python(abi) = 3.6
rhnlib
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PartialHardlinkSets) <= 4.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
subscription-manager = 1.28.33-1.el8
subscription-manager-migration-data

Comment 1 Pino Toscano 2022-12-05 11:17:32 UTC
After an internal discussion, the consensus was to simply drop subscription-manager-migration altogether, as it is not usable anymore -- this is bug 2150814.

Hence, closing this bug as WONTFIX.