Build failed in Jenkins: Knox-master-patch-scan #23600

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/apache/knox.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 2d77f09f86134f4b665a7bbae2d7c04461e114fc 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 2d77f09f86134f4b665a7bbae2d7c04461e114fc
 > git rev-list 2d77f09f86134f4b665a7bbae2d7c04461e114fc # timeout=10
[Knox-master-patch-scan] $ /bin/bash /tmp/hudson3534517244395758939.sh
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
curl: (52) Empty reply from server
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

Jenkins build is back to normal : Knox-master-patch-scan #23601

[Apache Jenkins Server]

See 

[jira] [Commented] (KNOX-762) Remove dependency on httpcomponents httpclient 4.5.2

[Larry McCay (JIRA)]

[ 
https://issues.apache.org/jira/browse/KNOX-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595246#comment-15595246
 ] 

Larry McCay commented on KNOX-762:
--

https://issues.apache.org/jira/browse/HTTPCLIENT-1712 including a change to 
have the service class in the SPN be based on the request scheme. This is an 
inappropriate change and has since been reverted.

Unfortunately, it there has not been a new release of httpclient that has this 
change removed.

For 0.10.0 release we will need to downgrade this dependency to 4.5.1 which was 
released a few months prior to the patch and 4.5.2 release.

Benjamin has tested with 4.4.1 and that seems to have fixed it for him.

> Remove dependency on httpcomponents httpclient 4.5.2
> 
>
> Key: KNOX-762
> URL: https://issues.apache.org/jira/browse/KNOX-762
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Reporter: Larry McCay
>Assignee: Larry McCay
> Fix For: 0.10.0
>
>
> Reported by Benjamin Ruland:
>  
> I am experiencing problems with Knox while using WebHDFS in a cluster with 
> Kerberos and SSL.
> The KDC is an Microsoft AD 2012. Kerberos-Encryption is set to AES256. Knox 
> is connected to AD via LDAP sync (this is working fine for other Knox 
> services).
> I am running HDP 2.5 with Knox 0.9.0
>  
> In general, the cluster runs fine. WebHDFS using SPNEGO is working.
>  
> But when accessing WebHDFS over Knox, I get an 401 error and some strange 
> logs.
> I suspect that Knox is trying to get a ticket for a HTTPS/namenode@REALM 
> principal, which does not exist. Although running SSL, all principals for 
> SPNEGO are HTTP/...
>  
> I this a Knox Bug or is this a misconfiguration at some point?
>  
> It would be great, if someone has advice.
>  
> Best regards,
> Benjamin
>  
>  
>  
>  
>  
> The used command is:
>  
> [root@utilitynode ~]# curl -ik -u validuser 
> "https://utilitynode:8443/gateway/default/webhdfs/v1/?OP=LISTSTATUS";
> Enter host password for user 'validuser':
> HTTP/1.1 401 Unauthorized
> Date: Wed, 12 Oct 2016 07:47:41 GMT
> Set-Cookie: rememberMe=deleteMe; Path=/gateway/default; Max-Age=0; 
> Expires=Tue,11-Oct-2016 07:47:41 GMT
> WWW-Authenticate: BASIC realm="application"
> Content-Length: 0
> Server: Jetty(9.2.15.v20160210)
>  
>  
> Debug Log in knox gateway.log
>  
> 2016-10-12 09:51:49,735 DEBUG hadoop.gateway 
> (GatewayFilter.java:doFilter(116)) - Received request: GET /webhdfs/v1/
> 2016-10-12 09:51:49,740 DEBUG hadoop.gateway 
> (KnoxLdapRealm.java:getUserDn(673)) - Searching from 
> OU=someOU,DC=somedomain,DC=de where 
> (&(objectclass=person)(sAMAccountName=validuser)) scope subtree
> 2016-10-12 09:51:49,745 INFO  hadoop.gateway 
> (KnoxLdapRealm.java:getUserDn(679)) - Computed userDn: 
> CN=validuser,OU=Users,OU=someOU,DC=somedomain,DC=de using ldapSearch for 
> principal: validuser
> 2016-10-12 09:51:49,749 DEBUG hadoop.gateway 
> (UrlRewriteProcessor.java:rewrite(166)) - Rewrote URL: 
> https://utilitynode:8443/gateway/default/webhdfs/v1/?OP=LISTSTATUS, 
> direction: IN via explicit rule: WEBHDFS/webhdfs/inbound/namenode/root to 
> URL: https://utilitynode.somedomain.de:50470/webhdfs/v1/?OP=LISTSTATUS
> 2016-10-12 09:51:49,749 DEBUG hadoop.gateway 
> (DefaultDispatch.java:executeOutboundRequest(120)) - Dispatch request: GET 
> https://utilitynode.somedomain.de:50470/webhdfs/v1/?OP=LISTSTATUS&doAs=validuser
> 2016-10-12 09:51:49,781 WARN  auth.HttpAuthenticator 
> (HttpAuthenticator.java:generateAuthResponse(207)) - NEGOTIATE authentication 
> error: No valid credentials provided (Mechanism level: No valid credentials 
> provided (Mechanism level: Server not found in Kerberos database (7)))
> 2016-10-12 09:51:49,782 DEBUG hadoop.gateway 
> (DefaultDispatch.java:executeOutboundRequest(133)) - Dispatch response 
> status: 401
> 2016-10-12 09:51:49,783 DEBUG hadoop.gateway 
> (DefaultDispatch.java:getInboundResponseContentType(202)) - Using explicit 
> character set ISO-8859-1 for entity of type text/html
> 2016-10-12 09:51:49,783 DEBUG hadoop.gateway 
> (DefaultDispatch.java:getInboundResponseContentType(210)) - Inbound response 
> entity content type: text/html; charset=iso-8859-1
>  
>  
> Log in knox gateway.out
>  
> Found ticket for knox/utilitynode.somedomain...@somedomain.de to go to 
> krbtgt/somedomain...@somedomain.de expiring on Wed Oct 12 19:53:51 CEST 2016
> Entered Krb5Context.initSecContext with state=STATE_NEW
> Service ticket not found in the subject
> >>> Credentials acquireServiceCreds: same realm
> default etypes for default_tgs_enctypes: 18.
> >>> CksumType: sun.security.krb5.internal.crypto.RsaMd5CksumType
> >>> EType: sun.security.krb5.internal.crypto.Aes256CtsHmacSha1EType
> getKDCFromDNS using UDP
> >>> KrbKdcReq send: kdc=domaincontroller.somedomain.de. TCP:88

[jira] [Created] (KNOX-762) Remove dependency on httpcomponents httpclient 4.5.2

[Larry McCay (JIRA)]

Larry McCay created KNOX-762:


 Summary: Remove dependency on httpcomponents httpclient 4.5.2
 Key: KNOX-762
 URL: https://issues.apache.org/jira/browse/KNOX-762
 Project: Apache Knox
  Issue Type: Bug
  Components: Server
Reporter: Larry McCay
Assignee: Larry McCay
 Fix For: 0.10.0


Reported by Benjamin Ruland:
 
I am experiencing problems with Knox while using WebHDFS in a cluster with 
Kerberos and SSL.
The KDC is an Microsoft AD 2012. Kerberos-Encryption is set to AES256. Knox is 
connected to AD via LDAP sync (this is working fine for other Knox services).
I am running HDP 2.5 with Knox 0.9.0
 
In general, the cluster runs fine. WebHDFS using SPNEGO is working.
 
But when accessing WebHDFS over Knox, I get an 401 error and some strange logs.
I suspect that Knox is trying to get a ticket for a HTTPS/namenode@REALM 
principal, which does not exist. Although running SSL, all principals for 
SPNEGO are HTTP/...
 
I this a Knox Bug or is this a misconfiguration at some point?
 
It would be great, if someone has advice.
 
Best regards,
Benjamin
 
 
 
 
 
The used command is:
 
[root@utilitynode ~]# curl -ik -u validuser 
"https://utilitynode:8443/gateway/default/webhdfs/v1/?OP=LISTSTATUS";
Enter host password for user 'validuser':
HTTP/1.1 401 Unauthorized
Date: Wed, 12 Oct 2016 07:47:41 GMT
Set-Cookie: rememberMe=deleteMe; Path=/gateway/default; Max-Age=0; 
Expires=Tue,11-Oct-2016 07:47:41 GMT
WWW-Authenticate: BASIC realm="application"
Content-Length: 0
Server: Jetty(9.2.15.v20160210)
 
 
Debug Log in knox gateway.log
 
