cloud-init

  1. Bug #1913354
  2. Comment #2

Comment 2 for bug 1913354

Revision history for this message
C de-Avillez (hggdh2) wrote :

Hi Dan, thank you for looking into this.

The issue seems to be driven by cloud-init.service starting *before* network is actually available (in the cloud-init.service definition, we have "Before=network-online.target"). But the rpc-statd* service definitions are set to only start *after* network is fully available (Wants=network-online.target, After=network-online.target.

So... c-i starts, and drives the NFS mounts. But the dependent services (again, specifically the rpc-statd*.service) will not start until we reach the required target.

I will check with CXs what we can post in a public bug (or I may move this bug to private) due to PII restrictions.