[ceph-users] Ceph Upgrade 18.2.2 -> 18.2.4 fails | Fatal glibc error: CPU does not support x86-64-v2 on virtualized hosts

Hi there, Last week I upgraded from 17.2.7 to 18.2.2 and the cluster worked fine except for a few bugs about IPv6. But it is working and cluster.health is HEALTH_OK. Hoping to fix some of these minor IPv6 issues, I tried upgrading to 18.2.4. I see 2 errors: The first is that the upgrade fails to

[ceph-users] Re: Ceph Upgrade 18.2.2 -> 18.2.4 fails | Fatal glibc error: CPU does not support x86-64-v2 on virtualized hosts

Hi Björn, have a look at the Type "max". Thus the proxmox cluster should choose the maximum cpu type, which allows for live migration and than ceph should run with v18.2.4 images. https://forum.proxmox.com/threads/max-cpu-type.94736/ Best regards, Gunnar --- Original Nachricht ---Betreff: [

[ceph-users] Re: Ceph Upgrade 18.2.2 -> 18.2.4 fails | Fatal glibc error: CPU does not support x86-64-v2 on virtualized hosts

On Thu, 2024-07-25 at 10:03 +0200, Björn Lässig wrote: > Jul 25 09:16:18 cephmgr1 reverent_hypatia[1171489]: Fatal glibc > error: CPU does not support x86-64-v2 > > When starting the container for 18.2.4. a glibc error occurs. > 18.2.2. to 18.2.4 is a minor upgrade and should run on same > hardwar

[ceph-users] Re: RBD Stuck Watcher

On Wed, Jul 3, 2024 at 5:45 PM Reid Guyett wrote: > > Hi, > > I have a small script in a Docker container we use for a type of CRUD test > to monitor availability. The script uses Python librbd/librados and is > launched by Telegraf input.exec. It does the following: > >1. Creates an rbd image

[ceph-users] Re: Ceph Upgrade 18.2.2 -> 18.2.4 fails | Fatal glibc error: CPU does not support x86-64-v2 on virtualized hosts

On Thu, 2024-07-25 at 10:13 +0200, Bandelow, Gunnar wrote: > > have a look at the Type "max". Thus the proxmox cluster should choose > the maximum cpu type, which allows for live migration and than ceph > should run with v18.2.4 images. > > https://forum.proxmox.com/threads/max-cpu-type.94736/ >

[ceph-users] Reef 18.2.4 EL8 packages ?

