The interface using on PXE could not be renamed on Ubuntu bootstrap (by udev)

Bug #1529631 reported by Albert Syriy
64
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Fix Released
Critical
Albert Syriy
7.0.x
Invalid
Critical
Albert Syriy
8.0.x
Fix Released
Critical
Albert Syriy
9.x
Fix Released
High
Albert Syriy

Bug Description

The interface using on PXE boot on Ubuntu bootstrap could not be renamed by udev.
Attempting rename the interface by udev get the error "device busy".
When we are not using the work-around ifdown/ifup eth0 we got following interface names
===
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:56:9c:63:15
          inet addr:10.20.0.3 Bcast:10.20.0.255 Mask:255.255.255.0
          inet6 addr: fe80::250:56ff:fe9c:6315/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:179224 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6795 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:270678633 (270.6 MB) TX bytes:1775628 (1.7 MB)

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

root@bootstrap:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 00:50:56:9c:63:15 brd ff:ff:ff:ff:ff:ff
3: eno33554960: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:50:56:9c:79:6e brd ff:ff:ff:ff:ff:ff
===
It happens because udev rules are applied too later, when interfaces have been up and configured.

tags: added: same-as-1529631
Revision history for this message
Alexander Gordeev (a-gordeev) wrote :

> It happens because udev rules are applied too later, when interfaces have been up and configured.

we can disable udev rules processing by

# udevadm control --stop-exec-queue

and then enable it back with

# udevadm control --start-exec-queue

however, this seems to be too fragile and could have additional side effects as well.

Changed in fuel:
importance: Undecided → High
affects: fuel → mos
Changed in mos:
milestone: 8.0 → none
milestone: none → 8.0
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :
tags: added: swarm-blocker
tags: removed: same-as-1529631
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

@asyriy please update the current state of the issue - I can see there are two patches abandoned, which is the WIP one?
Note, I also merged two ssh-related bugs as duplicates to this one as this seem the root cause for all of them

Revision history for this message
Albert Syriy (asyriy) wrote :

The fix has been committed for review
https://review.fuel-infra.org/#/c/16276/
https://review.openstack.org/#/c/270008/

The patch has been checked on the lab (successfully)

Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

7.0 is marked as affected by fuel-mcrobotson by mistake.

Revision history for this message
Albert Syriy (asyriy) wrote : Re: [Bug 1529631] Re: The interface using on PXE could not be renamed on Ubuntu bootstrap (by udev)

The fix has been tested and is about to merge.

Albert Syriy,

Software Engineer,
Mirantis

On Thu, Jan 21, 2016 at 6:55 PM, Roman Podoliaka <
<email address hidden>> wrote:

> 7.0 is marked as affected by fuel-mcrobotson by mistake.
>
> ** Changed in: mos/7.0.x
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1529631
>
> Title:
> The interface using on PXE could not be renamed on Ubuntu bootstrap
> (by udev)
>
> Status in Mirantis OpenStack:
> In Progress
> Status in Mirantis OpenStack 7.0.x series:
> Invalid
> Status in Mirantis OpenStack 8.0.x series:
> In Progress
> Status in Mirantis OpenStack 9.0.x series:
> In Progress
>
> Bug description:
> The interface using on PXE boot on Ubuntu bootstrap could not be renamed
> by udev.
> Attempting rename the interface by udev get the error "device busy".
> When we are not using the work-around ifdown/ifup eth0 we got following
> interface names
> ===
> # ifconfig
> eth0 Link encap:Ethernet HWaddr 00:50:56:9c:63:15
> inet addr:10.20.0.3 Bcast:10.20.0.255 Mask:255.255.255.0
> inet6 addr: fe80::250:56ff:fe9c:6315/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:179224 errors:0 dropped:0 overruns:0 frame:0
> TX packets:6795 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:270678633 (270.6 MB) TX bytes:1775628 (1.7 MB)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:65536 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> root@bootstrap:~# ip link
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
> DEFAULT group default
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP mode DEFAULT group default qlen 1000
> link/ether 00:50:56:9c:63:15 brd ff:ff:ff:ff:ff:ff
> 3: eno33554960: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
> mode DEFAULT group default qlen 1000
> link/ether 00:50:56:9c:79:6e brd ff:ff:ff:ff:ff:ff
> ===
> It happens because udev rules are applied too later, when interfaces
> have been up and configured.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mos/+bug/1529631/+subscriptions
>

Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

Looks like fix is on review https://review.openstack.org/#/c/270008/, so move issue status to in progress

Revision history for this message
Albert Syriy (asyriy) wrote :

The following request have been merged (branch 8.0)
https://review.fuel-infra.org/#/c/16365/

Revision history for this message
Albert Syriy (asyriy) wrote :

It was a fix for the issue, this one
https://review.openstack.org/#/c/270008/
just revert work-around

Revision history for this message
Aleksey Zvyagintsev (azvyagintsev) wrote :
Revision history for this message
Artem Panchenko (apanchenko-8) wrote :

verified

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "8.0"
  api: "1.0"
  build_number: "506"
  build_id: "506"
  fuel-nailgun_sha: "8e954abd70ef0083109f34289de2553dcda544d4"
  python-fuelclient_sha: "4f234669cfe88a9406f4e438b1e1f74f1ef484a5"
  fuel-agent_sha: "658be72c4b42d3e1436b86ac4567ab914bfb451b"
  fuel-nailgun-agent_sha: "b2bb466fd5bd92da614cdbd819d6999c510ebfb1"
  astute_sha: "b81577a5b7857c4be8748492bae1dec2fa89b446"
  fuel-library_sha: "ec7e212972ead554f21b52b9e165156665f659df"
  fuel-ostf_sha: "ab5fd151fc6c1aa0b35bc2023631b1f4836ecd61"
  fuel-mirror_sha: "351d568fa3b3e4dd062054b91d766aa54d379867"
  fuelmenu_sha: "234cb4cbb30fbd2df00f388c28f31606d9cae15f"
  shotgun_sha: "63645dea384a37dde5c01d4f8905566978e5d906"
  network-checker_sha: "a43cf96cd9532f10794dce736350bf5bed350e9d"
  fuel-upgrade_sha: "616a7490ec7199f69759e97e42f9b97dfc87e85b"
  fuelmain_sha: "94507c5e4dad6d8cfbd8f5d41aa8389d5335990a"

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.