As far as I can see, though, the default policy should work for the passwords that MAAS generates. When generating passwords we generate two; one simple (which doesn't comply) and one with special characters, which should be good enough.
Can you check the settings in XClarity to see if you have enable some additional restrictions?
I found some info on the password policy for Lenovo here: https:/ /sysmgt. lenovofiles. com/help/ index.jsp? topic=% 2Fcom.lenovo. systems. management. xcc.doc% 2FNN1ia_ c_accountsecuri typolicysetting s.html
As far as I can see, though, the default policy should work for the passwords that MAAS generates. When generating passwords we generate two; one simple (which doesn't comply) and one with special characters, which should be good enough.
Can you check the settings in XClarity to see if you have enable some additional restrictions?
Also, it would be good if you could upload this file as a commissioning script called 29-debug- 01-bmc- config: https:/ /people. canonical. com/~bjorn/ bug-1993916/ bmc_config. py
If you then re-run the commissioning you should see which password it's trying to use.