)]}'
{"doc/source/admin/troubleshooting.rst":[{"author":{"_account_id":24828,"name":"Kaifeng Wang","email":"kaifeng.w@gmail.com","username":"wangkf"},"change_message_id":"39251ced8dca76306948624e8cb8e0af75e7ba5c","unresolved":true,"context_lines":[{"line_number":1109,"context_line":"understand **why** cleaning failed. On the simple side of things, this may be"},{"line_number":1110,"context_line":"as simple as a DHCP failure, but on a complex side of things, it could be that"},{"line_number":1111,"context_line":"a cleaning action failed against the underlying hardware, possibly due to"},{"line_number":1112,"context_line":"a hardware failure."},{"line_number":1113,"context_line":""},{"line_number":1114,"context_line":"As such, we encourage everyone to attempt to understand **why** before exiting"},{"line_number":1115,"context_line":"the ``clean failed`` state, because you could potentially make things worse"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a39b0ce_a959bbe6","line":1112,"updated":"2023-01-26 12:55:12.000000000","message":"From my experience networking issue prevails and the ramdisk never got a change to run 😞. The second major reason could be a failed neutron request.","commit_id":"8604a799aa2768b93e3826b1e2c8b543c355282c"},{"author":{"_account_id":24828,"name":"Kaifeng Wang","email":"kaifeng.w@gmail.com","username":"wangkf"},"change_message_id":"39251ced8dca76306948624e8cb8e0af75e7ba5c","unresolved":true,"context_lines":[{"line_number":1129,"context_line":"* If the version of ironic supports the feature, consult the node history"},{"line_number":1130,"context_line":"  log, ``baremetal node history list`` and"},{"line_number":1131,"context_line":"  ``baremetal node history get \u003cuuid\u003e``."},{"line_number":1132,"context_line":"* Consult the acutal console screen of the physical machine. *If* the ramdisk"},{"line_number":1133,"context_line":"  booted, you will generally want to investigate the controller logs and see"},{"line_number":1134,"context_line":"  if an uploaded agent log is being stored on the conductor responsible for"},{"line_number":1135,"context_line":"  the baremetal node. Consult `Retrieving logs from the deploy ramdisk`_."}],"source_content_type":"text/x-rst","patch_set":2,"id":"d0f3c567_0d616bc5","line":1132,"range":{"start_line":1132,"start_character":14,"end_line":1132,"end_character":20},"updated":"2023-01-26 12:55:12.000000000","message":"actual","commit_id":"8604a799aa2768b93e3826b1e2c8b543c355282c"},{"author":{"_account_id":24828,"name":"Kaifeng Wang","email":"kaifeng.w@gmail.com","username":"wangkf"},"change_message_id":"39251ced8dca76306948624e8cb8e0af75e7ba5c","unresolved":true,"context_lines":[{"line_number":1130,"context_line":"  log, ``baremetal node history list`` and"},{"line_number":1131,"context_line":"  ``baremetal node history get \u003cuuid\u003e``."},{"line_number":1132,"context_line":"* Consult the acutal console screen of the physical machine. *If* the ramdisk"},{"line_number":1133,"context_line":"  booted, you will generally want to investigate the controller logs and see"},{"line_number":1134,"context_line":"  if an uploaded agent log is being stored on the conductor responsible for"},{"line_number":1135,"context_line":"  the baremetal node. Consult `Retrieving logs from the deploy ramdisk`_."},{"line_number":1136,"context_line":"  If the node did not boot for some reason, you can typically just retry"}],"source_content_type":"text/x-rst","patch_set":2,"id":"df2b6de9_cbb5e2b0","line":1133,"range":{"start_line":1133,"start_character":53,"end_line":1133,"end_character":63},"updated":"2023-01-26 12:55:12.000000000","message":"this could be a bit ambiguous and could be clarified with the conductor governing the node (another command story). Also there is a configuration option needs to be enabled I guess.","commit_id":"8604a799aa2768b93e3826b1e2c8b543c355282c"}]}