Description of problem:

New-style systemd NFS automount from fstab mounts properly when system is connected to network on boot, but fails to mount when (1) a system is disconnected from the network on boot (e.g. laptop) and is then connected to the network; (2) a system is connected to the network, then disconnected for a time, then reconnected (e.g. NetworkManager changes from a wired connection to a wireless network connection; or (3) a system that is connected to the a public network establishes a VPN tunnel (such as OpenVPN) to the private network hosting the automount share.

In each failure case, the automount item also cannot be manually mounted using the "mount" command from the Linux command line; the command hangs and eventually times out.

Version-Release number of selected component (if applicable):

systemd-25-1.fc15.x86_64
NetworkManager-0.8.998-4.git20110427.fc15.x86_64


Steps to Reproduce:

[This is one of several failure cases described above]

1.  On a laptop system, set up a "new style" automount entry in /etc/fstab for a NFS4 share:

192.168.2.1:/network-storage	/home/testuser1/network-storage	nfs4	comment=systemd.automount,wsize=4096,rsize=4096,user,soft,_netdev	0 0

2.  Boot system with a wired network connection to the network that is hosting the NFS4 share.  Confirm that systemd automounts the share properly.  Shut down system.

3.  Boot system with a wired network connection to a public network (i.e. not the network containing the NFS share to be mounted).

4.  Using NetworkManager, establish an OpenVPN tunnel to the network containing the NFS share to be mounted.  Ping the NFS server to confirm that it is reachable over the VPN connection.

5.  Using "mount," confirm that the NFS4 share has not been not mounted.  [I have also observed that nautilus, when used to view /home/testuser1, will "hang" while trying to display the directory's contents, presumably because it is waiting for the NFS4 directory to mount or fail to mount]

6.  From the command line, try to mount the directory manually using "sudo mount /home/testuser1/network-storage."  The command will "hang" the terminal and eventually fail.
  
Actual results:

The NFS4 share does not mount.

Expected results:

The NFS4 share automounts whenever the network state changes so as to make the NFS server available.

Additional info:

As best I can tell, systemd is not re-trying the automount each time NetworkManager changes the network state to bring up a new network connection (e.g. wired, wireless, or VPN connection becomes available, potentially giving the system a route to the previously-unavailable NFS share).

Systemd should probably re-try all automounts in fstab on each ifup-type change in network state, whether initiated manually or through NetworkManager.