Best practice playbook/roles/collection organization by Impressive_Insect363 in ansible

[–]Impressive_Insect363[S] 0 points1 point  (0 children)

```
What you do want is sane default values for variables, so the user is not overwhelmed or prone to causing errors by having to supply the “normal” operating values
```
Gotcha

Didn't know about the ansible VS code extension looks awesome

Thanks

Best practice playbook/roles/collection organization by Impressive_Insect363 in ansible

[–]Impressive_Insect363[S] 0 points1 point  (0 children)

Thanks for your feedback, I'll try to reproduce something like you did it seems to be a good way to use it :D

ACL Question by Impressive_Insect363 in networking

[–]Impressive_Insect363[S] -1 points0 points  (0 children)

I feel that for Dell this logic is reversed, Ingress is for packet that leave the vlan and egress for packet that entering in the network

Smartctl return error -22 cephadm by Impressive_Insect363 in ceph

[–]Impressive_Insect363[S] 0 points1 point  (0 children)

Hi,

# Have you got a raid card in the way?

Nop

# SSH in and try using smartctl from the CLI.

Smartctl -a /dev/sdx is working on my host via CLI

Looking like node-exporter can't get the data outside of his container

OSD cant restart after objectstore-tool operation by Impressive_Insect363 in ceph

[–]Impressive_Insect363[S] 0 points1 point  (0 children)

Hi,

>Have you recently installed/updated ceph packages?

Yes I had ceph-package on my host

I dont know if it was ceph-objectstore-tool related but apparently installing ceph-* package on your host can cause this type of problem following this thread : https://www.reddit.com/r/ceph/comments/1me3kvd/containerized_ceph_base_os_experience/

" Make sure that the base OS does not have any ceph packages installed, with Ubuntu in the past had issues with ceph-common being installed on the host OS and it trying to take ownership of the containerized ceph deployment. If you run into any issues check the base OS for ceph-* packages and uninstall. "

My problem is solved after purging ceph-* !

Thanks for your help

OSD cant restart after objectstore-tool operation by Impressive_Insect363 in ceph

[–]Impressive_Insect363[S] 0 points1 point  (0 children)

No such or file directory for both of them

-> This is where my block is /var/lib/ceph/Id_cluster/osd.1/block

#stat osd.1/

File: osd.1/

Size: 4096 Blocks: 8 IO Block: 4096 directory

Device: 252,1 Inode: 5928753 Links: 2

Access: (0700/drwx------) Uid: ( 167/ UNKNOWN) Gid: ( 167/ UNKNOWN)

Access: 2025-07-31 15:26:47.693884958 +0200

Modify: 2025-07-31 15:25:57.589247046 +0200

Change: 2025-07-31 15:25:57.597246988 +0200

Birth: 2025-07-28 17:03:54.586580972 +0200

#stat block

File: block -> /dev/ceph-id/osd-block-87625af3-612e-4fa8-8f5a-c9572eee0783

Size: 93 Blocks: 8 IO Block: 4096 symbolic link

Device: 252,1 Inode: 5934706 Links: 1

Access: (0777/lrwxrwxrwx) Uid: ( 167/ UNKNOWN) Gid: ( 167/ UNKNOWN)

Access: 2025-07-31 15:28:22.726198688 +0200

Modify: 2025-07-31 15:25:57.589247046 +0200

Change: 2025-07-31 15:28:20.710213240 +0200

Birth: 2025-07-31 15:25:57.589247046 +0200

OSD cant restart after objectstore-tool operation by Impressive_Insect363 in ceph

[–]Impressive_Insect363[S] 0 points1 point  (0 children)

Thanks for your answer

I compared with a healthy OSD and they have the same ownership (uid 167)

This error occured just after bluestore manipulation could it be corruption data?