From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <t.lamprecht@proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits))
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id 775E063512
 for <pve-devel@lists.proxmox.com>; Wed, 10 Feb 2021 08:19:20 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id 70227CF34
 for <pve-devel@lists.proxmox.com>; Wed, 10 Feb 2021 08:19:20 +0100 (CET)
Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com
 [212.186.127.180])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by firstgate.proxmox.com (Proxmox) with ESMTPS id 5816ACF24
 for <pve-devel@lists.proxmox.com>; Wed, 10 Feb 2021 08:19:19 +0100 (CET)
Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1])
 by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 2B8D4437BE
 for <pve-devel@lists.proxmox.com>; Wed, 10 Feb 2021 08:19:19 +0100 (CET)
Message-ID: <e1648cae-8156-a275-1147-1fa07c919d76@proxmox.com>
Date: Wed, 10 Feb 2021 08:19:18 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:86.0) Gecko/20100101
 Thunderbird/86.0
Content-Language: en-US
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
 Aaron Lauterer <a.lauterer@proxmox.com>
References: <20210209154531.11093-1-a.lauterer@proxmox.com>
 <20210209154531.11093-2-a.lauterer@proxmox.com>
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
In-Reply-To: <20210209154531.11093-2-a.lauterer@proxmox.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.071 Adjusted score from AWL reputation of From: address
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 NICE_REPLY_A           -0.265 Looks like a legit reply (A)
 RCVD_IN_DNSWL_MED        -2.3 Sender listed at https://www.dnswl.org/,
 medium trust
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: Re: [pve-devel] [PATCH v2 docs] ha-manager: simulator: add note for
 xauth when installing
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2021 07:19:20 -0000

On 09.02.21 16:45, Aaron Lauterer wrote:
> Installing the ha-simulator on a PVE node directly to start it via ssh
> and x11 forwarding will need the 'xauth' package installed on the PVE
> node as well.
> 
> Otherwise one is likely to encounter the following error when starting
> the simulator: `Unable to init server: Could not connect: Connection
> refused`
> 
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
> I added this patch as I think it might be good to have a hint in the
> docs as well and not just a suggested package.
> 

yeah, good idea. IMO that's even the better place to fix this than the
package control file.

> 
>  ha-manager.adoc | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/ha-manager.adoc b/ha-manager.adoc
> index 2162d25..f0a029a 100644
> --- a/ha-manager.adoc
> +++ b/ha-manager.adoc
> @@ -505,6 +505,10 @@ pve-ha-simulator working/
>  You can then start, stop, migrate the simulated HA services, or even check out
>  what happens on a node failure.
>  
> +NOTE: Should you install the simulator on a {pve} node, it is possible that
> +starting the simulator will fail at first. If that happens, consider installing
> +the 'xauth' package on the {pve} node.

IMO this is a bit weird wording. General failure can be much different things.
E.g., this sounds like it would help to install xauth for any error even if no
ssh X forwarding is involved at all.

Rather state the exact use case and requirements. Something short along the lines
of:

HINT: If you want to forward the simulator window over SSH, you need to install
the `xauth` package on the {pve} node.