Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Bug 1493554 - Error unexpected QEMU URI path should get handled
Summary: Error unexpected QEMU URI path should get handled
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - libvirt
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-20 13:29 UTC by Nikhil Kathole
Modified: 2019-08-12 14:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-03 19:19:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot of UI (36.08 KB, image/png)
2017-09-20 13:29 UTC, Nikhil Kathole
no flags Details
log in production.log file (26.92 KB, text/plain)
2017-09-20 13:30 UTC, Nikhil Kathole
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 21092 0 Normal New Error unexpected QEMU URI path should get handled 2020-03-19 10:03:53 UTC

Description Nikhil Kathole 2017-09-20 13:29:38 UTC
Created attachment 1328445 [details]
screenshot of UI

Description of problem: We were trying to provision a host. We created libvirt compute resource, providing invalid url and thus while trying compute profile it shows error as "Error making a connection to libvirt URI qemu+tcp:/hostname/system: Call to virConnectOpen failed: internal error: unexpected QEMU URI path,, try qemu:///system".


Version-Release number of selected component (if applicable): satellite 6.3 snap 16


How reproducible: always


Steps to Reproduce:
1. Navigate to Infrastructure -> compute resources 
2. Create libvirt compute resource providing invalid url
3. Try to create compute profile for same libvirt compute resource

Actual results:
Production.log shows 500 internal server error and page shows "Error making a connection to libvirt URI qemu+tcp:/hostname/system: Call to virConnectOpen failed: internal error: unexpected QEMU URI path,, try qemu:///system"

Expected results:
Error should get handled.

Additional info:

Comment 1 Nikhil Kathole 2017-09-20 13:30:02 UTC
Created attachment 1328446 [details]
log in production.log file

Comment 3 Ondřej Pražák 2017-09-25 12:49:12 UTC
Created redmine issue http://projects.theforeman.org/issues/21092 from this bug

Comment 4 Bryan Kearney 2018-10-03 19:19:03 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


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