Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
'Virtual Machines' tab on the Compute Resources(type vmware) page shows-
There was an error listing VMs: 500 Internal Server Error
Version-Release number of selected component (if applicable):
satellite-6.4.1-1.el7sat.noarch
foreman-vmware-1.18.0.39-1.el7sat.noarch
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Compute Resources>vmware compute resoure> 'Virtual Machines' tab shows '500 Internal Server Error'
Expected results:
Instead of a generic 500 ISE, more accurate error should be propagated from vCenter to the Satellite webUI.
Additional info:
foreman production log shows-
Failed generating link using ["%2fvmfs%2fvolumes%3f6c30ea7e-f4c0c20d-6bea-3091404632fc%2f<VM-NAME>%2fVM-NAME", {:controller=>"compute_resources_vms", :action=>"show", :use_route=>"compute_resource_vm", :compute_resource_id=>#<Foreman::Model::Vmware id: 3, name: "Datacenter", description: "VMWare DC", url: "<datacenter.url.com>", user: "dc-user\\dc-pwd", password: +FILTERED+ uuid: "Datacenter", type: "Foreman::Model::Vmware", created_at: "2018-12-07 08:55:09", updated_at: "2019-01-24 13:35:04", attrs: {:setpw=>0, :display=>"vmrc", :pubkey_hash=>""}, email: nil, caching_enabled: true, domain: nil, http_proxy_id: nil>, :id=>nil}, {}]
ActionController::UrlGenerationError: No route matches {:action=>"show", :compute_resource_id=>#<Foreman::Model::Vmware id: 3, name: "Datacenter", description: "VMWare DC", url: "<datacenter.url.com>", user: "dc-user\\dc-pwd", password: +FILTERED+ uuid: "Datacenter", type: "Foreman::Model::Vmware", created_at: "2018-12-07 08:55:09", updated_at: "2019-01-24 13:35:04", attrs: {:setpw=>0, :display=>"vmrc", :pubkey_hash=>""}, email: nil, caching_enabled: true, domain: nil, http_proxy_id: nil>, :controller=>"compute_resources_vms", :id=>nil}, possible unmatched constraints: [:id]
above trace shows the reference to a disk file and not an real VM. After removing this reference from the compute resource, virtual machines tab is rendering fine.
Note: We have tried to reproduce the issue but in vain. Customer is also unable to provide the steps to reproduce it. Raising this BZ to check the possibility to handle such scenario by passing-on the the accurate error from vCenter to the Satellite webUI. Which would help user to let them know that there is something wrong with the vCenter configuration.
Description of problem: 'Virtual Machines' tab on the Compute Resources(type vmware) page shows- There was an error listing VMs: 500 Internal Server Error Version-Release number of selected component (if applicable): satellite-6.4.1-1.el7sat.noarch foreman-vmware-1.18.0.39-1.el7sat.noarch How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Compute Resources>vmware compute resoure> 'Virtual Machines' tab shows '500 Internal Server Error' Expected results: Instead of a generic 500 ISE, more accurate error should be propagated from vCenter to the Satellite webUI. Additional info: foreman production log shows- Failed generating link using ["%2fvmfs%2fvolumes%3f6c30ea7e-f4c0c20d-6bea-3091404632fc%2f<VM-NAME>%2fVM-NAME", {:controller=>"compute_resources_vms", :action=>"show", :use_route=>"compute_resource_vm", :compute_resource_id=>#<Foreman::Model::Vmware id: 3, name: "Datacenter", description: "VMWare DC", url: "<datacenter.url.com>", user: "dc-user\\dc-pwd", password: +FILTERED+ uuid: "Datacenter", type: "Foreman::Model::Vmware", created_at: "2018-12-07 08:55:09", updated_at: "2019-01-24 13:35:04", attrs: {:setpw=>0, :display=>"vmrc", :pubkey_hash=>""}, email: nil, caching_enabled: true, domain: nil, http_proxy_id: nil>, :id=>nil}, {}] ActionController::UrlGenerationError: No route matches {:action=>"show", :compute_resource_id=>#<Foreman::Model::Vmware id: 3, name: "Datacenter", description: "VMWare DC", url: "<datacenter.url.com>", user: "dc-user\\dc-pwd", password: +FILTERED+ uuid: "Datacenter", type: "Foreman::Model::Vmware", created_at: "2018-12-07 08:55:09", updated_at: "2019-01-24 13:35:04", attrs: {:setpw=>0, :display=>"vmrc", :pubkey_hash=>""}, email: nil, caching_enabled: true, domain: nil, http_proxy_id: nil>, :controller=>"compute_resources_vms", :id=>nil}, possible unmatched constraints: [:id] above trace shows the reference to a disk file and not an real VM. After removing this reference from the compute resource, virtual machines tab is rendering fine. Note: We have tried to reproduce the issue but in vain. Customer is also unable to provide the steps to reproduce it. Raising this BZ to check the possibility to handle such scenario by passing-on the the accurate error from vCenter to the Satellite webUI. Which would help user to let them know that there is something wrong with the vCenter configuration.