Updating content in JBoss ON with a file that already exists causes the content history to reflect the latest version in each entry for all prior versions with the same file
Issue
- Deployment history audit trail only shows latest version number
- We see that only the latest version number is displayed in the audit trail
- All previous versions in the audit trail now show the latest version number
- Identical package results in the previous copies of the same package getting the newly specified version number
Environment
- Red Hat JBoss Operations Network (ON) 3.1.2
- Updating deployed package content from the resource's content page
- New package content file is identical to a previously deployed package version for the affected resource
- The version number specified for the new package content is different then the one used with the existing identical package content
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.