Bug 510100

Summary: Revision number cannot be set (Feat. req. "Set a new revision #")
Product: [Community] Spacewalk Reporter: Christoph Sievers <christoph.sievers>
Component: ServerAssignee: Justin Sherrill <jsherril>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: low    
Version: 0.5CC: cperry, jsherril
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-05 14:56:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 559281    

Comment 1 Justin Sherrill 2009-07-07 17:17:15 UTC
It is currently not possible to set a revision number on a configuration file
within spacewalk.

Instead the revision number always increases by one (which is harcoded within
the code).

Having more than one spacewalk server brings up questions about how to let
configuration files run through the different development stages (simple
scenario: having development spacewalk and production spacewalk).

d = development
p = production

current situation:

file a has revision 20 in spacewalk d

file a moves to spacewalk p with revision 1

I'd like to be able to set revision 20 on that file a on spacewalk p to provide
a certain grade of consistency between the spacewalks concerning the revision
of the file and the content of the file.

rgds
Christoph Sievers

Comment 2 Justin Sherrill 2010-02-12 22:00:44 UTC
663f0cb9c44dfaa49b115537d8989af9a4b0c1d1

added to master

Comment 3 Miroslav Suchý 2010-05-05 14:56:58 UTC
This bug has been fixed in Spacewalk 1.0.
Closing.