hardy->intrepid upgrade leaves cron job behind
Bug #288205 reported by
Andreas Hasenack
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Won't Fix
|
Medium
|
Unassigned | ||
Landscape Server |
Invalid
|
Low
|
Unassigned | ||
Smart Package Manager |
Invalid
|
Undecided
|
Unassigned | ||
smart (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
When upgrading a machine that has landscape installed from hardy to intrepid, the end result is two cron jobs installed in /etc/cron.hourly that do the same thing:
root@hardy-vm1:~# ls -la /etc/cron.hourly/
total 20
drwxr-xr-x 2 root root 4096 2008-10-23 11:29 .
drwxr-xr-x 77 root root 4096 2008-10-23 13:18 ..
-rwxr-xr-x 1 root root 214 2008-10-20 14:55 landscape-client
-rw-r--r-- 1 root root 102 2008-04-08 15:02 .placeholder
-rwxr-xr-x 1 root root 48 2008-10-10 15:24 smartpm-core
Both jobs basically run "smart update".
Changed in landscape: | |
importance: | Undecided → High |
milestone: | none → thames |
Changed in landscape: | |
milestone: | thames+1 → thames+2 |
Changed in landscape: | |
milestone: | mountainview-pre-1 → mountainview-pre-2 |
Changed in landscape: | |
milestone: | mountainview-pre-2 → mountainview-pre-3 |
Changed in landscape: | |
milestone: | mountainview-pre-3 → mountainview |
Changed in landscape-client: | |
status: | New → Won't Fix |
milestone: | 1.0.x → later |
To post a comment you must log in.
This is mostly annoying and a waste of bandwidth, but nothing particularly bad happens.