Re: [PATCH 2/5] util: don't log error in virNetDevVPortProfileGetStatus if instanceId is NULL

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Laine Stump <laine@xxxxxxxxx> wrote on 12/21/2015 12:17:54 PM:


>
> This does cause a difference in behavior, so I want confirmation from
> Cisco and IBM that this behavior change is desired (or at least not
> *un*desired) - rather than returning with status unchanged (and thus
> always 0, aka PORT_VDP_RESPONSE_SUCCESS) when instanceId is NULL, it
> will actually get the IFLA_PORT_RESPONSE. This could lead to
> revelation of error conditions we were previously ignoring. Or
> not. Only experimentation will tell. Note that for 802.1Qbg instanceId
> is *always* NULL, and for 802.1Qbh, it is NULL for all DISASSOCIATE
> commands.


I have forwarded this request to others who have the hardware to test with, though this may take some time to get an answer back...

   Stefan


--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]