| Summary: | [console] port=-1 may break some specific clients. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Germano Veit Michel <gveitmic> |
| Component: | ovirt-engine | Assignee: | Nobody <nobody> |
| Status: | CLOSED NOTABUG | QA Contact: | meital avital <mavital> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.0.3 | CC: | gklein, lsurette, rbalakri, Rhev-m-bugs, srevivo, ykaul |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-24 02:48:00 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Spice | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Germano Veit Michel
2016-09-30 01:42:04 UTC
What will the client do when they suddenly do not receive the port at all? (In reply to Yaniv Kaul from comment #1) > What will the client do when they suddenly do not receive the port at all? Hopefully it will do what it is supposed to do: stop misinterpreting the non secure port, since it's not there anymore, and use the tls-port. And if it still doesn't work, then the client must be fixed. We do use the -1 value in libvirt xml/vdsm/ovirt but I am not really sure if it should be presented to a console client too. Seems like adding useless information, doesn't it? Just to be clear, I don't see this as a bug on the engine, but more like something that perhaps could be improved for simplicity and better compatibility. We are actually trying to reproduce it since the IGEL client is based on Ubuntu LTS. If we do, I'll update the BZ. |