IBM Support

PM33853: 'cleartool rebase -cancel -force' leaves target view set to rebase activity

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In IBM Rational ClearCase, if a rebase is canceled ( by example
    via the command 'cleartool rebase -cancel -force') from a
    different view than the view it was started in and the views do
    not share a region, then the rebase is canceled, but the result
    is:
    1) the rebase activity is not deleted
    2) the original view is still set to this activity.
    
    This can happen when a user would cancel a rebase from a Windows
    view after starting the rebase from a Unix view.
    
    As example, from the command line the following output is
    generated by
      'cleartool rebase -cancel -force'
    
    cleartool: Error: Unable to find view by uuid:xxxxxxxxxx, last
    known at 'unknown:unknown'.
    cleartool: Error: Unable to get view handle.
    cleartool: Warning: Unable to construct object 'xxxxxxxxxx'.
    Rebase in progress on stream 'd'.
    Started by '?username?' at 2/28/2011 1:33:14 PM.
    Undoing checkins...
    Undoing file merges...
    Removing integration activity...
    cleartool: Error: Activity
    'activity:rebase.d.20110228.133314@\t1_test' is set in view
    '?no-tag-in-region?'.
    Unable to remove integration activity
    'rebase.d.20110228.133314'.
    Restoring rebase view's previous config spec...
    Checking snapshot view reload state...
    Rebase canceled.
    
    At this point the original view is 'locked': it is set to a
    rebase activity that cannot be unset through 'cleartool setact
    -none' and the rebase is no longer in progress.
    
    If the two views are in the same region, the rebase -cancel
    fails to start:
    
    Rebase in progress on stream 'd'.
    Started by '?username?' at 2/28/2011 1:34:26 PM.
    cleartool: Error: Rebase in progress on stream 'd' using
      view 't2_d1' does not match the view specified.
    cleartool: Error: View 't2_d2' is not the view in which you
    started this operation.
    cleartool: Error: Unable to cancel rebase.
    
    
    WORKAROUND:
    
    In order to cleanup an existing situation:
    - delete the view
    To prevent further occurrence:
    - create a trigger on preoperation 'rebase -cancel' that checks
    for this condition
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In IBM Rational ClearCase, if a rebase is canceled ( by
    example via the command 'cleartool rebase -cancel -force')
    from a different view than the view it was started in and
    the views do not share a region, then the rebase is
    canceled, but the result is:
    1) the rebase activity is not deleted
    2) the original view is still set to this activity.
    
    This can happen when a user would cancel a rebase from a
    Windows view after starting the rebase from a Unix view.
    
    As example, from the command line the following output is
    generated by
      'cleartool rebase -cancel -force'
    
    cleartool: Error: Unable to find view by uuid:xxxxxxxxxx,
    last known at "unknown:unknown".
    cleartool: Error: Unable to get view handle.
    cleartool: Warning: Unable to construct object "xxxxxxxxxx".
    Rebase in progress on stream "d".
    Started by "?username?" at 2/28/2011 1:33:14 PM.
    Undoing checkins...
    Undoing file merges...
    Removing integration activity...
    cleartool: Error: Activity
    "activity:rebase.d.20110228.133314@\t1_test" is set in view
    "?no-tag-in-region?".
    Unable to remove integration activity
    "rebase.d.20110228.133314".
    Restoring rebase view's previous config spec...
    Checking snapshot view reload state...
    Rebase canceled.
    
    At this point the original view is 'locked': it is set to a
    rebase activity that cannot be unset through 'cleartool
    setact -none' and the rebase is no longer in progress.
    
    If the two views are in the same region, the rebase -cancel
    fails to start:
    
    Rebase in progress on stream "d".
    Started by "?username?" at 2/28/2011 1:34:26 PM.
    cleartool: Error: Rebase in progress on stream "d" using
      view "t2_d1" does not match the view specified.
    cleartool: Error: View "t2_d2" is not the view in which you
    started this operation.
    cleartool: Error: Unable to cancel rebase.
    
    
    WORKAROUND:
    
    In order to cleanup an existing situation:
    - delete the view
    To prevent further occurrence:
    - create a trigger on preoperation 'rebase -cancel' that
    checks for this condition
    

Problem conclusion

  • A fix is available in ClearCase versions 7.1.1.8, 7.1.2.5
    and 8.0.0.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM33853

  • Reported component name

    CLEARCASE WIN

  • Reported component ID

    5724G2900

  • Reported release

    711

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-01

  • Closed date

    2011-12-16

  • Last modified date

    2011-12-16

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    CLEARCASE WIN

  • Fixed component ID

    5724G2900

Applicable component levels

  • R711 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
16 December 2011