yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1243962@xxxxxxxxxxxxxxxxxx>]

[Expired for ubuntu-cloud-archive because there has been no activity for
60 days.]

** Changed in: cloud-archive
       Status: Incomplete => Expired

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

Title:
  l3-agent does not initially work without a restart

Status in Ubuntu Cloud Archive:
  Expired
Status in OpenStack Neutron (virtual network service):
  Expired

Bug description:
  A colleague and I both recently deployed independent openstack grizzly
  clusters with neutron using juju charms and the Ubuntu Cloud Archive's
  grizzly packages for Ubuntu 12.04 LTS.

  In each case we discovered that nova instances could not contact
  nova's metadata server until the quantum-l3-agent service was
  restarted.

  While I was examining my cluster in its non-working state and
  comparing it with the working cluster, I noticed that some fields were
  missing from "net-show" in my setup.

  Here's one from my non-working setup:

  (quantum) net-show blorp_net
  +-----------------+--------------------------------------+
  | Field           | Value                                |
  +-----------------+--------------------------------------+
  | admin_state_up  | True                                 |
  | id              | 38bfbd31-5fb0-43b2-a521-a5715370aeb9 |
  | name            | blorp_net                            |
  | router:external | False                                |
  | shared          | False                                |
  | status          | ACTIVE                               |
  | subnets         | bd105168-6392-4af3-8830-5af95e54e562 |
  | tenant_id       | 4816b122400d4318b7e7cb8bad121e60     |
  +-----------------+--------------------------------------+

  And here's one from my colleague's working setup, after a restart of
  quantum-l3-agent.

  (quantum) net-show tenant_net
  +---------------------------+--------------------------------------+
  | Field                     | Value                                |
  +---------------------------+--------------------------------------+
  | admin_state_up            | True                                 |
  | id                        | 3e7b82bf-e611-41a0-96b2-c03fb8d5e386 |
  | name                      | tenant_net                           |
  | provider:network_type     | gre                                  |
  | provider:physical_network |                                      |
  | provider:segmentation_id  | 2                                    |
  | router:external           | False                                |
  | shared                    | True                                 |
  | status                    | ACTIVE                               |
  | subnets                   | c9b95300-3cfd-4564-a1b6-ef326bf458d3 |
  | tenant_id                 | ed2c9613f29442ed8d7f3979106e0184     |
  +---------------------------+--------------------------------------+

  After my colleague relayed the discovery that quantum-l3-agent might
  need a restart and I had applied this change and confirmed that it
  solved my problem, I looked again at net-show and now my network has
  the formerly-absent fields:

  (quantum) net-show 38bfbd31-5fb0-43b2-a521-a5715370aeb9
  +---------------------------+--------------------------------------+
  | Field                     | Value                                |
  +---------------------------+--------------------------------------+
  | admin_state_up            | True                                 |
  | id                        | 38bfbd31-5fb0-43b2-a521-a5715370aeb9 |
  | name                      | blorp_net                            |
  | provider:network_type     | gre                                  |
  | provider:physical_network |                                      |
  | provider:segmentation_id  | 2                                    |
  | router:external           | False                                |
  | shared                    | False                                |
  | status                    | ACTIVE                               |
  | subnets                   | bd105168-6392-4af3-8830-5af95e54e562 |
  | tenant_id                 | 4816b122400d4318b7e7cb8bad121e60     |
  +---------------------------+--------------------------------------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1243962/+subscriptions