)]}'
{".zuul.yaml":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"f5fab3b6cbdb6a585b2fada6be0215e01c4ef78f","unresolved":true,"context_lines":[{"line_number":212,"context_line":"              live_migration_events: True"},{"line_number":213,"context_line":"          $NOVA_CPU_CONF:"},{"line_number":214,"context_line":"              compute:"},{"line_number":215,"context_line":"                heal_instance_info_cache_interval: -1"},{"line_number":216,"context_line":"    group-vars:"},{"line_number":217,"context_line":"      subnode:"},{"line_number":218,"context_line":"        devstack_localrc:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"bdf25016_b74d11e8","line":215,"range":{"start_line":215,"start_character":51,"end_line":215,"end_character":53},"updated":"2025-01-16 19:20:47.000000000","message":"sigh i ment renable this in the hybrid plug job...","commit_id":"2f861fe82150ae40741b00e4fd65540b837fc652"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"fa8a1b0ca9b607d53f3670c55240b5700125e2d6","unresolved":false,"context_lines":[{"line_number":212,"context_line":"              live_migration_events: True"},{"line_number":213,"context_line":"          $NOVA_CPU_CONF:"},{"line_number":214,"context_line":"              compute:"},{"line_number":215,"context_line":"                heal_instance_info_cache_interval: -1"},{"line_number":216,"context_line":"    group-vars:"},{"line_number":217,"context_line":"      subnode:"},{"line_number":218,"context_line":"        devstack_localrc:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"a2ccadfe_c3e4d317","line":215,"range":{"start_line":215,"start_character":51,"end_line":215,"end_character":53},"in_reply_to":"bdf25016_b74d11e8","updated":"2025-01-17 02:22:39.000000000","message":"Done","commit_id":"2f861fe82150ae40741b00e4fd65540b837fc652"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":8878,"name":"Masahito Muroi","email":"masahito.muroi@linecorp.com","username":"masa"},"change_message_id":"3175c042e6424f13771e461183fefda2a329939f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"f3521064_4284ab5b","updated":"2025-01-17 06:51:45.000000000","message":"Nice update. Minor comment for the release note as a cloud operator perspective.","commit_id":"3d7a4ec4ed7c2dd8d8489351c2577001a4b5c1e5"},{"author":{"_account_id":26250,"name":"Johannes Kulik","email":"johannes.kulik@sap.com","username":"jkulik"},"change_message_id":"618600fe0b1995bc29f7d0f2da510656c9adcedd","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"e74422c0_0cd91784","updated":"2025-01-23 09:20:19.000000000","message":"What happens if a Neutron notification is missed e.g. because of a restart or DB problem at the wrong time? Then the cache will stay not updated forever?\n\nWe internally recently discussed, that we need rather more than less sync-loops, because things happen to get out of sync when solely relying on events.","commit_id":"3d7a4ec4ed7c2dd8d8489351c2577001a4b5c1e5"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"308fcaa51713236c7922ae2adc53db7f7bef3203","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"37a2bad9_e900e8bc","updated":"2025-02-04 16:39:38.000000000","message":"q","commit_id":"3d7a4ec4ed7c2dd8d8489351c2577001a4b5c1e5"},{"author":{"_account_id":8878,"name":"Masahito Muroi","email":"masahito.muroi@linecorp.com","username":"masa"},"change_message_id":"a9b14375649c99169bac0cc968389645a48fd54b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"90f8cdc8_729cd561","updated":"2025-01-21 03:33:11.000000000","message":"recheck ssh connection failure during resize confirm.","commit_id":"3d7a4ec4ed7c2dd8d8489351c2577001a4b5c1e5"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"f53a9abc9ef9ab6fd6b1e0265ba4403663ecb1f1","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"92ce8120_a77fe826","updated":"2025-01-17 02:27:23.000000000","message":"recheck ssh timeout in volume test","commit_id":"3d7a4ec4ed7c2dd8d8489351c2577001a4b5c1e5"},{"author":{"_account_id":8655,"name":"Jakub Libosvar","email":"libosvar@redhat.com","username":"jlibosva"},"change_message_id":"2f65611dd1606dc8a2e06c021ea40cae9977c492","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"42bd715a_86bedc1a","updated":"2025-01-22 18:57:15.000000000","message":"yay to this :)","commit_id":"3d7a4ec4ed7c2dd8d8489351c2577001a4b5c1e5"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"2687175cbd184f9d90648b5ecb4f0558be7fc3cd","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"b64a2560_08e46769","in_reply_to":"e74422c0_0cd91784","updated":"2025-01-30 21:24:45.000000000","message":"it will get updated the next time you modify a port but yes\nif that never happend it would never sync.\n\na user can fix it by detachign and attachign the port to force a resync or adding/removing a floating ip\n\nthere are many ways.\n\nwe are leaving the config in place so if you need to sync you can opt into it.\n\nwe could in the future provide a nova-manage commadn to do this or somthign like that for admins.\n\ni wont have time to do that this cycle.","commit_id":"3d7a4ec4ed7c2dd8d8489351c2577001a4b5c1e5"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"ba1837e348a513a2f59dc728b5fa7dabe87ff503","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"0b739fc9_99f615f9","updated":"2025-02-17 18:15:08.000000000","message":"Looks sensible to me","commit_id":"b3f881572088b16f693bf52d932273429996ca60"},{"author":{"_account_id":16207,"name":"ribaudr","display_name":"uggla","email":"rene.ribaud@gmail.com","username":"uggla","status":"Red Hat"},"change_message_id":"58e484bbd4d3f530c117554010e2921b2a3f6d98","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"64c53adc_debc1cff","updated":"2025-02-12 14:21:42.000000000","message":"Thanks for providing all the history of that change. This is useful and helpful.","commit_id":"b3f881572088b16f693bf52d932273429996ca60"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"ac288c3bd74e5c8dfd2cc93ba8eaf017cfb3594a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"8abf06ab_3342cc35","updated":"2025-02-06 10:18:18.000000000","message":"We\u0027re past the two-week notice period and I haven\u0027t arguments about that, so +2.","commit_id":"b3f881572088b16f693bf52d932273429996ca60"}],"nova/conf/compute.py":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"ba1837e348a513a2f59dc728b5fa7dabe87ff503","unresolved":true,"context_lines":[{"line_number":1084,"context_line":"  of sync between the hypervisor and the Nova database will have"},{"line_number":1085,"context_line":"  to be synchronized manually."},{"line_number":1086,"context_line":"\"\"\"),"},{"line_number":1087,"context_line":"    cfg.IntOpt(\u0027heal_instance_info_cache_interval\u0027,"},{"line_number":1088,"context_line":"        default\u003d-1,"},{"line_number":1089,"context_line":"        help\u003d\"\"\""},{"line_number":1090,"context_line":"Interval between instance network information cache updates."}],"source_content_type":"text/x-python","patch_set":3,"id":"4f30aea6_1f826b09","line":1087,"updated":"2025-02-17 18:15:08.000000000","message":"Do we want to deprecate this for removal?","commit_id":"b3f881572088b16f693bf52d932273429996ca60"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"ac288c3bd74e5c8dfd2cc93ba8eaf017cfb3594a","unresolved":true,"context_lines":[{"line_number":1085,"context_line":"  to be synchronized manually."},{"line_number":1086,"context_line":"\"\"\"),"},{"line_number":1087,"context_line":"    cfg.IntOpt(\u0027heal_instance_info_cache_interval\u0027,"},{"line_number":1088,"context_line":"        default\u003d-1,"},{"line_number":1089,"context_line":"        help\u003d\"\"\""},{"line_number":1090,"context_line":"Interval between instance network information cache updates."},{"line_number":1091,"context_line":""}],"source_content_type":"text/x-python","patch_set":3,"id":"08243152_5fd492e2","line":1088,"range":{"start_line":1088,"start_character":16,"end_line":1088,"end_character":18},"updated":"2025-02-06 10:18:18.000000000","message":"0 could have be another possibility AFAIK but fine by me.","commit_id":"b3f881572088b16f693bf52d932273429996ca60"}],"releasenotes/notes/disable_heal_instance_info_cache_interval-0d9ae7c12793bf7b.yaml":[{"author":{"_account_id":16137,"name":"Tobias Urdin","email":"tobias.urdin@binero.com","username":"tobasco"},"change_message_id":"21e3024edb309649d8c871fe06242d5f9401afbc","unresolved":true,"context_lines":[{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The ``[compute]heal_instance_info_cache_interval`` option now default to -1."},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"    In the early days of nova, all networking was internal then quantum, now"},{"line_number":7,"context_line":"    know as neutron was introduced. When the networking subsystem was being"},{"line_number":8,"context_line":"    externalized and neutron was optional nova still needed to keep track"},{"line_number":9,"context_line":"    or the ports associated with an instance in its db and did not want to"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"d7b4b859_9e8cacdf","line":6,"updated":"2025-01-22 13:59:54.000000000","message":"s/then/when/g","commit_id":"3d7a4ec4ed7c2dd8d8489351c2577001a4b5c1e5"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"407fc8fb557b6a29da52c3b6d612b5168333782f","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The ``[compute]heal_instance_info_cache_interval`` option now default to -1."},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"    In the early days of nova, all networking was internal then quantum, now"},{"line_number":7,"context_line":"    know as neutron was introduced. When the networking subsystem was being"},{"line_number":8,"context_line":"    externalized and neutron was optional nova still needed to keep track"},{"line_number":9,"context_line":"    or the ports associated with an instance in its db and did not want to"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"910057c7_4bc90ccd","line":6,"in_reply_to":"d7b4b859_9e8cacdf","updated":"2025-02-05 19:53:44.000000000","message":"Acknowledged","commit_id":"3d7a4ec4ed7c2dd8d8489351c2577001a4b5c1e5"},{"author":{"_account_id":8878,"name":"Masahito Muroi","email":"masahito.muroi@linecorp.com","username":"masa"},"change_message_id":"3175c042e6424f13771e461183fefda2a329939f","unresolved":true,"context_lines":[{"line_number":39,"context_line":"    medium to large clouds. If you have a neutron backend that"},{"line_number":40,"context_line":"    does not reliable send network-changed event notifications to nova you can"},{"line_number":41,"context_line":"    re-enable this periodic task by setting"},{"line_number":42,"context_line":"    ``[compute]heal_instance_info_cache_interval`` to a value greater than 0."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"c6d20f42_6f4d85e4","line":42,"updated":"2025-01-17 06:51:45.000000000","message":"It\u0027s helpful to mention corresponding config option in the Neutron which enables or disables the Neutron to send the event notification.","commit_id":"3d7a4ec4ed7c2dd8d8489351c2577001a4b5c1e5"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"407fc8fb557b6a29da52c3b6d612b5168333782f","unresolved":true,"context_lines":[{"line_number":39,"context_line":"    medium to large clouds. If you have a neutron backend that"},{"line_number":40,"context_line":"    does not reliable send network-changed event notifications to nova you can"},{"line_number":41,"context_line":"    re-enable this periodic task by setting"},{"line_number":42,"context_line":"    ``[compute]heal_instance_info_cache_interval`` to a value greater than 0."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"528a4c1b_99dc8a59","line":42,"in_reply_to":"7c42bf7b_cb5e4721","updated":"2025-02-05 19:53:44.000000000","message":"we generally avoid referencing config options in other projects.\n\nthe main reason this section is here is to let admins know they can opt into the old behavior if they have any issues.\n\nI probably have too much context in this already so I would prefer to avoid adding more detail regarding neutron.","commit_id":"3d7a4ec4ed7c2dd8d8489351c2577001a4b5c1e5"},{"author":{"_account_id":8878,"name":"Masahito Muroi","email":"masahito.muroi@linecorp.com","username":"masa"},"change_message_id":"46118daa87de2be248351e26a7a86e4b701f54aa","unresolved":true,"context_lines":[{"line_number":39,"context_line":"    medium to large clouds. If you have a neutron backend that"},{"line_number":40,"context_line":"    does not reliable send network-changed event notifications to nova you can"},{"line_number":41,"context_line":"    re-enable this periodic task by setting"},{"line_number":42,"context_line":"    ``[compute]heal_instance_info_cache_interval`` to a value greater than 0."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"7c42bf7b_cb5e4721","line":42,"in_reply_to":"81014331_5d7cfd23","updated":"2025-01-20 10:28:19.000000000","message":"Thank you for the detail.\n\nI meant if this release note mentions like \"your deployment configures the `send_events_interval` to non-zero value and your neutron agent sends updates to Nova, you can set the heal_instance_info_cache_interval to 0.\", it\u0027s helpful for cloud operator.\n\nThe `send_events_interval` is implemented in the Neutron which is out of Nova repository. So if Nova has a release note policy that any release note shouldn\u0027t mention specific non-nova repository config name because the name update is out of control by Nova, I agree the current release note description.","commit_id":"3d7a4ec4ed7c2dd8d8489351c2577001a4b5c1e5"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"ee1e5180195e3b31a57289859e3aa0d304fbd65d","unresolved":true,"context_lines":[{"line_number":39,"context_line":"    medium to large clouds. If you have a neutron backend that"},{"line_number":40,"context_line":"    does not reliable send network-changed event notifications to nova you can"},{"line_number":41,"context_line":"    re-enable this periodic task by setting"},{"line_number":42,"context_line":"    ``[compute]heal_instance_info_cache_interval`` to a value greater than 0."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"81014331_5d7cfd23","line":42,"in_reply_to":"c6d20f42_6f4d85e4","updated":"2025-01-17 16:00:30.000000000","message":"it is not meant to be configurable.\n\nneutron has some options like \n\nhttps://docs.openstack.org/neutron/latest/configuration/neutron.html#DEFAULT.send_events_interval\n\nto control the batching of sending the events\n\nthere were bugs in the past if I understand correctly but I do not have any to hand\nto reference here.\n\nas far as we know there is no reason to need to turn on the periodic anymore but i was hedging my bets by sayign \"hay operators if you notice odd behavior, you can turn this back on\"","commit_id":"3d7a4ec4ed7c2dd8d8489351c2577001a4b5c1e5"}]}