Comment # 12 on bug 946325 from Matthias Gerstner

Thank you all for the thorough analysis of the issue, testing and pointing to
the fix.

I'm sorry that the fix didn't make it into maintenance updates. This was
before my time as maintainer and I wasn't aware of this particular issue as
there was no open bug for it.

I will take care to backport this fix to Leap 42.2 and SLE-12*. Leap 42.1 is
out of maintenance now, however.

As I see it even with the fix of the ordering there might remain situations
when things don't work as expected. For example when nfs-server is not started
during boot, but manually afterwards. Can you confirm this?

This would be a use case for FATE#316295 which I implemented a while ago. For
this the nfs-server systemd service unit needs a line like:

  ExecStartPost=/usr/sbin/SuSEfirewall2 update-rpc -s nfs

This would make sure that the RPC mappings are always updated in SuSEfirewall2
when the nfs server is (re)started. This feature is implemented in SLE-12-SP3
and Leap 42.3 / Tumbleweed.

Would you be willing to test/consider this?

Thank you!