MAAS 2.3.0 RC1 no longer set proper BMC credentials at enlisting step.

[Andres Rodriguez]

Hi Gael,

MAAS 2.3.0 RC 1 has primarily 2 sets of fixes. The first one is Hardware
Testing and the second is HA. There's a couple other improvements as well
but none of them actually impact the BMC discovery and configuration. In
fact, no changes have been made in that area in the past 2 or 3 releases.

That said, I'd recommend you file a bug an attach the following:

1. Console log of the machine in question
2. /var/log/maas/rsyslog/<machine name>/  # If the machine is commissioning
3. /var/log/maas/rsyslog/maas-enlisting-node/ # if the machine is enlisting
(not previously known to MAAS)
4. /etc/maas/rackd.conf
5. /var/log/maas/regiond.log

That will help us determine what your issue could be.

Thanks!

On Tue, Nov 7, 2017 at 8:03 AM, Flint WALRUS <gael.therond at gmail.com> wrote:

> Hi everyone, just installed MAAS 2.3.0 RC1 using the PPA:Next channel.
>
> It seems there is a regression because all servers booting within maas
> supervision will no longer correctly set the BMC credentials.
>
> With RC1 I know have to manually set the power management settings where I
> didn't have to with an older 2.2.3 or 2.3.0 Beta3 release.
>
> It seems that maas doesn't set it own MAAS IPMI User during the enlisting
> process.
>
> Is that something expected?
>
> --
> Maas-devel mailing list
> Maas-devel at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/maas-devel
>
>


-- 
Andres Rodriguez
Engineering Manager, MAAS
Canonical USA, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/maas-devel/attachments/20171107/bfe41e7b/attachment.html>