From dahorak at redhat.com Fri Jun 1 12:40:43 2018 From: dahorak at redhat.com (=?UTF-8?Q?Daniel_Hor=c3=a1k?=) Date: Fri, 1 Jun 2018 14:40:43 +0200 Subject: [Tendrl-devel] Old/not required packages in Tendrl cop repos Message-ID: <8e35739f-71cf-8c80-8e88-89c370e6c76d@redhat.com> Hi Tim and all, I've reviewed RPM package validation tests results[1], and there seems to be some (possible) issues in tendrl/release and tendrl/dependencies repos. (tendrl/release) * Packages tendrl-node-selinux and tendrl-server-selinux were replaced by tendrl-selinux, right? Do we need to have the two older (separated) packages still available in the Copr repo? (tendrl/dependencies) * Packages http-parser, http-parser-devel and python2-ruamel-yaml are available also in base CentOS repo and in higher version than what we have in tendrl-dependencies repo. Could it be removed? [1] https://ci.centos.org/view/tendrl-build-release/ Regards, Daniel From rkanade at redhat.com Mon Jun 4 07:56:54 2018 From: rkanade at redhat.com (Rohan Kanade) Date: Mon, 4 Jun 2018 13:26:54 +0530 Subject: [Tendrl-devel] Old/not required packages in Tendrl cop repos In-Reply-To: <8e35739f-71cf-8c80-8e88-89c370e6c76d@redhat.com> References: <8e35739f-71cf-8c80-8e88-89c370e6c76d@redhat.com> Message-ID: @Timothy, Any updates on further action? On Fri, Jun 1, 2018 at 6:10 PM, Daniel Hor?k wrote: > Hi Tim and all, > > I've reviewed RPM package validation tests results[1], and there seems > to be some (possible) issues in tendrl/release and tendrl/dependencies > repos. > > (tendrl/release) > * Packages tendrl-node-selinux and tendrl-server-selinux were replaced > by tendrl-selinux, right? Do we need to have the two older (separated) > packages still available in the Copr repo? > > (tendrl/dependencies) > * Packages http-parser, http-parser-devel and python2-ruamel-yaml are > available also in base CentOS repo and in higher version than what > we have in tendrl-dependencies repo. Could it be removed? > > [1] https://ci.centos.org/view/tendrl-build-release/ > > Regards, > Daniel > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From mbukatov at redhat.com Mon Jun 4 08:10:59 2018 From: mbukatov at redhat.com (Martin Bukatovic) Date: Mon, 4 Jun 2018 10:10:59 +0200 Subject: [Tendrl-devel] large increase of failed unit tests in tendrl Message-ID: <49927650-f9c1-484d-e00c-0f2fb2186dfa@redhat.com> Hi, I just noticed that there is a large increase of failed unit tests in upstream tendrl ci. As you can see here on the chart linked below, while the total number of unit tests increased considerably, the number of failing cases raised even more: https://ci.centos.org/view/Tendrl/job/tendrl-pkgval-5-release-unittests/test/?width=800&height=600 This problem was first observed in job #138 on Jun 1, 2018 11:55 AM, see the full report here: https://ci.centos.org/view/Tendrl/job/tendrl-pkgval-5-release-unittests/138/testReport/ -- Martin Bukatovic USM QE team Red Hat From mbukatov at redhat.com Mon Jun 4 08:14:54 2018 From: mbukatov at redhat.com (Martin Bukatovic) Date: Mon, 4 Jun 2018 10:14:54 +0200 Subject: [Tendrl-devel] large increase of failed unit tests in tendrl In-Reply-To: <49927650-f9c1-484d-e00c-0f2fb2186dfa@redhat.com> References: <49927650-f9c1-484d-e00c-0f2fb2186dfa@redhat.com> Message-ID: <81558ad9-bc89-3971-c6cd-cb9368105f90@redhat.com> On 06/04/2018 10:10 AM, Martin Bukatovic wrote: > I just noticed that there is a large increase of failed unit > tests in upstream tendrl ci. > > As you can see here on the chart linked below, while the total number > of unit tests increased considerably, the number of failing cases > raised even more: > > https://ci.centos.org/view/Tendrl/job/tendrl-pkgval-5-release-unittests/test/?width=800&height=600 > > This problem was first observed in job #138 on Jun 1, 2018 11:55 AM, > see the full report here: > > https://ci.centos.org/view/Tendrl/job/tendrl-pkgval-5-release-unittests/138/testReport/ For reference, there is list of package version from that jenkins job: tendrl-ansible.noarch 0:1.6.3-2.el7.centos tendrl-api.noarch 0:1.6.3-4.el7 tendrl-api-httpd.noarch 0:1.6.3-4.el7 tendrl-collectd-selinux.noarch 0:1.5.4-2.el7.centos tendrl-commons.noarch 0:1.6.3-6.el7 tendrl-gluster-integration.noarch 0:1.6.3-5.el7 tendrl-grafana-plugins.noarch 0:1.6.3-5.el7 tendrl-grafana-selinux.noarch 0:1.5.4-2.el7.centos tendrl-monitoring-integration.noarch 0:1.6.3-5.el7 tendrl-node-agent.noarch 0:1.6.3-6.el7 tendrl-notifier.noarch 0:1.6.3-3.el7.centos tendrl-selinux.noarch 0:1.5.4-2.el7.centos tendrl-ui.noarch 0:1.6.3-3.el7 Taken from https://ci.centos.org/job/tendrl-pkgval-X-release-prepare/318/consoleFull -- Martin Bukatovic USM QE team Red Hat From tjeyasin at redhat.com Tue Jun 5 17:30:11 2018 From: tjeyasin at redhat.com (Timothy Asir Jeyasingh) Date: Tue, 5 Jun 2018 23:00:11 +0530 Subject: [Tendrl-devel] Old/not required packages in Tendrl cop repos In-Reply-To: <8e35739f-71cf-8c80-8e88-89c370e6c76d@redhat.com> References: <8e35739f-71cf-8c80-8e88-89c370e6c76d@redhat.com> Message-ID: On Fri, Jun 1, 2018 at 6:10 PM, Daniel Hor?k wrote: > Hi Tim and all, > > I've reviewed RPM package validation tests results[1], and there seems > to be some (possible) issues in tendrl/release and tendrl/dependencies > repos. > > (tendrl/release) > * Packages tendrl-node-selinux and tendrl-server-selinux were replaced > by tendrl-selinux, right? Do we need to have the two older (separated) > packages still available in the Copr repo? > > Sure, I will remove the older packages. > (tendrl/dependencies) > * Packages http-parser, http-parser-devel and python2-ruamel-yaml are > available also in base CentOS repo and in higher version than what > we have in tendrl-dependencies repo. Could it be removed? > > Yes we can remove http-parser. However we need to check with the latest version of python2-ruamel-yaml. It should not break anything with the latest one. @Daniel Any idea how tendrl works with latest version of this package ? Have you ever tried with latest version of these packages? [1] https://ci.centos.org/view/tendrl-build-release/ > > Regards, > Daniel > From dahorak at redhat.com Wed Jun 6 08:12:30 2018 From: dahorak at redhat.com (=?UTF-8?Q?Daniel_Hor=c3=a1k?=) Date: Wed, 6 Jun 2018 10:12:30 +0200 Subject: [Tendrl-devel] Old/not required packages in Tendrl cop repos In-Reply-To: References: <8e35739f-71cf-8c80-8e88-89c370e6c76d@redhat.com> Message-ID: On 06/05/18 19:30, Timothy Asir Jeyasingh wrote: > > > On Fri, Jun 1, 2018 at 6:10 PM, Daniel Hor?k > wrote: > > Hi Tim and all, > > I've reviewed RPM package validation tests results[1], and there seems > to be some (possible) issues in tendrl/release and tendrl/dependencies > repos. > > (tendrl/release) > * Packages tendrl-node-selinux and tendrl-server-selinux were replaced > ? by tendrl-selinux, right? Do we need to have the two older > (separated) > ? packages still available in the Copr repo? > > Sure, I will remove the older packages. Thanks > (tendrl/dependencies) > * Packages http-parser, http-parser-devel and python2-ruamel-yaml are > ? available also in base CentOS repo and in higher version than what > ? we have in tendrl-dependencies repo. Could it be removed? > > Yes we can remove http-parser. However we need to check with the latest > version of python2-ruamel-yaml. It should not break anything with the > latest one. > > @Daniel Any idea how tendrl works with latest version of this package ? > Have you ever tried with latest version of these packages? @Tim - the version of python2-ruamel-yaml from epel repository is higher, than what we are providing in the tendrl-dependencies repo and tendrl-commons package doesn't depend on specific version. So the newest package will be always installed - which means the version from epel repository: python2-ruamel-yaml.x86_64 0.12.14-9.el7.centos tendrl-dependencies python2-ruamel-yaml.x86_64 0.13.14-1.el7 epel Regards, Daniel > [1] https://ci.centos.org/view/tendrl-build-release/ > > > Regards, > Daniel > > From drive-shares-noreply at google.com Fri Jun 15 10:38:49 2018 From: drive-shares-noreply at google.com (Neha Gupta (via Google Docs)) Date: Fri, 15 Jun 2018 10:38:49 +0000 Subject: [Tendrl-devel] Steps for making upstream release for a component - Invitation to edit References: <5f469ae6-869c-4454-9689-6e34cabc29f9@docs-share.google.com> Message-ID: <0000000000003b880d056eabd2bb@google.com> I've shared an item with you: Steps for making upstream release for a component https://docs.google.com/document/d/1xvsTtNr2FxITzod4c87670EcKovwo-H8RScZ67XeXnE/edit?usp=sharing&invite=CJm4ufYI&ts=5b239739 It's not an attachment -- it's stored online. To open this item, just click the link above. From mbukatov at redhat.com Mon Jun 18 08:38:14 2018 From: mbukatov at redhat.com (Martin Bukatovic) Date: Mon, 18 Jun 2018 10:38:14 +0200 Subject: [Tendrl-devel] release in rpm spec file Message-ID: Hi, I just reverted the following commit in tendrl-ansible, because it did an invalid update of the spec file: ~~~ commit 4b82af403c495866ba87727feb39e8a9071173fb Author: Rohan Kanade Date: Wed May 16 12:19:29 2018 +0530 Update tendrl-ansible.spec diff --git a/tendrl-ansible.spec b/tendrl-ansible.spec index 66bc61b..71f562b 100644 --- a/tendrl-ansible.spec +++ b/tendrl-ansible.spec @@ -4,7 +4,7 @@ Name: tendrl-ansible Version: 1.6.3 -Release: 1%{?dist} +Release: 2%{?dist} Summary: Ansible roles and playbooks for Tendrl License: LGPLv2.1 @@ -86,6 +86,9 @@ yamlint $RPM_BUILD_ROOT && rm .yamlint %license %{_pkgdocdir}/LICENSE %changelog +* Wed May 16 2018 Rohan Kanade - 1.6.3-2 +- New build for upstream Tendrl v1.6.3 + * Mon Apr 16 2018 Martin Bukatovi? - 1.6.3-1 - New build for upstream Tendrl v1.6.3 ~~~ The Release in rpm spec file is tracking changes in the spec file itself (including patches applied during rpm build) and consequently builds itself. Updating just release and nothing else doesn't make sense. Example of a change when it makes sense to bump Release is eg. change minimal version of ansible specified in Requires. -- Martin Bukatovic USM QE team Red Hat From dahorak at redhat.com Tue Jun 19 10:46:32 2018 From: dahorak at redhat.com (=?UTF-8?Q?Daniel_Hor=c3=a1k?=) Date: Tue, 19 Jun 2018 12:46:32 +0200 Subject: [Tendrl-devel] Failing cluster import: Setting up cluster aliasnot yet complete. Timing out. Message-ID: <091fe1df-f79c-8ac4-946b-c9288d14b561@redhat.com> 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/import_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 From mbukatov at redhat.com Wed Jun 20 17:46:04 2018 From: mbukatov at redhat.com (Martin Bukatovic) Date: Wed, 20 Jun 2018 19:46:04 +0200 Subject: [Tendrl-devel] status of unit tests Message-ID: <18b42aa5-7c66-0b18-1b69-ddaa3ed6d318@redhat.com> Dear all, the status of unit test rerun results in CentOS CI got fixed, as can bee seen in this jenkins chart: https://ci.centos.org/view/Tendrl/job/tendrl-pkgval-5-release-unittests/test/?width=800&height=600 Thank you for getting this back on track. In the rerun from today, there are only 4 test failures (out of 271 test cases): https://ci.centos.org/view/Tendrl/job/tendrl-pkgval-5-release-unittests/158/testReport/ Could we get these remaining 4 fixed as well, so that we can start fully enforcing unit tests before merging code? -- Martin Bukatovic USM QE team Red Hat