Red Hat Bugzilla – Bug 117386
ccm upgrade command does not enforce application version dependnacies
Last modified: 2007-04-18 13:03:50 EDT
Description of problem: Consider the 'portal' and 'navigation' applications. Version 1.0 of navigation has a dependancy on version 1.0 of portal. Now the next release of navigation (1.1) comes along & has a dependancy on version 2.0 of portal. When you run 'ccm upgrade ccm-navigation', however, it does nothing to check that you've a) Installed the 1.1 version of navigation b) Run the upgrade scripts for this version Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Install RPMS portal 1.0 & navigation 1.0 2. Load the applications with ccm load 3. Upgrade the RPM for portal to 2.0 and navigation to 1.1 4. Run the upgrade for 'navigation' Actual results: Errors because portal has not yet been upgrade Expected results: If the command is ccm upgrade navigation then a error message should be printed & no action taken if the command is ccm upgrade portal navigation then they should be upgraded in dependancy sorted order. Additional info:
This one requires installed-package metadata that we don't have (though we've discussed adding it to support the smarter "ccm upgrade navigation". And since adding that metadata requires[1] refactoring loading and initialization, we should do it after the upcoming release. [1] "requires" is a little strong here. It could be tacked on to the existing infrastructure and so avoid refactoring initialization and require only simpler to changes to loading, but this would have to be de-tacked-on afterward, so I think it's a bad idea.
Closing old tickets