yahoo-eng-team team mailing list archive

[Bishoy <bishoysamy@xxxxxxxxxxx>]

@Byron McCollum (byron-mccollum) @Eugene Nikanorov (enikanorov): the
external network and the allocation of the floating ips was working fine
on the Havana until I installed the load balancing as a service and the
vpn as a service. Once you will enable this on the neutron and the
horizon will find your external network disappeared and the user with
the member role won't be able to allocate floating ips. I tried it and
tested it. So, we may change the bug info to this conclusion. Now, after
i disabled the vpn as a service and load balancing as a service normal
users can see in their topology the ext network and obviously they can't
attach it to their instances which is good and normal also they can
simply allocate ips.

** Summary changed:

- external network not available 
+ external network not available,, after enabling the load balancing as a service and vpn as a service

** Tags added: lbaas

** Description changed:

- the external network suddenly disappeared from the floating ips pools
- and the regular user with the role member can't allocate ips now only
- admins can do. I am using Havana and disabling the shared option in
- external network so that the user don't lunch instance using it. the
- external network doesn't appear on dashboard and APIs and this is a
- sudden change. I tried in a new installation privately on two servers
- using rdo and the new installation have the same problem and it's
- something weird. there is an old project I was working on at a site I
- checked it I found that every things working fine. I checked the
- policy.json and things are fine.
+ the external network suddenly disappeared after installing the lbaas and
+ vpn as a service from the floating ips pools and the regular user with
+ the role member can't allocate ips now only admins can do. I am using
+ Havana and disabling the shared option in external network so that the
+ user don't lunch instance using it. the external network doesn't appear
+ on dashboard and APIs and this is a sudden change. I tried in a new
+ installation privately on two servers using rdo and the new installation
+ have the same problem and it's something weird. there is an old project
+ I was working on at a site I checked it I found that every things
+ working fine. I checked the policy.json and things are fine.

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

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

Title:
  external network not available,, after enabling the load balancing as
  a service and vpn as a service

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  the external network suddenly disappeared after installing the lbaas
  and vpn as a service from the floating ips pools and the regular user
  with the role member can't allocate ips now only admins can do. I am
  using Havana and disabling the shared option in external network so
  that the user don't lunch instance using it. the external network
  doesn't appear on dashboard and APIs and this is a sudden change. I
  tried in a new installation privately on two servers using rdo and the
  new installation have the same problem and it's something weird. there
  is an old project I was working on at a site I checked it I found that
  every things working fine. I checked the policy.json and things are
  fine.

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