Bug 1822890

Summary:	Can not enable TCP/IP connection if running virtproxyd in the foreground
Product:	Red Hat Enterprise Linux 9	Reporter:	yafu <yafu>
Component:	libvirt	Assignee:	Virtualization Maintenance <virt-maint>
Status:	CLOSED NOTABUG	QA Contact:	yafu <yafu>
Severity:	low	Docs Contact:
Priority:	low
Version:	9.0	CC:	berrange, chhu, jsuchane, lmen, virt-maint, xuzhang, yalzhang
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-10 07:26:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description yafu 2020-04-10 10:19:46 UTC

Description of problem:
Can not enable TCP/IP connection if running virtproxyd in the foreground

Version-Release number of selected component (if applicable):
libvirt-6.0.0-17.module+el8.2.0+6257+0d066c28.x86_64

How reproducible:
100%

Steps to Reproduce:
1.# virtproxyd -h

Usage:
  virtproxyd [options]

Options:
  -h | --help            Display program help
  -v | --verbose         Verbose messages
  -d | --daemon          Run as a daemon & write PID file
  -t | --timeout <secs>  Exit after timeout period
  -f | --config <file>   Configuration file
  -V | --version         Display version information
  -p | --pid-file <file> Change name of PID file

libvirt management daemon:

  Default paths:
...
2.
3.

Actual results:
No '-l | --listen          Listen for TCP/IP connections' used to enable TCP/IP connection.

Expected results:
No way to enable TCP/IP connection if running virtproxyd in the foreground.

Additional info:

Comment 1 Jaroslav Suchanek 2020-04-14 13:38:04 UTC

Sounds more like missing feature. I am moving that to backlog, Daniel please review if this requires sooner focus. Thanks.

Comment 2 Daniel Berrangé 2020-04-16 13:37:14 UTC

(In reply to yafu from comment #0)
> Description of problem:
> Can not enable TCP/IP connection if running virtproxyd in the foreground
> 
> Version-Release number of selected component (if applicable):
> libvirt-6.0.0-17.module+el8.2.0+6257+0d066c28.x86_64
> 
> How reproducible:
> 100%
> 
> Steps to Reproduce:
> 1.# virtproxyd -h
> 
> Usage:
>   virtproxyd [options]
> 
> Options:
>   -h | --help            Display program help
>   -v | --verbose         Verbose messages
>   -d | --daemon          Run as a daemon & write PID file
>   -t | --timeout <secs>  Exit after timeout period
>   -f | --config <file>   Configuration file
>   -V | --version         Display version information
>   -p | --pid-file <file> Change name of PID file
> 
> libvirt management daemon:
> 
>   Default paths:
> ...
> 2.
> 3.
> 
> Actual results:
> No '-l | --listen          Listen for TCP/IP connections' used to enable
> TCP/IP connection.
> 
> Expected results:
> No way to enable TCP/IP connection if running virtproxyd in the foreground.

This is an intentional difference to libvirtd.

In libvirtd, "listen_tls" libvirtd.conf parameter defaults to 1 if not set. You then have to pass --listen to actually make it take effect.

In virtproxyd, "listen_tls" in virtproxyd.conf defaults to 0, and there is no --listen parameter. To enable TCP you merely need set  listen_tls to 1 in virtproxyd.conf.

Comment 4 John Ferlan 2021-09-08 13:29:51 UTC

Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.

Comment 6 RHEL Program Management 2021-10-10 07:26:54 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.