← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1370803] Re: Neutron client fetches 'neutron user' token but tries to create port on 'demo' tenant network

 

Yes, Neutron shows no bugs in this case. My fault.

Neutron behaves well and my bug comes in configuration.

Sorry for annoying and wasting your valuable time.....

** Changed in: neutron
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1370803

Title:
  Neutron client fetches 'neutron user' token but tries to create port
  on 'demo' tenant network

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  I'm following OpenStack Icehouse installation guide on Ubuntu 14.04.
  After Glance, Nova, Neutron and Keystone were deployed, I tried to
  boot a CirrOS instance. However it failed.

  I checked nova-compute.log, and found that before Neutron client tried
  to create a port for the VM on tenant network(username: demo,
  password: demopass, tenant: demo), it connected to Keystone server for
  token, with credential of user 'neutron'(username: neutron, password:
  REDACTED) attached to the request. After the token was returned by
  Keystone, the Neutron client put that token in the request to Neutron
  server to create port. And finally the Neutron server return 'HTTP
  401'.

  Is there a bug in neutron client of misusing the credential or the
  manual misled me in configuring Neutron?

  I don't know which manual page should be attached in this report......

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