The charm exposes no-op options to operators

Bug #2032869 reported by Nobuto Murata
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Manila-Ganesha Charm
In Progress
Undecided
Unassigned

Bug Description

The manila-ganesha inherits layer:openstack-api on purpose even though it doesn't offer any sort of OpenStack API service.

src/layer.yaml already has the following section not to expose OpenStack API related config options to operators:

config:
  deletes:
    - region
    - ssl_ca
    - ssl_cert
    - ssl_key

However, there are more no-op options exposed namely:

    - haproxy-server-timeout
    - haproxy-client-timeout
    - haproxy-queue-timeout
    - haproxy-connect-timeout
    - dns-ha
    - os-admin-hostname
    - os-admin-network
    - os-internal-hostname
    - os-internal-network
    - os-public-hostname
    - os-public-network

We can avoid confusions by hiding those no-op options.

Nobuto Murata (nobuto)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-manila-ganesha (master)
Changed in charm-manila-ganesha:
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.