Source: pcs
Version: 0.11.7-2
Severity: serious

Hi,

See https://ci.debian.net/packages/p/pcs/
It fails with:

test setup: test run
113s autopkgtest [13:34:07]: test setup: [-----------------------
113s Warning: Unable to read the known-hosts file: No such file or directory: '/var/lib/pcsd/known-hosts'
113s node1: Not authorized
114s Error: Unable to communicate with node1
114s Nodes to authorize: node1
115s passwd: password changed.
115s autopkgtest [13:34:09]: test setup: -----------------------]
▾ test setup: test results
115s autopkgtest [13:34:09]: test setup: - - - - - - - - - - results - - - - - - - - - -
115s setup FAIL non-zero exit status 1

I can reproduce the failure locally, but for me it also fails on
testing, while it does not on ci.debian.net. So I'm not sure where to go
from there.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, Feb 06, 2025 at 11:40:11PM +0100, Lucas Nussbaum wrote:

On 04/02/25 at 22:04 +0100, Lucas Nussbaum wrote:

Source: pcs
Version: 0.11.7-2
Severity: serious

Hi,

See https://ci.debian.net/packages/p/pcs/
It fails with:

test setup: test run
113s autopkgtest [13:34:07]: test setup: [-----------------------
113s Warning: Unable to read the known-hosts file: No such file or directory: '/var/lib/pcsd/known-hosts'
113s node1: Not authorized
114s Error: Unable to communicate with node1
114s Nodes to authorize: node1
115s passwd: password changed.
115s autopkgtest [13:34:09]: test setup: -----------------------]
▾ test setup: test results
115s autopkgtest [13:34:09]: test setup: - - - - - - - - - - results - - - - - - - - - -
115s setup FAIL non-zero exit status 1

I can reproduce the failure locally, but for me it also fails on
testing, while it does not on ci.debian.net. So I'm not sure where to go from there.

I don't understand how the 'setup' test is supposed to work.
The test is supposed to interact with a pcsd daemon, but it is never
started. I think something along the lines of this is needed:

--------------------------------------------------->8
--- debian/tests/setup.orig 2025-02-06 22:31:16.966589481 +0000
+++ debian/tests/setup 2025-02-06 22:32:29.543402182 +0000
@@ -1,26 +1,32 @@
#!/bin/sh

set -e

ulimit -H -l unlimited 2>/dev/null || {
# https://bugs.launchpad.net/bugs/1828228
echo "test disabled for unprivileged namespaces"
exit 77
}

cleanup () {
service pcsd stop
service pacemaker stop
service corosync stop
passwd --delete --lock hacluster
}

trap "cleanup" 0 2 3 15

+service corosync start
+service pacemaker start
+service pcsd start

When run in lxc (as in ci.d.n), the systems services are started, and
that's the preferred way of testing the installed package, just
exercising the daemons that get started system-wide. Now,
debian/tests/control is missing `Restrictions: isolation-container`
because the test needs at least a system container to work.

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmel27oACgkQ/A2xu81G C95p3w//TwU2CoWIMrPoBV6uqAVQski5gX2462nhNtc5wpDkQXAjjKFEse6K6CoE jZyho0gXkky5cIU/O5vW+2PZoAY6RlMzwQPWGiDRoVkOgv8gmgBvk/Ee8yateSJB uQ+E5cSKzN0ffQBnnM+Ss01EfeXNClTbG7MOPNv0ZawfR5ZOTST+v5HSeYtJlbjh 9IT1Th7jMS1bpvozybe/hKKj7hPhpZwAUmaicwHao4mQP77UH7xsWIhgwMXr7UOB qKxY/lq1u9BF95uV3pA28HeC2ktOtgCWMeuKCACQnMdpRgfbXLT12iy9j0kjVc+t 4zIH8nx4PbXc4jmkmUR+XN7hnxqLT5g2bDT7WIQnbmaDXFf9ZrdtN1OTLDPUNo4V oT9K5hhASG44f98KAqqlVI2A19RNsJ5K08zc1O8s4kHnSs4NdTieQOya43mVHb0E Wc4Umt/B5IKp/bBK/qquOWZLTKOE8r25b5C/hHTYfd0KD9iMG15k9M5b21dN7/m7 WwlvUhBQEWyLatXwJLTzQdDbpQTJ5VPO4MwZ/Inf1d5lXEGdn+N+UsMIX4hASZ1E M79aLmN1bsLO/XQrmHHsPJ61FfMLJ3IZaODfr+Ss79/uqHudgl+0XIlC+TyjjkMj R55Kb0Uc0yDDi6xmrSV7Bc3sB+EA2Neqg6tNzOYWAjrurLx2Mow=
=3hFF
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, Feb 07, 2025 at 07:33:35AM -0300, Antonio Terceiro wrote:

