Public bug reported: Neutron-metadata-agent does not *sometimes* reply to instance-id request by CirrOS VM in OpenStack environment created by Devstack. This causes a failure of upstream jobs (e.g. tempest-full-multinode-py3 [1]) as some tests are not able to successfully finish creation of a VM due to missing response from http://169.254.169.254/meta-data/instance-id (see attached log file).
[1] https://zuul.opendev.org/t/openstack/build/94f0cf28c8fd495d96099f888329dbb2/logs ** Affects: neutron Importance: Undecided Status: New ** Attachment added: "Example of failed tempest-full-multinode-py3 job (search for checking http://169.254.169.254/2009-04-04/instance-id)" https://bugs.launchpad.net/bugs/1999400/+attachment/5635397/+files/job-output.txt -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1999400 Title: neutron-metadata-agent does not sometimes provide instance-id Status in neutron: New Bug description: Neutron-metadata-agent does not *sometimes* reply to instance-id request by CirrOS VM in OpenStack environment created by Devstack. This causes a failure of upstream jobs (e.g. tempest-full-multinode- py3 [1]) as some tests are not able to successfully finish creation of a VM due to missing response from http://169.254.169.254/meta- data/instance-id (see attached log file). [1] https://zuul.opendev.org/t/openstack/build/94f0cf28c8fd495d96099f888329dbb2/logs To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1999400/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
