From: Stefan Sterz <s.sterz@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager] ui: remove ceph-mgr pools from rbd pool selection
Date: Wed, 12 Oct 2022 15:22:18 +0200 [thread overview]
Message-ID: <20221012132218.395848-1-s.sterz@proxmox.com> (raw)
when using a hyper-converged cluster it was previously possible to add
the pool used by the ceph-mgr modules (".mgr" since quincy or
"device_health_metrics" previously) as an RBD storage. this would lead
to all kinds of errors when that storage was used (e.g.: VMs missing
their disks after a migration). hence, filter these pools from the
list of available pools.
Signed-off-by: Stefan Sterz <s.sterz@proxmox.com>
---
www/manager6/form/CephPoolSelector.js | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/www/manager6/form/CephPoolSelector.js b/www/manager6/form/CephPoolSelector.js
index 5b96398d..eabb04ef 100644
--- a/www/manager6/form/CephPoolSelector.js
+++ b/www/manager6/form/CephPoolSelector.js
@@ -15,9 +15,17 @@ Ext.define('PVE.form.CephPoolSelector', {
throw "no nodename given";
}
+ let filterCephMgrPools = (item) => {
+ let name = item.data.pool_name;
+ return name !== ".mgr" && name !== "device_health_metrics";
+ };
+
var store = Ext.create('Ext.data.Store', {
fields: ['name'],
sorters: 'name',
+ filters: [
+ filterCephMgrPools,
+ ],
proxy: {
type: 'proxmox',
url: '/api2/json/nodes/' + me.nodename + '/ceph/pools',
@@ -32,8 +40,10 @@ Ext.define('PVE.form.CephPoolSelector', {
store.load({
callback: function(rec, op, success) {
- if (success && rec.length > 0) {
- me.select(rec[0]);
+ let filteredRec = rec.filter(filterCephMgrPools);
+
+ if (success && filteredRec.length > 0) {
+ me.select(filteredRec[0]);
}
},
});
--
2.30.2
next reply other threads:[~2022-10-12 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 13:22 Stefan Sterz [this message]
[not found] ` <40F19362-B31D-460A-B995-9F3E366C55F5@antreich.com>
2022-10-14 8:01 ` Stefan Sterz
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=20221012132218.395848-1-s.sterz@proxmox.com \
--to=s.sterz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox