Attachment 604369 Details for Bug 842785 – Verifying screen log

Verifying screen log

log (text/plain), 20.05 KB, created by mkovacik on 2012-08-14 17:00:03 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: mkovacik

Created: 2012-08-14 17:00:03 UTC

Size: 20.05 KB

patch

obsolete

>[root@ip-10-204-109-219 ~]# 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-204-109-219.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-204-109-219.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-1
>
>Display name for the custom repository [custom-1]:
>
>
>Path at which the repository will be served [custom-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: 2
>
>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-1
>  Name:            custom-1
>  Path:            custom-1
>  GPG Check        No
>  Red Hat GPG Key: No
>Proceed? (y/n) y
>
>
>Successfully created repository custom-1
>
>------------------------------------------------------------------------------
>rhui (repo) => rhui (repo) => c
>
>Unique ID for the custom repository (alphanumerics, _, and - only):
>custom-2
>
>Display name for the custom repository [custom-2]:
>
>
>Path at which the repository will be served [custom-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: 2
>
>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-2
>  Name:            custom-2
>  Path:            custom-2
>  GPG Check        No
>  Red Hat GPG Key: No
>Proceed? (y/n) y
>
>Successfully created repository custom-2
>
>------------------------------------------------------------------------------
>rhui (repo) => custom-protected
>Invalid menu item; type "?" for a list of available commands
>rhui (repo) => c
>
>Unique ID for the custom repository (alphanumerics, _, and - only):
>custom-protected
>
>Display name for the custom repository [custom-protected]:
>
>
>Path at which the repository will be served [custom-protected]:
>
>
>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: 2
>
>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-protected]:
>
>
>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-protected
>  Name:            custom-protected
>  Path:            custom-protected
>  Entitlement:     custom-protected
>  GPG Check        No
>  Red Hat GPG Key: No
>Proceed? (y/n) y
>
>Successfully created repository custom-protected
>
>------------------------------------------------------------------------------
>rhui (repo) => l
>
>Custom Repositories
>  custom-1
>  custom-2
>  custom-protected
>
>
>------------------------------------------------------------------------------
>rhui (repo) => i
>
>Select one or more repositories:
>
>  Custom Repositories
>    -  1 : custom-1
>    -  2 : custom-2
>    -  3 : custom-protected
>
>  Red Hat Repositories
>
>Enter value (1-3) to toggle selection, 'c' to confirm selections, or '?' for more commands: 1-3
>
>Select one or more repositories:
>
>  Custom Repositories
>    x  1 : custom-1
>    x  2 : custom-2
>    x  3 : custom-protected
>
>  Red Hat Repositories
>
>Enter value (1-3) to toggle selection, 'c' to confirm selections, or '?' for more commands: c
>
>
>Name:                custom-1
>Type:                Custom
>Relative Path:       custom-1
>GPG Check:           No
>Package Count:       0
>
>Name:                custom-2
>Type:                Custom
>Relative Path:       custom-2
>GPG Check:           No
>Package Count:       0
>
>Name:                custom-protected
>Type:                Custom
>Relative Path:       custom-protected
>Entitlement Path:    custom-protected
>GPG Check:           No
>Package Count:       0
>
>
>------------------------------------------------------------------------------
>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-204-109-219.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-204-109-219.ec2.internal
>------------------------------------------------------------------------------
>rhui (cds) => a
>
>Prior to registering a CDS, the CDS must be configured and running.
>
>Hostname of the CDS to register:
>ip-10-98-18-117.ec2.internal
>
>Client hostname (hostname clients will use to connect to the CDS) [ip-10-98-18-117.ec2.internal]:
>
>
>Display name for the CDS [ip-10-98-18-117.ec2.internal]:
>
>
>
>Enter a CDS cluster name:
>cluster-1
>
>The following CDS instance will be registered:
>  Hostname: ip-10-98-18-117.ec2.internal
>  Client Hostname: ip-10-98-18-117.ec2.internal
>  Name:     ip-10-98-18-117.ec2.internal
>  Cluster:  cluster-1
>Proceed? (y/n) y
>
>
>Successfully registered ip-10-98-18-117.ec2.internal
>
>------------------------------------------------------------------------------
>rhui (cds) => a
>
>Prior to registering a CDS, the CDS must be configured and running.
>
>Hostname of the CDS to register:
>ip-10-202-253-102.ec2.internal
>
>Client hostname (hostname clients will use to connect to the CDS) [ip-10-202-253-102.ec2.internal]:
>
>
>Display name for the CDS [ip-10-202-253-102.ec2.internal]:
>
>
>Select a CDS cluster or enter a new one:
>  1  - *** Create a new cluster ***
>  2  - cluster-1
>Enter value (1-2) or 'b' to abort: 1
>
>Enter a CDS cluster name:
>cluster-2
>
>The following CDS instance will be registered:
>  Hostname: ip-10-202-253-102.ec2.internal
>  Client Hostname: ip-10-202-253-102.ec2.internal
>  Name:     ip-10-202-253-102.ec2.internal
>  Cluster:  cluster-2
>Proceed? (y/n) y
>
>
>Successfully registered ip-10-202-253-102.ec2.internal
>
>------------------------------------------------------------------------------
>rhui (cds) => s
>
>-= RHUI Content Delivery Server Clusters =-
>
>Select the CDS Cluster for repo association:
>  1  - cluster-1
>  2  - cluster-2
>Enter value (1-2) or 'b' to abort: 1
>Select one or more repositories to associate with the cluster-1 cluster:
>
>  Custom Repositories
>    -  1 : custom-1
>    -  2 : custom-2
>    -  3 : custom-protected
>
>  Red Hat Repositories
>
>Enter value (1-3) to toggle selection, 'c' to confirm selections, or '?' for more commands: 3
>
>Select one or more repositories to associate with the cluster-1 cluster:
>
>  Custom Repositories
>    -  1 : custom-1
>    -  2 : custom-2
>    x  3 : custom-protected
>
>  Red Hat Repositories
>
>Enter value (1-3) to toggle selection, 'c' to confirm selections, or '?' for more commands: c
>
>
>The following repositories will be associated with the cluster-1 cluster:
>
>Custom Repositories
>  custom-protected
>
>Proceed? (y/n) y
>
>Associating repository custom-protected...
>  ... successfully associated repository
>
>Content will not be downloaded to the cluster until the next cluster sync is run.
>
>------------------------------------------------------------------------------
>rhui (cds) => s
>
>-= RHUI Content Delivery Server Clusters =-
>
>Select the CDS Cluster for repo association:
>  1  - cluster-1
>  2  - cluster-2
>Enter value (1-2) or 'b' to abort: 1
>Select one or more repositories to associate with the cluster-1 cluster:
>
>  Custom Repositories
>    -  1 : custom-1
>    -  2 : custom-2
>
>  Red Hat Repositories
>
>Enter value (1-2) to toggle selection, 'c' to confirm selections, or '?' for more commands: 1
>
>Select one or more repositories to associate with the cluster-1 cluster:
>
>  Custom Repositories
>    x  1 : custom-1
>    -  2 : custom-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 cluster-1 cluster:
>
>Custom Repositories
>  custom-1
>
>Proceed? (y/n) y
>
>Associating repository custom-1...
>  ... successfully associated repository
>
>Content will not be downloaded to the cluster until the next cluster sync is run.
>
>------------------------------------------------------------------------------
>rhui (cds) => s
>
>-= RHUI Content Delivery Server Clusters =-
>
>Select the CDS Cluster for repo association:
>  1  - cluster-1
>  2  - cluster-2
>Enter value (1-2) or 'b' to abort: 2
>Select one or more repositories to associate with the cluster-2 cluster:
>
>  Custom Repositories
>    -  1 : custom-1
>    -  2 : custom-2
>    -  3 : custom-protected
>
>  Red Hat Repositories
>
>Enter value (1-3) to toggle selection, 'c' to confirm selections, or '?' for more commands: 2-3
>
>Select one or more repositories to associate with the cluster-2 cluster:
>
>  Custom Repositories
>    -  1 : custom-1
>    x  2 : custom-2
>    x  3 : custom-protected
>
>  Red Hat Repositories
>
>Enter value (1-3) to toggle selection, 'c' to confirm selections, or '?' for more commands: c
>
>
>The following repositories will be associated with the cluster-2 cluster:
>
>Custom Repositories
>  custom-2
>  custom-protected
>
>Proceed? (y/n) y
>
>Associating repository custom-2...
>  ... successfully associated repository
>Associating repository custom-protected...
>  ... successfully associated repository
>
>Content will not be downloaded to the cluster until the next cluster sync is run.
>
>------------------------------------------------------------------------------
>rhui (cds) => i
>
>Select one or more CDS clusters:
>
>  -  1 : cluster-1
>  -  2 : cluster-2
>Enter value (1-2) to toggle selection, 'c' to confirm selections, or '?' for more commands: 1-2
>
>Select one or more CDS clusters:
>
>  x  1 : cluster-1
>  x  2 : cluster-2
>Enter value (1-2) to toggle selection, 'c' to confirm selections, or '?' for more commands: c
>
>-= RHUI CDS Clusters =-
>
>  cluster-1
>  ---------
>
>    CDS Instances
>    -------------
>    ip-10-98-18-117.ec2.internal
>      hostname:        ip-10-98-18-117.ec2.internal
>      client hostname: ip-10-98-18-117.ec2.internal
>
>    Repositories
>    ------------
>    custom-protected
>    custom-1
>
>
>  cluster-2
>  ---------
>
>    CDS Instances
>    -------------
>    ip-10-202-253-102.ec2.internal
>      hostname:        ip-10-202-253-102.ec2.internal
>      client hostname: ip-10-202-253-102.ec2.internal
>
>    Repositories
>    ------------
>    custom-2
>    custom-protected
>
>
>
>
>------------------------------------------------------------------------------
>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-204-109-219.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-204-109-219.ec2.internal
>------------------------------------------------------------------------------
>rhui (client) => e
>
>Select the CDS cluster that clients using this entitlement certificate will use to download content:
>
>  1  - cluster-1
>  2  - cluster-2
>Enter value (1-2) or 'b' to abort: 1
>
>Select one or more repositories to include in the entitlement certificate:
>
>  Custom Repositories
>    -  1 : custom-protected
>             custom-protected
>
>
>  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:
>
>  Custom Repositories
>    x  1 : custom-protected
>             custom-protected
>
>
>  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:
>abc
>
>Local directory in which to save the generated certificate [current directory]:
>/tmp/abc
>
>Number of days the certificate should be valid [365]:
>
>
>Repositories to be included in the entitlement certificate:
>
>  Custom Entitlements
>    custom-protected
>
>Proceed? (y/n) y
>
>.....................................+++
>.........................+++
>Entitlement certificate created at /tmp/abc/abc.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):
>/tmp/abc/
>
>Name of the RPM:
>abc
>
>Version of the configuration RPM [2.0]:
>
>
>Full path to the entitlement certificate authorizing the client to access
>specific channels:
>/tmp/abc/abc.crt
>
>Full path to the private key for the above entitlement certificate:
>/tmp/abc/abc.key
>
>
>Select the CDS cluster that clients will use to download content:
>
>  1  - cluster-1
>  2  - cluster-2
>Enter value (1-2) 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-98-18-117.ec2.internal
>Enter value (1-1) or 'b' to abort: 1
>
>Load Balancer Order:
>  ip-10-98-18-117.ec2.internal
>
>Select any unprotected repositories to be included in the client configuration:
>  -  1 : custom-1
>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-1
>Enter value (1-1) to toggle selection, 'c' to confirm selections, or '?' for more commands: c
>
>
>Successfully created client configuration RPM.
>RPMs can be found at /tmp/abc/
>
>------------------------------------------------------------------------------
>rhui (client) => e
>
>Select the CDS cluster that clients using this entitlement certificate will use to download content:
>
>  1  - cluster-1
>  2  - cluster-2
>Enter value (1-2) or 'b' to abort: 2
>
>Select one or more repositories to include in the entitlement certificate:
>
>  Custom Repositories
>    -  1 : custom-protected
>             custom-protected
>
>
>  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:
>
>  Custom Repositories
>    x  1 : custom-protected
>             custom-protected
>
>
>  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:
>xyz
>
>Local directory in which to save the generated certificate [current directory]:
>/tmp/xyz
>
>Number of days the certificate should be valid [365]:
>
>
>Repositories to be included in the entitlement certificate:
>
>  Custom Entitlements
>    custom-protected
>
>Proceed? (y/n) y
>
>......................................................+++
>................................................................................................................................................................................+++
>Entitlement certificate created at /tmp/xyz/xyz.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):
>/tmp/xyz
>
>Name of the RPM:
>xyz
>
>Version of the configuration RPM [2.0]:
>
>
>Full path to the entitlement certificate authorizing the client to access
>specific channels:
>/tmp/xyz/xyz.crt
>
>Full path to the private key for the above entitlement certificate:
>/tmp/xyz/xyz.key
>
>
>Select the CDS cluster that clients will use to download content:
>
>  1  - cluster-1
>  2  - cluster-2
>Enter value (1-2) or 'b' to abort: 2
>
>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-202-253-102.ec2.internal
>Enter value (1-1) or 'b' to abort: 1
>
>Load Balancer Order:
>  ip-10-202-253-102.ec2.internal
>
>Select any unprotected repositories to be included in the client configuration:
>  -  1 : custom-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-2
>Enter value (1-1) to toggle selection, 'c' to confirm selections, or '?' for more commands: c
>
>
>Successfully created client configuration RPM.
>RPMs can be found at /tmp/xyz
>
>------------------------------------------------------------------------------
>rhui (client) => q
>[root@ip-10-204-109-219 ~]#

Actions: View

Attachments on bug 842785: 600056 | 601301 | 603312 | 603449 | 603461 | 603579 | 603592 | 604296 | 604369