hi, we have a customer reporting the following behavior in cinder, using RHOSP 13 (Queens) and the SolidFire driver:
When SolidFire is under heavy load or being upgraded, the
SolidFire cluster may automatically move connections from primary
to secondary nodes, in order to rebalance cluster workload.
Although this operation ocurrs very quickly, if an operation is made
to a volume at the same time it's being moved, there might be a
chance that API calls such as create snapshot could fail with
xNotPrimary error. Normally this will succeed on a retry of the
I've already submitted a patch upstream addressing this issue and I'm working to get this merged. After we have it in stable/queens, when this might become available for them to update their rhosp environment?
(In reply to Fernando Ferraz from comment #0)
> I've already submitted a patch upstream addressing this issue and I'm
> working to get this merged. After we have it in stable/queens, when this
> might become available for them to update their rhosp environment?
I can't talk yet about the next OSP13 updates, so I can't say yet whether it will be a direct import or it will require some internal cherry-picking.
I don't think I'm incorrect if say that having that patch (thanks for it!) merged in stable/queens is a necessary condition, but not sufficient, for having the fix in OSP13 (unless it was a patch that couldn't be backport to stable branches, but it looks like it is a normal bugfix). So please continue the bugfix-and-backport process.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Red Hat OpenStack Platform 13.0 bug fix and enhancement advisory), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.