Hi all, I find this 18.2.4 release highly confusing. Can anyone please confirm that EL8 packages are no more supported ? The small remark in the release notes qa/distros: remove centos 8 from supported distros (pr#57932, Guillaume Abrioux, Casey Bodley, Adam King, Laura Flores) is a bit dist

[ceph-users] Subscribe

___ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: Subscribe

Sorry, the list has been wonky for me. I was logged in with my GitHub credentials and when I try and publish the post, I get the message This list is moderated, please subscribe to it before posting. When I try and manage my subscription, I get: Something went wrong Mailman REST API not avai

[ceph-users] Re: Subscribe

Known problem. I’m managing this list manually (think: interactive Python shell) until the CLT finds somebody with the chops to set it up fresh on better infra and not lose the archives. I’ll get dobr...@gmu.edu added. > On Jul 25, 2024, at 8:55 AM, Dan O'Brien wrote:

[ceph-users] Dashboard error on 18.2.4 when listing block images

I just yesterday updated by Ceph cluster from Quincy (17.2.7) to Reef (18.2.4, purely by accident; I didn't realize I was getting it THE EXACT SECOND it was pushed out). The upgrade resolved an issue I was having with HTTP 500 errors on the RGW UI, but seems to have created an issue in the dash

[ceph-users] Re: Solved: Ceph Upgrade 18.2.2 -> 18.2.4 fails | Fatal glibc error: CPU does not support x86-64-v2 on virtualized hosts

On Thu, 2024-07-25 at 12:04 +0200, Björn Lässig wrote: > On Thu, 2024-07-25 at 10:03 +0200, Björn Lässig wrote: > > Jul 25 09:16:18 cephmgr1 reverent_hypatia[1171489]: Fatal glibc > > error: CPU does not support x86-64-v2 > > > > When starting the container for 18.2.4. a glibc error occurs. > > 18

[ceph-users] Re: [RGW] Setup 2 zones within a cluster does not sync data

I'm not sure what's wrong, it says "data is caught up with source", how do you determine that it's not? Can you explain in more detail? I currently only have two different test clusters which I had to fix, they weren't replicating either, but due to a certificate issue. But since you don't us

[ceph-users] Re: Dashboard error on 18.2.4 when listing block images

I may be on to something. Going through the pools and listing the block images in them, I have one pool that gives an error message: [root@os-storage ~]# rbd --pool volumes-gpu ls --long rbd: error opening volume-28bbca8c-fec5-4a33-bbe2-30408f1ea37f: (2) No such file or directory rbd: error open

[ceph-users] 18.2.4 regression: 'diskprediction_local' has failed: No module named 'sklearn'

Upgraded to 18.2.4 yesterday.  Healthy cluster reported a few minutes after the upgrade completed.  Next morning, this: # ceph health detail HEALTH_ERR Module 'diskprediction_local' has failed: No module named 'sklearn' [ERR] MGR_MODULE_ERROR: Module 'diskprediction_local' has failed: No modul

[ceph-users] Re: v18.2.4 Reef released - blog release note missing issue 61948

Robin, thx We will fix the typo On Wed, Jul 24, 2024 at 5:18 PM Robin H. Johnson wrote: > > Hi Yuri et al, > > The email announcement includes the fix for 61948, but the linked blog > page omits it entirely. > > Suggest adding that note to the blog page. > > The language used also differs slightl

[ceph-users] Re: Dashboard error on 18.2.4 when listing block images

Both of the volumes mentioned above are showing a status of "error_deleting" in OpenStack. I'm probably going to have to remove them with openstack volume delete --force. I'm guessing this might be a regression in DiffIterate that doesn't handle volumes/RBD images in an inconsistent state. It

[ceph-users] Re: Dashboard error on 18.2.4 when listing block images

Hi Dan, What is the output of $ rbd info images-pubos/144ebab3-b2ee-4331-9d41-8505bcc4e19b Can you confirm that the problem lies with that image by running $ rbd diff --whole-object images-pubos/144ebab3-b2ee-4331-9d41-8505bcc4e19b Thanks, Ilya

[ceph-users] Re: Dashboard error on 18.2.4 when listing block images

Ilya - I don't think images-pubos/144ebab3-b2ee-4331-9d41-8505bcc4e19b is the problem; it was just the last RBD image listed in the log before the crash. The commands you suggested work fine when using that image: [root@os-storage ~]# rbd info images-pubos/144ebab3-b2ee-4331-9d41-8505bcc4e19b r

[ceph-users] Re: Reef 18.2.4 EL8 packages ?

Hi, > On 25 Jul 2024, at 14:39, Noe P. wrote: > > I find this 18.2.4 release highly confusing. > > Can anyone please confirm that EL8 packages are no more supported ? > The small remark in the release notes > > qa/distros: remove centos 8 from supported distros (pr#57932, Guillaume > Abrioux

[ceph-users] Re: [RGW] radosgw does not respond after some time after upgrade from pacific to quincy

It turned out that under heavy load one of the rgws have had too low soft NOFILE limit set (max number of open files). We also accidentally found that in our setup and hw the "round trips" under heavy load from frontend proxy (nginx in our case) to radosgw cost is pretty high (let us say 50% in cap

[ceph-users] Re: Dashboard error on 18.2.4 when listing block images

On Thu, Jul 25, 2024 at 10:10 PM Dan O'Brien wrote: > > Ilya - > > I don't think images-pubos/144ebab3-b2ee-4331-9d41-8505bcc4e19b is the > problem; it was just the last RBD image listed in the log before the crash. > The commands you suggested work fine when using that image: > > [root@os-stora

[ceph-users] Fwd: [community] [OpenInfra Event Update] The CFP For OpenInfra Days NA is now open!

Hello Community I want to share this with you in case anybody wants to send anything to the CFP \o/ Feel free to reach out in case of questions; I hope to see you there. Cheers! -- Forwarded message - From: Helena Spease Date: Tue, Jul 16, 2024 at 1:46 PM Subject: [community]