[mgr modules failing because pyO3 can't be imported more than once]
On 29/01/2024 12:27, Chris Palmer wrote:
I have logged this as https://tracker.ceph.com/issues/64213
I've noted there that it's related to
https://tracker.ceph.com/issues/63529 (an earlier report relating to the
dashboard);
Hi,
Just looking back through PyO3 issues, it would appear this functionality was
never supported:
https://github.com/PyO3/pyo3/issues/3451
https://github.com/PyO3/pyo3/issues/576
It just appears attempting to use this functionality (which does not
work/exist) wasn't successfully prevented
We have fundamental problems with the concept of cephadm and its
direction of travel. But that's a different story.
The nub of this problem is a design incompatibility with MGR and the
PyO3 package that python-cryptography relies on. It's actually unsafe as
it is, and the new package just
Would migrating to a cephadm orchestrated docker/podman cluster be an
acceptable workaround?
We are running that config with reef containers on Debian 12 hosts, with a
couple of debian 12 clients successfully mounting cephfs mounts, using the
reef client packages directly on Debian.
On Fri, Feb
On Fri, Feb 2, 2024 at 11:21 AM Chris Palmer wrote:
>
> Hi Matthew
>
> AFAIK the upgrade from quincy/deb11 to reef/deb12 is not possible:
>
> * The packaging problem you can work around, and a fix is pending
> * You have to upgrade both the OS and Ceph in one step
> * The MGR will not run
Hi Matthew
AFAIK the upgrade from quincy/deb11 to reef/deb12 is not possible:
* The packaging problem you can work around, and a fix is pending
* You have to upgrade both the OS and Ceph in one step
* The MGR will not run under deb12 due to the PyO3 lack of support for
subinterpreters.
Chris,
Thanks for all the investigations you are doing here. We're on
quincy/debian11. Is there any working path at this point to
reef/debian12? Ideally I want to go in two steps. Upgrade ceph first
or upgrade debian first, then do the upgrade to the other one. Most of
our infra is
I have logged this as https://tracker.ceph.com/issues/64213
On 16/01/2024 14:18, DERUMIER, Alexandre wrote:
Hi,
ImportError: PyO3 modules may only be initialized once per
interpreter
process
and ceph -s reports "Module 'dashboard' has failed dependency: PyO3
modules may only be initialized
On 1/17/24 20:49, Chris Palmer wrote:
>
>
> On 17/01/2024 16:11, kefu chai wrote:
>>
>>
>> On Tue, Jan 16, 2024 at 12:11 AM Chris Palmer wrote:
>>
>> Updates on both problems:
>>
>> Problem 1
>> --
>>
>> The bookworm/reef cephadm package needs updating to accommodate
On 17/01/2024 16:11, kefu chai wrote:
On Tue, Jan 16, 2024 at 12:11 AM Chris Palmer
wrote:
Updates on both problems:
Problem 1
--
The bookworm/reef cephadm package needs updating to accommodate
the last
change in
On Tue, Jan 16, 2024 at 12:11 AM Chris Palmer
wrote:
> Updates on both problems:
>
> Problem 1
> --
>
> The bookworm/reef cephadm package needs updating to accommodate the last
> change in /usr/share/doc/adduser/NEWS.Debian.gz:
>
>System user home defaults to /nonexistent if
Updates on both problems:
Problem 1
--
The bookworm/reef cephadm package needs updating to accommodate the last
change in /usr/share/doc/adduser/NEWS.Debian.gz:
System user home defaults to /nonexistent if --home is not specified.
Packages that call adduser to create system
More info on problem 2:
When starting the dashboard, the mgr seems to try to initialise cephadm,
which in turn uses python crypto libraries that lead to the python error:
$ ceph crash info
2024-01-12T11:10:03.938478Z_2263d2c8-8120-417e-84bc-bb01f5d81e52
{
"backtrace": [
" File
13 matches
Mail list logo
