3:53 p.m.
Test: 'set_dc_quota_audit' fails with:
detail: Cannot migrate MACs to another MAC pool, because that action would
create duplicates in target MAC pool, which are not allowed. Problematic
MACs are 54:52:c0:a8:c8:63
I'm now testing on Master to see if the same thing happens there.
The MAC above belongs to the HE VM. Perhaps I should pick one outside the
range?
Y.
6:12 p.m.
On Fri, Sep 22, 2017 at 11:53 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote:
Test: 'set_dc_quota_audit' fails with:
detail: Cannot migrate MACs to another MAC pool, because that action would
create duplicates in target MAC pool, which are not allowed. Problematic
MACs are 54:52:c0:a8:c8:63
I'm now testing on Master to see if the same thing happens there.
Master seems OK.
Y.
The MAC above belongs to the HE VM. Perhaps I should pick one outside the
range?
Y.
8:16 a.m.
On Sat, Sep 23, 2017 at 2:12 AM, Yaniv Kaul <ykaul(a)redhat.com> wrote:
On Fri, Sep 22, 2017 at 11:53 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote:
>
> Test: 'set_dc_quota_audit' fails with:
>
> detail: Cannot migrate MACs to another MAC pool, because that action would
> create duplicates in target MAC pool, which are not allowed. Problematic
> MACs are 54:52:c0:a8:c8:63
>
> I'm now testing on Master to see if the same thing happens there.
Master seems OK.
Y.
>
>
> The MAC above belongs to the HE VM. Perhaps I should pick one outside the
> range?
> Y.
in 4.1 we have a little mess, with 4 removeForceAddMAC patches not
yet backported (and 4 others have). This might be related - let's hope
for a quick merge of the remaining ones.
2645
days inactive
2648
days old
2 comments
2 participants
participants (2)
-
Dan Kenigsberg -
Yaniv Kaul