2016-10-12 09:51:49,735 DEBUG hadoop.gateway (GatewayFilter.java:doFilter(116)) 
- Received request: GET /webhdfs/v1/
2016-10-12 09:51:49,740 DEBUG hadoop.gateway 
(KnoxLdapRealm.java:getUserDn(673)) - Searching from 
OU=someOU,DC=somedomain,DC=de where 
(&(objectclass=person)(sAMAccountName=validuser)) scope subtree
2016-10-12 09:51:49,745 INFO  hadoop.gateway 
(KnoxLdapRealm.java:getUserDn(679)) - Computed userDn: 
CN=validuser,OU=Users,OU=someOU,DC=somedomain,DC=de using ldapSearch for 
principal: validuser
2016-10-12 09:51:49,749 DEBUG hadoop.gateway 
(UrlRewriteProcessor.java:rewrite(166)) - Rewrote URL: 
https://utilitynode:8443/gateway/default/webhdfs/v1/?OP=LISTSTATUS, direction: 
IN via explicit rule: WEBHDFS/webhdfs/inbound/namenode/root to URL: 
https://utilitynode.somedomain.de:50470/webhdfs/v1/?OP=LISTSTATUS
2016-10-12 09:51:49,749 DEBUG hadoop.gateway 
(DefaultDispatch.java:executeOutboundRequest(120)) - Dispatch request: GET 
https://utilitynode.somedomain.de:50470/webhdfs/v1/?OP=LISTSTATUS&doAs=validuser
2016-10-12 09:51:49,781 WARN  auth.HttpAuthenticator 
(HttpAuthenticator.java:generateAuthResponse(207)) - NEGOTIATE authentication 
error: No valid credentials provided (Mechanism level: No valid credentials 
provided (Mechanism level: Server not found in Kerberos database (7)))
2016-10-12 09:51:49,782 DEBUG hadoop.gateway 
(DefaultDispatch.java:executeOutboundRequest(133)) - Dispatch response status: 
401
2016-10-12 09:51:49,783 DEBUG hadoop.gateway 
(DefaultDispatch.java:getInboundResponseContentType(202)) - Using explicit 
character set ISO-8859-1 for entity of type text/html
2016-10-12 09:51:49,783 DEBUG hadoop.gateway 
(DefaultDispatch.java:getInboundResponseContentType(210)) - Inbound response 
entity content type: text/html; charset=iso-8859-1
 
 
Log in knox gateway.out
 
Found ticket for knox/utilitynode.somedomain...@somedomain.de to go to 
krbtgt/somedomain...@somedomain.de expiring on Wed Oct 12 19:53:51 CEST 2016
Entered Krb5Context.initSecContext with state=STATE_NEW
Service ticket not found in the subject
>>> Credentials acquireServiceCreds: same realm
default etypes for default_tgs_enctypes: 18.
>>> CksumType: sun.security.krb5.internal.crypto.RsaMd5CksumType
>>> EType: sun.security.krb5.internal.crypto.Aes256CtsHmacSha1EType
getKDCFromDNS using UDP
>>> KrbKdcReq send: kdc=domaincontroller.somedomain.de. TCP:88, timeout=3, 
>>> number of retries =3, #bytes=1661
>>> KDCCommunication: kdc=domaincontroller.somedomain.de. TCP:88, 
>>> timeout=3,Attempt =1, #bytes=1661
>>>DEBUG: TCPClient reading 127 bytes
>>> KrbKdcReq send: #bytes read=127
>>> KdcAccessibility: remove domaincontroller.somedomain.de.:88
>>> KDCRep: init() encoding tag is 126 req type is 13
>>>KRBError:
 sTime is Wed Oct 12 09:53:51 CEST 2016 1476258831000
 suSec is 8354   suSec is 8354
 error code is 7
 error Message is Server not found in Kerberos database
 sname is HTTPS/namenode.somedomain...@somedomain.de
 msgType is 30
 
 
Extracts from topology config:
 

 
  
 

  authentication
  ShiroProvider
  true
 

 

  identity-assertion
  Default
  true

 

  authorization
  XASecurePDPKnox
  true

 

  ha
  HaProvider
  true
 

[jira] [Commented] (KNOX-762) Remove dependency on httpcomponents httpclient 4.5.2

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KNOX-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595591#comment-15595591
 ] 

ASF subversion and git services commented on KNOX-762:
--

Commit 390fd1cc1cb4cc6914a54b535bbf8c85031b86b3 in knox's branch 
refs/heads/v0.9.0 from [~lmccay]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=390fd1c ]

KNOX-762 - Remove dependency on httpcomponents httpclient 4.5.2


> Remove dependency on httpcomponents httpclient 4.5.2
> 
>
> Key: KNOX-762
> URL: https://issues.apache.org/jira/browse/KNOX-762
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Reporter: Larry McCay
>Assignee: Larry McCay
> Fix For: 0.10.0
>
>
> Reported by Benjamin Ruland:
>  
> I am experiencing problems with Knox while using WebHDFS in a cluster with 
> Kerberos and SSL.
> The KDC is an Microsoft AD 2012. Kerberos-Encryption is set to AES256. Knox 
> is connected to AD via LDAP sync (this is working fine for other Knox 
> services).
> I am running HDP 2.5 with Knox 0.9.0
>  
> In general, the cluster runs fine. WebHDFS using SPNEGO is working.
>  
> But when accessing WebHDFS over Knox, I get an 401 error and some strange 
> logs.
> I suspect that Knox is trying to get a ticket for a HTTPS/namenode@REALM 
> principal, which does not exist. Although running SSL, all principals for 
> SPNEGO are HTTP/...
>  
> I this a Knox Bug or is this a misconfiguration at some point?
>  
> It would be great, if someone has advice.
>  
> Best regards,
> Benjamin
>  
>  
>  
>  
>  
> The used command is:
>  
> [root@utilitynode ~]# curl -ik -u validuser 
> "https://utilitynode:8443/gateway/default/webhdfs/v1/?OP=LISTSTATUS";
> Enter host password for user 'validuser':
> HTTP/1.1 401 Unauthorized
> Date: Wed, 12 Oct 2016 07:47:41 GMT
> Set-Cookie: rememberMe=deleteMe; Path=/gateway/default; Max-Age=0; 
> Expires=Tue,11-Oct-2016 07:47:41 GMT
> WWW-Authenticate: BASIC realm="application"
> Content-Length: 0
> Server: Jetty(9.2.15.v20160210)
>  
>  
> Debug Log in knox gateway.log
>  
> 2016-10-12 09:51:49,735 DEBUG hadoop.gateway 
> (GatewayFilter.java:doFilter(116)) - Received request: GET /webhdfs/v1/
> 2016-10-12 09:51:49,740 DEBUG hadoop.gateway 
> (KnoxLdapRealm.java:getUserDn(673)) - Searching from 
> OU=someOU,DC=somedomain,DC=de where 
> (&(objectclass=person)(sAMAccountName=validuser)) scope subtree
> 2016-10-12 09:51:49,745 INFO  hadoop.gateway 
> (KnoxLdapRealm.java:getUserDn(679)) - Computed userDn: 
> CN=validuser,OU=Users,OU=someOU,DC=somedomain,DC=de using ldapSearch for 
> principal: validuser
> 2016-10-12 09:51:49,749 DEBUG hadoop.gateway 
> (UrlRewriteProcessor.java:rewrite(166)) - Rewrote URL: 
> https://utilitynode:8443/gateway/default/webhdfs/v1/?OP=LISTSTATUS, 
> direction: IN via explicit rule: WEBHDFS/webhdfs/inbound/namenode/root to 
> URL: https://utilitynode.somedomain.de:50470/webhdfs/v1/?OP=LISTSTATUS
> 2016-10-12 09:51:49,749 DEBUG hadoop.gateway 
> (DefaultDispatch.java:executeOutboundRequest(120)) - Dispatch request: GET 
> https://utilitynode.somedomain.de:50470/webhdfs/v1/?OP=LISTSTATUS&doAs=validuser
> 2016-10-12 09:51:49,781 WARN  auth.HttpAuthenticator 
> (HttpAuthenticator.java:generateAuthResponse(207)) - NEGOTIATE authentication 
> error: No valid credentials provided (Mechanism level: No valid credentials 
> provided (Mechanism level: Server not found in Kerberos database (7)))
> 2016-10-12 09:51:49,782 DEBUG hadoop.gateway 
> (DefaultDispatch.java:executeOutboundRequest(133)) - Dispatch response 
> status: 401
> 2016-10-12 09:51:49,783 DEBUG hadoop.gateway 
> (DefaultDispatch.java:getInboundResponseContentType(202)) - Using explicit 
> character set ISO-8859-1 for entity of type text/html
> 2016-10-12 09:51:49,783 DEBUG hadoop.gateway 
> (DefaultDispatch.java:getInboundResponseContentType(210)) - Inbound response 
> entity content type: text/html; charset=iso-8859-1
>  
>  
> Log in knox gateway.out
>  
> Found ticket for knox/utilitynode.somedomain...@somedomain.de to go to 
> krbtgt/somedomain...@somedomain.de expiring on Wed Oct 12 19:53:51 CEST 2016
> Entered Krb5Context.initSecContext with state=STATE_NEW
> Service ticket not found in the subject
> >>> Credentials acquireServiceCreds: same realm
> default etypes for default_tgs_enctypes: 18.
> >>> CksumType: sun.security.krb5.internal.crypto.RsaMd5CksumType
> >>> EType: sun.security.krb5.internal.crypto.Aes256CtsHmacSha1EType
> getKDCFromDNS using UDP
> >>> KrbKdcReq send: kdc=domaincontroller.somedomain.de. TCP:88, 
> >>> timeout=3, number of retries =3, #bytes=1661
> >>> KDCCommunication: kdc=domaincontroller.somedomain.de. TCP:88, 
> >>> timeout=3,Attempt =1, #bytes=1661
> >>>DEBUG: TCPClient reading 127 bytes
> >>> KrbKdcReq send: #bytes read=12

