You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Kengo Seki (Jira)" <ji...@apache.org> on 2020/12/03 10:42:00 UTC

[jira] [Created] (BIGTOP-3460) Extend timeout for Ambari Server setup

Kengo Seki created BIGTOP-3460:
----------------------------------

             Summary: Extend timeout for Ambari Server setup
                 Key: BIGTOP-3460
                 URL: https://issues.apache.org/jira/browse/BIGTOP-3460
             Project: Bigtop
          Issue Type: Improvement
            Reporter: Kengo Seki
            Assignee: Kengo Seki
             Fix For: 1.5.0


I'm testing Bigtop 1.5.0 packages on Jenkins before release, and I found deploying Ambari repeatedly failed with timeout.

{code}
Error: Command exceeded timeout
Error: /Stage[main]/Ambari::Server/Exec[server setup]/returns: change from 'notrun' to ['0'] failed: Command exceeded timeout
{code}

https://ci.bigtop.apache.org/job/Bigtop-1.5.0-smoke-tests/1/COMPONENTS=ambari.bigtop-utils@ambari,OS=centos-8-x86_64-deploy/console
https://ci.bigtop.apache.org/job/Bigtop-1.5.0-smoke-tests/2/COMPONENTS=ambari.bigtop-utils@ambari,OS=centos-8-x86_64-deploy/console

Default timeout may be too strict for Ambari Server setup, so it should be extended.




--
This message was sent by Atlassian Jira
(v8.3.4#803005)