Bug 52564 – The Veyon backend fails to update client info if one host is not reachable

Bug 52564 - The Veyon backend fails to update client info if one host is not reachable


Summary:	The Veyon backend fails to update client info if one host is not reachable

Status:	VERIFIED WORKSFORME

Product:	UCS@school
Classification:	Unclassified
Component:	UMC - Computer room
Version:	UCS@school 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS@school 4.4 v9
Assigned To:	UCS@school maintainers
QA Contact:	Tobias Wenzel

URL:
Keywords:

Depends on:
Blocks:	52522 52915 52922
	Show dependency tree / graph

Reported:	2021-01-08 12:31 CET by Daniel Tröder
Modified:	2021-03-16 15:28 CET (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Daniel Tröder

2021-01-08 12:31:52 CET

+++ This bug was initially created as a clone of Bug #52522 +++

Computerrooms that are configured as using the Veyon backend should also finally be using the veyon backend for computerroom operations.

--------------------------------------------------------------------

If one computer in a computer room cannot be communicated with by the Veyon proxy, it hangs a long time waiting for it. In that time updates for other hosts are blocked. It's a blocking HTTP API…

As computers in computer rooms can have multiple IPs and can be turned off, the Veyon backend stack of the computer room module must handle such situations in a way that does not block any functionality of running & reachable hosts.

Comment 1 Ole Schwiegert

2021-02-05 10:06:11 CET

Tobias J. fixed this problem and implemented a non blocking API.
No code changes for this were necessary on our side.

Comment 2 Tobias Wenzel

2021-02-22 11:33:55 CET

QA → Verified

Tested with two computers, one with non-reachable IP: The computer room module worked as expected (no hanging).