What is the impact of this issue to you?

In RHEL 9.x, the waagent service starts automatically even on non-Azure environments (e.g., KVM, VMware).
Since these systems do not provide Azure metadata or infrastructure, waagent repeatedly throws errors

~~~~
 2025-12-04T08:46:57.797434Z INFO Daemon Daemon Found device: None
3[6739]: 2025-12-04T08:46:57.798384Z ERROR Daemon Daemon Failed to mount resource disk [ResourceDiskError] unable to detect disk topology
3[6739]: 2025-12-04T08:46:57.799375Z ERROR Daemon Daemon Event: name=WALinuxAgent, op=ActivateResourceDisk, message=[ResourceDiskError] unable to detect disk topology, duration=0
3[6739]: 2025-12-04T08:46:57.802595Z INFO Daemon Daemon Clean protocol and wireserver endpoint
3[6739]: 2025-12-04T08:46:57.803723Z INFO Daemon Daemon Running default provisioning handler
3[6739]: 2025-12-04T08:46:57.823759Z INFO Daemon Daemon Unable to get cloud-init enabled status from systemctl: Command '['systemctl', 'is-enabled', 'cloud-init-local.service']' re>
3[6739]: 2025-12-04T08:46:57.863606Z INFO Daemon Daemon Unable to get cloud-init enabled status from service: Command '['service', 'cloud-init', 'status']' returned non-zero exit s>
3[6739]: 2025-12-04T08:46:57.871383Z INFO Daemon Daemon cloud-init is enabled: False
3[6739]: 2025-12-04T08:46:57.872823Z INFO Daemon Daemon Copying ovf-env.xml
3[6739]: 2025-12-04T08:46:58.099263Z WARNING Daemon Daemon Mounting dvd failed [retry 1/5, sleeping 5 sec]
~~~~

Package NVR where the issue is seen

 
WALinuxAgent-2.13.1.1-3.el9.noarch (RHEL 9.7)

How reproducible is this bug?

100% reproducible on any RHEL 9.7 system running under KVM or any non-Azure virtualization platform.

Steps to reproduce

1. Install or boot a RHEL 9.7 VM under KVM.

1. Ensure WALinuxAgent package is installed:
   ~~~~
   # rpm -qa | grep -i WALinuxAgent
   ~~~~
    
2. Check service conditions:
   ~~~~
    
   # systemctl cat waagent | grep Condition
   ~~~~
   Output (missing Azure condition):
   ~~~~
   ConditionFileIsExecutable=/usr/sbin/waagentConditionPathExists=/etc/waagent.conf
   ~~~~
3. Start the agent manually:
   ~~~~
   # systemctl start waagent
   # systemctl status waagent
   ~~~~
   Expected results

• On non-Azure platforms (KVM, VMware, etc.), the waagent service should not start.

• The service should honor a systemd condition similar to RHEL 10.1:
  ~~~~
  ConditionVirtualization=|microsofT
  ~~~~
• No Azure-related errors should appear in logs for non-Azure machines.

Actual results

• In RHEL 9.x, the absence of the virtualization condition causes the service to start on all systems.

• This leads to repeated, irrelevant Azure errors such as:
  ~~~~
  {{Failed to mount resource disk
  unable to detect disk topology
  Unable to get cloud-init enabled status
  Mounting dvd failed [retry...] 
  ~~~~}}
• Behavior is inconsistent with RHEL 10.1, where the service is correctly skipped:
  ~~~~
  {{ConditionVirtualization=|microsoft was not met
  waagent.service was skipped}}
  ~~~~