Re: [ClusterLabs] Remote nodes in an opt-in cluster
Jochen, Just making sure you saw this, since you've replied to Andrei since then On Tue, Apr 23, 2024 at 12:39 AM Reid Wahl wrote: > > On Tue, Apr 23, 2024 at 12:03 AM Jochen wrote: > > > > When trying to add a remote node to an opt-in cluster, the cluster does not > > start the remote resource. When I change the cluster to opt-out the remote > > resource is started. > > > > I guess I have to add a location constraint to allow the cluster to > > schedule the resource. Is that correct? > > > > And if yes, how do I create a location constraint to allow the cluster to > > start the remote resource anywhere on the cluster? Since I don't want to > > name each node in the constraint, I looked for a rule that always is true, > > or an attribute that is defined by default, but did not find one. I then > > tried > > > > crm configure location skylla-location skylla rule > > skylla-location-rule: defined '#uname' > > > > But this did not work either. Any help would be greatly appreciated. > > Strange. I wonder if this is something specific to remote connection > resources. (I'm not able to test that right now.) What's your > Pacemaker version and can you share the CIB XML? > > The rule that you've described works for me (using a resource that's > not a remote connection resource): > > > > >operation="defined" attribute="#uname"/> > > > > > > > > > Regards > > Jochen > > > > > > > > ___ > > Manage your subscription: > > https://lists.clusterlabs.org/mailman/listinfo/users > > > > ClusterLabs home: https://www.clusterlabs.org/ > > > > > -- > Regards, > > Reid Wahl (He/Him) > Senior Software Engineer, Red Hat > RHEL High Availability - Pacemaker -- Regards, Reid Wahl (He/Him) Senior Software Engineer, Red Hat RHEL High Availability - Pacemaker ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] resource-agents v4.14.0
ClusterLabs is happy to announce resource-agents v4.14.0. Source code is available at: https://github.com/ClusterLabs/resource-agents/releases/tag/v4.14.0 The most significant enhancements in this release are: - bugfixes and enhancements: - doc: writing-python-agents: add description of is_probe() and distro() - all agents: remove -S state/status that are either ignored, or give an error message in newer versions of Pacemaker - configure: fix "C preprocessor "gcc -E" fails sanity check" error caused by autoconf 2.72 - configure: prepare to not build with -ansi by default in the future - docs: writing-python-agents: update required Python version to 3.6+ - spec: use /usr/sbin paths for Fedora 40+ - LVM-activate: avoid false positive for VG activation (fail when system_id_source and volume_list are set) - aws-vpc-move-ip/aws-vpc-route53/awseip/awsvip: add auth_type parameter and AWS Policy based authentication type - azure-lb: support IPv6 with Azure load balancer when using socat - db2: fix OCF_SUCESS typo in db2_notify - docker: return OCF_NOT_RUNNING when Docker isn't running - findif.sh: fix corner cases - findif.sh: fix loopback handling - findif: check that netmaskbits != EOS in addition to != NULL in all cases - galera: allow joiner to report non-Primary during initial IST - nfsserver: fix "server scope" functionality for both potentially other dropins AND multiple ExecStart - ocivip: fix PRIMARY_IFACE variable when it returns two lines - openstack-info: ensure no newlines in openstack_ports - portblock: accept numeric protocol from iptables (to fix regression in iptables 1.8.9 that has shipped in some distros) - portblock: remove write to tcp_tw_recycle - storage_mon: fix file handler out of scope leak and uninitialized values - storage_mon: use memset() to fix "uninitialized value" covscan error, as qb_ipcc_recv() will always set a message The full list of changes for resource-agents is available at: https://github.com/ClusterLabs/resource-agents/blob/v4.14.0/ChangeLog Everyone is encouraged to download and test the new release. We do many regression tests and simulations, but we can't cover all possible use cases, so your feedback is important and appreciated. Many thanks to all the contributors to this release. Best, The resource-agents maintainers ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
