Comment 0 for bug 804008

If you accept into landscape a computer with a tag, and that tag is associated with a repository profile, the following happens:

- two activities are queued: pending computer and apply repository profile

- on the client, the package reporter runs as root and creates the following two files with root ownership:

 /var/log/landscape/package-reporter.log
 /var/lib/landscape/client/package/reporter.lock

- subsequent runs of the package reporter fail:
 ==> monitor.log <==
2011-06-30 14:01:19,040 WARNING [MainThread] Package reporter output:
Traceback (most recent call last):
  File "/usr/bin/landscape-package-reporter", line 10, in <module>
    main(sys.argv[1:])
  File "/usr/lib/python2.5/site-packages/landscape/package/reporter.py", line 615, in main
    return run_task_handler(PackageReporter, args)
  File "/usr/lib/python2.5/site-packages/landscape/package/taskhandler.py", line 246, in run_task_handler
    lock_path(lock_filename)
  File "/usr/lib/python2.5/site-packages/landscape/lib/lock.py", line 11, in lock_path
    fd = os.open(path, os.O_CREAT)
OSError: [Errno 13] Permission denied: '/var/lib/landscape/client/package/reporter.lock'

As a result, no package is ever reported back to landscape.

If I accept the computer without the tag that triggers the repository profile activity, the package reporter files are created with "landscape" as their owner and everything works.

client version 11.06~bzr338-0ubuntu0.8.04