rhtconsulting / puppet-jboss_admin

Puppet module for runtime configuration of a JBoss container
MIT License
15 stars 12 forks source link

Could not prefetch jboss_resource provider 'cli': 399: unexpected token at 'timeout: failed to run command '/usr/share/jbossas/bin/jboss-cli.sh': No such file or directory]' #80

Closed itewk closed 7 years ago

itewk commented 9 years ago

I have no clue why but in my lab environment whenever I create a new VM on the first puppet run I get this error:

Could not prefetch jboss_resource provider 'cli': 399: unexpected token at 'timeout: failed to run command '/usr/share/jbossas/bin/jboss-cli.sh': No such file or directory]'

On the second puppet run everything works fine.

it is important to note on the first puppet run Jboss has not installed itself yet. On the second puppet run though JBoss has still not yet installed because the first puppet run failed, but on the second run puppet installs jboss and then jboss_admin does its thing without error.

For some reason on the first puppet run all of my attempts at forceing puppet to install jboss and start it before doing any jboss_admin work is just ignored. But then on the second puppet run it works.

@cpitman any smart ideas?

ldomb commented 9 years ago

That might be because the dependencies (require, include, contain) are not written correctly. On Jun 22, 2015 4:49 PM, "Ian Tewksbury" notifications@github.com wrote:

I have no clue why but in my lab environment whenever I create a new VM on the first puppet run I get this error:

Could not prefetch jboss_resource provider 'cli': 399: unexpected token at 'timeout: failed to run command '/usr/share/jbossas/bin/jboss-cli.sh': No such file or directory]'

On the second puppet run everything works fine.

it is important to note on the first puppet run Jboss has not installed itself yet. On the second puppet run though JBoss has still not yet installed because the first puppet run failed, but on the second run puppet installs jboss and then jboss_admin does its thing without error.

For some reason on the first puppet run all of my attempts at forceing puppet to install jboss and start it before doing any jboss_admin work is just ignored. But then on the second puppet run it works.

@cpitman https://github.com/cpitman any smart ideas?

— Reply to this email directly or view it on GitHub https://github.com/cpitman/puppet-jboss_admin/issues/80.

itewk commented 9 years ago

@idomb,

Iv checked and rechecked and checked again my ordering and it is all correct. I think for some reason the prefetch is ignoring the order, but that is just a hypothesis.

itewk commented 7 years ago

I no longer see this. Closing.