)]}'
{"releasenotes/notes/empty-physical-network-2248a4adef210289.yaml":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"83c849546aa8463d89fa2034c2d1f7dffc536fe5","unresolved":true,"context_lines":[{"line_number":2,"context_line":"fixes:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    It is no longer possible to set a port\u0027s ``physical_network`` to an empty"},{"line_number":5,"context_line":"    string, making the port unusable."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"29151369_bba5c50e","line":5,"updated":"2020-12-14 16:41:31.000000000","message":"It might be my English or how I interpret this: 1. by making it impossible to set this to an empty string, does it make the port unusable? or 2. we don\u0027t allow it to be set to an empty string, cuz when it was set to an empty string it made the port unusable.\n\nI\u0027m guessing 2, so maybe \u0027to any empty string because setting it to an empty string made the port unusable.\u0027","commit_id":"219bf0c373a805f96f44086ce63f4d9e0f31e21c"}],"releasenotes/notes/fix-inspection-for-idrac-34b3ea09452af8be.yaml":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"83c849546aa8463d89fa2034c2d1f7dffc536fe5","unresolved":true,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"fixes:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Fixes inspection with the ``idrac-redfish-virtual-media`` boot interface."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"55b9630e_18dbbf94","line":4,"updated":"2020-12-14 16:41:31.000000000","message":"Would be nice to link to a bug/story here, in case someone wanted more info about what the bug was.","commit_id":"219bf0c373a805f96f44086ce63f4d9e0f31e21c"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"481e0cad70eb5d0d11170d6062f3edf2e420da2f","unresolved":true,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"fixes:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    Fixes inspection with the ``idrac-redfish-virtual-media`` boot interface."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"96c54b85_3d9da8e6","line":4,"in_reply_to":"55b9630e_18dbbf94","updated":"2020-12-15 15:27:02.000000000","message":"I remember this, inspection would fail hard. It was actually a swift map lookup in driver_utils from some refactored code. It was super minor, just highly visible at that moment. :(","commit_id":"219bf0c373a805f96f44086ce63f4d9e0f31e21c"}],"releasenotes/notes/ipmi_command_retry_timeout-889a49b402e82b97.yaml":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"83c849546aa8463d89fa2034c2d1f7dffc536fe5","unresolved":true,"context_lines":[{"line_number":6,"context_line":"    now takes into account the 1 second interval increment that ipmitool adds"},{"line_number":7,"context_line":"    on each retry event."},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"    Failure-path ipmitool run duration will now be just less than"},{"line_number":10,"context_line":"    ``command_retry_timeout`` instead of much longer."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"12b80c9c_6c2cb75a","line":9,"updated":"2020-12-14 16:41:31.000000000","message":"Does \u0027Failure-path ipmitool run duration\u0027 mean \u0027With this change, if the ipmitool command fails, the elapsed time for the command will now be just shorter than the ...\u0027","commit_id":"219bf0c373a805f96f44086ce63f4d9e0f31e21c"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"481e0cad70eb5d0d11170d6062f3edf2e420da2f","unresolved":true,"context_lines":[{"line_number":6,"context_line":"    now takes into account the 1 second interval increment that ipmitool adds"},{"line_number":7,"context_line":"    on each retry event."},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"    Failure-path ipmitool run duration will now be just less than"},{"line_number":10,"context_line":"    ``command_retry_timeout`` instead of much longer."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"73cf2a2c_afb5357a","line":9,"in_reply_to":"12b80c9c_6c2cb75a","updated":"2020-12-15 15:27:02.000000000","message":"I think \"The failure path for ipmitool execution duration\" might make more sense, however Ruby\u0027s suggestion also looks good.","commit_id":"219bf0c373a805f96f44086ce63f4d9e0f31e21c"}],"releasenotes/notes/raid-remove-root-hint-ec87efd18e894256.yaml":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"83c849546aa8463d89fa2034c2d1f7dffc536fe5","unresolved":true,"context_lines":[{"line_number":7,"context_line":"  - |"},{"line_number":8,"context_line":"    Fixes the issue that root device hint is not removed after the ``agent``"},{"line_number":9,"context_line":"    RAID interface has successfully deleted RAID configuration. The previous"},{"line_number":10,"context_line":"    hint is not guranteed to be valid and may cause a deployment failure."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"cecbc109_db12efa8","line":10,"updated":"2020-12-14 16:41:31.000000000","message":"nit. s/guranteed/guaranteed/\n\nmaybe s/and may cause.../and might have caused a future deployment failure./","commit_id":"219bf0c373a805f96f44086ce63f4d9e0f31e21c"}]}