On 2012-02-28 18:31, Denis Ovsienko wrote:
> The new release, 0.19.11, is out, and I'd like to note a couple of things.
> This release was cut by Aaron, and so far it seems to work well (the amount
> of changes accumulated since 0.19.10 stands for 2-3 times the regular pack,
> see the ChangeLog). This means, 3 of 4 committers can make releases, it is
> one of the must-haves for a healthy team.
>
> Second, I need to make a special note on the "FOREIGN KEY violation" errors
> seen during upgrades. So far 0.19.11 is the release least subject for
> creating new FK errors in the database. A problem may be seen on an upgrade
> path to 0.19.11, including upgrades from relatively recent stable releases,
> including 0.19.7. Such rare situations are typically caused by a unique
> combination of loosely-matched rows in the database. A safe way of dealing
> with it is as follows.
Hi Denis,
I just attempted an upgrade from 0.19.7 to 0.19.11. I've upgraded many
times between point releases. This time I had an auth error that I couldn't
resolve.
I can authenticate correctly as the HTTP auth user "admin", which matches
user_id 1 in Racktables. The first line of Permissions is:
allow {$userid_1}
However, after passing this authentication, the HTTPAuth dialog changes
from mine "CompanyName login" to "Racktables upgrade". This dialog will not
accept any user/pass. I also tried removing HTTPauth entirely. This causes
"Racktables upgrade" to display as before, with the same results - no login
is accepted.
I've not had this problem before with previous upgrades. Any advice?
I rolled back to the 0.19.7 backup immediately.
Regards,
Tyler
--
"I disapprove of what you say, but I will defend to the death your right
to say it."
-- Evelyn Beatrice Hall
Attachment:
Selection_002.png
Description: PNG image