[jira] [Commented] (KNOX-762) Remove dependency on httpcomponents httpclient 4.5.2

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/KNOX-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595595#comment-15595595
 ] 

ASF subversion and git services commented on KNOX-762:
--

Commit 0ff2c9edac99f7b16b9361d15841f8be3741ada5 in knox's branch 
refs/heads/master from [~lmccay]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=0ff2c9e ]

KNOX-762 - Remove dependency on httpcomponents httpclient 4.5.2


> Remove dependency on httpcomponents httpclient 4.5.2
> 
>
> Key: KNOX-762
> URL: https://issues.apache.org/jira/browse/KNOX-762
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Reporter: Larry McCay
>Assignee: Larry McCay
> Fix For: 0.10.0
>
>
> Reported by Benjamin Ruland:
>  
> I am experiencing problems with Knox while using WebHDFS in a cluster with 
> Kerberos and SSL.
> The KDC is an Microsoft AD 2012. Kerberos-Encryption is set to AES256. Knox 
> is connected to AD via LDAP sync (this is working fine for other Knox 
> services).
> I am running HDP 2.5 with Knox 0.9.0
>  
> In general, the cluster runs fine. WebHDFS using SPNEGO is working.
>  
> But when accessing WebHDFS over Knox, I get an 401 error and some strange 
> logs.
> I suspect that Knox is trying to get a ticket for a HTTPS/namenode@REALM 
> principal, which does not exist. Although running SSL, all principals for 
> SPNEGO are HTTP/...
>  
> I this a Knox Bug or is this a misconfiguration at some point?
>  
> It would be great, if someone has advice.
>  
> Best regards,
> Benjamin
>  
>  
>  
>  
>  
> The used command is:
>  
> [root@utilitynode ~]# curl -ik -u validuser 
> "https://utilitynode:8443/gateway/default/webhdfs/v1/?OP=LISTSTATUS";
> Enter host password for user 'validuser':
> HTTP/1.1 401 Unauthorized
> Date: Wed, 12 Oct 2016 07:47:41 GMT
> Set-Cookie: rememberMe=deleteMe; Path=/gateway/default; Max-Age=0; 
> Expires=Tue,11-Oct-2016 07:47:41 GMT
> WWW-Authenticate: BASIC realm="application"
> Content-Length: 0
> Server: Jetty(9.2.15.v20160210)
>  
>  
> Debug Log in knox gateway.log
>  
> 2016-10-12 09:51:49,735 DEBUG hadoop.gateway 
> (GatewayFilter.java:doFilter(116)) - Received request: GET /webhdfs/v1/
> 2016-10-12 09:51:49,740 DEBUG hadoop.gateway 
> (KnoxLdapRealm.java:getUserDn(673)) - Searching from 
> OU=someOU,DC=somedomain,DC=de where 
> (&(objectclass=person)(sAMAccountName=validuser)) scope subtree
> 2016-10-12 09:51:49,745 INFO  hadoop.gateway 
> (KnoxLdapRealm.java:getUserDn(679)) - Computed userDn: 
> CN=validuser,OU=Users,OU=someOU,DC=somedomain,DC=de using ldapSearch for 
> principal: validuser
> 2016-10-12 09:51:49,749 DEBUG hadoop.gateway 
> (UrlRewriteProcessor.java:rewrite(166)) - Rewrote URL: 
> https://utilitynode:8443/gateway/default/webhdfs/v1/?OP=LISTSTATUS, 
> direction: IN via explicit rule: WEBHDFS/webhdfs/inbound/namenode/root to 
> URL: https://utilitynode.somedomain.de:50470/webhdfs/v1/?OP=LISTSTATUS
> 2016-10-12 09:51:49,749 DEBUG hadoop.gateway 
> (DefaultDispatch.java:executeOutboundRequest(120)) - Dispatch request: GET 
> https://utilitynode.somedomain.de:50470/webhdfs/v1/?OP=LISTSTATUS&doAs=validuser
> 2016-10-12 09:51:49,781 WARN  auth.HttpAuthenticator 
> (HttpAuthenticator.java:generateAuthResponse(207)) - NEGOTIATE authentication 
> error: No valid credentials provided (Mechanism level: No valid credentials 
> provided (Mechanism level: Server not found in Kerberos database (7)))
> 2016-10-12 09:51:49,782 DEBUG hadoop.gateway 
> (DefaultDispatch.java:executeOutboundRequest(133)) - Dispatch response 
> status: 401
> 2016-10-12 09:51:49,783 DEBUG hadoop.gateway 
> (DefaultDispatch.java:getInboundResponseContentType(202)) - Using explicit 
> character set ISO-8859-1 for entity of type text/html
> 2016-10-12 09:51:49,783 DEBUG hadoop.gateway 
> (DefaultDispatch.java:getInboundResponseContentType(210)) - Inbound response 
> entity content type: text/html; charset=iso-8859-1
>  
>  
> Log in knox gateway.out
>  
> Found ticket for knox/utilitynode.somedomain...@somedomain.de to go to 
> krbtgt/somedomain...@somedomain.de expiring on Wed Oct 12 19:53:51 CEST 2016
> Entered Krb5Context.initSecContext with state=STATE_NEW
> Service ticket not found in the subject
> >>> Credentials acquireServiceCreds: same realm
> default etypes for default_tgs_enctypes: 18.
> >>> CksumType: sun.security.krb5.internal.crypto.RsaMd5CksumType
> >>> EType: sun.security.krb5.internal.crypto.Aes256CtsHmacSha1EType
> getKDCFromDNS using UDP
> >>> KrbKdcReq send: kdc=domaincontroller.somedomain.de. TCP:88, 
> >>> timeout=3, number of retries =3, #bytes=1661
> >>> KDCCommunication: kdc=domaincontroller.somedomain.de. TCP:88, 
> >>> timeout=3,Attempt =1, #bytes=1661
> >>>DEBUG: TCPClient reading 127 bytes
> >>> KrbKdcReq send: #bytes read=12

[jira] [Resolved] (KNOX-762) Remove dependency on httpcomponents httpclient 4.5.2

