Bug 748826 - wallaby upgrade-db checking new items
Summary: wallaby upgrade-db checking new items
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: wallaby
Version: Development
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: grid-maint-list
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-25 13:26 UTC by Lubos Trilety
Modified: 2016-05-26 19:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-26 19:57:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lubos Trilety 2011-10-25 13:26:18 UTC
Description of problem:
Wallaby upgrade db tool should also check if there is not the same item as
added one. User can accidentally use the same name.


Version-Release number of selected component (if applicable):
wallaby-0.12.0-1


How reproducible:
100%


Steps to Reproduce:
1. before patch 1.15 add a parameter CAROD
# ccs -l -p CAROD
Parameter "CAROD":
Name: CAROD
Type: string
Default: test value
Description: test description
MustChange: False
VisibilityLevel: 0
RequiresRestart: False
Dependencies:
Conflicts:

2. run wallaby upgrade-db with patch 1.15 (without --force/-f option)

3. check CAROD parameter
# ccs -l -p CAROD
Parameter "CAROD":
Name: CAROD
Type: String
Default: $(SBIN)/carod
Description: The location of the carod daemon
MustChange: False
VisibilityLevel: 0
RequiresRestart: True
Dependencies:
Conflicts:


Actual results:
The item was changed without any problem.

Expected results:
Wallaby print error message and revert upgrade.

Additional info:

Comment 2 Anne-Louise Tangring 2016-05-26 19:57:33 UTC
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.


Note You need to log in before you can comment on or make changes to this bug.