Bug 1770230 - Replace rhts-sync-set/block commands with rstrnt-sync-set/block commands
Summary: Replace rhts-sync-set/block commands with rstrnt-sync-set/block commands
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Restraint
Classification: Retired
Component: general
Version: 0.1.40
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 0.1.45
Assignee: Carol Bouchard
QA Contact:
URL:
Whiteboard:
: 1748989 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-08 14:32 UTC by Carol Bouchard
Modified: 2020-02-25 22:12 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-05 16:27:01 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Beaker Project Gerrit 6682 0 'None' MERGED Replace rhts-sync cmds with rstrnt-sync-... cmds 2020-08-04 07:55:47 UTC

Description Carol Bouchard 2019-11-08 14:32:50 UTC 
Description of problem:
While reworking beaker multihost documentation, I noticed pieces of it actually belong in restraint documentation which includes description of the commands rhts-sync-set and rhts-sync-block.

Version-Release number of selected component (if applicable):
0.1.42

How reproducible:
always

Steps to Reproduce:
1. review command documentation
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Tomas Klohna 🔧 2019-11-08 14:45:52 UTC 
The reason for that is because restraint contains new commands as rstrnt-sync which are placed on top of rhts-sync-* and that can be tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=1748989
Comment 2 Carol Bouchard 2019-11-12 18:37:53 UTC 
The command rstrnt-sync command is not complete.  I've copied rhts-sync-... commands as rstrnt-sync-... commands and documented accordingly.  Also linked rhts-sync-... commands to the new rstrnt-sync-... commands so we are backward compatible.
Comment 3 Carol Bouchard 2020-02-04 14:09:45 UTC 
*** Bug 1748989 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.