phoshor-network manager daemon + IPMI

[Patrick Venture]

On Mon, Oct 23, 2017 at 10:18 AM, Dave Cobbley
<david.j.cobbley at linux.intel.com> wrote:
> I have been digging into the network manager as well.
> The link local problem has been popping up on our systems as well.
>
> I'm not sure why linklocaladdress causes our systems to get the 169.XX IP
> Address.
> I suspect is has something to do with the way our DHCP servers are setup on
> the network, systemd-networkd is not recognizing that we do in fact get an
> IP from DHCP.
>
> I'm assuming engineers at IBM are not seeing this behavior since the patch
> was accepted (please correct me if I'm wrong).
> Therefore this is more likely not a bug in systemd, but something strange
> with the configuration of network infrastructure.
> Either way, root cause needs to be identified.
>
> To work around it, simply delete the line linklocaladdress=xxxx from
> /etc/systemd/networkd/00-bmc-ethx.network

I ended up updating the default configuration file writer to not set
that, then found that once it had DHCP=yes in it, it also would crash
on attempt to delete (from the exception it raises when you try)

>
> Let me know if you make any more observations about the strange behavior (it
> would be nice to get past this issue).
>
> Thanks,
> -Dave Cobbley
>
>
> On 10/23/2017 07:48 AM, Patrick Venture wrote:
>
>> I'm curious if anyone has experience using the phosphor-network
>> manager daemon. I've run into some oddities using it for instance, if
>> you don't configure anything it sets up both links as LinkLocal and
>> enables DHCP, etc -- and then even if DHCP fails, it doesn't update it
>> (although it's aware of the failure) -- and when I then go to set the
>> IP address over IPMI to a static IP, I run the two lan channel set
>> commands which work (because they just set the object contents) --
>> when i call "access on" over IPMI, it tries to delete all the dbus
>> objects for the network, which fail because of checks in the network
>> daemon that prevent this, which causes the network daemon to crash.
>>
>> Ultimately I'm going to enable the host ipmi daemon to support
>> multiple channels -- the trick is then to map the channel to an
>> ethernet device...  Some patches will be send up today to reviewing
>> this type of change.
>>
>> I'm going through the uses cases now trying to get it working, and
>> just curious what I should be doing to get it to work.
>>
>> Also of note, when I set the MAC address -- which works :), it doesn't
>> update the configuration for the systemd network file with that
>> information  -- I'll be sending a patch for that today -- but I was
>> curious if that was deliberate, etc.
>>
>> Thanks,
>> Patrick
>
>