[Larry McCay (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KNOX-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay resolved KNOX-762.
--
Resolution: Fixed

> Remove dependency on httpcomponents httpclient 4.5.2
> 
>
> Key: KNOX-762
> URL: https://issues.apache.org/jira/browse/KNOX-762
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Reporter: Larry McCay
>Assignee: Larry McCay
> Fix For: 0.10.0
>
>
> Reported by Benjamin Ruland:
>  
> I am experiencing problems with Knox while using WebHDFS in a cluster with 
> Kerberos and SSL.
> The KDC is an Microsoft AD 2012. Kerberos-Encryption is set to AES256. Knox 
> is connected to AD via LDAP sync (this is working fine for other Knox 
> services).
> I am running HDP 2.5 with Knox 0.9.0
>  
> In general, the cluster runs fine. WebHDFS using SPNEGO is working.
>  
> But when accessing WebHDFS over Knox, I get an 401 error and some strange 
> logs.
> I suspect that Knox is trying to get a ticket for a HTTPS/namenode@REALM 
> principal, which does not exist. Although running SSL, all principals for 
> SPNEGO are HTTP/...
>  
> I this a Knox Bug or is this a misconfiguration at some point?
>  
> It would be great, if someone has advice.
>  
> Best regards,
> Benjamin
>  
>  
>  
>  
>  
> The used command is:
>  
> [root@utilitynode ~]# curl -ik -u validuser 
> "https://utilitynode:8443/gateway/default/webhdfs/v1/?OP=LISTSTATUS";
> Enter host password for user 'validuser':
> HTTP/1.1 401 Unauthorized
> Date: Wed, 12 Oct 2016 07:47:41 GMT
> Set-Cookie: rememberMe=deleteMe; Path=/gateway/default; Max-Age=0; 
> Expires=Tue,11-Oct-2016 07:47:41 GMT
> WWW-Authenticate: BASIC realm="application"
> Content-Length: 0
> Server: Jetty(9.2.15.v20160210)
>  
>  
> Debug Log in knox gateway.log
>  
> 2016-10-12 09:51:49,735 DEBUG hadoop.gateway 
> (GatewayFilter.java:doFilter(116)) - Received request: GET /webhdfs/v1/
> 2016-10-12 09:51:49,740 DEBUG hadoop.gateway 
> (KnoxLdapRealm.java:getUserDn(673)) - Searching from 
> OU=someOU,DC=somedomain,DC=de where 
> (&(objectclass=person)(sAMAccountName=validuser)) scope subtree
> 2016-10-12 09:51:49,745 INFO  hadoop.gateway 
> (KnoxLdapRealm.java:getUserDn(679)) - Computed userDn: 
> CN=validuser,OU=Users,OU=someOU,DC=somedomain,DC=de using ldapSearch for 
> principal: validuser
> 2016-10-12 09:51:49,749 DEBUG hadoop.gateway 
> (UrlRewriteProcessor.java:rewrite(166)) - Rewrote URL: 
> https://utilitynode:8443/gateway/default/webhdfs/v1/?OP=LISTSTATUS, 
> direction: IN via explicit rule: WEBHDFS/webhdfs/inbound/namenode/root to 
> URL: https://utilitynode.somedomain.de:50470/webhdfs/v1/?OP=LISTSTATUS
> 2016-10-12 09:51:49,749 DEBUG hadoop.gateway 
> (DefaultDispatch.java:executeOutboundRequest(120)) - Dispatch request: GET 
> https://utilitynode.somedomain.de:50470/webhdfs/v1/?OP=LISTSTATUS&doAs=validuser
> 2016-10-12 09:51:49,781 WARN  auth.HttpAuthenticator 
> (HttpAuthenticator.java:generateAuthResponse(207)) - NEGOTIATE authentication 
> error: No valid credentials provided (Mechanism level: No valid credentials 
> provided (Mechanism level: Server not found in Kerberos database (7)))
> 2016-10-12 09:51:49,782 DEBUG hadoop.gateway 
> (DefaultDispatch.java:executeOutboundRequest(133)) - Dispatch response 
> status: 401
> 2016-10-12 09:51:49,783 DEBUG hadoop.gateway 
> (DefaultDispatch.java:getInboundResponseContentType(202)) - Using explicit 
> character set ISO-8859-1 for entity of type text/html
> 2016-10-12 09:51:49,783 DEBUG hadoop.gateway 
> (DefaultDispatch.java:getInboundResponseContentType(210)) - Inbound response 
> entity content type: text/html; charset=iso-8859-1
>  
>  
> Log in knox gateway.out
>  
> Found ticket for knox/utilitynode.somedomain...@somedomain.de to go to 
> krbtgt/somedomain...@somedomain.de expiring on Wed Oct 12 19:53:51 CEST 2016
> Entered Krb5Context.initSecContext with state=STATE_NEW
> Service ticket not found in the subject
> >>> Credentials acquireServiceCreds: same realm
> default etypes for default_tgs_enctypes: 18.
> >>> CksumType: sun.security.krb5.internal.crypto.RsaMd5CksumType
> >>> EType: sun.security.krb5.internal.crypto.Aes256CtsHmacSha1EType
> getKDCFromDNS using UDP
> >>> KrbKdcReq send: kdc=domaincontroller.somedomain.de. TCP:88, 
> >>> timeout=3, number of retries =3, #bytes=1661
> >>> KDCCommunication: kdc=domaincontroller.somedomain.de. TCP:88, 
> >>> timeout=3,Attempt =1, #bytes=1661
> >>>DEBUG: TCPClient reading 127 bytes
> >>> KrbKdcReq send: #bytes read=127
> >>> KdcAccessibility: remove domaincontroller.somedomain.de.:88
> >>> KDCRep: init() encoding tag is 126 req type is 13
> >>>KRBError:
>  sTime is Wed Oct 12 09:53:51 CEST 2016 1476258831000
>  suSec is 8354   suSec is 8354
>  error code is 7
>  error Message is Serve

[jira] [Commented] (KNOX-762) Remove dependency on httpcomponents httpclient 4.5.2

[Larry McCay (JIRA)]

[ 
https://issues.apache.org/jira/browse/KNOX-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595606#comment-15595606
 ] 

Larry McCay commented on KNOX-762:
--

I have committed a fix to downgrade to 4.5.1.
We need to track httpcomponents httpclient for a new release that includes the 
fix for this issue.

> Remove dependency on httpcomponents httpclient 4.5.2
> 
>
> Key: KNOX-762
> URL: https://issues.apache.org/jira/browse/KNOX-762
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Reporter: Larry McCay
>Assignee: Larry McCay
> Fix For: 0.10.0
>
>
> Reported by Benjamin Ruland:
>  
> I am experiencing problems with Knox while using WebHDFS in a cluster with 
> Kerberos and SSL.
> The KDC is an Microsoft AD 2012. Kerberos-Encryption is set to AES256. Knox 
> is connected to AD via LDAP sync (this is working fine for other Knox 
> services).
> I am running HDP 2.5 with Knox 0.9.0
>  
> In general, the cluster runs fine. WebHDFS using SPNEGO is working.
>  
> But when accessing WebHDFS over Knox, I get an 401 error and some strange 
> logs.
> I suspect that Knox is trying to get a ticket for a HTTPS/namenode@REALM 
> principal, which does not exist. Although running SSL, all principals for 
> SPNEGO are HTTP/...
>  
> I this a Knox Bug or is this a misconfiguration at some point?
>  
> It would be great, if someone has advice.
>  
> Best regards,
> Benjamin
>  
>  
>  
>  
>  
> The used command is:
>  
> [root@utilitynode ~]# curl -ik -u validuser 
> "https://utilitynode:8443/gateway/default/webhdfs/v1/?OP=LISTSTATUS";
> Enter host password for user 'validuser':
> HTTP/1.1 401 Unauthorized
> Date: Wed, 12 Oct 2016 07:47:41 GMT
> Set-Cookie: rememberMe=deleteMe; Path=/gateway/default; Max-Age=0; 
> Expires=Tue,11-Oct-2016 07:47:41 GMT
> WWW-Authenticate: BASIC realm="application"
> Content-Length: 0
> Server: Jetty(9.2.15.v20160210)
>  
>  
> Debug Log in knox gateway.log
>  
> 2016-10-12 09:51:49,735 DEBUG hadoop.gateway 
> (GatewayFilter.java:doFilter(116)) - Received request: GET /webhdfs/v1/
> 2016-10-12 09:51:49,740 DEBUG hadoop.gateway 
> (KnoxLdapRealm.java:getUserDn(673)) - Searching from 
> OU=someOU,DC=somedomain,DC=de where 
> (&(objectclass=person)(sAMAccountName=validuser)) scope subtree
> 2016-10-12 09:51:49,745 INFO  hadoop.gateway 
> (KnoxLdapRealm.java:getUserDn(679)) - Computed userDn: 
> CN=validuser,OU=Users,OU=someOU,DC=somedomain,DC=de using ldapSearch for 
> principal: validuser
> 2016-10-12 09:51:49,749 DEBUG hadoop.gateway 
> (UrlRewriteProcessor.java:rewrite(166)) - Rewrote URL: 
> https://utilitynode:8443/gateway/default/webhdfs/v1/?OP=LISTSTATUS, 
> direction: IN via explicit rule: WEBHDFS/webhdfs/inbound/namenode/root to 
> URL: https://utilitynode.somedomain.de:50470/webhdfs/v1/?OP=LISTSTATUS
> 2016-10-12 09:51:49,749 DEBUG hadoop.gateway 
> (DefaultDispatch.java:executeOutboundRequest(120)) - Dispatch request: GET 
> https://utilitynode.somedomain.de:50470/webhdfs/v1/?OP=LISTSTATUS&doAs=validuser
> 2016-10-12 09:51:49,781 WARN  auth.HttpAuthenticator 
> (HttpAuthenticator.java:generateAuthResponse(207)) - NEGOTIATE authentication 
> error: No valid credentials provided (Mechanism level: No valid credentials 
> provided (Mechanism level: Server not found in Kerberos database (7)))
> 2016-10-12 09:51:49,782 DEBUG hadoop.gateway 
> (DefaultDispatch.java:executeOutboundRequest(133)) - Dispatch response 
> status: 401
> 2016-10-12 09:51:49,783 DEBUG hadoop.gateway 
> (DefaultDispatch.java:getInboundResponseContentType(202)) - Using explicit 
> character set ISO-8859-1 for entity of type text/html
> 2016-10-12 09:51:49,783 DEBUG hadoop.gateway 
> (DefaultDispatch.java:getInboundResponseContentType(210)) - Inbound response 
> entity content type: text/html; charset=iso-8859-1
>  
>  
> Log in knox gateway.out
>  
> Found ticket for knox/utilitynode.somedomain...@somedomain.de to go to 
> krbtgt/somedomain...@somedomain.de expiring on Wed Oct 12 19:53:51 CEST 2016
> Entered Krb5Context.initSecContext with state=STATE_NEW
> Service ticket not found in the subject
> >>> Credentials acquireServiceCreds: same realm
> default etypes for default_tgs_enctypes: 18.
> >>> CksumType: sun.security.krb5.internal.crypto.RsaMd5CksumType
> >>> EType: sun.security.krb5.internal.crypto.Aes256CtsHmacSha1EType
> getKDCFromDNS using UDP
> >>> KrbKdcReq send: kdc=domaincontroller.somedomain.de. TCP:88, 
> >>> timeout=3, number of retries =3, #bytes=1661
> >>> KDCCommunication: kdc=domaincontroller.somedomain.de. TCP:88, 
> >>> timeout=3,Attempt =1, #bytes=1661
> >>>DEBUG: TCPClient reading 127 bytes
> >>> KrbKdcReq send: #bytes read=127
> >>> KdcAccessibility: remove domaincontroller.somedomain.de.:88
> >>> KDCRep: init() encoding tag is 126 req type is 13

[DISCUSS] Need for 0.9.2 Release

[larry mccay]

All -

There have been a number of bug fixes on the 0.9.0 branch in the event that
we may need to cut an 0.9.2 release for a serious enough issue.

Off the top of my head, I know that we have LDAP response paging, Location
header encoding and just now I had to downgrade httpclient to 4.5.1 to fix
an issue with SPNEGO+SSL.

Since 0.9.1 will not work for secure clusters with SSL enabled, I believe
that it warrants an 0.9.2 release.

Thoughts?

thanks.

--larry

Build failed in Jenkins: Knox-master-patch-scan #23655

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/apache/knox.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://github.com/apache/knox.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.plugins.git.GitException: Command "git -c core.askpass=true 
fetch --tags --progress https://github.com/apache/knox.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: fatal: unable to access 'https://github.com/apache/knox.git/': Could 
not resolve host: github.com

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1723)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1459)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:332)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H1(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:781)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor729.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at com.sun.proxy.$Proxy149.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797)
... 11 more
ERROR: null
Retrying after 10 seconds
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/apache/knox.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://github.com/apache/knox.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)

