Rosetta branch scanner using incorrect db user

Bug #402891 reported by Stuart Bishop
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Данило Шеган

Bug Description

Every script needs to connect as a unique database user.

The rosettabranches script is currently reusing the 'branchscanner' db user which makes monitoring difficult, as this is the user used by the existing branch scanning script.

Related branches

Revision history for this message
Stuart Bishop (stub) wrote :

See the [garbo], [garbo_daily] and [garbo_hourly] sections in security.cfg if the scripts do need identical database permissions.

Changed in rosetta:
importance: Undecided → Medium
milestone: none → 2.2.9
status: New → Triaged
Revision history for this message
Matthew Revell (matthew.revell) wrote :

Retargeting to 3.0, which is the new name for 2.2.9. Haven't renamed the milestone as the 3.0 milestone is in a different series.

Changed in rosetta:
milestone: 2.2.9 → 3.0
Changed in rosetta:
milestone: 3.0 → 2.2.8
Changed in rosetta:
assignee: nobody → Данило Шеган (danilo)
Revision history for this message
Данило Шеган (danilo) wrote :

Fixed in devel 9195.

Changed in rosetta:
status: Triaged → Fix Committed
Changed in rosetta:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.