Jinja2 for loop doesn't follow original dictionary order - ansible

Question

So I'm using a .j2 template file to generate a report regarding primary and secondary disk devices in a system.
I have to print the primary disk first and I'm covering only sd* and vd* device naming scheme.
Problem is the for loop always do a reverse lookup on the dictionary.
Here's the a ansible_devices variable on my system.
ansible1 | SUCCESS => {
"ansible_facts": {
"ansible_devices": {
"dm-0": {
"holders": [],
"host": "",
"links": {
"ids": [
"dm-name-rhel_rhel8-root",
"dm-uuid-LVM-DOufRu3rljRtRzbfEbU3jOt0XPsF4dTm8muvelhzXFaWdS0ivguPLcwB1EQaTdOj"
],
"labels": [],
"masters": [],
"uuids": [
"26028eb5-091e-41f5-993c-8639ded7c1c5"
]
},
"model": null,
"partitions": {},
"removable": "0",
"rotational": "1",
"sas_address": null,
"sas_device_handle": null,
"scheduler_mode": "",
"sectors": "146800640",
"sectorsize": "512",
"serial": "VB011d5a18",
"size": "70.00 GB",
"support_discard": "0",
"vendor": null,
"virtual": 1
},
"dm-1": {
"holders": [],
"host": "",
"links": {
"ids": [
"dm-name-rhel_rhel8-swap",
"dm-uuid-LVM-DOufRu3rljRtRzbfEbU3jOt0XPsF4dTmv7C9OKBjTw1x1xQ4VeF7G2iGYeCHi6Y2"
],
"labels": [],
"masters": [],
"uuids": [
"15cb7bae-eec8-421e-a324-5c8087b31b17"
]
},
"model": null,
"partitions": {},
"removable": "0",
"rotational": "1",
"sas_address": null,
"sas_device_handle": null,
"scheduler_mode": "",
"sectors": "4317184",
"sectorsize": "512",
"serial": "VB011d5a18",
"size": "2.06 GB",
"support_discard": "0",
"vendor": null,
"virtual": 1
},
"sda": {
"holders": [],
"host": "IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)",
"links": {
"ids": [
"ata-VBOX_HARDDISK_VB011d5a18-fc7b8d75",
"scsi-0ATA_VBOX_HARDDISK_VB011d5a18-fc7b8d75",
"scsi-1ATA_VBOX_HARDDISK_VB011d5a18-fc7b8d75",
"scsi-SATA_VBOX_HARDDISK_VB011d5a18-fc7b8d75"
],
"labels": [],
"masters": [],
"uuids": []
},
"model": "VBOX HARDDISK",
"partitions": {
"sda1": {
"holders": [],
"links": {
"ids": [
"ata-VBOX_HARDDISK_VB011d5a18-fc7b8d75-part1",
"scsi-0ATA_VBOX_HARDDISK_VB011d5a18-fc7b8d75-part1",
"scsi-1ATA_VBOX_HARDDISK_VB011d5a18-fc7b8d75-part1",
"scsi-SATA_VBOX_HARDDISK_VB011d5a18-fc7b8d75-part1"
],
"labels": [],
"masters": [],
"uuids": [
"7431a3cf-0ed2-4813-9df7-083f8ee4f6ae"
]
},
"sectors": "2097152",
"sectorsize": 512,
"size": "1.00 GB",
"start": "2048",
"uuid": "7431a3cf-0ed2-4813-9df7-083f8ee4f6ae"
},
"sda2": {
"holders": [
"rhel_rhel8-swap",
"rhel_rhel8-root"
],
"links": {
"ids": [
"ata-VBOX_HARDDISK_VB011d5a18-fc7b8d75-part2",
"lvm-pv-uuid-hBGpnr-FYc6-95QG-dsoT-qD3k-Imd0-0yoWzd",
"scsi-0ATA_VBOX_HARDDISK_VB011d5a18-fc7b8d75-part2",
"scsi-1ATA_VBOX_HARDDISK_VB011d5a18-fc7b8d75-part2",
"scsi-SATA_VBOX_HARDDISK_VB011d5a18-fc7b8d75-part2"
],
"labels": [],
"masters": [
"dm-0",
"dm-1"
],
"uuids": []
},
"sectors": "266336256",
"sectorsize": 512,
"size": "127.00 GB",
"start": "2099200",
"uuid": null
}
},
"removable": "0",
"rotational": "1",
"sas_address": null,
"sas_device_handle": null,
"scheduler_mode": "mq-deadline",
"sectors": "268435456",
"sectorsize": "512",
"serial": "VB011d5a18",
"size": "128.00 GB",
"support_discard": "0",
"vendor": "ATA",
"virtual": 1
},
"sdb": {
"holders": [],
"host": "IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)",
"links": {
"ids": [
"ata-VBOX_HARDDISK_VB6207845b-7aa2bea6",
"scsi-0ATA_VBOX_HARDDISK_VB6207845b-7aa2bea6",
"scsi-1ATA_VBOX_HARDDISK_VB6207845b-7aa2bea6",
"scsi-SATA_VBOX_HARDDISK_VB6207845b-7aa2bea6"
],
"labels": [],
"masters": [],
"uuids": []
},
"model": "VBOX HARDDISK",
"partitions": {},
"removable": "0",
"rotational": "1",
"sas_address": null,
"sas_device_handle": null,
"scheduler_mode": "mq-deadline",
"sectors": "10485760",
"sectorsize": "512",
"serial": "VB6207845b",
"size": "5.00 GB",
"support_discard": "0",
"vendor": "ATA",
"virtual": 1
}
},
"discovered_interpreter_python": "/usr/libexec/platform-python"
},
"changed": false
}
As it can be seen, the order is as;
dm-0
dm-1
sda
sdb
My template file is below;
{% for dev in ansible_devices %}
{% if dev == 'sda' %}
primary device {{ dev }} found on {{ ansible_hostname }}
{% endif %}
{% if dev == 'sdb' %}
second device {{ dev }} found on {{ ansible_hostname }}
{% endif %}
{% if dev == 'vda' %}
primary device {{ dev }} found on {{ ansible_hostname }}
{% endif %}
{% if dev == 'vdb' %}
second device {{ dev }} found on {{ ansible_hostname }}
{% endif %}
{% endfor %}
{% if ('sdb' not in ansible_devices) and ('vdb' not in ansible_devices) %}
no second device found on {{ ansible_hostname }}
{% endif %}
If I execute this within a playbook, the following content is generated;
--- before
+++ after: /home/ansible/.ansible/tmp/ansible-local 12580ell0d0oq/tmp1qs9mu2y/devices.j2
## -0,0 +1,2 ##
+primary device sda found on ansible3
+no second device found on ansible3
changed: [ansible3]
--- before
+++ after: /home/ansible/.ansible/tmp/ansible-local-12580ell0d0oq /tmpej185qb4/devices.j2
## -0,0 +1,2 ##
+second device sdb found on ansible2
+primary device sda found on ansible2
changed: [ansible2]
--- before
+++ after: /home/ansible/.ansible/tmp/ansible-local-12580ell0d0oq/tmpkbcmuhqa/devices.j2
## -0,0 +1,2 ##
+primary device sda found on ansible4
+no second device found on ansible4
changed: [ansible4]
--- before
+++ after: /home/ansible/.ansible/tmp/ansible-local-12580ell0d0oq/tmpvkm3uid6/devices.j2
## -0,0 +1,2 ##
+second device sdb found on ansible1
+primary device sda found on ansible1
changed: [ansible1]
Somehow, the iteration is going in reverse order, I've seen this in all the alternative tests for the given scenario.
Am I missing something here?