ifupdown=0.7.47.2ubuntu4.3 from trusty-updates breaks networking if we bridge vlans over bonded interfaces

[Dmitry Bilunov]

We need to have a patched version of ifupdown=0.7.47.2ubuntu4.3 in our repositories for Fuel 8.0 and 9.0
to avoid regression, introduced by recursion detection code.
Here is a patch which fixes the problem: http://launchpadlibrarian.net/235926320/ifupdown_0.7.47.2ubuntu4.1_0.7.47.2ubuntu4.3.diff.gz

[Dmitry Bilunov (dbilunov)]

Fixing this bug will also fix #1546947

[Roman Podoliaka (rpodolyaka)]

Do we really need a separate bug for this? Why not just specify the root cause in the original bug?

[Dmitry Bilunov (dbilunov)]

dteselkin asked for a separate bug.

[Fuel Devops McRobotson (fuel-devops-robot)]

Related fix proposed to branch: master
Change author: Aleksandr Mogylchenko <email address hidden>
Review: https://review.fuel-infra.org/17300

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/17300
Submitter: Mateusz Matuszkowiak <email address hidden>
Branch: master

Commit: f4ae3d34f371f2c0f8d9e8c171f59d981803554d
Author: Aleksandr Mogylchenko <email address hidden>
Date: Mon Feb 22 12:46:32 2016

Add new project

- packages/trusty/ifupdown

We need to rebuild ifupdown with the patch that is not yet proposed, thus
custom project.

Change-Id: Iffb7ac5f04e3ed558f7f87eaae2f156d6f084c47
Related-Bug: #1547545

[Fuel Devops McRobotson (fuel-devops-robot)]

Fix proposed to branch: master
Change author: Aleksandr Mogylchenko <email address hidden>
Review: https://review.fuel-infra.org/17305

[Artem Panchenko (apanchenko-8)]

>Here is a patch which fixes the problem: http://launchpadlibrarian.net/235926320/ifupdown_0.7.47.2ubuntu4.1_0.7.47.2ubuntu4.3.diff.gz

Actually, that patch broke things, see details in https://bugs.launchpad.net/fuel/+bug/1546947/comments/8 We don't need to re-build 'ifupdown' package, we can just re-use older Ubuntu's package which worked fine on Fuel:

http://launchpadlibrarian.net/175234326/ifupdown_0.7.47.2ubuntu4.1_amd64.deb

Can we just put ifupdown_0.7.47.2ubuntu4.1 package into the our holdback repo 'mos8.0-holdback' until upstream bug #1545302 is fixed and Ubuntu prepared new package for Trusty updates?

[Aleksander Mogylchenko (amogylchenko)]

@apanchenko, I'm not sure I understood your comment. We are rebuilding ifupdown with this patch:
https://launchpadlibrarian.net/240329706/trusty_ifupdown_0.7.47.2ubuntu4.4.debdiff

As to the pinning - it is a bad idea to downgrade package versions, especially when a fix is available. Since recursion detection was added for a reason, and it will be present in the package when upstream bug is fixed, it is better to preserve it.

[Fuel Devops McRobotson (fuel-devops-robot)]

Fix proposed to branch: 9.0
Change author: Aleksandr Mogylchenko <email address hidden>
Review: https://review.fuel-infra.org/17307

[Fuel Devops McRobotson (fuel-devops-robot)]

Change abandoned by Aleksandr Mogylchenko <email address hidden> on branch: 9.0
Review: https://review.fuel-infra.org/17307

[Aleksander Mogylchenko (amogylchenko)]

As per comment:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1545302/comments/33

updated ifupdown was released to trusty-updates. Changelog confirms the fix:
http://changelogs.ubuntu.com/changelogs/pool/main/i/ifupdown/ifupdown_0.7.47.2ubuntu4.4/changelog

[Timur Nurlygayanov (tnurlygayanov)]

Ok marked as released for MOS 9.0 #495 RC2.

[Fuel Devops McRobotson (fuel-devops-robot)]

Change abandoned by Dmitry Teselkin <email address hidden> on branch: master
Review: https://review.fuel-infra.org/17305
Reason: updated ifupdown was released to trusty-updates, we don't need this CR anymore