Public bug reported:
We see most ppc64el machines fail to acquire network IPs on scalingstack
with errors like
ValueError: Unable to find a system nic for {'mtu': 1458, 'type':
'physical', 'subnets': [{'type': 'dhcp4'}], 'mac_address':
'fa:16:3e:6d:95:51'}
In those cases, openstack generated two networks, but only one device is
actually present in the VM.
ubuntu@juju-4d1272-prod-proposed-migration-9:~$ openstack console log show
jak-s390x-impish | grep fa:16
[ 7.113131] cloud-init[439]: ValueError: Unable to find a system nic for
{'mtu': 1458, 'type': 'physical', 'subnets': [{'type': 'dhcp4'}],
'mac_address': 'fa:16:3e:a4:29:ce'}
[ 7.681157] cloud-init[464]: ci-info: | enp0s1 | False | . | .
| . | fa:16:3e:c1:f9:61 |
[ 7.761093] cloud-init[464]: ValueError: Unable to find a system nic for
{'mtu': 1458, 'type': 'physical', 'subnets': [{'type': 'dhcp4'}],
'mac_address': 'fa:16:3e:a4:29:ce'}
ubuntu@juju-4d1272-prod-proposed-migration-9:~$ openstack port list --server
jak-s390x-impish
+--------------------------------------+------+-------------------+-----------------------------------------------------------------------------+--------+
| ID | Name | MAC Address | Fixed IP
Addresses | Status |
+--------------------------------------+------+-------------------+-----------------------------------------------------------------------------+--------+
| 7c68497d-348a-4438-99df-4a7bd31734df | | fa:16:3e:a4:29:ce |
ip_address='10.44.124.6', subnet_id='694adc9c-c852-4654-937f-b2438a1bad23' |
DOWN |
| ec5f644c-6151-4ad9-bd09-7908e8956faa | | fa:16:3e:c1:f9:61 |
ip_address='10.44.124.73', subnet_id='694adc9c-c852-4654-937f-b2438a1bad23' |
ACTIVE |
+--------------------------------------+------+-------------------+-----------------------------------------------------------------------------+--------+
cloud-init must not abort here, but continue configuring the active network
device.
** Affects: cloud-init
Importance: Undecided
Status: New
** Summary changed:
- ValueError: Unable to find a system nic for {'mtu': 1458, 'type': 'physical',
'subnets': [{'type': 'dhcp4'}], 'mac_address': 'fa:16:3e:6d:95:51'}
+ "Unable to find a system nic" if openstack lists down ports in json config
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1949371
Title:
"Unable to find a system nic" if openstack lists down ports in json
config
Status in cloud-init:
New
Bug description:
We see most ppc64el machines fail to acquire network IPs on
scalingstack with errors like
ValueError: Unable to find a system nic for {'mtu': 1458, 'type':
'physical', 'subnets': [{'type': 'dhcp4'}], 'mac_address':
'fa:16:3e:6d:95:51'}
In those cases, openstack generated two networks, but only one device is
actually present in the VM.
ubuntu@juju-4d1272-prod-proposed-migration-9:~$ openstack console log show
jak-s390x-impish | grep fa:16
[ 7.113131] cloud-init[439]: ValueError: Unable to find a system nic for
{'mtu': 1458, 'type': 'physical', 'subnets': [{'type': 'dhcp4'}],
'mac_address': 'fa:16:3e:a4:29:ce'}
[ 7.681157] cloud-init[464]: ci-info: | enp0s1 | False | . | .
| . | fa:16:3e:c1:f9:61 |
[ 7.761093] cloud-init[464]: ValueError: Unable to find a system nic for
{'mtu': 1458, 'type': 'physical', 'subnets': [{'type': 'dhcp4'}],
'mac_address': 'fa:16:3e:a4:29:ce'}
ubuntu@juju-4d1272-prod-proposed-migration-9:~$ openstack port list --server
jak-s390x-impish
+--------------------------------------+------+-------------------+-----------------------------------------------------------------------------+--------+
| ID | Name | MAC Address | Fixed IP
Addresses | Status |
+--------------------------------------+------+-------------------+-----------------------------------------------------------------------------+--------+
| 7c68497d-348a-4438-99df-4a7bd31734df | | fa:16:3e:a4:29:ce |
ip_address='10.44.124.6', subnet_id='694adc9c-c852-4654-937f-b2438a1bad23' |
DOWN |
| ec5f644c-6151-4ad9-bd09-7908e8956faa | | fa:16:3e:c1:f9:61 |
ip_address='10.44.124.73', subnet_id='694adc9c-c852-4654-937f-b2438a1bad23' |
ACTIVE |
+--------------------------------------+------+-------------------+-----------------------------------------------------------------------------+--------+
cloud-init must not abort here, but continue configuring the active network
device.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1949371/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
