I'm doing this in our official puppet container, so the version should be 
aligned. Will dig more into this in the afternoon and report back. Thanks!
--
Regards,
  Cos

On February 28, 2018 2:17:41 AM PST, Olaf Flebbe <o...@oflebbe.de> wrote:
>This may relate to the puppet version change. The gradle command should
>work.
>
>> Am 28.02.2018 um 10:35 schrieb Evans Ye <evan...@apache.org>:
>> 
>> Cos,
>> 
>> Not sure what's the problem you encountered but form
>>
>https://ci.bigtop.apache.org/view/Provisioner/job/Bigtop-trunk-deployments/
>> I can see the Puppet deployment is doing well.
>> 
>> Can you share more info? Env, config, command, etc.
>> 
>> 
>> 2018-02-28 14:34 GMT+08:00 Konstantin Boudnik <c...@apache.org>:
>> 
>>> Guys,
>>> 
>>> I am trying to run the following command:
>>> 
>>> puppet apply -d
>>> --modulepath=bigtop-deploy/puppet/modules:/etc/puppet/modules
>>> bigtop-deploy/puppet/manifests/site.pp
>>> 
>>> from the top-level directory of Bigtop source tree.
>>> 
>>> to deploy some cluster configuration in a container. All I am
>getting
>>> though is this error message:
>>> 
>>> Debug: Caching environment 'production' (ttl = 0 sec)
>>> Error: Could not find class jdk for c41f94213de4 on node
>c41f94213de4
>>> 
>>> Looks like class jdk under bigtop-deploy/puppet/manifests could not
>be
>>> found. The latest change related to this has happened in hash
>40e796b
>>> (made by Kevin), but I am kinda sure I was able to deploy cluster
>>> after that.
>>> 
>>> Did something got changed which I missed and their new rules of
>using
>>> the recipes? Thanks for any leads!
>>> --
>>>  With regards,
>>> Konstantin (Cos) Boudnik
>>> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
>>> 
>>> Disclaimer: Opinions expressed in this email are those of the
>author,
>>> and do not necessarily represent the views of any company the author
>>> might be affiliated with at the moment of writing.
>>> 

Reply via email to