Hi all,
The error message comes from pcs.
Pacemaker doesn't allow '@' to be used in a resource name. The name is
an XML ID and those cannot contain '@' (and some other) characters. If
pcs allowed '@' in the resource name, pacemaker would reject such a CIB.
As long as this is the case, there's
On Sat, Feb 20, 2021 at 09:35:33AM +, lejeczek wrote:
> -> $ pcs resource create "dropbox\@me" systemd:"dropbox\@me"
>
> as you can see I've been trying to escape '@' too, in various ways, to no
> avail.
Right, but just changing the resource name should work:
$ pcs resource create dropbox_
On 19/02/2021 19:50, Ken Gaillot wrote:
On Fri, 2021-02-19 at 19:13 +, lejeczek wrote:
Hi guys.
I wonder if there is presently a way to create systemd type
of resources when service definition contains '@' ?
That is is a common practice I'm sure you know, where you
can have systemd servi
Hi guys.
I wonder if there is presently a way to create systemd type
of resources when service definition contains '@' ?
That is is a common practice I'm sure you know, where you
can have systemd services 'per-config' . eg. openvpn-clien@
I get:
...
Error: invalid resource name 'openvpn-client
On Fri, 2021-02-19 at 19:13 +, lejeczek wrote:
> Hi guys.
>
> I wonder if there is presently a way to create systemd type
> of resources when service definition contains '@' ?
> That is is a common practice I'm sure you know, where you
> can have systemd services 'per-config' . eg. openvpn-c
