Public bug reported:
we configured lbaasv2. LB , listener are created . Thenext step is the
pool and members
neutron lbaas-pool-create --lb-algorithm ROUND_ROBIN --listener 5dd91024
-148e-4d80-842f-3122725d0164 --protocol HTTP
neutron lbaas-member-create 6b7b5daa-f773-46ca-8045-bb1f8ae8fcec
--pr
Public bug reported:
pool creation with LBmethod least connection + session persistanence
causes loadbalncing traffic to fail
neutron lbaas-loadbalancer-create 67897b9a-e5dd-405a-80db-7e36ead62c27
neutron lbaas-listener-create --loadbalancer
2b737c74-9a11-41d5-a2fa-625c20152ef5 --protocol-port 8
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs
Public bug reported:
Latest branch of horizon, when viewing project/network_topology/, error
occurs:
2015-06-29 03:44:23.857338 Internal Server Error: /project/network_topology/
2015-06-29 03:44:23.857371 Traceback (most recent call last):
2015-06-29 03:44:23.857377 File
"/usr/local/lib/python
marking invalid for Tempest as of now as Nova does not support xvda.
Once we have that fixed in nova feel free to reopen it for Tempest.
** Changed in: tempest
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscr
Public bug reported:
Subnet updating with both allocation-pool and gateway_ip options is
failing if parameter of the gateway_ip conflicts with allocation pools
in db even if the parameter of gateway_ip not conflicts with parameters
of the allocation-pool.
Steps to reproduce:
1. Create one networ
For reference, the "python-keystoneclient>=0.10.0,<1.2.0" in your log
implies that this is occurring for you on the stable/juno branch (that's
the only place horizon seems to be pinning to that exact version range).
It looks like oslo.i18n 2.0.0 has broken compatibility with python-
keystoneclient
Public bug reported:
Fernet tokens do not maintain the expiration time when rescoping tokens.
** Affects: keystone
Importance: High
Status: Triaged
** Affects: keystone/kilo
Importance: High
Status: Triaged
** Affects: keystone/liberty
Importance: High
Public bug reported:
The Federation manager's get_mapping_from_idp_and_protocol method is returning
a dict where the 'rules' value is a JSON string. That 'rules' is stored as a
JSON string is an implementation detail that shouldn't be exposed to callers.
The 'rules' value of the dict returned
Public bug reported:
Description of problem:
After booting an instance from an image with insufficient disk space, the
action failed with NeutronClientException, while the real reason for the
failure is that the disk flavor is too small for requested image
Version-Release number of selected co
Public bug reported:
I killed the haproxy process and the process did not recover automatically.
We believe we should make it recover automatically.
kilo +rhel7.1
openstack-neutron-common-2015.1.0-10.el7ost.noarch
python-neutron-lbaas-2015.1.0-5.el7ost.noarch
openstack-neutron-openvswitch-201
Public bug reported:
When we create a Lbaas pool with session persistence it configured OK
neutron lbaas-pool-create --session-persistence type=HTTP_COOKIE
--lb-algorithm LEAST_CONNECTIONS --listener
4658a507-dccc-41f9-87d7-913d31cab3a1 --protocol HTTP
Created a new pool:
+---
13 matches
Mail list logo
