I spend few hours trying to backport to Havana, but than I found, that
Havana seems be immune to the bug. I'm not 100% sure, so someone else
advised to look too.
The bug was that icehouse+ accepts all supported schemas. Fix excludes
'bad' schemes. Although Havana have explicitly given list of
As a note, since I've seen some responses about users and/or groups on this
survey, I will be sending a survey about identity out today. This survey is
strictly about projects/tenants and roles/role assignments in LDAP.
Sent via mobile
On Jan 6, 2015, at 11:22, Morgan Fainberg
Hi all,
after some more tests it seems some gratuitous arp issue because if I start
a new connection (ping) from an inside instance to an external host like
google it will work.
This means that instance advertises the switch that in fact something has
changed and it should update arp table.
Hi,
Will a Cinder volume creation request ever timeout and be rescheduled in case
the host with the volume service it has been scheduled to is not consuming the
corresponding message?
Similarly: if the host the volume has been created on and to which later the
deletion request is scheduled
Your understanding is correct. I have the same problem as well. For now, my
plan is to just move cinder-volume to our more robust hosts, and run
database changes to modify the host, as needed.
I have noticed a growing trend to replace the host parameter with a
generic, but I agree that this
Hey Tom,
Thanks for organizing this. We're really looking forward to this event.
On 29/12/14 02:53 AM, Tom Fifield wrote:
Registration and details to come. We'll do our regular etherpad
brainstorming, but since some of us are having a well-earned break at
the moment, let's hold off on that
+1 on the issue faced.
We too had to use a generic name and modify db records to make this work.
However we had to struggle for couple of days on a multi node setup before
digging out the root cause.
Worth looping the dev group if they have some alternate suggestions.
On 7 Jan 2015 20:45, Warren
+1 in that we experienced this as well. We implemented an HA iscsi cinder and
failover from one node to the other works great until you have to do some
administrative action on the volume and the mismatched name in the database
messes that up. We’ve had to change hostnames in the DB or fail
