BIGTOP-3460. Extend timeout for Ambari Server setup. (#708)
(cherry picked from commit 87733f52077d54cf0d68502e0d78baab22d2499c)
diff --git a/bigtop-deploy/puppet/modules/ambari/manifests/init.pp b/bigtop-deploy/puppet/modules/ambari/manifests/init.pp
index a8f2219..7143215 100644
--- a/bigtop-deploy/puppet/modules/ambari/manifests/init.pp
+++ b/bigtop-deploy/puppet/modules/ambari/manifests/init.pp
@@ -36,7 +36,11 @@
exec {
"server setup":
command => "/usr/sbin/ambari-server setup -j $(readlink -f /usr/bin/java | sed -e 's@jre/bin/java@@' -e 's@bin/java@@') -s",
- require => [ Package["ambari-server"], Package["jdk"], Exec["mpack install"] ]
+ require => [ Package["ambari-server"], Package["jdk"], Exec["mpack install"] ],
+ # The default timeout is 300 seconds, but it's sometimes too short to setup Ambari Server.
+ # In most of the successful cases, applying puppet manifest finishes within 600 seconds on CI,
+ # so extend the timeout to that value.
+ timeout => 600,
}
service { "ambari-server":
