update-pkgcache.py needs to connect as a unique database user

Bug #517098 reported by Stuart Bishop
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Julian Edwards

Bug Description

update-pkgcache.py is currently connecting as the statistician database user, which makes it impossible to tell its activity from the update-stats.py script.

All scripts should connect as a unique database user.

This involves adding the new user to security.cfg (it can inherit permissions from the statistician user for a quick fix) and hardcoding the new database user into cronscripts/update-pkgcache.py (there isn't much point configuring database usernames in config files because we have never overridden them in the last 5 years).

Tags: lp-soyuz qa-ok

Related branches

Changed in soyuz:
status: New → Triaged
importance: Undecided → High
milestone: none → 10.03
Changed in soyuz:
status: Triaged → In Progress
assignee: nobody → Julian Edwards (julian-edwards)
Revision history for this message
Ursula Junque (ursinha) wrote : Bug fixed by a commit
Changed in soyuz:
status: In Progress → Fix Committed
tags: added: qa-needstesting
tags: added: qa-ok
removed: qa-needstesting
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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