create network availability zone missing

[Satish Patel]

When trying to create network in skyline its asking for availability zone but my installation is default and I haven't done anything yet so why this field is mandatory and it should be using default AZ (nova)

Horizon using default nova during creating network.

Find attached screenshoot of horizon and skyline to compare.

[Satish Patel (satish-txt)]

Update:

I am running zed release of openstack with OVN based deployment.

[Satish Patel (satish-txt)]

[1] based on doc OVN doesn't have availability zone for network because OVN is distributed system. But regardless I have created availability zone in OVN using following command

# ovs-vsctl set open_vswitch . external_ids:ovn-cms-options="enable-chassis-as-gw,availability-zones=nova"

# # openstack availability zone list --network
+-----------+-------------+
| Zone Name | Zone Status |
+-----------+-------------+
| nova | available |
+-----------+-------------+

But still skyline UI can't see this AZ during network create tab. I did re-login to get new token but no luck

[Satish Patel (satish-txt)]

[1] https://docs.openstack.org/neutron/xena/admin/ovn/availability_zones.html

[Satish Patel (satish-txt)]

Just curious, any update here?

[Boxiang Zhu (bxzhu-5355)]

Run debug command like: "openstack --debug availability zone list --network" , then please supply the information of the command output. Thanks :)

[Satish Patel (satish-txt)]

@Boxiang,

Here is the full debug output - https://paste.opendev.org/show/bpSyjWDW3nMDZUiYnkkl/

[Boxiang Zhu (bxzhu-5355)]

Got it, from your debug information. I find that you only have router resource AZ to return as followed:

REQ: curl -g -i -X GET http://192.168.18.100:9696/v2.0/availability_zones -H "Accept: application/json" -H "User-Agent: openstacksdk/1.4.0 keystoneauth1/5.2.1 python-requests/2.31.0 CPython/3.10.12" -H "X-Auth-Token: {SHA256}bb5237118d960cec6fcef411492bb7124fbf42d974e272547975e792de8db133"
http://192.168.18.100:9696 "GET /v2.0/availability_zones HTTP/1.1" 200 86
RESP: [200] content-length: 86 content-type: application/json date: Tue, 19 Sep 2023 01:40:45 GMT x-openstack-request-id: req-1aa0c51d-3524-4569-b955-15e5c87b77b9
RESP BODY: {"availability_zones": [{"name": "nova", "resource": "router", "state": "available"}]}
GET call to network for http://192.168.18.100:9696/v2.0/availability_zones used request id req-1aa0c51d-3524-4569-b955-15e5c87b77b9

And from the neutron codes, the network resource AZ is returned by AZ of dhcp agent and the router resource AZ is returned by AZ of l3 agent. Some code of neutron is as followed:

https://opendev.org/openstack/neutron/src/branch/master/neutron/db/agentschedulers_db.py#L514-L520

    def get_router_availability_zones(self, router):
        return list({agent.availability_zone for agent in router.l3_agents})

https://opendev.org/openstack/neutron/src/branch/master/neutron/db/l3_agentschedulers_db.py#L532-L533

    def get_router_availability_zones(self, router):
        return list({agent.availability_zone for agent in router.l3_agents})

So I think you can run command "openstack network agent list" to verify whether you have dhcp agents or not.

Thanks :)

[Satish Patel (satish-txt)]

This is what I am trying to tell that OVN doesn't have any AZ concept because its distributed openflow and there is no such thing DHCP agent. It works with openvswitch plugin but not with OVN plugin.

We should remove AZ option in network create or make it optional.

