From julim at redhat.com  Tue Jul  3 14:27:15 2018
From: julim at redhat.com (Ju Lim)
Date: Tue, 3 Jul 2018 10:27:15 -0400
Subject: [Tendrl-devel] Failing cluster import: Setting up cluster
 aliasnot yet complete. Timing out.
In-Reply-To: <091fe1df-f79c-8ac4-946b-c9288d14b561@redhat.com>
References: <091fe1df-f79c-8ac4-946b-c9288d14b561@redhat.com>
Message-ID: <CAKcuoAnQ+eMq_yHomWtiqL4zA5iZccz1ZVvPq1gqwLxPEPLm9g@mail.gmail.com>

Daniel:

I don't this issue has been resolved yet -- see

Sometimes monitoring-integration is not up (
https://github.com/Tendrl/tendrl-ansible/issues/95).  I am facing the same
issue myself.


Thanks,
Ju

On Tue, Jun 19, 2018 at 6:46 AM, Daniel Hor?k <dahorak at redhat.com> wrote:

> Hello,
>
> There seems to be some problem with importing Gluster cluster into
> Tendrl in the last days (or weeks).
>
> Import cluster tasks is failing with following error,
> but quite often the overall status is Completed:
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> * error
>   Failure in Job 8dbf2e9f-a80c-40f1-b0d5-517b56f6906c
>   Flow tendrl.flows.ImportCluster with error:
>   Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/tendrl/commons/jobs/__init__.py",
>     line 242,
>     in process_job the_flow.run()
>   File "/usr/lib/python2.7/site-packages/tendrl/commons/flows/impor
> t_cluster/__init__.py",
>     line 124,
>     in run raise ex AtomExecutionFailedError: Atom Execution failed.
>   Error: Error executing post run function:
>     tendrl.objects.Cluster.atoms.SetupClusterAlias
>
> * error
>   Failed post-run:
>     tendrl.objects.Cluster.atoms.SetupClusterAlias for flow:
>     Import existing Gluster Cluster
>
> * error
>   Setting up cluster aliasnot yet complete. Timing out.
>   (7c104bfb-1bd8-4bf2-bcd4-d880e1c4db59)
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> There were some timing issues causing failures in our import test
> previously, so I'm not sure when exactly this particular issue appears.
>
> CI jobs in CentOS CI are probably failing with the same error.
>
> I'm not sure, if it is problem with Tendrl, or in (version of) Gluster.
>
> Tendrl Server:
>   CentOS Linux release 7.5.1804 (Core)
>   tendrl-ansible-1.6.3-2.el7.centos.noarch
>   tendrl-api-1.6.3-4.el7.noarch
>   tendrl-api-httpd-1.6.3-4.el7.noarch
>   tendrl-commons-1.6.3-7.el7.noarch
>   tendrl-grafana-plugins-1.6.3-6.el7.noarch
>   tendrl-grafana-selinux-1.5.4-2.el7.centos.noarch
>   tendrl-monitoring-integration-1.6.3-6.el7.noarch
>   tendrl-node-agent-1.6.3-7.el7.noarch
>   tendrl-notifier-1.6.3-4.el7.noarch
>   tendrl-selinux-1.5.4-2.el7.centos.noarch
>   tendrl-ui-1.6.3-4.el7.noarch
>
> Gluster Storage Nodes:
>   CentOS Linux release 7.5.1804 (Core)
>   glusterfs-4.2dev-0.99.git1058185.el7.x86_64
>   glusterfs-api-4.2dev-0.99.git1058185.el7.x86_64
>   glusterfs-cli-4.2dev-0.99.git1058185.el7.x86_64
>   glusterfs-client-xlators-4.2dev-0.99.git1058185.el7.x86_64
>   glusterfs-events-4.2dev-0.99.git1058185.el7.x86_64
>   glusterfs-fuse-4.2dev-0.99.git1058185.el7.x86_64
>   glusterfs-geo-replication-4.2dev-0.99.git1058185.el7.x86_64
>   glusterfs-libs-4.2dev-0.99.git1058185.el7.x86_64
>   glusterfs-server-4.2dev-0.99.git1058185.el7.x86_64
>   python2-gluster-4.2dev-0.99.git1058185.el7.x86_64
>   tendrl-collectd-selinux-1.5.4-2.el7.centos.noarch
>   tendrl-commons-1.6.3-7.el7.noarch
>   tendrl-gluster-integration-1.6.3-6.el7.noarch
>   tendrl-node-agent-1.6.3-7.el7.noarch
>   tendrl-selinux-1.5.4-2.el7.centos.noarch
>
> Are you observing similar issue?
>
> Thanks,
> Daniel
>
> _______________________________________________
> Tendrl-devel mailing list
> Tendrl-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/tendrl-devel
>