Error after Ceph 17 Upgrade from 16

J

JCNED

Member
Proxmox Subscriber
Sep 23, 2022
12
4
8
On our old development cluster we did a test upgrade from Ceph 16 to 17. When this was built forever ago for some reason the Image storage was contained within device_health_metrics which was renamed to .mgr.

I was able to edit the config to point the RBD for HDD-VM from device_health_metrics to .mgr (thankfully this is the only cluster with this silly config issue) and I can view summary now, but no VM Disk images are listing and I cannot shut and start VM's. I figure before i restore from backup if anyone has a suggestion.

Code: 
rbd: error opening base-129-disk-0: (2) No such file or directory
rbd: error opening base-129-disk-1: (2) No such file or directory
rbd: error opening base-129-disk-2: (2) No such file or directory
rbd: error opening vm-100-disk-0: (2) No such file or directory
rbd: error opening vm-101-disk-0: (2) No such file or directory
rbd: error opening vm-101-state-PreUpgrade: (2) No such file or directory
rbd: error opening vm-102-disk-0: (2) No such file or directory
rbd: error opening vm-103-disk-0: (2) No such file or directory
rbd: error opening vm-103-disk-1: (2) No such file or directory
rbd: error opening vm-103-disk-2: (2) No such file or directory
rbd: error opening vm-104-disk-0: (2) No such file or directory
rbd: error opening vm-104-disk-1: (2) No such file or directory
rbd: error opening vm-104-disk-2: (2) No such file or directory
rbd: error opening vm-105-disk-0: (2) No such file or directory
rbd: error opening vm-105-disk-1: (2) No such file or directory
rbd: error opening vm-105-disk-2: (2) No such file or directory
rbd: error opening vm-109-disk-0: (2) No such file or directory
rbd: error opening vm-109-state-Zabbiximage: (2) No such file or directory
rbd: error opening vm-113-disk-0: (2) No such file or directory
rbd: error opening vm-113-disk-1: (2) No such file or directory
rbd: error opening vm-113-disk-2: (2) No such file or directory
rbd: error opening vm-114-disk-0: (2) No such file or directory
rbd: error opening vm-114-disk-1: (2) No such file or directory
rbd: error opening vm-114-disk-2: (2) No such file or directory
rbd: error opening vm-115-disk-0: (2) No such file or directory
rbd: error opening vm-116-disk-0: (2) No such file or directory
rbd: error opening vm-116-disk-1: (2) No such file or directory
rbd: error opening vm-116-disk-2: (2) No such file or directory
rbd: error opening vm-117-disk-0: (2) No such file or directory
rbd: error opening vm-118-disk-0: (2) No such file or directory
rbd: error opening vm-119-disk-0: (2) No such file or directory
rbd: error opening vm-120-disk-0: (2) No such file or directory
rbd: error opening vm-120-disk-1: (2) No such file or directory
rbd: error opening vm-120-disk-2: (2) No such file or directory
rbd: error opening vm-122-disk-0: (2) No such file or directory
rbd: error opening vm-123-disk-0: (2) No such file or directory
rbd: error opening vm-124-disk-0: (2) No such file or directory
rbd: error opening vm-125-disk-0: (2) No such file or directory
rbd: error opening vm-125-disk-1: (2) No such file or directory
rbd: error opening vm-125-disk-2: (2) No such file or directory
rbd: error opening vm-125-disk-3: (2) No such file or directory
rbd: error opening vm-125-disk-4: (2) No such file or directory
rbd: error opening vm-125-disk-5: (2) No such file or directory
rbd: error opening vm-126-disk-0: (2) No such file or directory
rbd: error opening vm-126-disk-1: (2) No such file or directory
rbd: error opening vm-126-disk-2: (2) No such file or directory
rbd: error opening vm-127-disk-0: (2) No such file or directory
rbd: error opening vm-127-disk-1: (2) No such file or directory
rbd: error opening vm-127-disk-2: (2) No such file or directory
rbd: error opening vm-128-disk-0: (2) No such file or directory
rbd: error opening vm-128-disk-1: (2) No such file or directory
rbd: error opening vm-128-disk-2: (2) No such file or directory
rbd: error opening vm-130-disk-0: (2) No such file or directory
rbd: error opening vm-130-disk-1: (2) No such file or directory
rbd: error opening vm-131-disk-0: (2) No such file or directory
rbd: error opening vm-132-disk-0: (2) No such file or directory
rbd: error opening vm-132-disk-1: (2) No such file or directory
rbd: error opening vm-132-disk-2: (2) No such file or directory
rbd: error opening vm-133-disk-0: (2) No such file or directory
rbd: error opening vm-135-disk-0: (2) No such file or directory
rbd: error opening vm-136-disk-0: (2) No such file or directory
rbd: error opening vm-137-disk-0: (2) No such file or directory
rbd: error opening vm-138-disk-0: (2) No such file or directory
rbd: error opening vm-139-disk-0: (2) No such file or directory
rbd: error opening vm-140-disk-0: (2) No such file or directory
rbd: error opening vm-141-disk-0: (2) No such file or directory
rbd: error opening vm-142-disk-0: (2) No such file or directory
rbd: error opening vm-143-disk-0: (2) No such file or directory
rbd: error opening vm-144-disk-0: (2) No such file or directory
rbd: error opening vm-145-disk-0: (2) No such file or directory
rbd: error opening vm-145-disk-1: (2) No such file or directory
rbd: error opening vm-145-disk-2: (2) No such file or directory
rbd: error opening vm-146-disk-0: (2) No such file or directory
rbd: error opening vm-146-disk-1: (2) No such file or directory
rbd: error opening vm-146-disk-2: (2) No such file or directory
rbd: error opening vm-147-disk-0: (2) No such file or directory
rbd: error opening vm-147-disk-1: (2) No such file or directory
rbd: error opening vm-147-disk-2: (2) No such file or directory
rbd: error opening vm-148-disk-0: (2) No such file or directory
rbd: error opening vm-148-disk-1: (2) No such file or directory
rbd: error opening vm-149-disk-0: (2) No such file or directory
rbd: error opening vm-150-disk-0: (2) No such file or directory
rbd: error opening vm-151-disk-0: (2) No such file or directory
rbd: error opening vm-154-disk-0: (2) No such file or directory
rbd: error opening vm-160-disk-0: (2) No such file or directory
rbd: error opening vm-161-disk-0: (2) No such file or directory
rbd: error opening vm-161-disk-1: (2) No such file or directory
rbd: error opening vm-162-disk-0: (2) No such file or directory
rbd: error opening vm-162-state-DomainPrior: (2) No such file or directory
rbd: error opening vm-163-disk-0: (2) No such file or directory
rbd: error opening vm-164-disk-0: (2) No such file or directory
rbd: error opening vm-166-disk-0: (2) No such file or directory
rbd: error opening vm-166-disk-1: (2) No such file or directory
rbd: error opening vm-166-disk-2: (2) No such file or directory
rbd: error opening vm-167-disk-0: (2) No such file or directory
rbd: error opening vm-167-disk-1: (2) No such file or directory
rbd: error opening vm-167-disk-2: (2) No such file or directory
rbd: error opening vm-168-disk-0: (2) No such file or directory
rbd: error opening vm-168-disk-1: (2) No such file or directory
rbd: error opening vm-168-disk-2: (2) No such file or directory
rbd: error opening vm-170-disk-0: (2) No such file or directory
rbd: error opening vm-171-disk-0: (2) No such file or directory
rbd: error opening vm-172-disk-0: (2) No such file or directory
rbd: error opening vm-173-disk-0: (2) No such file or directory
rbd: error opening vm-174-disk-0: (2) No such file or directory
rbd: error opening vm-175-disk-0: (2) No such file or directory
rbd: error opening vm-176-disk-0: (2) No such file or directory
rbd: error opening vm-177-disk-0: (2) No such file or directory
rbd: error opening vm-178-disk-0: (2) No such file or directory
rbd: error opening vm-178-state-Sql04_pre_v20_2: (2) No such file or directory
rbd: error opening vm-179-disk-0: (2) No such file or directory
rbd: error opening vm-179-state-Jboss04_pre_v20_2: (2) No such file or directory
rbd: error opening vm-180-disk-0: (2) No such file or directory
rbd: error opening vm-180-disk-1: (2) No such file or directory
rbd: error opening vm-181-disk-0: (2) No such file or directory
rbd: error opening vm-182-disk-0: (2) No such file or directory
rbd: error opening vm-189-disk-0: (2) No such file or directory
rbd: error opening vm-191-disk-0: (2) No such file or directory
rbd: error opening vm-191-disk-1: (2) No such file or directory
rbd: error opening vm-191-disk-2: (2) No such file or directory
rbd: error opening vm-192-disk-0: (2) No such file or directory
rbd: error opening vm-192-disk-1: (2) No such file or directory
rbd: error opening vm-192-disk-2: (2) No such file or directory
rbd: error opening vm-194-disk-0: (2) No such file or directory
rbd: error opening vm-195-disk-0: (2) No such file or directory
NAME  SIZE  PARENT  FMT  PROT  LOCK
rbd: listing images failed: (2) No such file or directory
 
JCNED said:
When this was built forever ago for some reason the Image storage was contained within device_health_metrics which was renamed to .mgr.
Click to expand...

This pool should only be used for internal data of the MGR. Use another pool for RBD data (call it "rbd").

Are you sure that you found all places where device_health_metrics was used as a pool name? Have you scanned the VMs' config files?
 
gurubert said:
This pool should only be used for internal data of the MGR. Use another pool for RBD data (call it "rbd").

Are you sure that you found all places where device_health_metrics was used as a pool name? Have you scanned the VMs' config files?
Click to expand...
Yeah, it was an oversight when this cluster was setup, none of our true production clusters are setup that way. I'll dig through the config files as well, good point.
 
You must log in or register to reply here.
Top Bottom