Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

smartctl could not scrape metrics from HPE Smart Array in HBA mode #2205

Closed
mirex05 opened this issue May 3, 2024 · 2 comments
Closed

smartctl could not scrape metrics from HPE Smart Array in HBA mode #2205

mirex05 opened this issue May 3, 2024 · 2 comments
Labels

Comments

@mirex05
Copy link

mirex05 commented May 3, 2024

Is this a bug report or feature request?

  • Bug Report

Bug Report

What happened: on current reef image (ceph:v18.2.2), in case of deploy on HW with HPE Smart Array controllers in HBA mode, smartctl could not scrape any SMART metrics, because it's requires option -d cciss,N. This behavior was changed in smartmontools 7.3 (https://www.smartmontools.org/ticket/1472), but current Ceph image contains smartmontools 7.1.

If manually add to container a newer smartmontools version (tested on smartmontools-next repo at runtime), scrape is successful and Ceph shows disk health data.

What you expected to happen: SMART metrics scraped successfully

How to reproduce it (minimal and precise):

Deploy 18.2.2 Ceph image on any HW with HPE Smart Array in HBA mode and try to scrape SMART metrics.

Environment:

  • OS (e.g. from /etc/os-release): Debian 12
  • Kernel (e.g. uname -a): 6.1.0-20-amd64
  • Docker version (e.g. docker version): podman 4.3.1
  • Ceph version (e.g. ceph -v): 18.2.2
@mirex05 mirex05 changed the title smartctl colud not scrape metrics from HPE Smart Array in HBA mode smartctl could not scrape metrics from HPE Smart Array in HBA mode May 3, 2024
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

Copy link

This issue has been automatically closed due to inactivity. Please re-open if this still requires investigation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant