Ticket #2919 (closed defect: Fixed)

Opened 8 months ago

Last modified 7 weeks ago

When updating a ZenPack remove previous version from filesystem if necessary

Reported by: jstevens Owned by: jstevens
Priority: 3 - Medium Milestone: zenoss-2.2
Component: ZenPack Version: 2.1.2
Keywords: Cc:
Community Patch Attached: Deployed @ Customer:
Installer: Maintenance Target:
Specific ZenPack: Maintenance Status:
Documentation Note?: Not required Regression:

Description

Simple case: when a zenpack is first created it exists in $ZENHOME/ZenPacks. If a developer copies that elsewhere and does "zenpack --link --install .." from the new location Zenoss should delete it from the $ZENHOME/ZenPacks directory.

Another example: a zenpack is installed via --link then installed again into the $ZENHOME/ZenPacks directory. Zenoss needs to make sure the previously linked version is no longer linked.

Change History

Changed 8 months ago by jstevens

  • status changed from new to assigned

Changed 8 months ago by jstevens

(In [8996]) refs #2919

  • When upgrading from old-style to new-style (python egg) zenpacks the upgrade code better handles transfering packables from old to new zenpack
  • When upgrading old to new style the old one is removed correctly even if it has a different id (the previous id is specified as metadata in the egg.)
  • Better deletion of removed/upgraded zenpack directiors/eggs.

Changed 8 months ago by jstevens

  • status changed from assigned to closed
  • resolution set to fixed

Changed 7 weeks ago by bbibeault

  • reviewed set to 1
Note: See TracTickets for help on using tickets.