Re: [DISCUSS] Need for 0.9.2 Release

[Sandeep More]

Hello Larry,

I think that's a good idea the only thing is we are closer to cutting 0.10
release.
If 0.10 is not drastically different than 0.9.X one might just jump to 0.10
than going to 0.9.2, I think.

Best,
Sandeep


On Fri, Oct 21, 2016 at 12:48 PM, larry mccay  wrote:

> All -
>
> There have been a number of bug fixes on the 0.9.0 branch in the event that
> we may need to cut an 0.9.2 release for a serious enough issue.
>
> Off the top of my head, I know that we have LDAP response paging, Location
> header encoding and just now I had to downgrade httpclient to 4.5.1 to fix
> an issue with SPNEGO+SSL.
>
> Since 0.9.1 will not work for secure clusters with SSL enabled, I believe
> that it warrants an 0.9.2 release.
>
> Thoughts?
>
> thanks.
>
> --larry
>

Build failed in Jenkins: Knox-master-patch-scan #23656

[Apache Jenkins Server]

See 

--
Started by timer
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/apache/knox.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://github.com/apache/knox.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.plugins.git.GitException: Command "git -c core.askpass=true 
fetch --tags --progress https://github.com/apache/knox.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: fatal: unable to access 'https://github.com/apache/knox.git/': Could 
not resolve host: github.com

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1723)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1459)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:332)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H1(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:781)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor729.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at com.sun.proxy.$Proxy149.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797)
... 11 more
ERROR: null
Retrying after 10 seconds
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/apache/knox.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://github.com/apache/knox.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractPr

Build failed in Jenkins: Knox-master-patch-scan #23657

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/apache/knox.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://github.com/apache/knox.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.plugins.git.GitException: Command "git -c core.askpass=true 
fetch --tags --progress https://github.com/apache/knox.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: fatal: unable to access 'https://github.com/apache/knox.git/': Could 
not resolve host: github.com

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1723)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1459)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:332)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H1(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:781)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor729.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at com.sun.proxy.$Proxy149.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797)
... 11 more
ERROR: null
Retrying after 10 seconds
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/apache/knox.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://github.com/apache/knox.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)

Build failed in Jenkins: Knox-master-patch-scan #23658

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/apache/knox.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://github.com/apache/knox.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.plugins.git.GitException: Command "git -c core.askpass=true 
fetch --tags --progress https://github.com/apache/knox.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: fatal: unable to access 'https://github.com/apache/knox.git/': Could 
not resolve host: github.com

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1723)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1459)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:332)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H1(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:781)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor729.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at com.sun.proxy.$Proxy149.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797)
... 11 more
ERROR: null
Retrying after 10 seconds
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/apache/knox.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://github.com/apache/knox.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)

Build failed in Jenkins: Knox-master-patch-scan #23659

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/apache/knox.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://github.com/apache/knox.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.plugins.git.GitException: Command "git -c core.askpass=true 
fetch --tags --progress https://github.com/apache/knox.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: fatal: unable to access 'https://github.com/apache/knox.git/': Could 
not resolve host: github.com

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1723)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1459)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:332)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H1(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:781)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor729.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at com.sun.proxy.$Proxy149.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797)
... 11 more
ERROR: null
Retrying after 10 seconds
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/apache/knox.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://github.com/apache/knox.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)

