The bug is fixed in kilo version .
** Changed in: horizon
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1449544
Title:
Neutron
i think the max bandwidth limitation would not exceed 0x7fff(2147483647).
Since because of your configuration of RX_TX factor for 1GB/s network exceeds
the max limit the vmware server is throwing error.
Also, in your log 2147483 is truncation of 2147483647
--
** Changed in: neutron
Kindly refer the API reference link,
http://developer.openstack.org/api-ref-networking-v2-ext.html
Under “Networks multiple provider extension” , it is stated that the
provider attributes cannot be updated.
Not allowing to update the provider attributes is the expected behavior
as per the API ref
.
Validation needs to be done for Pool-Create and Member-Create
** Affects: neutron
Importance: Undecided
Assignee: senthilmageswaran (senthilmageswaran-muthusamy)
Status: New
** Tags: lbaas
** Changed in: neutron
Assignee: (unassigned) => senthilmageswaran (senthilmageswa
On checking this behavior, i think this is not a bug. When all the ip
addresses are exhausted, new audit is done(during new instance creation)
and the table “ ipavailabilityranges “ is updated correctly.
kindly check the following reference,
https://review.openstack.org/#/c/58017/
In the followi
Assignee: senthilmageswaran (senthilmageswaran-muthusamy)
Status: New
** Attachment added: "LB_monitor_list.JPG"
https://bugs.launchpad.net/bugs/1449546/+attachment/4386605/+files/LB_monitor_list.JPG
** Changed in: neutron
Assignee: (unassigned) => senthilmageswa
** Affects: neutron
Importance: Undecided
Assignee: senthilmageswaran (senthilmageswaran-muthusamy)
Status: New
** Tags: lbaas
** Attachment added: "LB_HM_default_assoc_CLI_and_UI.zip"
https://bugs.launchpad.net/bugs/1449544/+attachment/4386604/+files/LB_HM_default_assoc
@Itzik Brown==> kindly let us know for which network_type you tried to
modify segmentation_id
** Changed in: neutron
Status: New => Opinion
** Changed in: neutron
Status: Opinion => Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Te
Public bug reported:
Load Balancer fails to open in Horizon, after deleting the Assigned
"Network"
Steps:
1)Create Network and Subnetwork
2)Create pool in Load Balancer and assign a subnet
3)Delete the Network assigned to the Pool
4)load balancer failed to open from horizon.
B
9 matches
Mail list logo
