Activity log for bug #2068502

Date Who What changed Old value New value Message
2024-06-05 15:15:07 Jeff Lane  bug added bug
2024-06-05 15:15:30 Jeff Lane  description MAAS: 3.4.2 I am enlisting and commissioning a Lenovo SD550 V3 server in our MAAS. I powered the machine on and it completed enlistment and appeared in the UI as a New server. However, power status was marked as an Error. On further investigation, the Cipher Suite ID in the Configuration for that machine was set to 3. To see if that had anything to do with the power control issues, I set it to 17 and saved the config change. After that, MAAS was able to successfully probe power status and was able to control the power to turn the machine on when I selected "Commission" from the action menu. Commissioning was successful as well, however, after commissioning, power status checking was again failing. I went back to the machines Configuration page and noted that the Cipher Suite ID had been changed back to 3 again. So once more, changing that to 17 and saving it allowed MAAS to successfully probe power on this machine. As a check, I then recommissioned the machine. MAAS again was able to power the machine on, which successfully completed commissioning a second time. And just as before, MAAS changed the Cipher Suite ID back to 3, causing power control to fail. MAAS: 3.4.2 I am enlisting and commissioning a Lenovo SD550 V3 server in our MAAS. I powered the machine on and it completed enlistment and appeared in the UI as a New server. However, power status was marked as an Error. On further investigation, the Cipher Suite ID in the Configuration for that machine was set to 3. To see if that had anything to do with the power control issues, I set it to 17 and saved the config change. After that, MAAS was able to successfully probe power status and was able to control the power to turn the machine on when I selected "Commission" from the action menu. Commissioning was successful as well, however, after commissioning, power status checking was again failing. I went back to the machines Configuration page and noted that the Cipher Suite ID had been changed back to 3 again. So once more, changing that to 17 and saving it allowed MAAS to successfully probe power on this machine. As a check, I then recommissioned the machine. MAAS again was able to power the machine on, which successfully completed commissioning a second time. And just as before, MAAS changed the Cipher Suite ID back to 3, causing power control to fail. Ref: Yakkey in the Cert Lab
2024-06-06 09:25:25 Alessandro Marcolini maas: status New Invalid
2024-06-06 13:42:33 Jeff Lane  maas: status Invalid New
2024-06-10 12:24:23 Mauricio Faria de Oliveira bug added subscriber Mauricio Faria de Oliveira
2024-06-10 14:22:50 Alessandro Marcolini bug added subscriber Alessandro Marcolini
2024-06-10 14:27:02 Jacopo Rota summary MAAS 3.4.2 keeps resetting Cipher Suite ID during commissioning MAAS sets an invalid choice for the IPMI cipher suite ID during commissioning
2024-06-10 14:27:18 Jacopo Rota maas: status New Triaged
2024-06-10 14:27:20 Jacopo Rota maas: importance Undecided High
2024-06-10 14:27:27 Jacopo Rota maas: milestone 3.6.0
2024-06-10 14:27:31 Jacopo Rota maas: importance High Medium