Build failed in Jenkins: Knox-master-patch-scan #23660

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/apache/knox.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://github.com/apache/knox.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.plugins.git.GitException: Command "git -c core.askpass=true 
fetch --tags --progress https://github.com/apache/knox.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: fatal: unable to access 'https://github.com/apache/knox.git/': Could 
not resolve host: github.com

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1723)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1459)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:332)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H1(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:781)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor729.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at com.sun.proxy.$Proxy149.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797)
... 11 more
ERROR: null
Retrying after 10 seconds
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/apache/knox.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://github.com/apache/knox.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)

Build failed in Jenkins: Knox-master-patch-scan #23661

[Apache Jenkins Server]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/apache/knox.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://github.com/apache/knox.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.plugins.git.GitException: Command "git -c core.askpass=true 
fetch --tags --progress https://github.com/apache/knox.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: fatal: unable to access 'https://github.com/apache/knox.git/': Could 
not resolve host: github.com

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1723)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1459)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:332)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H1(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:781)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor729.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at com.sun.proxy.$Proxy149.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797)
... 11 more
ERROR: null
Retrying after 10 seconds
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://github.com/apache/knox.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://github.com/apache/knox.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)

Jenkins build is back to normal : Knox-master-patch-scan #23662

[Apache Jenkins Server]

See 

Re: [DISCUSS] Need for 0.9.2 Release

[larry mccay]

Hi Sandeep -

That is a good point

While 0.10.0 is feature bearing, we may be able to defer more of the
outstanding tasks to an 0.10.1 or 0.11.0 and keep 0.10.0 as close to bug
fixes as possible.

I will have a look at the changes that have already made it in and see if
we can make that make sense.

thanks,

--larry

On Fri, Oct 21, 2016 at 2:05 PM, Sandeep More  wrote:

> Hello Larry,
>
> I think that's a good idea the only thing is we are closer to cutting 0.10
> release.
> If 0.10 is not drastically different than 0.9.X one might just jump to 0.10
> than going to 0.9.2, I think.
>
> Best,
> Sandeep
>
>
> On Fri, Oct 21, 2016 at 12:48 PM, larry mccay  wrote:
>
> > All -
> >
> > There have been a number of bug fixes on the 0.9.0 branch in the event
> that
> > we may need to cut an 0.9.2 release for a serious enough issue.
> >
> > Off the top of my head, I know that we have LDAP response paging,
> Location
> > header encoding and just now I had to downgrade httpclient to 4.5.1 to
> fix
> > an issue with SPNEGO+SSL.
> >
> > Since 0.9.1 will not work for secure clusters with SSL enabled, I believe
> > that it warrants an 0.9.2 release.
> >
> > Thoughts?
> >
> > thanks.
> >
> > --larry
> >
>

[jira] [Resolved] (KNOX-750) Change test-patch to attempt -p0 and -p1 patches before failing

