You need to enable Firewalls for the dashboard to be able to view them. You can edit it this file(ubuntu):

/etc/openstack-dashboard/local_settings.py

You will see options for what the Dashboard will load, you need to change firewall to True then restart apache2/httpd:

OPENSTACK_NEUTRON_NETWORK = {
    'enable_lb': False,
    'enable_firewall': True,
    'enable_quotas': True,
    'enable_vpn': False,
    # The profile_support option is used to detect if an external router can be
    # configured via the dashboard. When using specific plugins the
    # profile_support can be turned on if needed.
    'profile_support': None,
    #'profile_support': 'cisco',
}

After that you should be able to view the Firewall option in the Dashboard. If you login and it says "something went wrong" then you need to verify the Firewall service and ensure that it is configured correctly. If you need to revert just change it back to False and restart apache2/httpd.

Also when you edit neutron.conf you need to restart neutron-server:

/etc/init.d/neutron-server restart

To translate the bug you are referring to:

Edit neutron.conf on the service server - You will edit neutron.conf where neutron-server is running, this is usually on the controller node/nodes. Then restart neutron-server on those nodes.

Edit neutron.conf on the L3 machine - You need to edit neutron.conf on the L3 machine which is usually a controller or a network node. If you setup your own network node then you would edit neutron.conf on this node.

To sum it up, if you have an all in one node then you need to verify that neutron.conf matches what was placed in the bug report, then restart the necessary services.