From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v4 manager] ui: ceph: improve discoverability of warning details
Date: Tue, 30 May 2023 11:33:11 +0200 [thread overview]
Message-ID: <f7777f84-f7c6-440f-a6be-cff3bf62c7db@proxmox.com> (raw)
In-Reply-To: <23e7f1a0-e69b-ac3d-98d5-73eb0664522c@proxmox.com>
On 5/28/23 19:32, Thomas Lamprecht wrote:
> Am 26/05/2023 um 10:39 schrieb Aaron Lauterer:
>> ping? Considering that some users are rather hesitant to upgrade to a major version, it might be a good idea to still get this into Proxmox VE 7 to make it easier for users to discover more details about any issues they experience.
>
> I think that's probably the best argument can make here, as this is to much
> in "new feature" territory for my taste.
> But, wouldn't this be possible besser solved in the checker script though?
> If one gets as far as seeing warnings in the UI overview but just can't figure
> out how to view details on them I'd think that they either ask on a support
> channel or could see more details in the checker script which they should run
> anyway, avoiding any breakage potential.
If you mean the pve7to8 script with the checker script, then yeah, having that
in there too is of course a good idea, if it isn't yet.
My argument is that with the details for warnings easier to discover, we could
reduce the amount of people asking in the forum or opening support tickets.
Going from experience with PVE 6, PVE 7 will (unfortunately) still be in use for
quite a while after 8 has been released. That is why I would like to still see
this change in PVE 7.
But as you see fit.
prev parent reply other threads:[~2023-05-30 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 13:09 Aaron Lauterer
2023-05-26 8:39 ` Aaron Lauterer
2023-05-28 17:32 ` Thomas Lamprecht
2023-05-30 9:33 ` Aaron Lauterer [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=f7777f84-f7c6-440f-a6be-cff3bf62c7db@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox