)]}'
{"cyborg/conf/nvme.py":[{"author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"128c7f15573aa2935a1af1a4700bbf4620aa2bcc","unresolved":false,"context_lines":[{"line_number":22,"context_line":""},{"line_number":23,"context_line":"nvme_opts \u003d ["},{"line_number":24,"context_line":"    cfg.MultiStrOpt("},{"line_number":25,"context_line":"        \u0027device_spec\u0027,"},{"line_number":26,"context_line":"        default\u003d[],"},{"line_number":27,"context_line":"        help\u003d\"\"\""},{"line_number":28,"context_line":"Specifications for NVMe devices to manage."}],"source_content_type":"text/x-python","patch_set":11,"id":"3d73ee54_60f19160","line":25,"updated":"2026-08-14 14:52:45.000000000","message":"The device_spec option defaults to []. For operators, an empty spec in the final NVMe driver series most likely means no NVMe devices are discovered/managed. Neither the help text nor the commit message documents this consequence or that discovery is entirely opt-in.\n\n**Severity**: WARNING | **Confidence**: 0.8\n\n**Impact**: Operators deploying the NVMe support enabled in this series may expect devices to be discovered automatically and see none, with no warning pointing at [nvme]/device_spec as the cause.\n\n**Suggestion**:\nAdd a sentence to the device_spec help text stating that with no device_spec set the NVMe driver discovers no devices (empty spec \u003d discovery disabled), and that multiple device_spec lines may be supplied to match several device classes.","commit_id":"2be9e9d58612fbcd65c1c8b33de260a314851dd0"}]}