Cisco Bug: CSCul18724 - PPM 1.4 upgrade script errors when moving files with space in filename
Last Modified
Jul 03, 2014
Products (1)
- Cisco Prime Performance Manager
Known Affected Releases
1.4(0)
Description (partial)
Symptom: During the upgrade from 1.3.1 to 1.4, the upgrade script generated a bunch of errors on the unix mv command as it hit a file with space in the file name which the mv command was attempting to move each part of the file name as individual file. Upgrading Views and TCAs ... cp: cannot stat `CPU': No such file or directory cp: cannot stat `AVERAGE': No such file or directory cp: cannot stat `UTILIZATION': No such file or directory cp: cannot stat `.xml': No such file or directory cat: /opt/CSCOppm-gw/tmp/newtcas/CPU: No such file or directory cat: AVERAGE: No such file or directory cat: UTILIZATION: No such file or directory cat: .xml: No such file or directory mv: target `.xml' is not a directory cat: /opt/CSCOppm-gw/tmp/newtcas/CPU: No such file or directory cat: AVERAGE: No such file or directory cat: UTILIZATION: No such file or directory cat: .xml: No such file or directory mv: target `.xml' is not a directory cat: /opt/CSCOppm-gw/tmp/newtcas/CPU: No such file or directory cat: AVERAGE: No such file or directory cat: UTILIZATION: No such file or directory cat: .xml: No such file or directory mv: target `.xml' is not a directory Conditions: Only occurs when customer has manually created TCA or View definition files that include spaces.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Status
- Severity
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases