[
https://issues.apache.org/jira/browse/BIGTOP-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13972302#comment-13972302
]
Evans Ye commented on BIGTOP-1163:
----------------------------------
Allow me to explain this clearly.
This bug will not be introduced while provisioning a new cluster.
The problem here is that for an existing running cluster, you have oozie db
running when you try to apply some changes like configurations or components by
running puppet apply again. At that moment you'll get an error shows that
{{Exec[Oozie DB init]}} failed, which will be sort of confusing since we don't
know what if there is actually an error occurred in my environment or not.
Here's the reproduce steps using
[vagrant-puppet|https://github.com/apache/bigtop/tree/master/bigtop-deploy/vm/vagrant-puppet]:
1.) specify oozie to be deployed in the cluster
{code}
...
jdk_package_name,java-1.7.0-openjdk-devel.x86_64
components,hadoop,hbase,oozie
EOF
...
{code}
2.) Spin up the cluster, which will succeed
{code}
$ ./startup.sh --cluster
{code}
3.) run puppet apply again
{code}
$ vagrant provision --provision-with puppet
{code}
This will introduce the problem.
> puppet apply shows db init error if the oozie server is already running
> -----------------------------------------------------------------------
>
> Key: BIGTOP-1163
> URL: https://issues.apache.org/jira/browse/BIGTOP-1163
> Project: Bigtop
> Issue Type: Improvement
> Components: Deployment
> Affects Versions: 0.4.0
> Reporter: Evans Ye
> Priority: Minor
> Fix For: 0.8.0
>
> Attachments: BIGTOP-1163.1.patch
>
>
> When deploying hadoop with bigtop's puppet scripts, it will output error
> message like below If the oozie server is already running.
> {code}
> debug: Exec[Oozie DB init](provider=posix): Executing '/etc/init.d/oozie init'
> debug: Executing '/etc/init.d/oozie init'
> err: /Stage[main]/Hadoop_head_node/Hadoop-oozie::Server[oozie
> server]/Exec[Oozie DB init]/returns: change from notrun to 0 failed:
> /etc/init.d/oozie init returned 1 instead of one of [0] at
> /home/vagrant/bigtop/bigtop-deploy/puppet/modules/hadoop-oozie/manifests/init.pp:46
> notice: /Stage[main]/Hadoop_head_node/Hadoop-oozie::Server[oozie
> server]/Service[oozie]: Dependency Exec[Oozie DB init] has failures: true
> warning: /Stage[main]/Hadoop_head_node/Hadoop-oozie::Server[oozie
> server]/Service[oozie]: Skipping because of failed dependencies
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
