Node Exporter keep failing while upgrading cluster in Air-gapped ( isolated environment ).

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

We are facing an issue with node-exporter entering an error state while upgrading our cluster in an air-gapped environment. 
Specifically, we are upgrading from quincyv17.2.0 to reefv18.2.2. To facilitate this upgrade, we have set up a custom repository on a separate machine within the same network and pushed required images to this private repository.

Here are the images that we have pushed:

root@custom-registry:~# docker images
REPOSITORY                                             TAG       IMAGE ID       CREATED         SIZE
192.168.1.10:5000/ceph/ceph                          v18.2.2   3c937764e6f5   7 weeks ago     1.25GB
192.168.1.10:5000/ceph/ceph-grafana                  9.4.7     954c08fa6188   7 months ago    633MB
192.168.1.10:5000/prometheus/prometheus              v2.43.0   a07b618ecd1d   16 months ago   234MB
192.168.1.10:5000/prometheus/alertmanager            v0.25.0   c8568f914cd2   19 months ago   65.1MB
192.168.1.10:5000/prometheus/node-exporter           v1.5.0    0da6a335fe13   19 months ago   22.5MB

Since we have configured insecure private registry, we added following lines in "/etc/containers/registries.conf" file on each node of the cluster.
[[registry]]
location = "192.168.1.10:5000"
insecure = true

Ceph image upgradation done by the command (ceph orch upgrade start --image 192.168.1.10:5000/ceph/ceph:v18.2.2) but we encountered issues from the node-exporter image, which fails to start and remains in an error state.

For the remaining images ( except ceph ) we used "ceph-config" command. We are here now getting the new images values by executing the following command that seems to be default ones.
root@node-01:~# ceph config get mgr mgr/cephadm/container_image_node_exporter
quay.io/prometheus/node-exporter:v1.5.0

Does an internet connection is required to pull these images (Monitoring stack components images)? I am unsure because whenever we attempt to run the following command, node-exporter enters an error state and not coming into the running state even after redeploy.
root@node-01:~# ceph config set mgr mgr/cephadm/container_image_node_exporter  quay.io/prometheus/node-exporter:v1.5.0

Please advise the best approach to upgrade the cluster including all images in Air-gapped environment?

Any guidance on resolving this issue would be appreciated.

Regards,
Mohammad Saif
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux