F5 | 1311309

Bug ID 1311309: On r2k or r4k systems, improved VF creation by adding health checks and retrials ... On r2k or r4k systems, the VFs creation process under each PF were intermittently not having relevant sysfs entries under each VF created. ... Tenant creation stalls as there are insufficient/Unready/Unhealth VFs to consume for Datapath. ... Conditions ... When the r2k or r4k system boots up, VF creation under each PF gets triggered and checks for the VF state and retries the VF creation, if we hit any of the following: 1. ... Not all the 4VFs are created under a PF(Ex: ip link show <PF>) 2. `driver` soft link is not created for VF in sysfs 3. `net` directory is missing for VF in sysfs 4. `net` directory had no entries when creating a new VF in sysfs ... Workaround ... Even on six retrials for about three minutes after booting the system, if the VF creation does not succeed, reboot the host system with a message(s) in /var/log/messages. ... Fixed validating the VF entries in sysfs.