FDO official container is mounting var folder on /dev/mapper/rootvg-rootlv[/ostree/deploy/redhat/var]

[mcattamoredhat]

Our downstream CI has detected that FDO official container is mounting var folder on /dev/mapper/rootvg-rootlv[/ostree/deploy/redhat/var]. This means ansible-playbook command variable os_name of the script is not aligned with the actual stdout.

https://artifacts.osci.redhat.com/testing-farm/7327e019-e749-4a0a-8777-8236bd844a03/work-edge-fdo-container1nkqqxzv/tmt/plans/edge-test/edge-fdo-container/execute/data/guest/default-0/tmt/tests/edge-test-1/output.txt

TASK [check /var mount point] **************************************************
changed: [192.168.100.50] => changed=true 
  cmd:
  - findmnt
  - -r
  - -o
  - SOURCE
  - -n
  - /var
  delta: '0:00:00.005815'
  end: '2024-08-08 04:57:39.318704'
  msg: ''
  rc: 0
  start: '2024-08-08 04:57:39.312889'
  stderr: ''
  stderr_lines: <omitted>
  stdout: /dev/mapper/rootvg-rootlv[/ostree/deploy/redhat/var]
  stdout_lines: <omitted>
TASK [assert] ******************************************************************
fatal: [192.168.100.50]: FAILED! => changed=false 
  assertion: result_var_mount_point.stdout == "/dev/mapper/rootvg-rootlv[/ostree/deploy/rhel-edge/var]"
  evaluated_to: false
  msg: /var does not mount on /dev/mapper/rootvg-rootlv[/ostree/deploy/rhel-edge/var]

The workaround is straightforward: update os_name variable to redhat, but we should discuss this topic with developers.
In addition we should monitor if the same situation will happen in fdo community container.