Document Details
High Availability Guide Suse Pacemaker
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_tools
⚠️
windows_first
Summary:
The documentation is highly focused on SUSE Linux Enterprise Server (SLES) and Pacemaker on Azure, with all configuration and operational examples using Linux commands and tools. However, there is a notable Windows bias in the following ways: (1) The only example for creating and attaching Azure shared disks is given in PowerShell, a Windows-centric tool, rather than Azure CLI or ARM templates, which are more cross-platform and native to Linux users. (2) In the 'Overview' and some cross-references, Windows is mentioned before Linux (e.g., 'virtual-machines-windows,virtual-network,storage' in metadata, and [virtual-machines-windows-maintenance] is referenced before [virtual-machines-linux-maintenance]). There are no missing Linux examples for the core SLES/Pacemaker content, but the disk provisioning step assumes PowerShell, which may be unfamiliar or unavailable to Linux users.
Recommendations:
- Provide Azure CLI examples for creating and attaching Azure shared disks, as Azure CLI is cross-platform and more familiar to Linux users.
- Reorder references and metadata to mention Linux before Windows where appropriate, especially since the guide is Linux-specific.
- Explicitly state that PowerShell examples are for illustration only and provide equivalent steps for Linux environments.
- Where possible, include ARM/Bicep template snippets for infrastructure provisioning to ensure parity for users who prefer declarative approaches.
- Audit other cross-references and links to ensure Linux documentation is not deprioritized or omitted in favor of Windows.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-08-20 00:01 | #86 | completed | ✅ Clean |
| 2025-08-19 00:01 | #85 | completed | ✅ Clean |
| 2025-08-17 00:01 | #83 | in_progress | ✅ Clean |
| 2025-08-11 00:00 | #77 | completed | ✅ Clean |
| 2025-08-10 00:00 | #76 | completed | ✅ Clean |
| 2025-08-09 00:00 | #75 | completed | ✅ Clean |
| 2025-08-08 00:00 | #74 | completed | ✅ Clean |
| 2025-08-07 00:00 | #73 | completed | ✅ Clean |
| 2025-08-06 00:00 | #72 | completed | ✅ Clean |
| 2025-08-05 00:00 | #71 | completed | ✅ Clean |
| 2025-08-03 00:00 | #69 | completed | ✅ Clean |
| 2025-07-22 00:01 | #57 | completed | ✅ Clean |
| 2025-07-13 21:37 | #48 | completed | ❌ Biased |
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
Flagged Code Snippets
$VM1 = "prod-cl1-0"
$VM2 = "prod-cl1-1"
$ResourceGroup = "MyResourceGroup"
$Location = "MyAzureRegion"
$DiskSizeInGB = 4
$DiskName = "SBD-disk1"
$ShareNodes = 2
$SkuName = "Premium_LRS"
$SkuName = "Premium_ZRS"
$diskConfig = New-AzDiskConfig -Location $Location -SkuName $SkuName -CreateOption Empty -DiskSizeGB $DiskSizeInGB -MaxSharesCount $ShareNodes
$dataDisk = New-AzDisk -ResourceGroupName $ResourceGroup -DiskName $DiskName -Disk $diskConfig
$vm = Get-AzVM -ResourceGroupName $ResourceGroup -Name $VM1
$vm = Add-AzVMDataDisk -VM $vm -Name $DiskName -CreateOption Attach -ManagedDiskId $dataDisk.Id -Lun 0
Update-AzVm -VM $vm -ResourceGroupName $ResourceGroup -Verbose
$vm = Get-AzVM -ResourceGroupName $ResourceGroup -Name $VM2
$vm = Add-AzVMDataDisk -VM $vm -Name $DiskName -CreateOption Attach -ManagedDiskId $dataDisk.Id -Lun 0
Update-AzVm -VM $vm -ResourceGroupName $ResourceGroup -Verbose