Bug 1009129 - puppet repo bind fails from consumer
Summary: puppet repo bind fails from consumer
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Pulp
Classification: Retired
Component: puppet-support
Version: Master
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: 2.3.0
Assignee: Jeff Ortel
QA Contact: Preethi Thomas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-17 18:26 UTC by Preethi Thomas
Modified: 2013-12-09 14:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-09 14:29:56 UTC
Embargoed:


Attachments (Terms of Use)

Description Preethi Thomas 2013-09-17 18:26:40 UTC
Description of problem:
Trying to bind a puppet repo to consumer ends with task failed

Version-Release number of selected component (if applicable):
[root@pulp-v2-client ~]# rpm -qa pulp-consumer-client
pulp-consumer-client-2.3.0-0.12.alpha.el6.noarch
[root@pulp-v2-client ~]# 


How reproducible:


Steps to Reproduce:
[root@pulp-v2-client ~]# pulp-consumer -u admin -p admin puppet bind --repo-id puppet-repo
This command may be exited via ctrl+c without affecting the request.

-- Updating Pulp Server --
[-]
Waiting to begin...

[-]
Running...

Task Succeeded


-- Notifying the Consumer --
[-]
Waiting to begin...

[-]
Running...

Task Failed

[u"AuthenticationFailure: Error in sasl_client_start (-1) SASL(-1): generic
failure: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more
information (Credentials cache file '/tmp/krb5cc_48' not found)\n"]

Error in sasl_client_start (-1) SASL(-1): generic failure: GSSAPI Error:
Unspecified GSS failure.  Minor code may provide more information (Credentials
cache file '/tmp/krb5cc_48' not found)

[root@pulp-v2-client ~]# 

Actual results:


Expected results:


Additional info:

Comment 1 Preethi Thomas 2013-09-17 18:35:43 UTC
[root@pulp-v2-server ~]# pulp-admin  puppet consumer install run --consumer-id pulp-client -u puppetlabs/stdlib/
This command may be exited via ctrl+c without affecting the request.

[-]
Waiting to begin...


Install Failed

Error in sasl_client_start (-1) SASL(-1): generic failure: GSSAPI Error:
Unspecified GSS failure.  Minor code may provide more information (Credentials
cache file '/tmp/krb5cc_48' not found)

[root@pulp-v2-server ~]#

Comment 2 Jeff Ortel 2013-10-02 17:02:22 UTC
Works for me:

[root@pulp1 ~]# pulp-admin puppet consumer bind --repo-id=forge --consumer-id=pulp3
This command may be exited via ctrl+c without affecting the request.

-- Updating Pulp Server --
[-]
Waiting to begin...

[-]
Running...

Task Succeeded


-- Notifying the Consumer --
[-]
Waiting to begin...

[\]
Running...

Task Succeeded


[root@pulp2 ~]# pulp-consumer -u admin -p admin puppet bind --repo-id=forge
This command may be exited via ctrl+c without affecting the request.

-- Updating Pulp Server --
[-]
Waiting to begin...

[-]
Running...

Task Succeeded


-- Notifying the Consumer --
[-]
Waiting to begin...

[-]
Running...

Task Succeeded



Please retest.

Comment 3 Preethi Thomas 2013-10-04 14:03:00 UTC
[root@pulp-v2-client ~]# rpm -qa pulp-consumer-client
pulp-consumer-client-2.3.0-0.17.beta.el6.noarch
[root@pulp-v2-client ~]# 


[root@pulp-v2-client ~]# pulp-consumer -u admin -p admin puppet bind --repo-id puppet-repo
This command may be exited via ctrl+c without affecting the request.

-- Updating Pulp Server --
[-]
Waiting to begin...

[-]
Running...

Task Succeeded


-- Notifying the Consumer --
[-]
Waiting to begin...

[-]
Running...

Task Succeeded


[root@pulp-v2-client ~]# pulp-consumer puppet repos
+----------------------------------------------------------------------+
                              Repositories
+----------------------------------------------------------------------+

Id:                  puppet-repo
Display Name:        puppet-repo
Description:         None
Content Unit Counts: 
  Puppet Module: 38
Notes:               


[root@pulp-v2-client ~]#

Comment 4 Preethi Thomas 2013-12-09 14:29:56 UTC
Pulp 2.3 released.


Note You need to log in before you can comment on or make changes to this bug.