On 28/09/15 14:01 +0200, dan wrote:
> If I do pcs resource standards
> I get:
> ocf
> lsb
> service
> upstart
> stonith
>
> But if I do pcs resource create XXXX upstart:yyy
> I get:
> Error: Unable to create resource 'upstart:yyy', it is not installed on this
> system (use --force to override)
>
> What can be the problem?
> I I do strace on the above I see that it looks at:
> stat("/usr/lib/ocf/resource.d/heartbeat/upstart:yyy", 0x7ffc8694f6b0) = -1
> ENOENT (No such file or directory)
> stat("/usr/lib/ocf/resource.d/linbit/upstart:yyy", 0x7ffc8694f6b0) = -1
> ENOENT (No such file or directory)
> stat("/usr/lib/ocf/resource.d/pacemaker/upstart:yyy", 0x7ffc8694f6b0) = -1
> ENOENT (No such file or directory)
> stat("/usr/lib/ocf/resource.d/redhat/upstart:yyy", 0x7ffc8694f6b0) = -1
> ENOENT (No such file or directory)This is simply a matter of the development not confronted with the world of proper Upstart jobs so far, hence currently the logic falls through directly to assuming ocf class of resources as a last resort to look the specified resource up. It should likely look at /etc/init[1] directory for the upstart class of resources. [1] http://upstart.ubuntu.com/cookbook/#system-job -- Jan (Poki)
pgpZA88GvBPcb.pgp
Description: PGP signature
_______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
