Attachment 696464 Details for Bug 815975 – Verification log

Verification log

success-tcms8211.test_bug_815975.test_02_test.txt (text/plain), 9.53 KB, created by Vitaly Kuznetsov on 2013-02-12 11:05:36 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Vitaly Kuznetsov

Created: 2013-02-12 11:05:36 UTC

Size: 9.53 KB

patch

obsolete

>q
>rhui-manager
>[root@rhua ~]# rhui-manager
>[H[J[0m
>------------------------------------------------------------------------------
>             -= 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: rhua.example.com
>------------------------------------------------------------------------------
>rhui (home) => r
>[H[J
>------------------------------------------------------------------------------
>             -= 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: rhua.example.com
>------------------------------------------------------------------------------
>rhui (repo) => c
>
>Unique ID for the custom repository (alphanumerics, _, and - only):
>custom-i386-x86_64
>
>Display name for the custom repository [custom-i386-x86_64]:
>
>
>Path at which the repository will be served [custom-i386-x86_64]:
>custom/i386/x86_64
>
>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
>
>Based on the repository's relative path, the suggested entitlement path is:
>  custom/i386/x86_64
>
>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/i386/x86_64]:
>
>
>Should the repository require clients to perform a GPG check and
>verify packages are signed by a GPG key? (y/n)
>y
>
>Will the repository be used to host any Red Hat GPG signed content? (y/n)
>y
>
>Will the repository be used to host any custom GPG signed content? (y/n)
>n
>
>The following repository will be created:
>  ID:              custom-i386-x86_64
>  Name:            custom-i386-x86_64
>  Path:            custom/i386/x86_64
>  Entitlement:     custom/i386/x86_64
>  GPG Check        Yes
>  Custom GPG Keys: (None)
>  Red Hat GPG Key: Yes
>Proceed? (y/n) y
>
>Successfully created repository custom-i386-x86_64
>
>------------------------------------------------------------------------------
>rhui (repo) => q
>rhui-manager
>[root@rhua ~]# rhui-manager
>[H[J[0m
>------------------------------------------------------------------------------
>             -= 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: rhua.example.com
>------------------------------------------------------------------------------
>rhui (home) => r
>[H[J
>------------------------------------------------------------------------------
>             -= 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: rhua.example.com
>------------------------------------------------------------------------------
>rhui (repo) => c
>
>Unique ID for the custom repository (alphanumerics, _, and - only):
>custom-x86_64-x86_64
>
>Display name for the custom repository [custom-x86_64-x86_64]:
>
>
>Path at which the repository will be served [custom-x86_64-x86_64]:
>custom/x86_64/x86_64
>
>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
>
>Based on the repository's relative path, the suggested entitlement path is:
>  custom/x86_64/x86_64
>
>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/x86_64/x86_64]:
>
>
>Should the repository require clients to perform a GPG check and
>verify packages are signed by a GPG key? (y/n)
>y
>
>Will the repository be used to host any Red Hat GPG signed content? (y/n)
>y
>
>Will the repository be used to host any custom GPG signed content? (y/n)
>n
>
>The following repository will be created:
>  ID:              custom-x86_64-x86_64
>  Name:            custom-x86_64-x86_64
>  Path:            custom/x86_64/x86_64
>  Entitlement:     custom/x86_64/x86_64
>  GPG Check        Yes
>  Custom GPG Keys: (None)
>  Red Hat GPG Key: Yes
>Proceed? (y/n) y
>
>Successfully created repository custom-x86_64-x86_64
>
>------------------------------------------------------------------------------
>rhui (repo) => q
>rhui-manager
>[root@rhua ~]# rhui-manager
>[H[J[0m
>------------------------------------------------------------------------------
>             -= 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: rhua.example.com
>------------------------------------------------------------------------------
>rhui (home) => r
>[H[J
>------------------------------------------------------------------------------
>             -= 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: rhua.example.com
>------------------------------------------------------------------------------
>rhui (repo) => c
>
>Unique ID for the custom repository (alphanumerics, _, and - only):
>custom-i386-i386
>
>Display name for the custom repository [custom-i386-i386]:
>
>
>Path at which the repository will be served [custom-i386-i386]:
>custom/i386/i386
>
>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
>
>Based on the repository's relative path, the suggested entitlement path is:
>  custom/i386/i386
>
>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/i386/i386]:
>
>
>Should the repository require clients to perform a GPG check and
>verify packages are signed by a GPG key? (y/n)
>y
>
>Will the repository be used to host any Red Hat GPG signed content? (y/n)
>y
>
>Will the repository be used to host any custom GPG signed content? (y/n)
>n
>
>The following repository will be created:
>  ID:              custom-i386-i386
>  Name:            custom-i386-i386
>  Path:            custom/i386/i386
>  Entitlement:     custom/i386/i386
>  GPG Check        Yes
>  Custom GPG Keys: (None)
>  Red Hat GPG Key: Yes
>Proceed? (y/n) y
>
>Successfully created repository custom-i386-i386
>
>------------------------------------------------------------------------------
>rhui (repo) =>

Actions: View

Attachments on bug 815975: 580019 | 580020 | 580021 | 580022 | 580826 | 584992 | 601923 | 693298 | 696464