[Bug 1589775] Re: ifupdown of ucarp interface fails

[Sangeetha Srikanth]

Hi, Thanks for confirming the defect. Is there a quick solution (patch)
for this defect as it is affecting our deployment?

** Description changed:

  lsb_release -rd
  Description:	Ubuntu 14.04.4 LTS
  Release:	14.04
  
  apt-cache policy ifupdown
  ifupdown:
-   Installed: 0.7.47.2ubuntu4.4
-   Candidate: 0.7.47.2ubuntu4.4
- 
+   Installed: 0.7.47.2ubuntu4.4
+   Candidate: 0.7.47.2ubuntu4.4
  
  ifupdown of ucarp interface fails if the interface name >=16 chars.
  
  Example configuration,
  
  bond0.1234:ucarp
  
  /usr/share/ucarp/vip-up bond0.1234 10.10.20.2
  
  RTNETLINK answers: Numerical result out of range
  Failed to bring up bond0.1234:ucarp.
  
  To work around this issue,
  1) Rename the bond0.1234:ucarp interface manually in /etc/network/interfaces file to bond0.1234:u
  2) Edit /usr/share/ucarp/vip-up and /usr/share/ucarp/vip-down script
  to use the modified interface name.
  
  /sbin/ifup $1:u
  
- 
  This issue affects all ucarp interfaces on vlans > 999.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1589775

Title:
  ifupdown of ucarp interface fails

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:	Ubuntu 14.04.4 LTS
  Release:	14.04

  apt-cache policy ifupdown
  ifupdown:
    Installed: 0.7.47.2ubuntu4.4
    Candidate: 0.7.47.2ubuntu4.4

  ifupdown of ucarp interface fails if the interface name >=16 chars.

  Example configuration,

  bond0.1234:ucarp

  /usr/share/ucarp/vip-up bond0.1234 10.10.20.2

  RTNETLINK answers: Numerical result out of range
  Failed to bring up bond0.1234:ucarp.

  To work around this issue,
  1) Rename the bond0.1234:ucarp interface manually in /etc/network/interfaces file to bond0.1234:u
  2) Edit /usr/share/ucarp/vip-up and /usr/share/ucarp/vip-down script
  to use the modified interface name.

  /sbin/ifup $1:u

  This issue affects all ucarp interfaces on vlans > 999.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1589775/+subscriptions