1:20 a.m.
Hi,
While trying to delete the Default cluster in oVirt it shows the below
error message -
"Cannot remove default Host Cluster.
Cannot remove Cluster. One or more Template(s) are still associated with it"
But in the case of RHSC, Templates are not used and this message is not
relevant. [1].
Can we opt for not installing the templates while engine setup? And
would it be having any impact/consequences ?
Kindly provide your thoughts and possibility of the same.
Thanks and Regards,
Shubhendu
PS:
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1019838
11:14 a.m.
----- Original Message -----
From: "Shubhendu Tripathi" <shtripat(a)redhat.com>
To: "engine-devel" <engine-devel(a)ovirt.org>, "michal skrivanek"
<michal.skrivanek(a)redhat.com>, "Omer Frenkel"
<ofrenkel(a)redhat.com>, "Allon Mureinik" <amureini(a)redhat.com>
Cc: "Dusmant Pati" <dpati(a)redhat.com>
Sent: Monday, November 11, 2013 8:20:41 AM
Subject: Error message while trying to delete default cluster
Hi,
While trying to delete the Default cluster in oVirt it shows the below
error message -
"Cannot remove default Host Cluster.
Cannot remove Cluster. One or more Template(s) are still associated with it"
But in the case of RHSC, Templates are not used and this message is not
relevant. [1].
Can we opt for not installing the templates while engine setup? And
would it be having any impact/consequences ?
Kindly provide your thoughts and possibility of the same.
Thanks and Regards,
Shubhendu
PS:
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1019838
removing the blank template means the system couldn't be used to create vms at all.
but blank template is not the only problem,
there is an explicit check that prevent deleting the default cluster
(RemoveVdsGroupCommand class, line #35),
i couldn't find the commit that added this,
but i /think/ its because by default host registration is done to the default cluster,
so it had to exist.
so this should be solved first.
then, if we decide to have a 'non-virt' installation we probably could avoid
default cluster and blank template.
but what if user changes his mind after installation?
another option is to remove the protection from DB level and make cluster-id nullable in
the vm_static table,
and have logic to allow removing last cluster and update template on new cluster
addition.
4060
days inactive
4063
days old
1 comments
2 participants
participants (2)
-
Omer Frenkel -
Shubhendu Tripathi