The above error from comment #5 is actually caused by having duplicate IPMI BMCs where the IP+username is the same but the password is different. I have filed a new bug for this case: https://bugs.launchpad.net/maas/+bug/2025026
I did note the following in that bug relevant to this bug
> While it makes sense to avoid duplicate IPMI IP/Username/Password combinations, the current unique constraint also does not really achieve that properly since any differing config value in power_parameters would cause the Unique constraint to pass. So I also wonder if this particular Unique constraint is the best enforcement mechanism.
The above error from comment #5 is actually caused by having duplicate IPMI BMCs where the IP+username is the same but the password is different. I have filed a new bug for this case: /bugs.launchpad .net/maas/ +bug/2025026
https:/
I did note the following in that bug relevant to this bug
> While it makes sense to avoid duplicate IPMI IP/Username/ Password combinations, the current unique constraint also does not really achieve that properly since any differing config value in power_parameters would cause the Unique constraint to pass. So I also wonder if this particular Unique constraint is the best enforcement mechanism.