image_conversion_cpu_limit and image_conversion_address_space_limit settings ignored in /etc/cinder/cinder.conf

This is how I found the problem:
I tried to create cinder volume from the image, but, encountered the following errors:
Command: /opt/openstack/venv/cinder/bin/python -m oslo_concurrency.prlimit --as=1073741824 --cpu=60 -- sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C qemu-img info /var/cinder/conversion/tmplioz9ua5example.com
Exit code: -6
Stdout: ''
Stderr: 'fatal error: runtime: cannot allocate memory

After some digging, it related to the size of the address space (https://access.redhat.com/solutions/2800111)

So, I tried to configure /etc/cinder/cinder.conf to define image_conversion_cpu_limit=60 and image_conversion_address_space_limit=10 attributes. However, after I configured the attributes, I continue to see the errors are still showing "--as=1073741824 --cpu=60"...

So the values configured in the conf file did not seem to have an effect on the call to 'qeum-img info'.

Troubleshooting:
I moved https://github.com/openstack/cinder/blob/85975fb2b63866ba6e216e621b84d571b9dbe90e/cinder/image/image_utils.py#L66-L72 these lines inside the qemu_img_info function https://github.com/openstack/cinder/blob/85975fb2b63866ba6e216e621b84d571b9dbe90e/cinder/image/image_utils.py#L122. The configurd values could be loaded as expected.

Please help to investigate this issue, thanks

This issue has been posted in #openstack-cinder channel.
http://eavesdrop.openstack.org/irclogs/%23openstack-cinder/%23openstack-cinder.2021-03-01.log.html