yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

Public bug reported:

I'm seeing these warnings all over the n-api logs in an ocata CI job
run:

http://logs.openstack.org/11/349011/3/check/gate-tempest-dsvm-neutron-
full-ubuntu-xenial-
ocata/bee08f9/logs/screen-n-api.txt.gz?level=TRACE#_2017-02-14_22_13_03_345

2017-02-14 22:15:27.415 2678 WARNING
nova.api.metadata.vendordata_dynamic [req-eb314972-d29e-436c-
a2a7-fb189effb5c4 - -] Passing insecure dynamic vendordata requests
because of missing or incorrect service account configuration.

It's coming from here:

http://git.openstack.org/cgit/openstack/nova/tree/nova/api/metadata/vendordata_dynamic.py#n52

We should probably only log that once the first time we hit it since I
don't think you can fix it without fixing the [vendordata] credentials
in nova.conf and restarting nova-api.

** Affects: nova
     Importance: Medium
         Status: Confirmed


** Tags: api logging low-hanging-fruit vendordata

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1665693

Title:
  "Passing insecure dynamic vendordata requests because of missing or
  incorrect service account configuration." warnings all over n-api logs

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  I'm seeing these warnings all over the n-api logs in an ocata CI job
  run:

  http://logs.openstack.org/11/349011/3/check/gate-tempest-dsvm-neutron-
  full-ubuntu-xenial-
  ocata/bee08f9/logs/screen-n-api.txt.gz?level=TRACE#_2017-02-14_22_13_03_345

  2017-02-14 22:15:27.415 2678 WARNING
  nova.api.metadata.vendordata_dynamic [req-eb314972-d29e-436c-
  a2a7-fb189effb5c4 - -] Passing insecure dynamic vendordata requests
  because of missing or incorrect service account configuration.

  It's coming from here:

  http://git.openstack.org/cgit/openstack/nova/tree/nova/api/metadata/vendordata_dynamic.py#n52

  We should probably only log that once the first time we hit it since I
  don't think you can fix it without fixing the [vendordata] credentials
  in nova.conf and restarting nova-api.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1665693/+subscriptions