Bug 1728306
| Summary: | [Discovery] 'Create Host' and 'Customize Host' buttons not functionoing in Quick Provision dialog | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Jitendra Yejare <jyejare> | ||||
| Component: | Discovery Plugin | Assignee: | Lukas Zapletal <lzap> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Jitendra Yejare <jyejare> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.6.0 | CC: | apatel, asharvit, dvoss, egolov, lzap, mhulan, ohadlevy, rabajaj, spetrosi, walden | ||||
| Target Milestone: | 6.6.0 | Keywords: | Regression, Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | tfm-rubygem-foreman_discovery-15.0.2 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: |
When you discover a host in the Satellite web UI, the Provision button at the Select Action list does not work. Instead, navigate to Hosts > Discovered Hosts and click Provision to the right of the host that you want.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-10-22 12:47:50 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: | |||||||
| Attachments: |
|
||||||
|
Description
Jitendra Yejare
2019-07-09 15:27:36 UTC
Created attachment 1588795 [details]
Non-Functioning-Buttons
There's a workaround for the same functionality in UI that works Steps to Reproduce: 1. Discover the host in the satellite. 2. Create an hostgroup for provisioning the above-discovered host. 3. Go to Hosts -> Discovered Hosts. 4. Don't go to discovered host detail page, instead on the table row, navigate to right and click Provision 5. From Provision dialog, choose HostGroup, Org, and Location. 6. Click 'Create Host' or 'Customize Host' button. This flow (change is in step 4) works fine. Another finding - if you go to detail page and back using breadcrumbs, even there it stops working. If you go to the discovered host detail page and refresh it, the it even works there. Meaning this has something to do with turbolinks/react. Sadly I don't see any JS error in the console. @Marek, To be noted : Nikhil tried on Firefox 60.6 and this bug is not reproducible in Firefox 60.6. But it's reproducible for me every-time when I tried on my firefox Quantum 66.0.4 Also, I tried your steps from comment 9, but again it lands me to the same dialog and again its reproducible for me on Firefox Quantum 66.0.4 Hello guys, I am aware that this *randomly* happens but I have no idea why. This probably needs some JS expert to take a look. Since refreshing a page does help, can we remove blocker for beta? This is not regression in 6.6, I can confirm this misbehavior for years (6.4+ at least). Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27278 has been resolved. Yeah the GEM was just released. Thanks for help with this one! Verified! @ Satellite 6.6 snap 17 Steps: 1. Discover the host in the satellite. 2. Create an hostgroup for provisioning the above-discovered host. 3. Go to Hosts -> Discovered Hosts. 4. Select the discovered host by clicking on the discovered hostname. 5. From 'Select Action' choose 'Provision'. 6. From Provision dialog, choose HostGroup, Org, and Location. 7. Click 'Create Host' or 'Customize Host' button. Observation: The buttons are now functioning and after clicking, its navigating to the host create page. (Automation Test - Jenkins - automation-6.6-tier3-rhel7 - #26 Satellite 6.6.0-17.0 - Test Results - tests.foreman.ui - test_discoveredhost - test_positive_provision_using_quick_host_button) Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:3172 |