fixed_network_name still exists in drivers except heat

Bug #1902293 reported by Sebastian Schmid on 2020-10-30
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
magnum (Ubuntu)
Undecided
Unassigned

Bug Description

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) wrote :

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

Changed in magnum (Ubuntu):
status: New → Confirmed
Thiago Martins (martinx) wrote :

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

Thiago Martins (martinx) wrote :

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.

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

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

Other bug subscribers