Unable to configure binding hostname
Bug #2037580 reported by
Mohammed Naser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Mohammed Naser |
Bug Description
This codebase uses `gethostname()` by default, in an environment where FQDNs are used for agent names (specified by `host`), no way to override that in Manila.
There should be a flag that allows you to override this.
Changed in manila: | |
status: | New → In Progress |
Changed in manila: | |
status: | In Progress → New |
Changed in manila: | |
importance: | Undecided → Medium |
assignee: | nobody → Mohammed Naser (mnaser) |
milestone: | none → caracal-1 |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/c/openstack /manila/ +/896692 /opendev. org/openstack/ manila/ commit/ 809253f3e8ce29b 1cefd7afdb8acc1 eb476f102c
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 809253f3e8ce29b 1cefd7afdb8acc1 eb476f102c
Author: Mohammed Naser <email address hidden>
Date: Wed Sep 27 17:40:40 2023 +0000
Respect provided "host" when plugging ports
When creating port bindings for ports inside Neutron, Manila gethostname( )" rather
just uses the hostname using "socket.
than the one provided via CONF.host
The default behaviour of CONF.host is "socket. gethostname( )"
anyways, so it should work just fine.
Closes-Bug: #2037580 bf356d6363300b2 d420921e7fa
Change-Id: I4181a6f1527c80