From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dietmar@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) server-digest SHA256)
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id BD3E27215A
 for <pve-devel@lists.proxmox.com>; Mon, 24 May 2021 09:45:57 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id ACCF42076B
 for <pve-devel@lists.proxmox.com>; Mon, 24 May 2021 09:45:57 +0200 (CEST)
Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com
 [94.136.29.106])
 (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 1AF272075D
 for <pve-devel@lists.proxmox.com>; Mon, 24 May 2021 09:45:55 +0200 (CEST)
Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1])
 by proxmox-new.maurer-it.com (Proxmox) with ESMTP id AF50B43EB1;
 Mon, 24 May 2021 09:45:49 +0200 (CEST)
Date: Mon, 24 May 2021 09:45:15 +0200 (CEST)
From: Dietmar Maurer <dietmar@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
 wb <webmaster@jbsky.fr>
Message-ID: <606562427.786.1621842315013@webmail.proxmox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.5-Rev11
X-Originating-Client: open-xchange-appsuite
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.209 Adjusted score from AWL reputation of From: address
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 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] cfs-locked 'authkey' operation: pve cluster
 filesystem not online
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: Mon, 24 May 2021 07:45:57 -0000

Hi Julien,


> Hello to all.
>=20
> I have the plan to implement the SSO authentication feature with the SAML=
 protocol.
> However, I have an error that prevents me from validating the authenticat=
ion process.
> It is about the locks.
> The first step is to store the request_saml_id. If I try to create a file=
 by your libraries, I get an 500 error with msg:
> error during cfs-locked \'file-request_tmp\' operation: pve cluster files=
ystem not online /etc/pve/priv/lock.

Your cluster fs is not working (pmxcfs). See you run on a broken installati=
on.

> https://github.com/jbsky/proxmox-saml2-auth/commit/d75dc621aae719c8fdd251=
859af9641cda0e526b
> Ok, I can make a temp workaround.
>=20
> 2nd step=C2=A0:
> When I try to create a ticket with the function create_ticket in package =
PVE::API2::AccessControl;
> I've got this error :
> authentication failure; rhost=3D127.0.0.1 user=3Dadmin@DOM msg=3Derror du=
ring cfs-locked 'authkey' operation: pve cluster filesystem not online /etc=
/pve/priv/lock

Again, the pmxcfs is not online.

> src : https://github.com/jbsky/proxmox-saml2-auth/commit/93b02727d2e17296=
8c14c4ce3a7c27e8d5c0feb0
>=20
> I have really bad luck with these locks!
> Can you help me to understand the prerequisites to make the lock work?

You need a working PVE installation before doing any API calls...