fixed_network_name still exists in drivers except heat

[Sebastian Schmid]

Bug:

I have installed OpenStack Ussuri via Kolla ansible in a "all in one" Installation on Ubuntu 18.04 including Magnum.

The core Modules are working, i could also define a Cluster Template, but on Cluster Create I get the following Error:

Status
    CREATE_FAILED
Status Reason
    ERROR: The Parameter (fixed_network_name) was not defined in template.

I can not find a Parameter "fixed_network_name" in the cluster Template or the Magnum Docs.

This is the output of "openstack coe cluster show":
+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field | Value |
+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+
| status | CREATE_FAILED |
| health_status | None |
| cluster_template_id | 17e0cf90-aa46-4deb-94d0-588f51c4425e |
| node_addresses | [] |
| uuid | 1fd23a29-c3d5-418e-b5de-88748be9aed0 |
| stack_id | None |
| status_reason | ERROR: The Parameter (fixed_network_name) was not defined in template. |
| created_at | 2020-10-27T15:28:03+00:00 |
| updated_at | 2020-10-27T15:28:07+00:00 |
| coe_version | None |
| labels | {'kube_dashboard_enabled': '0', 'kube_tag': '1.16.2', 'availability_zone': 'nova', 'auto_scaling_enabled': 'False', 'auto_healing_enabled': 'False'} |
| labels_overridden | {} |
| labels_skipped | {} |
| labels_added | {'availability_zone': 'nova', 'auto_scaling_enabled': 'False', 'auto_healing_enabled': 'False'} |
| fixed_network | None |
| fixed_subnet | None |
| floating_ip_enabled | True |
| faults | {} |
| keypair | mykey |
| api_address | None |
| master_addresses | [] |
| master_lb_enabled | False |
| create_timeout | 60 |
| node_count | 1 |
| discovery_url | https://discovery.etcd.io/bb6df4122b6fb40ac379069c9e8504cd |
| master_count | 1 |
| container_version | None |
| name | test |
| master_flavor_id | m1.small |
| flavor_id | m1.small |
| health_status_reason | {} |
| project_id | 3d5630059f3c4e678eea1a76a94c6f3c |
+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+

~danvatca found out the following (https://answers.launchpad.net/ubuntu/+source/magnum/+question/693674):
It looks as the fixed_network_name was removed from the template configuration, and is now read from the fixed_network object.
However only the heat driver got the memo and the updates.
The coreos, fedora_coreos, fedora_atomic and other drivers are still looking for that parameter.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Thiago Martins (martinx)]

I'm facing the very same problem with OpenStack Ansible, branch `stable/ussuri`, on Ubuntu 20.04.1.

[Thiago Martins (martinx)]

I actually changed the value os `os_distro` from just "coreos" to "fedora-coreos" and it worked!
I mean, I'm not seeing this error anymore.

[Dmitriy Rabotyagov (noonedeadpunk)]

fedora-coreos worked for me as well. That totally sounds like magnum bug...

[Dmitriy Rabotyagov (noonedeadpunk)]

I've reported bug to magnum https://storyboard.openstack.org/#!/story/2008596

[Noel Ashford (nashford77)]

I have this problem and I have fedora-coreos set, also tried with coreos, both giving me the same on 2023.1 kolla ansible? Did this regress ?

2024-01-27 05:31:13.291 733 ERROR oslo_messaging.rpc.server result = f(*args, **kwargs)
2024-01-27 05:31:13.291 733 ERROR oslo_messaging.rpc.server File "/var/lib/kolla/venv/lib/python3.10/site-packages/magnum/conductor/handlers/cluster_conductor.py", line 95, in cluster_create
2024-01-27 05:31:13.291 733 ERROR oslo_messaging.rpc.server raise e
2024-01-27 05:31:13.291 733 ERROR oslo_messaging.rpc.server magnum.common.exception.InvalidParameterValue: ERROR: The Parameter (fixed_network_name) was not defined in template.
2024-01-27 05:31:13.291 733 ERROR oslo_messaging.rpc.server

(kolla-2023.1) root@cube-server:~# openstack image show 9ef2e161-ef52-4bb6-a582-af76da53ca6e
+------------------+-------------------------------------------------------------------------------------------------------+
| Field | Value |
+------------------+-------------------------------------------------------------------------------------------------------+
| checksum | 9e7192c038d96481659148a744ae9109 |
| container_format | bare |
| created_at | 2023-08-07T03:17:27Z |
| disk_format | qcow2 |
| file | /v2/images/9ef2e161-ef52-4bb6-a582-af76da53ca6e/file |
| id | 9ef2e161-ef52-4bb6-a582-af76da53ca6e |
| min_disk | 0 |
| min_ram | 0 |
| name | CoreOS |
| owner | e5b9296fbd9e4d9ea5e925780c64690f |
| properties | os_distro='fedora-coreos', os_hash_algo='sha512', os_hash_value='65b1cd8a986b8914827ca2d50d38d1fbff17 |
| | 53bc8f56927efab94fc7be638cd795c6c76d58b65bbf2449eca2ed592f2c2ab2e0d5d03a307607eeae504fe7618e', |
| | os_hidden='False', owner_specified.openstack.md5='', |
| | owner_specified.openstack.object='images/CoreOS', owner_specified.openstack.sha256='', stores='swift' |
| protected | False |
| schema | /v2/schemas/image ...

[Noel Ashford (nashford77)]

Never mind, once i deleted the bad template and made a new one post the distro metadata update, it was fine. Can someone also please fix the documentation online as this is happening i think as that still says to use coreos incorrectly. This snagged me twice ;0