Description of problem:
When the rados exports list is longer than 1024 bytes in ganesha.conf, the parser fails to load the config file. (This is related to nfs-ganesha, but I see the issue is fixed upstream. We need the fix in the osp13 containers)
https://github.com/nfs-ganesha/nfs-ganesha/issues/369

Version-Release number of selected component (if applicable):
Red Hat OpenStack Platform 13
rhceph/rhceph-3-rhel7:3-25


How reproducible:
100%

Steps to Reproduce:
1. Have an exports list greater than 1024 bytes in size specified in ganesha.conf as 
%url rados://manila_data/ganesha-export-index
2. Try to start the container with:
/usr/bin/docker run --rm --net=host \
  -v /var/lib/ceph:/var/lib/ceph:z \
  -v /etc/ceph:/etc/ceph:z \
  -v /var/lib/nfs/ganesha:/var/lib/nfs/ganesha:z \
  -v /etc/ganesha:/etc/ganesha:z \
  -v /var/run/ceph:/var/run/ceph:z \
    --privileged \
  -v /var/run/dbus/system_bus_socket:/var/run/dbus/system_bus_socket \
  -v /etc/localtime:/etc/localtime:ro \
  -e CLUSTER=ceph \
  -e CEPH_DAEMON=NFS \
   \
  --name=ceph-nfs-pacemaker \
  registry.access.redhat.com/rhceph/rhceph-3-rhel7:3-25
3. No joy. 


Actual results:

01/07/2019 12:16:16 : epoch 5d196cf0 : controller-0 : ganesha.nfsd-84[main] main :NFS STARTUP :CRIT :Error (token scan, parser rule) while parsing (/etc/ganesha/ganesha.conf)
01/07/2019 12:16:16 : epoch 5d196cf0 : controller-0 : ganesha.nfsd-84[main] config_errs_to_log :CONFIG :CRIT :Config File (rados://manila/ganesha-export:13): new url (rados://manila_data/gan) open error (Unknown error -2), ignored
01/07/2019 12:16:16 : epoch 5d196cf0 : controller-0 : ganesha.nfsd-84[main] config_errs_to_log :CONFIG :CRIT :Config File (rados://manila/ganesha-export:13): Unexpected character (!)
01/07/2019 12:16:16 : epoch 5d196cf0 : controller-0 : ganesha.nfsd-84[main] config_errs_to_log :CONFIG :CRIT :Config File (/etc/ganesha/ganesha.conf:0): Configuration syntax errors found

Expected results:
nfs-ganesha@pacemaker would successfully launch the container

Additional info:
We fixed this by truncating the list of exports and starting the container to verify this is indeed the issue.