# openstack network agent list
+--------------------------------------+------------------------------+----------+-------------------+-------+-------+----------------------------+
| ID | Agent Type | Host | Availability Zone | Alive | State | Binary |
+--------------------------------------+------------------------------+----------+-------------------+-------+-------+----------------------------+
| 734531b5-175a-5bba-8d35-df88ac80754b | OVN Metadata agent | os-ctrl1 | nova | :-) | UP | neutron-ovn-metadata-agent |
| os-ctrl1 | OVN Controller Gateway agent | os-ctrl1 | nova | :-) | UP | ovn-controller |
| ed3f844a-73c6-517e-9108-3c4511869954 | OVN Metadata agent | os-ctrl2 | nova | :-) | UP | neutron-ovn-metadata-agent |
| os-ctrl2 | OVN Controller Gateway agent | os-ctrl2 | nova | :-) | UP | ovn-controller |
| 34bafdf6-05f2-5129-ac0c-bfffce60ee36 | OVN Metadata agent | os-comp4 | | :-) | UP | neutron-ovn-metadata-agent |
| os-comp4 | OVN Controller agent | os-comp4 | | :-) | UP | ovn-controller |
| ba44ee41-4d31-5d28-9d65-961d0399ee90 | OVN Metadata agent | os-comp5 | | :-) | UP | neutron-ovn-metadata-agent |
| os-comp5 | OVN Controller agent | os-comp5 | | :-) | UP | ovn-controller |
| b5a95522-13ee-59d5-b093-8aab843f9efe | OVN Metadata agent | os-comp2 | | :-) | UP | neutron-ovn-metadata-agent |
| os-comp2 | OVN Controller agent | os-comp2 | | :-) | UP | ovn-controller |
| afa98165-a0ad-5f74-abc2-f46048fa5ec2 | OVN Metadata agent | os-comp1 | | :-) | UP | neutron-ovn-metadata-agent |
| os-comp1 | OVN Controller agent | os-comp1 | | :-) | UP | ovn-controller |
| c36ba86c-1742-5b08-842e-fe805e3df3e4 | OVN Metadata agent | os-ctrl3 | nova | :-) | UP | neutron-ovn-metadata-agent |
| os-ctrl3 | OVN Controller Gateway agent | os-ctrl3 | nova | :-) | UP | ovn-controller |
| 3b8100d3-0671-5953-b2e3-c8639dea6006 | OVN Metadata agent | os-comp3 | | :-) | UP | neutron-ovn-metadata-agent |
| os-comp3 | OVN Controller agent | os-comp3 | | :-) | UP | ovn-controller |
+--------------------------------------+------------------------------+----------+---...

[Boxiang Zhu (bxzhu-5355)]

Got it. So the skyline-console will set the AZ as optional when we try to create network. We will handle this as feature and will be released with the following release 2023.2 . Thanks :)

[Boxiang Zhu (bxzhu-5355)]

hi satish, I changed this issue affects from skyline-apiserver to skyline-console. So we will handle this in skyline-console project.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/skyline-console/+/895868

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/2023.2
Review: https://review.opendev.org/c/openstack/skyline-console/+/895797

[Satish Patel (satish-txt)]

Thank you so much!! How do I patch my existing deployment? Or should I just get new docker image?

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/skyline-console/+/895868
Committed: https://opendev.org/openstack/skyline-console/commit/b1f8c8201065f03537ce232c3262dcae03673192
Submitter: "Zuul (22348)"
Branch: master

commit b1f8c8201065f03537ce232c3262dcae03673192
Author: Jingwei.Zhang <[e-mail]>
Date: Wed Sep 20 09:31:50 2023 +0800

    fix: set az as optional when create network

    set the az selector as an optional select when create a network

    Closes-Bug: #2035012
    Change-Id: Ica30d2b71ad3ef38430c0d862f4d0eab56b6b125

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/skyline-console/+/895797
Committed: https://opendev.org/openstack/skyline-console/commit/d2565177488bfbb9a3fef5a38c2e161de5b6fa3e
Submitter: "Zuul (22348)"
Branch: stable/2023.2

commit d2565177488bfbb9a3fef5a38c2e161de5b6fa3e
Author: Jingwei.Zhang <[e-mail]>
Date: Wed Sep 20 09:31:50 2023 +0800

    fix: set az as optional when create network

    set the az selector as an optional select when create a network

    Closes-Bug: #2035012
    Change-Id: Ica30d2b71ad3ef38430c0d862f4d0eab56b6b125
    (cherry picked from commit b1f8c8201065f03537ce232c3262dcae03673192)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/skyline-console 3.0.0.0rc2 release candidate.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/skyline-console 4.0.0.0rc1 release candidate.