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.
Created attachment 1029882[details]
host_not found error on toggling manage/unmanged host
Description of problem:
I discovered a host and when I tried to provision that manually I clicked on 'provision'. On Edit host form, found two buttons:
- unmanaged host and
- disassociate host
On clicking any of them, page is redirected and throws error:
'Host Not found'
production.log:
===============
2015-05-26 13:45:39 [I] Processing by HostsController#toggle_manage as HTML
2015-05-26 13:45:39 [I] Parameters: {"authenticity_token"=>"2SBPzy2vKKZsPlLWEvgPWBmq3WnO+Q3eNSYJQCPfHDE=", "id"=>"mac5254007e20b8"}
2015-05-26 13:45:39 [I] Rendered common/404.html.erb within layouts/application (1.8ms)
2015-05-26 13:45:39 [I] Rendered layouts/base.html.erb (1.8ms)
2015-05-26 13:45:39 [I] Completed 404 Not Found in 33ms (Views: 6.8ms | ActiveRecord: 2.8ms)
on_clicking disassociate host:
============================
2015-05-26 13:47:25 [I] Processing by HostsController#disassociate as HTML
2015-05-26 13:47:25 [I] Parameters: {"authenticity_token"=>"2SBPzy2vKKZsPlLWEvgPWBmq3WnO+Q3eNSYJQCPfHDE=", "id"=>"mac5254007e20b8"}
2015-05-26 13:47:25 [I] Rendered common/404.html.erb within layouts/application (2.4ms)
2015-05-26 13:47:25 [I] Rendered layouts/base.html.erb (1.6ms)
2015-05-26 13:47:25 [I] Completed 404 Not Found in 38ms (Views: 7.4ms | ActiveRecord: 3.6ms)
Version-Release number of selected component (if applicable):
sat6.1 GA snap5
How reproducible:
always
Steps to Reproduce:
1. discover a host
2. provision it
3.
Actual results:
on edit host page, on clicking unmanaged host or disassociate host throws 'Host not found error on UI.
Expected results:
First I'm not sure what's the purpose of these buttons. I *think* this is to make managed or unmanaged host or to disassociate a host from a VM image.
But if these are not relevant anyway with discovery then we should disable them while provisioning a discovered host.
Additional info:
This is an older bug which I do not envision being fixed in the near term. I am closing this out. If you belive doing so is an issue, please feel free to re-open and provide additional business information. Thank you.
Created attachment 1029882 [details] host_not found error on toggling manage/unmanged host Description of problem: I discovered a host and when I tried to provision that manually I clicked on 'provision'. On Edit host form, found two buttons: - unmanaged host and - disassociate host On clicking any of them, page is redirected and throws error: 'Host Not found' production.log: =============== 2015-05-26 13:45:39 [I] Processing by HostsController#toggle_manage as HTML 2015-05-26 13:45:39 [I] Parameters: {"authenticity_token"=>"2SBPzy2vKKZsPlLWEvgPWBmq3WnO+Q3eNSYJQCPfHDE=", "id"=>"mac5254007e20b8"} 2015-05-26 13:45:39 [I] Rendered common/404.html.erb within layouts/application (1.8ms) 2015-05-26 13:45:39 [I] Rendered layouts/base.html.erb (1.8ms) 2015-05-26 13:45:39 [I] Completed 404 Not Found in 33ms (Views: 6.8ms | ActiveRecord: 2.8ms) on_clicking disassociate host: ============================ 2015-05-26 13:47:25 [I] Processing by HostsController#disassociate as HTML 2015-05-26 13:47:25 [I] Parameters: {"authenticity_token"=>"2SBPzy2vKKZsPlLWEvgPWBmq3WnO+Q3eNSYJQCPfHDE=", "id"=>"mac5254007e20b8"} 2015-05-26 13:47:25 [I] Rendered common/404.html.erb within layouts/application (2.4ms) 2015-05-26 13:47:25 [I] Rendered layouts/base.html.erb (1.6ms) 2015-05-26 13:47:25 [I] Completed 404 Not Found in 38ms (Views: 7.4ms | ActiveRecord: 3.6ms) Version-Release number of selected component (if applicable): sat6.1 GA snap5 How reproducible: always Steps to Reproduce: 1. discover a host 2. provision it 3. Actual results: on edit host page, on clicking unmanaged host or disassociate host throws 'Host not found error on UI. Expected results: First I'm not sure what's the purpose of these buttons. I *think* this is to make managed or unmanaged host or to disassociate a host from a VM image. But if these are not relevant anyway with discovery then we should disable them while provisioning a discovered host. Additional info: