Attachment 602789 Details for Bug 846386 – screen log

screen log

screen_log.txt (text/plain), 15.15 KB, created by Pavlina Bartikova on 2012-08-07 15:45:49 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Pavlina Bartikova

Created: 2012-08-07 15:45:49 UTC

Size: 15.15 KB

patch

obsolete

>[root@ip-10-32-82-147 ~]# rhui-manager 
>
>
>------------------------------------------------------------------------------
>             -= Red Hat Update Infrastructure Management Tool =-
>
>
>-= Home =-
>
>   r   manage repositories
>   c   manage content delivery servers (CDS)
>   s   synchronization status and scheduling
>   e   create entitlement certificates and client configuration RPMs
>   n   manage Red Hat entitlement certificates
>   u   manage users
>   i   manage identity certificate
>
>   logout
>       removes stored authentication credentials and exits
>
>   <   move to the previous screen
>   ^, home
>       move to the home screen
>   /, clear
>       clears the screen
>   ?, help
>       display help
>   q, quit, exit
>       exit
>
>                                       Connected: ip-10-32-82-147.ec2.internal
>------------------------------------------------------------------------------
>rhui (home) => r
>
>------------------------------------------------------------------------------
>             -= Red Hat Update Infrastructure Management Tool =-
>
>
>-= Repository Management =-
>
>   l   list repositories currently managed by the RHUI
>   i   display detailed information on a repository
>   a   add a new Red Hat content repository
>   c   create a new custom repository
>   d   delete a repository from the RHUI
>   u   upload content to a custom repository
>   p   list packages in a repository
>
>                                       Connected: ip-10-32-82-147.ec2.internal
>------------------------------------------------------------------------------
>rhui (repo) => l
>
>No repositories are currently managed by the RHUI
>
>------------------------------------------------------------------------------
>rhui (repo) => c
>
>Unique ID for the custom repository (alphanumerics, _, and - only):
>custom_repo_1
>
>Display name for the custom repository [custom_repo_1]:
>custom_repo_1
>
>Path at which the repository will be served [custom_repo_1]:
>custom_repo_1
>
>Algorithm to use when calculating the checksum values for repository metadata:
>* Select "sha256" for RHEL6:
>* Select "sha1" for either RHEL5 or RHEL6:
>
>  1  - sha256
>  2  - sha1
>Enter value (1-2) or 'b' to abort: 1
>
>Should the repository require an entitlement certificate to access? (y/n)
>y
>
>Path that should be used when granting an entitlement for this repository. This
>may use yum variable substitutions (e.g. $basearch) to group this together with
>other repositories that share the entitlement [custom_repo_1]:
>
>
>Should the repository require clients to perform a GPG check and
>verify packages are signed by a GPG key? (y/n)
>n
>
>The following repository will be created:
>  ID:              custom_repo_1
>  Name:            custom_repo_1
>  Path:            custom_repo_1
>  Entitlement:     custom_repo_1
>  GPG Check        No
>  Red Hat GPG Key: No
>Proceed? (y/n) y
>
>Successfully created repository custom_repo_1
>
>------------------------------------------------------------------------------
>rhui (repo) => c
>
>Unique ID for the custom repository (alphanumerics, _, and - only):
>custom_repo_2
>
>Display name for the custom repository [custom_repo_2]:
>custom_repo_2
>
>Path at which the repository will be served [custom_repo_2]:
>custom_repo_2
>
>Algorithm to use when calculating the checksum values for repository metadata:
>* Select "sha256" for RHEL6:
>* Select "sha1" for either RHEL5 or RHEL6:
>
>  1  - sha256
>  2  - sha1
>Enter value (1-2) or 'b' to abort: 1
>
>Should the repository require an entitlement certificate to access? (y/n)
>n
>
>Should the repository require clients to perform a GPG check and
>verify packages are signed by a GPG key? (y/n)
>n
>
>The following repository will be created:
>  ID:              custom_repo_2
>  Name:            custom_repo_2
>  Path:            custom_repo_2
>  GPG Check        No
>  Red Hat GPG Key: No
>Proceed? (y/n) y
>
>Successfully created repository custom_repo_2
>
>------------------------------------------------------------------------------
>rhui (repo) => u
>
>Select the repositories to upload the package into:
>  -  1 : custom_repo_1
>  -  2 : custom_repo_2
>Enter value (1-2) to toggle selection, 'c' to confirm selections, or '?' for more commands: 2
>
>Select the repositories to upload the package into:
>  -  1 : custom_repo_1
>  x  2 : custom_repo_2
>Enter value (1-2) to toggle selection, 'c' to confirm selections, or '?' for more commands: c
>
>
>Enter the location of the packages to upload. If the location is an RPM,
>the file will be uploaded. If the location is a directory, all RPMs in that
>directory will be uploaded:
>/root/custom_repo_1.rpm
>
>The following RPMs will be uploaded:
>  custom_repo_1.rpm
>Proceed? (y/n) y
>
>
>Uploading /root/custom_repo_1.rpm...
>
>------------------------------------------------------------------------------
>rhui (repo) => i
>
>Select one or more repositories:
>
>  Custom Repositories
>    -  1 : custom_repo_1
>    -  2 : custom_repo_2
>
>  Red Hat Repositories
>
>Enter value (1-2) to toggle selection, 'c' to confirm selections, or '?' for more commands: 1-2
>
>Select one or more repositories:
>
>  Custom Repositories
>    x  1 : custom_repo_1
>    x  2 : custom_repo_2
>
>  Red Hat Repositories
>
>Enter value (1-2) to toggle selection, 'c' to confirm selections, or '?' for more commands: c
>
>
>Name:                custom_repo_1
>Type:                Custom
>Relative Path:       custom_repo_1
>Entitlement Path:    custom_repo_1
>GPG Check:           No
>Package Count:       0
>
>Name:                custom_repo_2
>Type:                Custom
>Relative Path:       custom_repo_2
>GPG Check:           No
>Package Count:       1
>
>
>------------------------------------------------------------------------------
>rhui (repo) => ^
>
>------------------------------------------------------------------------------
>             -= Red Hat Update Infrastructure Management Tool =-
>
>
>-= Home =-
>
>   r   manage repositories
>   c   manage content delivery servers (CDS)
>   s   synchronization status and scheduling
>   e   create entitlement certificates and client configuration RPMs
>   n   manage Red Hat entitlement certificates
>   u   manage users
>   i   manage identity certificate
>
>                                       Connected: ip-10-32-82-147.ec2.internal
>------------------------------------------------------------------------------
>rhui (home) => c
>
>------------------------------------------------------------------------------
>             -= Red Hat Update Infrastructure Management Tool =-
>
>
>-= Content Delivery Server (CDS) Management =-
>
>   l   list all CDS clusters and instances managed by the RHUI
>   i   display detailed information on a CDS cluster
>   a   register (add) a new CDS instance
>   m   move CDS(s) to a different cluster
>   d   unregister (delete) a CDS instance from the RHUI
>   s   associate a repository with a CDS cluster
>   u   unassociate a repository from a CDS cluster
>
>                                       Connected: ip-10-32-82-147.ec2.internal
>------------------------------------------------------------------------------
>rhui (cds) => s
>
>-= RHUI Content Delivery Server Clusters =-
>
>Select the CDS Cluster for repo association:
>  1  - cluster1
>Enter value (1-1) or 'b' to abort: 1
>Select one or more repositories to associate with the cluster1 cluster: 
>
>  Custom Repositories
>    -  1 : custom_repo_1
>    -  2 : custom_repo_2
>
>  Red Hat Repositories
>
>Enter value (1-2) to toggle selection, 'c' to confirm selections, or '?' for more commands: 1-2
>
>Select one or more repositories to associate with the cluster1 cluster: 
>
>  Custom Repositories
>    x  1 : custom_repo_1
>    x  2 : custom_repo_2
>
>  Red Hat Repositories
>
>Enter value (1-2) to toggle selection, 'c' to confirm selections, or '?' for more commands: c
>
>
>The following repositories will be associated with the cluster1 cluster:
>
>Custom Repositories
>  custom_repo_1
>  custom_repo_2
>
>Proceed? (y/n) y
>
>Associating repository custom_repo_1...
>  ... successfully associated repository
>Associating repository custom_repo_2...
>  ... successfully associated repository
>
>Content will not be downloaded to the cluster until the next cluster sync is run.
>
>------------------------------------------------------------------------------
>rhui (cds) => ^
>
>------------------------------------------------------------------------------
>             -= Red Hat Update Infrastructure Management Tool =-
>
>
>-= Home =-
>
>   r   manage repositories
>   c   manage content delivery servers (CDS)
>   s   synchronization status and scheduling
>   e   create entitlement certificates and client configuration RPMs
>   n   manage Red Hat entitlement certificates
>   u   manage users
>   i   manage identity certificate
>
>                                       Connected: ip-10-32-82-147.ec2.internal
>------------------------------------------------------------------------------
>rhui (home) => s
>
>------------------------------------------------------------------------------
>             -= Red Hat Update Infrastructure Management Tool =-
>
>
>-= Synchronization Status =-
>
>   dr  display repo sync summary
>   vr  view the details of the last repository sync
>   sr  sync an individual repository immediately
>   dc  display CDS sync summary
>   vc  view the details of the last CDS sync
>   sc  sync an individual CDS immediately
>   sl  sync a CDS cluster immediately
>
>                                       Connected: ip-10-32-82-147.ec2.internal
>------------------------------------------------------------------------------
>rhui (sync) => sl
>
>Select one or more CDS clusters to schedule to be synchronized before its scheduled time.
>The sync will happen as soon as possible depending on other tasks that may be executing
>in the RHUI.  Only CDS clusters that currently do not have a CDS instance sychronizing are displayed.
>         ------------------------------------------
>  -  1 : cluster1
>Enter value (1-1) to toggle selection, 'c' to confirm selections, or '?' for more commands: 1
>
>Select one or more CDS clusters to schedule to be synchronized before its scheduled time.
>The sync will happen as soon as possible depending on other tasks that may be executing
>in the RHUI.  Only CDS clusters that currently do not have a CDS instance sychronizing are displayed.
>         ------------------------------------------
>  x  1 : cluster1
>Enter value (1-1) to toggle selection, 'c' to confirm selections, or '?' for more commands: c
>
>
>The following CDS clusters will be scheduled for synchronization:
>  cluster1
>Proceed? (y/n) y
>
>
>Scheduling sync for cluster1...
>... successfully scheduled for the next available timeslot.
>
>------------------------------------------------------------------------------
>rhui (sync) => dc
>
>------------------------------------------------------------------------------
>             -= Red Hat Update Infrastructure Management Tool =-
>
>
>-= CDS Synchronization Status =-
>
>Last Refreshed: 09:40:58
>(updated every 5 seconds, ctrl+c to exit)
>
>
>ip-10-32-46-222.ec2.internal ................................ [  UP  ]
>
>
>Next Sync                    Last Sync                    Last Result         
>------------------------------------------------------------------------------
>ip-10-32-46-222.ec2.internal
>08-07-2012 11:16             08-07-2012 09:40             Success    
>
>
>                                       Connected: ip-10-32-82-147.ec2.internal
>------------------------------------------------------------------------------
>^Crhui (sync) => ^
>
>------------------------------------------------------------------------------
>             -= Red Hat Update Infrastructure Management Tool =-
>
>
>-= Home =-
>
>   r   manage repositories
>   c   manage content delivery servers (CDS)
>   s   synchronization status and scheduling
>   e   create entitlement certificates and client configuration RPMs
>   n   manage Red Hat entitlement certificates
>   u   manage users
>   i   manage identity certificate
>
>                                       Connected: ip-10-32-82-147.ec2.internal
>------------------------------------------------------------------------------
>rhui (home) => e
>
>------------------------------------------------------------------------------
>             -= Red Hat Update Infrastructure Management Tool =-
>
>
>-= Client Entitlement Management =-
>
>   e   generate an entitlement certificate
>   c   create a client configuration RPM from an entitlement certificate
>
>                                       Connected: ip-10-32-82-147.ec2.internal
>------------------------------------------------------------------------------
>rhui (client) => e
>
>Select the CDS cluster that clients using this entitlement certificate will use to download content:
>
>  1  - cluster1
>Enter value (1-1) or 'b' to abort: 1
>
>Select one or more repositories to include in the entitlement certificate:
>(an * next to a Red Hat repository indicates it is deployed in the RHUI)
>
>  Custom Repositories
>    -  1 : custom_repo_1
>             custom_repo_1
>
>
>  Red Hat Repositories
>
>Enter value (1-1) to toggle selection, 'c' to confirm selections, or '?' for more commands: 1
>
>Select one or more repositories to include in the entitlement certificate:
>(an * next to a Red Hat repository indicates it is deployed in the RHUI)
>
>  Custom Repositories
>    x  1 : custom_repo_1
>             custom_repo_1
>
>
>  Red Hat Repositories
>
>Enter value (1-1) to toggle selection, 'c' to confirm selections, or '?' for more commands: c
>
>
>Name of the certificate. This will be used as the name of the certificate file
>(name.crt) and its associated private key (name.key). Choose something that will
>help identify the products contained with it:
>client_cert
>
>Local directory in which to save the generated certificate [current directory]:
>/root/client_cert
>
>Number of days the certificate should be valid [365]:
>365
>
>Repositories to be included in the entitlement certificate:
>
>  Custom Entitlements
>    custom_repo_1
>
>Proceed? (y/n) y
>
>.......+++
>........................+++
>Entitlement certificate created at /root/client_cert/client_cert.crt
>
>------------------------------------------------------------------------------
>rhui (client) => c
>
>Full path to local directory in which the client configuration files generated by this tool
>should be stored (if this directory does not exist, it will be created):
>/root/client_rpm
>
>Name of the RPM:
>client_rpm
>
>Version of the configuration RPM [2.0]:
>
>
>Full path to the entitlement certificate authorizing the client to access
>specific channels:
>/root/client_cert/client_cert.crt
>
>Full path to the private key for the above entitlement certificate:
>/root/client_cert/client_cert.key
>
>
>Select the CDS cluster that clients will use to download content:
>
>  1  - cluster1
>Enter value (1-1) or 'b' to abort: 1
>
>Select the CDS instance (client hostnames are shown)
>that should be the primary load balancer for the
>client. All other CDS instances will be listed as
>back up load balancers in the client's mirror list:
>
>  1  - ip-10-32-46-222.ec2.internal
>Enter value (1-1) or 'b' to abort: 1
>
>Load Balancer Order:
>  ip-10-32-46-222.ec2.internal
>
>Select any unprotected repositories to be included in the client configuration:
>  -  1 : custom_repo_2
>Enter value (1-1) to toggle selection, 'c' to confirm selections, or '?' for more commands: 1
>
>Select any unprotected repositories to be included in the client configuration:
>  x  1 : custom_repo_2
>Enter value (1-1) to toggle selection, 'c' to confirm selections, or '?' for more commands: c
>
>
>Error occurred during RPM creation, check the log file for more information
>
>------------------------------------------------------------------------------
>rhui (client) => 
>

Actions: View

Attachments on bug 846386: 602789 | 602790