On Tue, Feb 04, 2025 at 10:04:52PM +0100, Lucas Nussbaum wrote:

Source: pcs
Version: 0.11.7-2
Severity: serious

Hi,

See https://ci.debian.net/packages/p/pcs/
It fails with:

test setup: test run
113s autopkgtest [13:34:07]: test setup: [-----------------------
113s Warning: Unable to read the known-hosts file: No such file or directory: '/var/lib/pcsd/known-hosts'
113s node1: Not authorized
114s Error: Unable to communicate with node1
114s Nodes to authorize: node1
115s passwd: password changed.
115s autopkgtest [13:34:09]: test setup: -----------------------]
▾ test setup: test results
115s autopkgtest [13:34:09]: test setup: - - - - - - - - - - results - - - - - - - - - -
115s setup FAIL non-zero exit status 1

I can reproduce the failure locally, but for me it also fails on
testing, while it does not on ci.debian.net. So I'm not sure where to go from there.

I investigated this a little bit, and pcs is missing a dependency on `ruby-rackup`. Due to this, pcs-ruby.service fails to start, what causes pcs.service to not start due to the failed dependency.

This is due to the upgrade of ruby-rack to version 3.x.

I tried to prepare an NMU, but then pcs FTBFS on current unstable due to
a failure in the Python unit tests. I'm running a clean build here with sbuild and will report a bug if that's really the case.

... and of course it is already reported by Lucas himself. :)

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmel5F8ACgkQ/A2xu81G C95gdQ/9EreD4fUReyoEc4GCSCXQ1yCPgKfcff3Bdwq6D3bgFkFaKeik6RoSyZ4U 8Q2xLsnlK+xBQVSXyKUaJXqir/S4F11u1ghtvG2oPmDi4Ac5tMumf2s4xneRHsGV f3HP1ngko+GIONCFf111gWe5HgnGvrzjMusPGK+ngKNRWfiLqb0kur5G2LwwnebP KwM2Eacd9R3Gy0rEuyQe+Rh03vmv5167FT9rQrUq96aIQyC8vk1TUeV452Ol7KUV nZltf+hjbGLvy59Uezh3AE1Lcvrwm7EX6m1M5cK3jGppQfrKnTWg8oWNvZoU6wih Q2mvXvUT+21k2xphVhTzN+ghSM/BiWII6xKPre4AFXyezWL2o8yHt/i88MRs7o5n 7chbNfnDPI7o5Ja6L4fTeu8SNE4TUGaLD2PQh0xTsaV85ydk9tZI1JhLN1s8W2vD hBVCfhSzWodcAO4Jgh7Jd9JOpgh269dSXNEWmxo5C2ApBd96JOi26v428LRvkdDA Lya586gcGlUR55crvgLse93sLL7r4PBSJ4HGU8jqXbHET4mj6ps3WH2gSFIljXgu 0cypepro3LMBFasv/0iE18VgqwTnD47G95xN7kIaKiv6zoRjZtmFomX+tq51a/TK HIDsWJozt/QuxoT394D+qwPefsmfc1aTV+aSQKuARu8Gpw7EvNM=
=UwpP
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Sat, 08 Feb 2025 21:49:40 +0000
with message-id <E1tgsho-008BeG-F6@fasolo.debian.org>
and subject line Bug#1095183: fixed in pcs 0.11.7-3
has caused the Debian Bug report #1095183,
regarding pcs: autopkgtest fails in unstable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


--
1095183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095183
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 4 Feb 2025 21:04:57 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-105.1 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,
FROMDEVELOPER,SPF_HELO_NONE,SPF_NONE,UNPARSEABLE_RELAY,
USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST autolearn=ham
autolearn_force=no version=3.4.6-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 7; hammy, 131; neutral, 24; spammy, 0.
spammytokens: hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
0.000-+--H*RT:311, 0.000-+--H*RT:108
Return-path: <lucas@debian.org>
Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:57