Manila-share in error for missing br-int
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Manila Generic Backend Charm |
New
|
Undecided
|
Unassigned | ||
Bug Description
This is on yoga/stable, manila rev. 240, manila-generic rev 45
ubuntu@
Model Controller Cloud/Region Version SLA Timestamp
openstack foundations-maas maas_cloud 3.6.3 unsupported 11:53:15Z
App Version Status Scale Charm Channel Rev Exposed Message
hacluster-manila 2.0.3 active 3 hacluster 2.4/stable 131 no Unit is ready and clustered
manila 14.1.1 active 3 manila yoga/stable 240 no Unit is ready
manila-generic 14.1.1 active 3 manila-generic yoga/stable 45 no Unit is ready
manila-mysql-router 8.0.41 active 3 mysql-router 8.0/stable 257 no Unit is ready
public-
Unit Workload Agent Machine Public address Ports Message
manila/0* active idle 0/lxd/13 10.17.2.36 8786/tcp Unit is ready
hacluster-
manila-generic/0* active idle 10.17.2.36 Unit is ready
manila-
public-
manila/1 active idle 1/lxd/19 10.17.2.32 8786/tcp Unit is ready
hacluster-
manila-generic/2 active idle 10.17.2.32 Unit is ready
manila-
public-
manila/2 active idle 2/lxd/17 10.17.2.34 8786/tcp Unit is ready
hacluster-
manila-generic/1 active idle 10.17.2.34 Unit is ready
manila-
public-
Machine State Address Inst id Base AZ Message
0 started 10.17.2.125 pc6a-rb3-n1 ubuntu@22.04 zone1 Deployed
0/lxd/13 started 10.17.2.36 juju-5addf7-
1 started 10.17.2.124 pc6a-rb3-n3 ubuntu@22.04 zone3 Deployed
1/lxd/19 started 10.17.2.32 juju-5addf7-
2 started 10.17.2.129 pc6a-rb3-n4 ubuntu@22.04 zone1 Deployed
2/lxd/17 started 10.17.2.34 juju-5addf7-
Manila-share is constantly in error loop with
```
2025-03-13 11:50:36.193 378627 INFO manila.service [-] Starting manila-share node (version 14.1.1)
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
2025-03-13 11:50:36.705 378627 ERROR oslo_service.
```
Manually installing openvswitch-switch and running `ovs-vsctl add br-int` makes the error stopping
But I am not sure if I need any additional bridge and any connection to an interface on the lxd.
It seems that manila needs a similar configuration like Octavia when trying to work with Manila Generic driver
I think that the charm needs some relations similar to the octavia charm to be able to connect to the VMs on the overlay network:
manila- ovn-chassis: ovsdb-subordina te manila- generic: ovsdb-subordina te ovsdb-cms manila- generic: ovsdb-cms
ovn-central: