Auto-approve new installations in package activities doesn't work with upgrades
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Invalid
|
Low
|
Unassigned |
Bug Description
It's not working because an upgrade is basically a removal and a installation. Then the check in the code that makes sure there are no removals is tricked into thinking an upgrade is or has a removal, and the automatic approval doesn't happen.
Here are some logs from a client. The activity was to upgrade libsasl2-modules, which depends on libsasl2:
==> /var/log/
2010-03-15 18:04:35,843 INFO [MainThread] may_complement_
2010-03-15 18:04:35,843 INFO [MainThread] policy = 1
2010-03-15 18:04:35,844 INFO [MainThread] result.
2010-03-15 18:04:35,844 INFO [MainThread] result.
2010-03-15 18:04:35,844 INFO [MainThread] policy is ALLOW_INSTALLS
2010-03-15 18:04:35,844 INFO [MainThread] returning false
landscape_
id | name | version
-------
115439 | libsasl2 | 2.1.19.
284239 | libsasl2 | 2.1.19.
(2 rows)
We can see that there is a removal, but in this case it's part of an upgrade. See also the screenshot at http://
Changed in landscape: | |
importance: | Undecided → Low |
affects: | landscape → landscape-client |
visibility: | private → public |
Changed in landscape-client: | |
milestone: | none → later |
This bug has not seen any activity in the last 6 months, so it is being automatically closed.
If you are still experiencing this issue, please feel free to re-open.
Landscape Team