Description of problem: Right after I created Import cluster job via UI there was some delay before `Import` button on Clusters page become disabled so I clicked on it again and created another Import job for the same cluster. One of the jobs failed and the second job successfully finished. Version-Release number of selected component (if applicable): tendrl-node-agent-1.5.4-8.el7rhgs.noarch tendrl-notifier-1.5.4-5.el7rhgs.noarch tendrl-selinux-1.5.4-1.el7rhgs.noarch tendrl-commons-1.5.4-5.el7rhgs.noarch tendrl-api-1.5.4-3.el7rhgs.noarch tendrl-api-httpd-1.5.4-3.el7rhgs.noarch tendrl-monitoring-integration-1.5.4-8.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-1.el7rhgs.noarch tendrl-ansible-1.5.4-2.el7rhgs.noarch tendrl-ui-1.5.4-4.el7rhgs.noarch tendrl-grafana-plugins-1.5.4-8.el7rhgs.noarch How reproducible: 80% Steps to Reproduce: 1. Import cluster via UI. 2. Right after job creation click on `Clusters` in left menu. There is a chance that `Import` button for the cluster is not disabled yet. 3. Click on `Import` again and create second Import cluster job. 4. Wait for jobs to be processed. Actual results: It takes a while before the button `Import` is disabled (after a few seconds it is disabled) and user is able to create two Import jobs for the same cluster from the same browser. There are created two jobs for Cluster import. One fails and one finishes. Expected results: Right after the cluster job is created the `Import` button should be disabled. Additional info:
There is no impact on the functionality. As sankarshan mentioned above its a hit or miss case. In case if this happens, back-end processes only one job and the second job is clearly marked as failed.
Is this still valid issue?
(In reply to Shubhendu Tripathi from comment #5) > Is this still valid issue? Lets reopen if it is.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days