landscape-client should avoid racing with do-release-upgrade
Bug #1652854 reported by
James Troup
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Client |
New
|
Undecided
|
Unassigned | ||
Bug Description
While upgrading a machine to Xenial, I ran into the following problem
| Searching for obsolete software
|
| Unable to get exclusive lock
|
| This usually means that another package management application (like
| apt-get or aptitude) is already running. Please close that
| application first.
AFAICT this was because landscape-client had been started back up by
the upgrade process. I'm pretty sure do-release-upgrade leaves
evidence it's running. It'd be nice if landscape-client could look for
that evidence and back off when it's found (with appropriate logging).
| description: | updated |
| information type: | Proprietary → Public |
| affects: | landscape → landscape-client |
To post a comment you must log in.
