Created attachment 1437423 [details] logs and configuration files Description of problem: Sometimes cluster import fails with error ``` Failure in Job d05a77ac-b366-43b9-81fa-ba870966ac70 Flow tendrl.flows.ImportCluster with error: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/tendrl/commons/jobs/__init__.py", line 233, in process_job the_flow.run() File "/usr/lib/python2.7/site-packages/tendrl/commons/flows/import_cluster/__init__.py", line 40, in run "Cluster with name: %s already exists" % short_name FlowExecutionFailedError: Cluster with name: cluster1 already exists ``` when imported with specified Cluster Name. It happens on a fresh setup where import didn't happen yet. There are more errors in import job: ``` Failure in Job 99d8c8a6-a39e-4246-81f8-b46d99eb7c82 Flow tendrl.flows.ImportCluster with error: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/tendrl/commons/jobs/__init__.py", line 233, in process_job the_flow.run() File "/usr/lib/python2.7/site-packages/tendrl/commons/flows/import_cluster/__init__.py", line 123, in run raise ex AtomExecutionFailedError: Atom Execution failed. Error: Error executing atom: tendrl.objects.Cluster.atoms.ImportCluster on flow: Import existing Gluster Cluster Failed atom: tendrl.objects.Cluster.atoms.ImportCluster on flow: Import existing Gluster Cluster Could not find atom tendrl.objects.Cluster.atoms.ImportCluster ``` Version-Release number of selected component (if applicable): tendrl-ansible-1.6.3-3.el7rhgs.noarch tendrl-api-1.6.3-3.el7rhgs.noarch tendrl-api-httpd-1.6.3-3.el7rhgs.noarch tendrl-commons-1.6.3-4.el7rhgs.noarch tendrl-gluster-integration-1.6.3-2.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-2.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-2.el7rhgs.noarch tendrl-node-agent-1.6.3-4.el7rhgs.noarch tendrl-notifier-1.6.3-2.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-1.el7rhgs.noarch How reproducible: 20% Steps to Reproduce: 1. Install WA. 2. Import cluster, set Cluster Name parameter. 3. Open task detail. Actual results: In some cases there happens to appear an error and import fails. Expected results: Import should succeed. Additional info: In attachment are logs and configuration files from setup where this happened collected by https://github.com/usmqe/usmqe-setup/blob/master/qe_evidence.tendrl.yml
Created attachment 1437424 [details] Cluster Import screen
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-2018:2616