onitake opened a new issue #3557: cloud-init fails to fetch metadata when shared networks are present URL: https://github.com/apache/cloudstack/issues/3557 <!-- Verify first that your issue/request is not already reported on GitHub. Also test if the latest release and master branch are affected too. Always add information AFTER of these HTML comments, but no need to delete the comments. --> ##### ISSUE TYPE <!-- Pick one below and delete the rest --> * Bug Report ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ VR metadata cloud-init ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ 4.11.2 likely others affected as well ~~~ ##### CONFIGURATION <!-- Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise --> Advanced networking, with isolated and shared networks. ##### OS / ENVIRONMENT <!-- Information about the environment if relevant, N/A otherwise --> CentOS 7, but likely other VM operating systems affected as well. ##### SUMMARY <!-- Explain the problem/feature briefly --> As reported here: https://bugs.launchpad.net/cloud-init/+bug/1839854 cloud-init is longer able to fetch metadata on VMs that have both isolated and shared networks attached. In older cloud-init versions (0.7.5), acquiring metadata would still succeed if network manager was used, because cloud-init would then ignore the DHCP lease files and use the default gateway. The logic in cloud-init is to use the latest created DHCP lease file for obtaining the metadata server IP, but if that is ##### STEPS TO REPRODUCE <!-- For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate. For new features, show how the feature would be used. --> * Deploy a VM that has cloud-init newer than 0.7.5 and attach an isolated and a shared network to the VM * Configure cloud-init to use CloudStack metadata * Depending on the OS, ensure that the shared network obtains a DHCP lease last * Apply metadata to the VM <!-- Paste example playbooks or commands between quotes below --> <!-- You can also paste gist.github.com links for larger files --> ##### EXPECTED RESULTS <!-- What did you expect to happen when running the steps above? --> * cloud-init obtains and applies metadata on boot ##### ACTUAL RESULTS <!-- What actually happened? --> * The VM takes much longer to boot than normal, * fails to obtain metadata because it isn't offered by the shared network router * and doesn't apply metadata to the host <!-- Paste verbatim command output between quotes below -->
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
