Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1076069

Summary: Unable to add additional ssh keys
Product: OpenShift Container Platform Reporter: Dan Varga <dvarga>
Component: NodeAssignee: Brenton Leanhardt <bleanhar>
Status: CLOSED ERRATA QA Contact: Gaoyun Pei <gpei>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.0.0CC: abutcher, ahecox, bleanhar, ihands, jialiu, kroberts, libra-onpremise-devel
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-15 14:40:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Broker stacktrace /var/log/openshift/broker/production.log
none
Mcollective logs from hosts where his applications live. none

Description Dan Varga 2014-03-13 13:14:27 UTC 
Description of problem:
In support of the Red Hat Customer Portal Labs applications we have a namespace shared by many users.  While attempting to add a new developers ssh key, the management console takes a significant amount of time and eventually returns an error.  The new user has been added to some, but not all of the applications in the namespace.


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


How reproducible:
100% for the labsdev namespace.


Steps to Reproduce:
1. Attempt to add a new ssh key

Actual results:

Timeout and the ssh key has not been added to all apps in the namespace.


Expected results:
ssh key added to all apps in the namespace.


Additional info:
abutcher will attach logs with additional information shortly.
Comment 1 Andrew Butcher 2014-03-13 13:22:17 UTC 
Created attachment 873987 [details]
Broker stacktrace /var/log/openshift/broker/production.log

This is the stacktrace seen on the broker host.
Comment 2 Andrew Butcher 2014-03-13 13:28:06 UTC 
Created attachment 873988 [details]
Mcollective logs from hosts where his applications live.

These are mcollective logs from hosts that the applications to be updated live on. Looking for updates to ssh-key for user 'erich' will show the operation.

One instance of an application not being updated is 'ivammapper' which lives on int-general-small-014. This application is not listed as being updated on that host but can be seen in application list for user.
Comment 4 Brenton Leanhardt 2014-03-20 20:34:47 UTC 
We've confirmed that the OSE 2.1 codebase improves the efficiency of sshkey addition significantly.  We could easily add 100 gears and 100 keys without the risk of anything timing out.

As for the timeout in 2.0 our suspicion now is that it was a proxy timeout in Apache.
Comment 6 Gaoyun Pei 2014-03-24 01:15:03 UTC 
Move this bug to VERIFIED according to Comment 4