Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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 1Jaroslav 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.
(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.
Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.
Comment 6RHEL 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.