)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"9b9d7993b1b5c2f7b61bfa8f59aad8fa3bebf037","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"6be072c0_30e6af64","updated":"2023-03-28 14:57:27.000000000","message":"recheck","commit_id":"3e21560bf70e5e6b529d9a2d37a2897461076395"}],"doc/source/admin/troubleshooting.rst":[{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"778d43c9aa17e6bfb241a63786407c16ebfe269b","unresolved":true,"context_lines":[{"line_number":108,"context_line":"   properties must have been set either manually or via inspection."},{"line_number":109,"context_line":"   For each node with ``available`` state check that the ``properties``"},{"line_number":110,"context_line":"   JSON field has valid values for the keys ``cpus``, ``cpu_arch``,"},{"line_number":111,"context_line":"   ``memory_mb`` and ``local_gb``. Example of valid properties::"},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"        $ baremetal node show \u003cIRONIC NODE\u003e --fields properties"},{"line_number":114,"context_line":"        +------------+------------------------------------------------------------------------------------+"}],"source_content_type":"text/x-rst","patch_set":1,"id":"6b63485d_d48ca76b","side":"PARENT","line":111,"updated":"2023-03-24 21:12:51.000000000","message":"Why are we removing this whole thing, when in other docs we leave stuff in place telling people to set, e.g. memory_mb on the node? (enrollment.rst).","commit_id":"b201e52f8904a5d3d546ea58e6e384d81c3ae066"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"7cd858b83c465cfbc2d078523ab995fa6bec823a","unresolved":false,"context_lines":[{"line_number":108,"context_line":"   properties must have been set either manually or via inspection."},{"line_number":109,"context_line":"   For each node with ``available`` state check that the ``properties``"},{"line_number":110,"context_line":"   JSON field has valid values for the keys ``cpus``, ``cpu_arch``,"},{"line_number":111,"context_line":"   ``memory_mb`` and ``local_gb``. Example of valid properties::"},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"        $ baremetal node show \u003cIRONIC NODE\u003e --fields properties"},{"line_number":114,"context_line":"        +------------+------------------------------------------------------------------------------------+"}],"source_content_type":"text/x-rst","patch_set":1,"id":"b4c2ec79_1e7ef8c2","side":"PARENT","line":111,"in_reply_to":"6b63485d_d48ca76b","updated":"2023-03-28 09:49:51.000000000","message":"But these properties no longer have anything to do with scheduling, so this item is wrong. Their absence or invalid values cannot cause a scheduling failure.\n\nYet, cpu_arch, memory_mb and local_gb are used by some internal logic in Ironic, while cpu_arch is also reported by Nova.","commit_id":"b201e52f8904a5d3d546ea58e6e384d81c3ae066"}],"releasenotes/notes/no-cpus-c79717303470bf3c.yaml":[{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"778d43c9aa17e6bfb241a63786407c16ebfe269b","unresolved":true,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The inspection implementations (except for ironic-inspector, which is"},{"line_number":5,"context_line":"    a separate service) no longer update the ``cpus`` property. It has not"},{"line_number":6,"context_line":"    been used by Nova for many releases and has never been used by Ironic"},{"line_number":7,"context_line":"    itself."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"badd25be_15f2eef2","line":4,"updated":"2023-03-24 21:12:51.000000000","message":"I\u0027m not sure an operator would be able to understand what this means? \n\nHow about:\nFully removes ``cpus`` property from docs and inspection. It was never used internally by Ironic, and is no longer used by Nova.","commit_id":"2127d4d3fbd266b4ede99ca796b00d4a98a099ab"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"7cd858b83c465cfbc2d078523ab995fa6bec823a","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"upgrade:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The inspection implementations (except for ironic-inspector, which is"},{"line_number":5,"context_line":"    a separate service) no longer update the ``cpus`` property. It has not"},{"line_number":6,"context_line":"    been used by Nova for many releases and has never been used by Ironic"},{"line_number":7,"context_line":"    itself."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"a8d7df2d_277668b4","line":4,"in_reply_to":"badd25be_15f2eef2","updated":"2023-03-28 09:49:51.000000000","message":"Done","commit_id":"2127d4d3fbd266b4ede99ca796b00d4a98a099ab"}]}