Comment 29 for bug 482419

Okay steve!

Shortening the patch !

regards

On Thu, Jul 15, 2010 at 1:18 AM, Steve Langasek
<email address hidden> wrote:
> Hi Bhavani,
>
> What dpkg trigger error are you trying to fix?  The changes to the
> maintainer scripts should have no effect on dpkg triggers.  In fact,
> they should have no effect in Ubuntu at all because the change only
> applies to upgrades from version 1.1.0-6 or before, which is the version
> that was in dapper.  (If a user *does* try to upgrade directly from
> dapper, then this won't work either, because you use the wrong conffile
> names in your patch to the preinst).  If you believe this is an
> important change to make in spite of this, please provide a separate bug
> reference in the changelog; there should be a separate bug report in
> Launchpad for each issue being fixed in SRU.
>
> As for the pre-up change:  why is this function being split into two?
> The two halves of the function are still being called, in the same
> order, with nothing else between them, so that seems unnecessary for an
> SRU?  The change appears to be equivalent to this much shorter patch:
>
> @@ -128,2 +131,2 @@
> -enslave_slaves
>  setup_master
> +enslave_slaves
>
> Have I overlooked some reason that we want to split the function?
>
> --
> 802.3ad interface bonding fails if started too early
> https://bugs.launchpad.net/bugs/482419
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “ifenslave-2.6” package in Ubuntu: Fix Released
> Status in “ifenslave-2.6” source package in Lucid: Triaged
> Status in “ifenslave-2.6” package in Debian: Unknown
>
> Bug description:
> 802.3ad bonding configurations that formerly worked on jaunty are now failing on startup under karmic. After the system has started, restarting networking will bring the bond up correctly. This only applies to bond_mode 4 / 802.3ad, I've tested that switching to bond_mode 0 corrects the issue, and other users experiencing this bug all were using bond_mode 4 as well.
>
> dmesg output fills with "bonding: bond0: Warning: Found an uninitialized port", even after the system starts up and the port should be "initialized"
>
> It appears to occur on multiple drivers (bnx2, e1000 confirmed).
>
> One initially wants to blame the startup ordering due to the switch to upstart, but I believe it is an edge case that hasn't been seen before because we haven't been starting up so quickly that the hardware hasn't had time to fully initialized.
>
> Configuration and output from multiple users is in this thread:
> http://ubuntuforums.org/showthread.php?p=8311572
>
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/ifenslave-2.6/+bug/482419/+subscribe
>

--
Bhavani Shankar.R
https://launchpad.net/~bhavi, a proud ubuntu community  member.
What matters in life is application of mind!,
It makes great sense to have some common sense..!