Error getting instance data: instance-flavor-check tool is not available

This document (000021279) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 4.3
SUSE Linux Enterprise Server for SAP 15 Sp3

Situation

Configured PAYG instance connection with SLES for SAP 15SP3 AWS instance and encounters the issue:

"Error getting instance data: instance-flavor-check tool is not available. For a correct PAYG detection please install the 'python-instance-flavor-check' package"

Log excerpt:

tail -n 50 /var/log/rhn/rhn_taskomatic_daemon.log
2023-11-17 13:50:30,342 [DefaultQuartzScheduler_Worker-1] ERROR com.redhat.rhn.taskomatic.task.payg.PaygAuthDataExtractor - Exit status: 1
2023-11-17 13:50:30,342 [DefaultQuartzScheduler_Worker-1] ERROR com.redhat.rhn.taskomatic.task.payg.PaygAuthDataExtractor - stderr:
instance-flavor-check tool is not available.
For a correct PAYG detection please install the 'python-instance-billing-flavor-check' package
2023-11-17 13:50:30,342 [DefaultQuartzScheduler_Worker-1] ERROR com.redhat.rhn.taskomatic.task.payg.PaygUpdateAuthTask - error getting instance data
com.redhat.rhn.taskomatic.task.payg.PaygDataExtractException: instance-flavor-check tool is not available.
For a correct PAYG detection please install the 'python-instance-billing-flavor-check' package
at com.redhat.rhn.taskomatic.task.payg.PaygAuthDataExtractor.processOutput(PaygAuthDataExtractor.java:117) ~[rhn.jar:?]
at com.redhat.rhn.taskomatic.task.payg.PaygAuthDataExtractor.extractAuthDataSSH(PaygAuthDataExtractor.java:193) ~[rhn.jar:?]
at com.redhat.rhn.taskomatic.task.payg.PaygAuthDataExtractor.extractAuthData(PaygAuthDataExtractor.java:278) ~[rhn.jar:?]
at com.redhat.rhn.taskomatic.task.payg.PaygUpdateAuthTask.updateInstanceData(PaygUpdateAuthTask.java:158) ~[rhn.jar:?]
at java.util.ArrayList.forEach(ArrayList.java:1541) ~[?:?]
at com.redhat.rhn.taskomatic.task.payg.PaygUpdateAuthTask.lambda$execute$1(PaygUpdateAuthTask.java:111) ~[rhn.jar:?]
at com.redhat.rhn.common.util.FileLocks.lambda$withFileLock$1(FileLocks.java:79) ~[rhn.jar:?]
at com.redhat.rhn.common.util.FileLocks.withFileLock(FileLocks.java:112) ~[rhn.jar:?]
at com.redhat.rhn.common.util.FileLocks.withFileLock(FileLocks.java:78) ~[rhn.jar:?]
at com.redhat.rhn.taskomatic.task.payg.PaygUpdateAuthTask.execute(PaygUpdateAuthTask.java:110) ~[rhn.jar:?]
at com.redhat.rhn.taskomatic.task.RhnJavaJob.execute(RhnJavaJob.java:56) ~[rhn.jar:?]
at com.redhat.rhn.taskomatic.TaskoJob.doExecute(TaskoJob.java:240) ~[rhn.jar:?]
at com.redhat.rhn.taskomatic.TaskoJob.runTemplate(TaskoJob.java:193) ~[rhn.jar:?]
at com.redhat.rhn.taskomatic.TaskoJob.execute(TaskoJob.java:145) ~[rhn.jar:?]
at org.quartz.core.JobRunShell.run(JobRunShell.java:202) ~[quartz-2.3.0.jar:?]
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) ~[quartz-2.3.0.jar:?]

Resolution

Verify whether the python-instance-billing-flavor-check package is installed on the client-server. The package is available from the Public Cloud module:

rpm -qa | grep python-instance

If the package is not installed, install it with:

zypper in python-instance-billing-flavor-check

If the package can not be found, ensure the Public Cloud Module is activated:

SUSEConnect -p sle-module-public-cloud/15.3/x86_64

Then reconfigure the PAYG instance connection again from the SUMA server as per the online documenation:
https://documentation.suse.com/suma/4.3/en/suse-manager/installation-and-upgrade/connect-payg.html#_connecting_pay_as_you_go_instance

Verify the new PAYG instance details exist in the SUMA server:

spacewalk-sql --select-mode - <<< "select * from susecredentials"

Finally sync the repository again manually:

spacewalk-repo-sync --c sle-product-sles_sap15-sp3-updates-x86_64

Cause

Missing python-instance-billing-flavor-check on the client.

Status

Reported to Engineering

Additional Information

For a fully operational PAYG Connection, it’s crucial to have the "instance-flavor-check" tool available, which is bundled within the "python-instance-billing-flavor-check" package.

While this package is automatically installed on all newly created instances, for older running instances, manual installation is necessary to prevent potential errors. If you’re working with older Cloud instances, you can install this package manually from the Public Cloud Module.

The fix will be available with version 4.3.10.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.