1. the value AutoRegistrationDefaultVdsGroupID needs to get valid cluster id by default. 2. counting on cluster "default" can lead to unclear error if user deletes this cluster - if cluster id does not exist addVdsCommand will receive groupid null and will fail the canDoAction - it's are to understand from the log why the failure occurred. I suggest to add more info to the audit log. 3. rhevh does not expose auto registration option in TUI afaik. and the config value AutoApprovePatterns not so clear (at least to me) In this bug scope I'd like to understand how the auto approval should work and be exposed to the user. for instance - the default cluster for auto approval should be set somewhere in the ui as global value imo
(In reply to Yaniv Bronhaim from comment #0) > 1. the value AutoRegistrationDefaultVdsGroupID needs to get valid cluster id > by default. addressed by gerrit.ovirt.org/#/c/37813
(In reply to Yaniv Bronhaim from comment #0) > 2. counting on cluster "default" can lead to unclear error if user deletes > this cluster - if cluster id does not exist addVdsCommand will receive > groupid null and will fail the canDoAction - it's are to understand from the > log why the failure occurred. I suggest to add more info to the audit log. > addressed by gerrit.ovirt.org/#/c/37842
Yaniv , can we move that to POST after 1) and 2) were resolved (I think 3) deserve a separate issue that is more to the long term and 1) and 2) can be applied to 3.6)
1,2 relates also to regular registration in PendingApproval state, the auto approval verification can be done separately . I'll open another bug regarding that.