all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] Proxmox 7.0 Beta - Ceph "a password is required" error messages?
Date: Wed, 30 Jun 2021 09:57:51 +0200	[thread overview]
Message-ID: <d8ffcaa1-e191-0430-c3a5-f6bc08da0646@proxmox.com> (raw)
In-Reply-To: <CAMnnoULrcogMaE7AddZsgW32tYBwYX8bT8cER1KU_n6_gA5e6Q@mail.gmail.com>

Am 29.06.21 um 01:19 schrieb Victor Hooi:
> Hi,
> 
> Yes, I can confirm that file exists on my system:
> 
> root@angusmtv-vm01:/etc/sudoers.d# cat ceph-osd-smartctl
>> ## allow ceph-osd (which runs as user ceph) to collect device health
>> metrics
> 
> 
> ceph ALL=NOPASSWD: /usr/sbin/smartctl -x --json=o /dev/*
>> ceph ALL=NOPASSWD: /usr/sbin/nvme * smart-log-add --json /dev/*
> 
> 
> This was a fresh install of Proxmox 7.0 beta, with Ceph, I haven't really
> made any changes outside of setting the Ceph keyring, so that ceph-volume
> batch would work:
> 
> ceph auth get client.bootstrap-osd >
>> /var/lib/ceph/bootstrap-osd/ceph.keyring
> 
> 
> The nvme-cli package was *not* installed:
> 
> # dpkg -s nvme-cli
>> dpkg-query: package 'nvme-cli' is not installed and no information is
>> available
>> Use dpkg --info (= dpkg-deb --info) to examine archive files.
> 
> 
> I've just installed it - should that make those errors go away?
> 

Yes. I now debugged this a bit further: Ceph uses 'sudo nvme ...' when 
executing the command, but if 'nvme' can't be found in the PATH, the 
sudoers rule does not seem to apply, because it is for '/usr/sbin/nvme'.

Seems like something with sudo changed too. Given the same sudoers file 
and not having 'nvme-cli' installed, for an unprivileged user using
     sudo nvme qemu smart-log-add --json /dev/sdc
and Ctrl+D-ing the password prompt results in a notification in PVE 7.0, 
but not in PVE 6.4.

> Should we install nvme-cli by default then?
> 

It is in Recommends for the ceph package, but when installing via the 
API we use 'apt --no-install-recommends' for some reason. Maybe somebody 
else knows why?

> Out of curiosity - where do you see the hardware status via Ceph
>

I think you can use
     ceph device ls
to get the list of devices and then
     ceph device get-health-metrics <DEVICE>

> Thanks
> Victor
> 
> On Mon, Jun 28, 2021 at 5:54 PM Fabian Ebner <f.ebner@proxmox.com> wrote:
> 
>> Am 25.06.21 um 03:31 schrieb Victor Hooi:
>>> Hi,
>>>
>>> I've setup a new Ceph cluster with the Proxmox 7.0 beta
>>>
>>> I'm getting notification emails like this:
>>>
>>> ceph : a password is required ; PWD=/ ; USER=root ; COMMAND=nvme intel
>>>> smart-log-add --json /dev/nvme0n1
>>>
>>>
>>> Do you know if this is expected behaviour, or what it means? Is this some
>>> kind of new logging in Ceph 16 or Proxmox 7?
>>>
>>> Thanks,
>>> Victor
>>> _______________________________________________
>>> pve-devel mailing list
>>> pve-devel@lists.proxmox.com
>>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>>>
>>>
>>
>> Hi,
>>
>> in addition to what Dominik said: Is nvme-cli installed?
>>
>> Best Regards,
>> Fabi
>>
>>
>> _______________________________________________
>> pve-devel mailing list
>> pve-devel@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>>
>>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> 
> 




      reply	other threads:[~2021-06-30  7:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMnnoULK0y8YvsWZCJpwmGgQKtq=3rTG_ttEtWbDYF3+12hFzA.ref@mail.gmail.com>
2021-06-25  1:31 ` Victor Hooi
2021-06-25 11:36   ` Dominik Csapak
2021-06-25 11:39     ` Dominik Csapak
2021-06-28  7:54   ` Fabian Ebner
2021-06-28 23:19     ` Victor Hooi
2021-06-30  7:57       ` Fabian Ebner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d8ffcaa1-e191-0430-c3a5-f6bc08da0646@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal