Bug 2044544
| Summary: | Cloud init attempts to rename physical interface with bridge name after reboot | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | James Parker <jparker> |
| Component: | openstack-tripleo-common | Assignee: | Adriano Petrich <apetrich> |
| Status: | CLOSED DUPLICATE | QA Contact: | David Rosenfeld <drosenfe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17.0 (Wallaby) | CC: | dvd, mburns, sbaker, slinaber |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-01-25 20:45:20 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** This bug has been marked as a duplicate of bug 1773642 *** |
Description of problem: Cloud-init attempts to rename the physical interface attached to the bridge with the the bridge name (see below). This seems to be very similar to the previously filed BZ [1], but now cloud-init is reporting a RTNETLINK File exists when it attempts to set the physical interface name to the bridge name, e.g. 'ip link set ens4 name br-isolated'. This is can currently be triggered after the network configuration has been applied and a reboot as been executed. In the below output the reboot was triggered by OOO to apply KernelArgs from the deployment. Job logs can be found here [2]. This has been reproduced in both virtualized and physical environments. # Deployment calls reboot on compute for KernelArgs to take effect: [heat-admin@compute-0 ~]$ sudo journalctl -u cloud-init ... Jan 24 12:43:23 compute-0 systemd[1]: Started Initial cloud-init job (metadata service crawler). Jan 24 12:50:03 compute-0 systemd[1]: cloud-init.service: Succeeded. Jan 24 12:50:03 compute-0 systemd[1]: Stopped Initial cloud-init job (metadata service crawler). -- Reboot -- Jan 24 12:50:38 compute-0 systemd[1]: Starting Initial cloud-init job (metadata service crawler)... Jan 24 12:50:39 compute-0 cloud-init[2095]: Cloud-init v. 20.3-10.el8_4.5 running 'init' at Mon, 24 Jan 2022 17:50:39 +0000. Up 30.36 seconds. Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: ++++++++++++++++++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++++++++++++++++ Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: +-------------+-------+------------------------------+---------------+--------+-------------------+ Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: +-------------+-------+------------------------------+---------------+--------+-------------------+ Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | br-isolated | True | fe80::5054:ff:fec6:3242/64 | . | link | 52:54:00:c6:32:42 | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | ens3 | True | 192.168.24.21 | 255.255.255.0 | global | 52:54:00:ec:28:04 | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | ens3 | True | fe80::5054:ff:feec:2804/64 | . | link | 52:54:00:ec:28:04 | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | ens4 | True | fe80::5054:ff:fec6:3242/64 | . | link | 52:54:00:c6:32:42 | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | ens5 | True | fe80::5054:ff:fe10:8ce6/64 | . | link | 52:54:00:10:8c:e6 | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | host | . | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | lo | True | ::1/128 | . | host | . | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | ovs-system | False | . | . | . | 72:32:13:15:9a:15 | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | vlan20 | True | 172.17.1.91 | 255.255.255.0 | global | a2:9a:20:cd:2c:c2 | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | vlan20 | True | fe80::a09a:20ff:fecd:2cc2/64 | . | link | a2:9a:20:cd:2c:c2 | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | vlan30 | True | 172.17.3.125 | 255.255.255.0 | global | 22:21:4d:17:99:a0 | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | vlan30 | True | fe80::2021:4dff:fe17:99a0/64 | . | link | 22:21:4d:17:99:a0 | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | vlan50 | True | 172.17.2.74 | 255.255.255.0 | global | 76:a0:4e:62:e8:8b | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | vlan50 | True | fe80::74a0:4eff:fe62:e88b/64 | . | link | 76:a0:4e:62:e8:8b | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: +-------------+-------+------------------------------+---------------+--------+-------------------+ Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: ++++++++++++++++++++++++++++++Route IPv4 info++++++++++++++++++++++++++++++ Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: +-------+--------------+--------------+---------------+-----------+-------+ Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: +-------+--------------+--------------+---------------+-----------+-------+ Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 0 | 0.0.0.0 | 192.168.24.1 | 0.0.0.0 | ens3 | UG | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 1 | 172.17.1.0 | 0.0.0.0 | 255.255.255.0 | vlan20 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 2 | 172.17.2.0 | 0.0.0.0 | 255.255.255.0 | vlan50 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 3 | 172.17.3.0 | 0.0.0.0 | 255.255.255.0 | vlan30 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 4 | 192.168.24.0 | 0.0.0.0 | 255.255.255.0 | ens3 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: +-------+--------------+--------------+---------------+-----------+-------+ Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: ++++++++++++++++++++++++++++++++Route IPv6 info++++++++++++++++++++++++++++++++ Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: +-------+---------------------+-------------------------+-------------+-------+ Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | Route | Destination | Gateway | Interface | Flags | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: +-------+---------------------+-------------------------+-------------+-------+ Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 9 | 2620:52:0:13b8::/64 | :: | ens5 | Ue | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 11 | fe80::/64 | :: | br-isolated | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 12 | fe80::/64 | :: | ens3 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 13 | fe80::/64 | :: | ens4 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 14 | fe80::/64 | :: | ens5 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 15 | fe80::/64 | :: | vlan20 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 16 | fe80::/64 | :: | vlan30 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 17 | fe80::/64 | :: | vlan50 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 18 | ::/0 | fe80::5054:ff:fe01:82d7 | ens5 | UGe | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 20 | local | :: | vlan30 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 21 | local | :: | ens5 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 22 | local | :: | br-isolated | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 23 | local | :: | ens4 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 24 | local | :: | ens3 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 25 | local | :: | vlan50 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 26 | local | :: | vlan20 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 27 | ff00::/8 | :: | br-isolated | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 28 | ff00::/8 | :: | ens3 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 29 | ff00::/8 | :: | ens4 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 30 | ff00::/8 | :: | ens5 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 31 | ff00::/8 | :: | vlan20 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 32 | ff00::/8 | :: | vlan30 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: | 33 | ff00::/8 | :: | vlan50 | U | Jan 24 12:50:39 compute-0 cloud-init[2095]: ci-info: +-------+---------------------+-------------------------+-------------+-------+ Jan 24 12:50:39 compute-0 cloud-init[2095]: 2022-01-24 17:50:39,348 - stages.py[WARNING]: Failed to rename devices: [unknown] Error performing rename('ens4', 'br-isolated') for 52:54> Jan 24 12:50:39 compute-0 cloud-init[2095]: Command: ['ip', 'link', 'set', 'ens4', 'name', 'br-isolated'] Jan 24 12:50:39 compute-0 cloud-init[2095]: Exit code: 2 Jan 24 12:50:39 compute-0 cloud-init[2095]: Reason: - Jan 24 12:50:39 compute-0 cloud-init[2095]: Stdout: Jan 24 12:50:39 compute-0 cloud-init[2095]: Stderr: RTNETLINK answers: File exists Jan 24 12:50:39 compute-0 systemd[1]: Started Initial cloud-init job (metadata service crawler). Version-Release number of selected component (if applicable): RHOS 17.0 How reproducible: 100% of the time Steps to Reproduce: 1. Deploy a 17 environment 2. Have THT parameters that reboot the computes after networking config is applied, or reboot computes after deployment is finalized 3. Actual results: cloud-init fails to finalized, the physcial interface associated with its respective bridge is in a down stage, connectivity with the controller is lost Expected results: Interface rename is not executed, cloud-init finalizes, controller to compute connectivity remains. Additional info: [1] https://bugzilla.redhat.com/show_bug.cgi?id=1795383 [2] http://rhos-ci-logs.lab.eng.tlv2.redhat.com/logs/staging/DFG-compute-nova-17.0_director-rhel-virthost-1cont_2comp-ipv4-geneve-smt-whitebox-numa-tests-phase3/4/