Bug 1225001
| Summary: | On clicking 'unmanaged host' or 'disassociate host' while provisioning a discovered host throws 'Host not found' error on UI. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Sachin Ghai <sghai> | ||||
| Component: | Discovery Plugin | Assignee: | orabin | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Sachin Ghai <sghai> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.1.0 | CC: | bbuckingham, bkearney, lzap | ||||
| Target Milestone: | Unspecified | Keywords: | Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-01-05 14:09:20 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: | |||||||
| Bug Depends On: | 1190570 | ||||||
| Bug Blocks: | 1193977 | ||||||
| Attachments: |
|
||||||
Thanks, not a blocker definitely. Marking as low severity as these buttons needs to be hidden for discovery as they are not related. 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: