ERROR: Azure Resource Manager Python SDK not found or not accessible...this is in azure government.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@rjohnson318 can you tell me at which point in the doc you are getting this error?
@rjohnson318 can you tell me at which point in the doc you are getting this error?
Once I finished the doc and the setup. I tried to test the fence with this command.
fence_azure_arm --username=12312231231231231231 --password=123123123123123123 --plug=APP43 --resourceGroup=resource.group --tenantId=1231231231231231231 --subscriptionId=123123123123 --verbose --action=status --power-timeout=6000
seems like I need to have Azure Resource Manager Python SDK but it did not say to install it or where to get it from.
@MSSedusch @rolyon could either of you comment further on this issue? I am not overly familiar with this specific implementation
@rjohnson318 How did you deploy the RHEL VM? Did you use a VM Image from the Azure gallery, if yes, which one? How did you install the Azure fence agent? If you send me more details, I can try to repro the issue.
Thanks
@MSSedusch I deployed the RHEL VM through the portal (RHEL 7.6). Configured the cluster using this document [https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/high-availability-guide-rhel-pacemaker]
specifically using this command to create it:

I was not able to reproduce the issue. I deployed a new RHEL 7.6 image from the Azure marketplace and executed the following commands on the VM
sudo subscription-manager register
sudo subscription-manager attach --pool=
sudo subscription-manager repos --disable "*"
sudo subscription-manager repos --enable=rhel-7-server-rpms
sudo subscription-manager repos --enable=rhel-ha-for-rhel-7-server-rpms
sudo subscription-manager repos --enable="rhel-sap-for-rhel-7-server-rpms"
sudo yum install -y pcs pacemaker fence-agents-azure-arm nmap-ncat
When I run fence_azure_arm, it works (I get an InvalidClientIdError but that is expected when I use your command).
Can you check if the dependecies of the fence-agent-azure-arm packages are correct i.e. run the following commands and send us the output?
sudo yum info fence-agents-azure-arm
sudo yum deplist fence-agents-azure-arm
@MSSedusch hmmmmm....did you deploy it in the same cloud environment as me? I am using azure government (usdodeast), which its feature set is different from the public azure cloud with different offerings some even not available for instance vmss autoscaling.
Thanks for the extra details @rjohnson318
The fact that you are using this in the Gov cloud might very well be the issue.
I will let @MSSedusch comment further as he would know more than I.
@MicahMcKittrick-MSFT @MSSedusch thanks for the reply and help with this.
@MSSedusch could you possibly comment further on this?
Sorry for the delayed reply.
I think we need to involve Red Hat. If the package dependecies are not correct, they should be able to find the root cause. Can you open a support request with Red Hat?
Thanks @MSSedusch
@rjohnson318 at this point it would be best to open a support request. Do you have the ability to open a technical support ticket? If not, you can email me at [email protected] and provide me with your subscriptionID and link to this issue. I can enable your subscription for that request.
I will close this for now and be on the lookout for your email if needed.
@MSSedusch at this point I was told not to persue it. We will use Centos 7 instead. Thanks for your help on this issue guys.
Since this is a guide about how to set up Pacemaker for SAP, I just wanted to mention that CentOS is not supported by SAP.
@MSSedusch Does this imply that you need to register your instance with Red Hat (either via the Red Hat portal or Satellite)? Or does the Marketplace instance include all the repos needed? Thanks.
There is currently no RHEL image in the Azure Marketplace that has access to the HA package. You need to register the VM and attach the VM to a pool that contains the repositories for the HA packages. See https://access.redhat.com/articles/3252491