)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":15197,"name":"Pierre Riteau","email":"pierre@stackhpc.com","username":"priteau","status":"StackHPC"},"change_message_id":"fd8eabd507e91db2f2ba9a08695ecb5b8852679e","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b6e53c40_c7bb0113","updated":"2025-10-23 09:57:48.000000000","message":"I am not really convinced this is the right change. There is an existing tag called `ip-allocation` which you can use. Many Kayobe host configure tasks have dependencies on previous ones: should we add the `lvm` tag to the `mdadm` playbook, just because your LVM PV might be a software RAID array?","commit_id":"b11f8d18f82a9c907a81327ee2738438bc00c7be"},{"author":{"_account_id":28048,"name":"Will Szumski","email":"will@stackhpc.com","username":"jovial"},"change_message_id":"e0ae235cc53b2e8610e02b92e3149c0be9df6705","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"8c8116df_b03ba345","updated":"2026-04-09 16:20:47.000000000","message":"Jakub - did you have time to refresh this one?","commit_id":"b11f8d18f82a9c907a81327ee2738438bc00c7be"},{"author":{"_account_id":14200,"name":"Maksim Malchuk","email":"maksim.malchuk@gmail.com","username":"mmalchuk"},"change_message_id":"58a68bc5bfac22362bd2c825eb1f7d6e61117f5e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"62155ba5_a07d23b5","updated":"2025-10-23 13:08:07.000000000","message":"let\u0027s dig deeper","commit_id":"b11f8d18f82a9c907a81327ee2738438bc00c7be"},{"author":{"_account_id":14200,"name":"Maksim Malchuk","email":"maksim.malchuk@gmail.com","username":"mmalchuk"},"change_message_id":"8058dad5edf1e5a8c74433c91153d454cc92e914","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1ae61af6_e5606085","updated":"2025-10-22 13:14:36.000000000","message":"nice catch","commit_id":"b11f8d18f82a9c907a81327ee2738438bc00c7be"},{"author":{"_account_id":34076,"name":"Jakub Darmach","email":"jakub@stackhpc.com","username":"darmach"},"change_message_id":"42db37869c6e619383fd29f653ba392cfdfacde5","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"451beb91_97ca3964","in_reply_to":"167eb754_33a63cd9","updated":"2025-10-29 13:56:32.000000000","message":"For me @will@stackhpc.com approach makes sense - IP allocation is indeed required for more playbooks than the network ones. To be honest, I would say that the general idea of mine would be to have my addresses allocated and up to date when I\u0027m doing something.","commit_id":"b11f8d18f82a9c907a81327ee2738438bc00c7be"},{"author":{"_account_id":28048,"name":"Will Szumski","email":"will@stackhpc.com","username":"jovial"},"change_message_id":"91693f40be410de3fc4ba1ccc9a3bf16413355f8","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e96a6a54_e9580fcd","in_reply_to":"b6e53c40_c7bb0113","updated":"2025-10-24 09:48:34.000000000","message":"We could treat it a bit like the kolla-ansible config generation and use tags:always. You could then skip it with:\n\n   --tags lvm --skip-tags ip-allocation\n\nAn IP allocation is required for any playbook (not just the network related ones) as we need the IP on the admin network to login in with (unless you\u0027ve overridden ansible_host)\n\nWhat do people think?","commit_id":"b11f8d18f82a9c907a81327ee2738438bc00c7be"},{"author":{"_account_id":14200,"name":"Maksim Malchuk","email":"maksim.malchuk@gmail.com","username":"mmalchuk"},"change_message_id":"5c6865d96485f30d4e42593f0324383dd557df1f","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"167eb754_33a63cd9","in_reply_to":"e96a6a54_e9580fcd","updated":"2025-10-24 12:07:41.000000000","message":"skip is a real thing, and widely used where ip-allocation not needed (eg. static inventory). but the report described in the bug the opposite issue.","commit_id":"b11f8d18f82a9c907a81327ee2738438bc00c7be"}]}