[Larry McCay (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KNOX-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay resolved KNOX-750.
--
Resolution: Fixed

> Change test-patch to attempt -p0 and -p1 patches before failing
> ---
>
> Key: KNOX-750
> URL: https://issues.apache.org/jira/browse/KNOX-750
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Build
>Reporter: Larry McCay
>Assignee: Larry McCay
> Fix For: 0.10.0
>
>
> Currently scans for patches try to apply with only -p0 and fails if it 
> doesn't apply. This change will attempt with -p1 before throwing up our hands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KNOX-741) Centralize Common Provider Configuration

[Larry McCay (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KNOX-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay updated KNOX-741:
-
Fix Version/s: (was: 0.10.0)
   0.11.0

> Centralize Common Provider Configuration
> 
>
> Key: KNOX-741
> URL: https://issues.apache.org/jira/browse/KNOX-741
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Reporter: Larry McCay
> Fix For: 0.11.0
>
>
> At times, multiple topologies require the same provider configuration. This 
> is often LDAP/AD configuration that is painful to redundantly maintain and 
> can lead to inconsistencies and human error.
> By centralizing such configuration in specialized topology snippets that can 
> be imported, we can eliminate this pain and provide a much more concise 
> configuration.
> This is described in the LDAP improvements KIP-1 wiki page: 
> https://cwiki.apache.org/confluence/display/KNOX/KIP-1+LDAP+Improvements



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KNOX-461) Leverage Directory Computed Attribute for User Group Discovery

[Larry McCay (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KNOX-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay updated KNOX-461:
-
Fix Version/s: (was: 0.10.0)
   Future

> Leverage Directory Computed  Attribute for User Group Discovery
> ---
>
> Key: KNOX-461
> URL: https://issues.apache.org/jira/browse/KNOX-461
> Project: Apache Knox
>  Issue Type: Improvement
>Reporter: Dilli Arumugam
>Priority: Critical
> Fix For: Future
>
>
> Leverage Directory Computed  Attribute for User Group Discovery
> We should use computed attribute memberof supported by Active Driectory to 
> discover groups of the authenticated user. This would significantly boost 
> performance as compared we computing groups using group search.
> OpenLDAP also could be configured to return computed groups.
> However, OpenLDAP would return this attribute as memberof.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KNOX-461) Leverage Directory Computed Attribute for User Group Discovery

[Larry McCay (JIRA)]

[ 
https://issues.apache.org/jira/browse/KNOX-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596173#comment-15596173
 ] 

Larry McCay commented on KNOX-461:
--

Moving this out to Future.
We need to determine whether this usecase is accommodated by PAM module support 
before committing to doing it in a release.

> Leverage Directory Computed  Attribute for User Group Discovery
> ---
>
> Key: KNOX-461
> URL: https://issues.apache.org/jira/browse/KNOX-461
> Project: Apache Knox
>  Issue Type: Improvement
>Reporter: Dilli Arumugam
>Priority: Critical
> Fix For: Future
>
>
> Leverage Directory Computed  Attribute for User Group Discovery
> We should use computed attribute memberof supported by Active Driectory to 
> discover groups of the authenticated user. This would significantly boost 
> performance as compared we computing groups using group search.
> OpenLDAP also could be configured to return computed groups.
> However, OpenLDAP would return this attribute as memberof.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KNOX-458) Surface Config for Shiro LDAP Connection Pooling

[Larry McCay (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KNOX-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay updated KNOX-458:
-
Fix Version/s: (was: 0.10.0)
   Future

> Surface Config for Shiro LDAP Connection Pooling
> 
>
> Key: KNOX-458
> URL: https://issues.apache.org/jira/browse/KNOX-458
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: Server
>Reporter: Larry McCay
>Assignee: Larry McCay
> Fix For: Future
>
>
> The default connection pooling in Shiro provides pooling for system-users but 
> not end users. The assumption being that the JSESSIONID cookie and session 
> state can optimize away the hits to the LDAP server.
> This assumption isn't sufficient for all possible REST clients and some 
> deployments may know that they need additional connection pooling.
> Shiro does not appear to provide standard shiro.ini configuration for this 
> and we likely need to programmatically surface a configuration item for this 
> provider in order to set it properly within our realm implementation.
> Usecase described by [~acoliver].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KNOX-749) Simple Admin UI

[Larry McCay (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KNOX-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay updated KNOX-749:
-
Fix Version/s: (was: 0.10.0)
   0.11.0

> Simple Admin UI
> ---
>
> Key: KNOX-749
> URL: https://issues.apache.org/jira/browse/KNOX-749
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Reporter: Larry McCay
>Assignee: Zachary Blanco
> Fix For: 0.11.0
>
> Attachments: knox-admin-ui-001.patch
>
>
> We need to a simple UI for management/admin insights based on the Knox Admin 
> API.
> We can start with a read-only iteration and extend it in a future release.
> [~zacblanco] has expressed interest in this effort on the dev list and 
> possibly other JIRAs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KNOX-761) KnoxSSO Needs to Support Multi-tenant Usecases

[Larry McCay (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KNOX-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay updated KNOX-761:
-
Fix Version/s: (was: 0.10.0)
   0.11.0

> KnoxSSO Needs to Support Multi-tenant Usecases
> --
>
> Key: KNOX-761
> URL: https://issues.apache.org/jira/browse/KNOX-761
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Reporter: Larry McCay
>Assignee: Larry McCay
> Fix For: 0.11.0
>
>
> In a deployment that separates tenant access to Hadoop resources through 
> dedicated topologies with tenant specific authentication, there are a couple 
> issues:
> * pac4j provider seems to be caching config settings in a singleton which 
> makes the redirect url nondeterministic.
> * knoxsso cookie would be trusted across tenant specific topologies which 
> could lead to unauthorized access to resources that belongs to another tenant
> The use of tenant specific audience claims within the JWT token could be used 
> to mitigate the cross tenant trust issue.
> We need to investigate the pac4j provider issue with the singleton config.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KNOX-536) LDAP authentication against nested OU

[Larry McCay (JIRA)]

[ 
https://issues.apache.org/jira/browse/KNOX-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596185#comment-15596185
 ] 

Larry McCay commented on KNOX-536:
--

[~eyang] - thank you for the additional information here. I think that this 
issue will be satisfied by the PAM support. We will need to do some testing of 
it using the information provided here. It will also be helpful for docs.

Thanks again!

> LDAP authentication against nested OU
> -
>
> Key: KNOX-536
> URL: https://issues.apache.org/jira/browse/KNOX-536
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.5.0, 0.6.0, 0.7.0
> Environment: All
>Reporter: Jeffrey E  Rodriguez
> Fix For: 0.10.0
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Knox Gateway provides HTTP BASIC authentication against an LDAP user 
> directory. It currently supports only a single Organizational Unit (OU) and 
> does not support nested OUs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KNOX-727) Authorization Support for Knox Hosted Applications

[Larry McCay (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KNOX-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay updated KNOX-727:
-
Fix Version/s: (was: 0.10.0)
   0.11.0

> Authorization Support for Knox Hosted Applications
> --
>
> Key: KNOX-727
> URL: https://issues.apache.org/jira/browse/KNOX-727
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.9.0
>Reporter: Zachary Blanco
>Assignee: Zachary Blanco
> Fix For: 0.11.0
>
> Attachments: admin.xml, knoxsso.xml
>
>
> In the process of making an Administrator UI for the Knox, I've encountered 
> an issue where we can log into the app as an unauthorized user, but then fail 
> to make any AJAX requests. The Ajax requests return a 403 - which is probably 
> what should happen when logging into the app with an unauthorized user.
> Steps to reproduce:
> 1. Set up the Knox admin UI app using the instructions here: 
> https://github.com/ZacBlanco/knox-admin-ui/blob/master/README.md
> 2. Place attached knoxsso and admin topology files under conf/topologies
> 3. Navigate to https://www.local.com:8443/gateway/admin/knox-manager
> 4. Attempt to login with guest:guest-password
> The knox-manager page should render but in the dev console you should see 
> 403-Forbidden on the Ajax requests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KNOX-718) Whitelist Violation should Result in Error to User

[Larry McCay (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KNOX-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay updated KNOX-718:
-
Fix Version/s: (was: 0.10.0)
   0.11.0

> Whitelist Violation should Result in Error to User
> --
>
> Key: KNOX-718
> URL: https://issues.apache.org/jira/browse/KNOX-718
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Reporter: Krishna Pandey
> Fix For: 0.11.0
>
>
> User does not get any warning for rejection due to whitelist when logging 
> through KnoxSSO form based authentication. Refer logs below from gateway.log
> "2016-06-21 18:26:02,074 WARN  service.knoxsso (WebSSOResource.java:init(89)) 
> - The SSO cookie SecureOnly flag is set to FALSE and is therefore insecure.
> 2016-06-21 18:26:02,076 INFO  service.knoxsso 
> (WebSSOResource.java:getCookieValue(265)) - Unable to find cookie with name: 
> original-url
> 2016-06-21 18:26:02,077 ERROR service.knoxsso 
> (WebSSOResource.java:getAuthenticationToken(159)) - The original URL: 
> http://:6080/ for redirecting back after authentication is not 
> valid according to the configured whitelist: 
> ^https?:\/\/(localhost|127\.0\.0\.1|0:0:0:0:0:0:0:1|::1):[0-9].*$. See 
> documentation for KnoxSSO Whitelisting."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KNOX-237) GroupMappingServiceProvider as a Knox Provider

[Larry McCay (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KNOX-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay updated KNOX-237:
-
Fix Version/s: (was: 0.10.0)
   0.11.0

> GroupMappingServiceProvider as a Knox Provider
> --
>
> Key: KNOX-237
> URL: https://issues.apache.org/jira/browse/KNOX-237
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Reporter: Larry McCay
>Assignee: Larry McCay
> Fix For: 0.11.0
>
>
> Introduce a specific provider for integrating the Hadoop 
> GroupMappingServiceProvider for looking up group membership of the 
> authenticated (asserted) identity.
> This will allow customers' existing investments in the Hadoop hook to be 
> leveraged within Knox and used within the access control policy enforcement 
> at the perimeter.
> This mechanism will likely be mutual exclusive of the Shiro provider group 
> support - though there may be use cases where they could supplement each 
> other.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KNOX-744) Logout for KnoxSSO WebSSO API

[Larry McCay (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KNOX-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Larry McCay updated KNOX-744:
-
Fix Version/s: (was: 0.10.0)
   0.11.0

> Logout for KnoxSSO WebSSO API
> -
>
> Key: KNOX-744
> URL: https://issues.apache.org/jira/browse/KNOX-744
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: Server
>Reporter: Larry McCay
>Assignee: Larry McCay
> Fix For: 0.11.0
>
>
> WebSSO needs to expose a method to "logout" of a KnoxSSO session. This simply 
> means that the hadoop-jwt cookie be removed. Any other application level 
> sessions will need to be managed by the application itself.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KNOX-751) Need rewrite function to capture href information from single page host to rewrite output of node hosts

[Larry McCay (JIRA)]

[ 
https://issues.apache.org/jira/browse/KNOX-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596211#comment-15596211
 ] 

Larry McCay commented on KNOX-751:
--

[~jeffreyr97] - I am starting the process of closing down on 0.10.0 and 
deferring open issues out to 0.11.0 or or Future. If you plan to provide a 
patch, please do so in the next couple days. Otherwise, I will probably move 
this out to 0.11.0.

Thanks!

> Need rewrite function to capture href information from single page host to 
> rewrite output of node hosts
> ---
>
> Key: KNOX-751
> URL: https://issues.apache.org/jira/browse/KNOX-751
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.7.0, 0.8.0, 0.9.0, 0.9.1
> Environment: All environment support Knox
>Reporter: Jeffrey E  Rodriguez
>Assignee: Jeffrey E  Rodriguez
> Fix For: 0.10.0
>
>
> User Interface page rewriting through Knox presents many challenges. One of 
> the challenges is that a Web page may have more than one link to other hosts 
> of a given type (e.g. Yarn may have a link to more than one  host) which may 
> be different from the originating one. The main issue here is that Knox maps 
> a single host to a rewrite and service. If the page has multiple hosts of a 
> single type the rewrite rules may not be enough without some extra 
> information. For example, Yarn UI may have links to Node URLs (more than one 
> node) and even through the Yarn page may be rewritten to include the schema, 
> and hostname as a query parameters so the dispatcher is able to fetch the 
> correct host like:
> https://localhost:8443/gateway/nodeui/node?scheme=http?host=sandbox1?port=8042
> https://localhost:8443/gateway/nodeui/node?scheme=http?host=sandbox2?port=8042
> https://localhost:8443/gateway/nodeui/node?scheme=http?host=sandbox3?port=8042
> the response pages from each node need to have the right scheme, host, and 
> port attached to their query parameters.   We need a function that given a 
> request to one of the links above can save the information needed to rewrite 
> their request output with the query parameters needed for every response 
> links.
> e.g. 
> if we click link 
> http://localhost:8443/gateway/nodeui/node?scheme=http?host=sandbox2?port=8042
> this can be rewritten as: 
> “/node/node” to 
> https://localhost:8443/gateway/nodeui/node/node?scheme=http?host=sandbox2?port=8042
> These functions are needed:
> $hrefUrl.ur
> $hrefUrl.host
> $hrefUrl.scheme
> $hrefUrl.port
> $hrefUrl.path
> $hrefUrl.query
> The rewrite would then be something like this:
> {code:xml}
> 
>   
> template="{$gateway[url]}/node/node?scheme={hrefUrl.scheme}?host={hrefUrl.host}?port={hrefUrl.port}?{**}”
> 
> {code}
> This way then we are not only able to request the page as we do today but the 
> output response would be rewritten to have the information needed to be 
> accessed.
> There is a KNOX-618 ( patch) but after evaluation we think that relying on 
> the “Host” header still doesn’t provide all the information needed such as 
> the scheme. We have access to the request object so it may be easier to get 
> the information directly from the href request than expecting a header. The 
> “Host” header see https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html 
> section 14.23, only defines host and port. There is no reliable way to get 
> the scheme from the response headers. Thus we can't really make use of the 
> patch since we would still need the function to provide us the scheme 
> function. Also there is still more information we may want such the path and 
> query but those as not as critical to our effort to map all links from Yarn 
> UI at this point.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [DISCUSS] Need for 0.9.2 Release

[larry mccay]

I have deferred a bunch of the 0.10.0 issues in order to make it more of a
bug fix release and also make the target of end of the month.
I do think that it makes sense to forego a 0.9.2 release for now.


On Fri, Oct 21, 2016 at 3:43 PM, larry mccay  wrote:

> Hi Sandeep -
>
> That is a good point
>
> While 0.10.0 is feature bearing, we may be able to defer more of the
> outstanding tasks to an 0.10.1 or 0.11.0 and keep 0.10.0 as close to bug
> fixes as possible.
>
> I will have a look at the changes that have already made it in and see if
> we can make that make sense.
>
> thanks,
>
> --larry
>
> On Fri, Oct 21, 2016 at 2:05 PM, Sandeep More 
> wrote:
>
>> Hello Larry,
>>
>> I think that's a good idea the only thing is we are closer to cutting 0.10
>> release.
>> If 0.10 is not drastically different than 0.9.X one might just jump to
>> 0.10
>> than going to 0.9.2, I think.
>>
>> Best,
>> Sandeep
>>
>>
>> On Fri, Oct 21, 2016 at 12:48 PM, larry mccay  wrote:
>>
>> > All -
>> >
>> > There have been a number of bug fixes on the 0.9.0 branch in the event
>> that
>> > we may need to cut an 0.9.2 release for a serious enough issue.
>> >
>> > Off the top of my head, I know that we have LDAP response paging,
>> Location
>> > header encoding and just now I had to downgrade httpclient to 4.5.1 to
>> fix
>> > an issue with SPNEGO+SSL.
>> >
>> > Since 0.9.1 will not work for secure clusters with SSL enabled, I
>> believe
>> > that it warrants an 0.9.2 release.
>> >
>> > Thoughts?
>> >
>> > thanks.
>> >
>> > --larry
>> >
>>
>
>

Re: [DISCUSS] Planning for 0.10.0 Release

[larry mccay]

All -

I have spent some time deferring JIRAs out to 0.11.0 that I thought were:

a. Just not going to make it in time
b. More of a feature when we need a bug fix release now and don't want to
flood it with many new features

If you feel that you have an issue in the 0.10.0 list that can be deferred
please speak up and we will move it out to 0.11.0 as well.

If I've moved an issue out that you feel we need to get into 0.10.0 and
think can be reasonably ready in time then also speak up and we can pull it
back in.

thanks,

--larry


On Tue, Oct 18, 2016 at 3:22 PM, larry mccay  wrote:

> Hey folks -
>
> Those fixes would be great to get into this release as well.
> 10/31 is certainly reasonable.
>
> Let's go with that for now.
>
> thanks,
>
> --larry
>
> On Tue, Oct 18, 2016 at 3:17 PM, Sandeep More 
> wrote:
>
>> Hello Larry,
>>
>> Still working on KNOX-752 
>> -
>> Websocket support, I am hoping to get a patch out by the end of this week
>> but not sure.
>> I second Sumit's suggestion of 10/31, if that works.
>>
>> Best,
>> Sandeep
>>
>>
>> On Tue, Oct 18, 2016 at 2:10 PM, Sumit Gupta > >
>> wrote:
>>
>> > Hi Larry,
>> >
>> > Thanks for bringing the focus back to the 0.10.0 release and looking to
>> > close things down. I think the LDAP improvements are great and need to
>> get
>> > released soon. We also have had a fix regarding an encoding regression
>> > that would be good to get in release, KNOX-754 (it could also be in a
>> > 0.9.2 though).
>> >
>> > As for the date, I would recommend another week out, 10/31 maybe? I
>> would
>> > hope we can get KNOX-752 in as well if we can allow for some more time.
>> >
>> > Sumit.
>> >
>> >
>> > On 10/17/16, 7:14 AM, "larry mccay"  wrote:
>> >
>> > >Folks -
>> > >
>> > >I would like to start the process of closing down on 0.10.0.
>> > >We still have ~16 open JIRAs designated for 0.10.0 and we need to start
>> > >resolving these or deferring them to 0.11.0.
>> > >
>> > >A number of the KIP-1 related issues have either been resolved or have
>> > >their usecases awaiting testing from one other other JIRAs - for
>> instance
>> > >KNOX-536 LDAP authentication against nested OU is likely accomplishable
>> > >via
>> > >KNOX-537 - Linux PAM Authentication Module. We just need to test it
>> out.
>> > >
>> > >Over the next couple days, I will start moving some issues out to
>> 0.11.0.
>> > >If you have a patch for something in the wings then you may want to get
>> > >this attached along with tests to help get it committed in time for the
>> > >release.
>> > >
>> > >I know that we were targeting 9/23 for this release but vacations and
>> > >other
>> > >commitments have made it slip.
>> > >I propose that we try and target 10/23 to have an RC available for
>> > >testing.
>> > >
>> > >Thoughts?
>> > >
>> > >thanks!
>> > >
>> > >--larry
>> > >
>> > >On Wed, Aug 10, 2016 at 9:34 AM, Sumit Gupta <
>> sumit.gu...@hortonworks.com
>> > >
>> > >wrote:
>> > >
>> > >> That would be awesome Zac. Let me know when you get close, as
>> promised
>> > >> before I would be happy to help with the integration into the main
>> line
>> > >> (build/packing etc).
>> > >>
>> > >> We should also create a JIRA other than KNOX-727 to track and discuss
>> > >> this. There may be one already and I just missed itŠ
>> > >>
>> > >> Sumit
>> > >>
>> > >>
>> > >> On 8/10/16, 12:54 AM, "Zac Blanco"  wrote:
>> > >>
>> > >> >I've been working on the admin page on and off over the last month.
>> If
>> > >> >we're aiming for read-only then I think I should have something up
>> in a
>> > >> >week or so. (If I'm only working with the current feature set of the
>> > >>admin
>> > >> >API).
>> > >> >
>> > >> >Definitely doable for 0.10.0.
>> > >> >
>> > >> >On Aug 9, 2016 1:40 PM, "Sumit Gupta" 
>> > >> wrote:
>> > >> >
>> > >> >9/23 is a good goal for 0.10.0. +1.
>> > >> >
>> > >> >
>> > >> >On 8/9/16, 4:16 PM, "larry mccay"  wrote:
>> > >> >
>> > >> >>Yes, 1.5 months gets a +1 from me.
>> > >> >>Should we call it 9/23rd?
>> > >> >>
>> > >> >>Metrics and a read-only admin page for that timeframe sound great.
>> > >> >>
>> > >> >>Personally, I would like to see an admin page and some uptake of
>> LDAP
>> > >> >>improvements before we stamp a 1.0.0.
>> > >> >>I could be convinced to go before anyone wants to try. :)
>> > >> >>
>> > >> >>On Tue, Aug 9, 2016 at 4:10 PM, Sumit Gupta
>> > >>> > >> >
>> > >> >>wrote:
>> > >> >>
>> > >> >>> Hey Larry,
>> > >> >>>
>> > >> >>> Thanks for reviving the thread.
>> > >> >>>
>> > >> >>> LDAP improvements seems like a decent theme and there is
>> definitely
>> > >>a
>> > >> >>> bunch of work to be done there.
>> > >> >>>
>> > >> >>> A couple of other things that would be good to have before we go
>> > >>for a
>> > >> >>>1.0
>> > >> >>> are (so we could consider including it in 0.10.0):
>> > >> >>>
>> > >> >>> 1. Adding metrics capabiltiies (so that we can get to metering
>> and
>> > >> >>> throttling) : KNOX-643
>> > >> >>> 2. A basic a