Permission error raised viewing new changesets

[Markus Tacker <m@…>]

In r3521

Trac [/var/trac/xxx]> permission list

User                           Action
---------------------------------------------
customerUserA                  customer
customer                       BROWSER_VIEW
customer                       CHANGESET_VIEW
customer                       FILE_VIEW
customer                       LOG_VIEW
customer                       REPORT_VIEW
customer                       TICKET_APPEND
customer                       TICKET_CREATE
customer                       TICKET_VIEW
customer                       WIKI_CREATE
customer                       WIKI_MODIFY
customer                       WIKI_VIEW

if the logged in customerUserA views a changeset he gets a Insufficient permissions to access changeset.

[Markus Tacker <m@…>]

I cannot reproduce this with a fresh install. I set up a new install an gave anonymous only CHANGESET_VIEW, which works. It also works with an authenticated user there.

I tried removing all permissions and readding them to no avail.

Is there a way to debug this?

[Markus Tacker <m@…>]

And, of course it used to work for about six months.

[Markus Tacker <m@…>]

Today it happened again. This time I am logged in as TRC_ADMIN.

I go to a wiki page listing our releases. Note that the link to r1057 is greyed.

I clicked on resulting in "Forbidden".

Now I went to the timeline. From there I could access the revision.

I have the feeling that this happens only with the latest revision and only the first time it is accessed.

[soporte@…]

I ended in this issue too.

happends only one time, even when Im log as a TRAC_ADMIN, then I visit the wiki or some other page, return to the changeset, and the error message is gone.

Im running: trac 0.9.6 Python 2.4.3 mod_python-3.2.8 with apache 2.2.2 in FC5.

[Matthew Good]

The error actually has nothing to do with the users' permissions. The error message is obviously confusing, but the real issue is that Trac is not resyncing with the repository before trying to display the changeset, so it's not available in the cache.

[Markus Tacker <m@…>]

If I visit the "Browse Source" page and reload the Timeline page, the new rev is / accessable.

[Matthew Good]

Fixed in r3971 and r3972.