Skip to content

docs(KOB-54041): update docs and release note #689

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
IT-Kobiton wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(KOB-54041): update docs and release note #689

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions docs/modules/release-notes/partials/KOB-54041.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
// Release-note partial generated by Robot Ranch for docs-team review.
// Do not publish without review.

== virtualUSB

- Saving host machine settings in *Device Management* no longer disables virtualUSB on host machines with routing managed by Kobiton. Previously, after a save, the *Connect* button could become unavailable in the virtualUSB app, and the virtualUSB CLI rejected connections with "This device does not support virtualUsb feature yet."
- Host machines that were set up for virtualUSB before host machine settings moved to *Device Management* now show as self-managed and continue to connect.

// REVIEWER NOTE: "Routing managed by Kobiton" is the public label used on the 2026-09-18
// release page for the virtualUSB tab. The Jira evidence describes the affected machines in
// internal routing terms; confirm with engineering that the two are the same before
// publishing.
//
// REVIEWER NOTE: The Jira summary and description describe the bug as all earlier-configured
// virtualUSB machines failing after the virtualUSB 2 backend release. The resolution field
// describes the root cause as host machine settings saves clearing connection details. Both
// produce the same customer symptom. Confirm the framing before publishing.
//
// REVIEWER NOTE: The fix is live in production since 2026-09-14 per the Jira resolution
// field. Assign this partial to the matching Cloud release page; no release date is set here.
//
// REVIEWER NOTE: The ticket's database-level workaround is operator-only and was omitted.

// Source: KOB-54041
Loading