[jira] [Updated] (KNOX-1157) Scoped rewrite rules are treated as global rules in some cases

[Larry McCay (JIRA)]

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

Larry McCay updated KNOX-1157:
--
Fix Version/s: 1.0.0

> Scoped rewrite rules are treated as global rules in some cases
> --
>
> Key: KNOX-1157
> URL: https://issues.apache.org/jira/browse/KNOX-1157
> Project: Apache Knox
>  Issue Type: Bug
>Reporter: Wei Han
>Assignee: Wei Han
>Priority: Minor
> Fix For: 1.0.0
>
> Attachments: 
> 0001-bug-fix-use-a-map-to-store-all-rules-in-ScopedMatche.patch
>
>
> https://issues.apache.org/jira/browse/KNOX-711 introduced the concept of 
> 'scope' for rewrite rules. A rewrite rule can be applied to an input url only 
> if they share the same scope, unless the rule is explicitly defined as 
> 'global' rules. 
> However given the following rewrite.xml, and input url "/foo/bar" with role 
> service-1, the second rule(service-2) will win because the second rule is 
> more specific, even the scope is different from the input url. 
> 
> 
> 
> 
> 
> 
> The root cause is the templates for these two rules are different, so in 
> ScopedMatcher.java(https://github.com/apache/knox/commit/286e02a44dfb5f9ee101007b46bcb8ee47fa62d7#diff-6cffc9c391024e27c73a85ba8e736e60R118),
>  we don't create a separate matcher and the two rules share the same matcher 
> object. 
> My proposal is to change the implementation to create a brand new matcher for 
> each scope, and store them in a map keyed by scope name.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KNOX-1157) Scoped rewrite rules are treated as global rules in some cases

[Larry McCay (JIRA)]

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

Larry McCay commented on KNOX-1157:
---

[~weihan] - I have assigned this to you since you have provided a patch.
I will try and review this in the next day or so and determine whether we need 
this in 1.0.0 or not.

We need to try and keep it as close to 0.14.0 as possible.
The initial idea was to only have items that fix issues that would be a problem 
with the backward compatibility implied by a 1.0.0 release and security related 
items.

It has since started some scope creep for low risk items.

> Scoped rewrite rules are treated as global rules in some cases
> --
>
> Key: KNOX-1157
> URL: https://issues.apache.org/jira/browse/KNOX-1157
> Project: Apache Knox
>  Issue Type: Bug
>Reporter: Wei Han
>Assignee: Wei Han
>Priority: Minor
> Fix For: 1.0.0
>
> Attachments: 
> 0001-bug-fix-use-a-map-to-store-all-rules-in-ScopedMatche.patch
>
>
> https://issues.apache.org/jira/browse/KNOX-711 introduced the concept of 
> 'scope' for rewrite rules. A rewrite rule can be applied to an input url only 
> if they share the same scope, unless the rule is explicitly defined as 
> 'global' rules. 
> However given the following rewrite.xml, and input url "/foo/bar" with role 
> service-1, the second rule(service-2) will win because the second rule is 
> more specific, even the scope is different from the input url. 
> 
> 
> 
> 
> 
> 
> The root cause is the templates for these two rules are different, so in 
> ScopedMatcher.java(https://github.com/apache/knox/commit/286e02a44dfb5f9ee101007b46bcb8ee47fa62d7#diff-6cffc9c391024e27c73a85ba8e736e60R118),
>  we don't create a separate matcher and the two rules share the same matcher 
> object. 
> My proposal is to change the implementation to create a brand new matcher for 
> each scope, and store them in a map keyed by scope name.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (KNOX-1157) Scoped rewrite rules are treated as global rules in some cases

[Larry McCay (JIRA)]

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

Larry McCay reassigned KNOX-1157:
-

Assignee: Wei Han  (was: Sumit Gupta)

> Scoped rewrite rules are treated as global rules in some cases
> --
>
> Key: KNOX-1157
> URL: https://issues.apache.org/jira/browse/KNOX-1157
> Project: Apache Knox
>  Issue Type: Bug
>Reporter: Wei Han
>Assignee: Wei Han
>Priority: Minor
> Attachments: 
> 0001-bug-fix-use-a-map-to-store-all-rules-in-ScopedMatche.patch
>
>
> https://issues.apache.org/jira/browse/KNOX-711 introduced the concept of 
> 'scope' for rewrite rules. A rewrite rule can be applied to an input url only 
> if they share the same scope, unless the rule is explicitly defined as 
> 'global' rules. 
> However given the following rewrite.xml, and input url "/foo/bar" with role 
> service-1, the second rule(service-2) will win because the second rule is 
> more specific, even the scope is different from the input url. 
> 
> 
> 
> 
> 
> 
> The root cause is the templates for these two rules are different, so in 
> ScopedMatcher.java(https://github.com/apache/knox/commit/286e02a44dfb5f9ee101007b46bcb8ee47fa62d7#diff-6cffc9c391024e27c73a85ba8e736e60R118),
>  we don't create a separate matcher and the two rules share the same matcher 
> object. 
> My proposal is to change the implementation to create a brand new matcher for 
> each scope, and store them in a map keyed by scope name.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KNOX-1156) Disabled / Multiple Providers Yield Broken Deployment

[Larry McCay (JIRA)]

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

Larry McCay commented on KNOX-1156:
---

[~rkellogg] - thank you for those additional details!
I am going to push this out to 1.1.0 for now but we should definitely pick this 
up and clean up those items and address the enabled flag process.

> Disabled / Multiple Providers Yield Broken Deployment
> -
>
> Key: KNOX-1156
> URL: https://issues.apache.org/jira/browse/KNOX-1156
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.10.0, 0.11.0, 0.12.0, 0.13.0, 0.14.0
>Reporter: Rick Kellogg
>Assignee: Rick Kellogg
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: KNOX-1056.patch
>
>
> Within the topology XML file, the providers include an enabled element.  If 
> you include multiple providers with the same role the generated gateway.xml 
> file might not include the enabled providers. 
> In my specific example, I had two authentication providers.  The first of 
> which was disabled and the second was enabled.  The second provider was 
> ignored yielding no authentication provider in the gateway.xml and then 
> subsequent use of the identity provider failed with a missing Subject.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1156) Disabled / Multiple Providers Yield Broken Deployment

[Larry McCay (JIRA)]

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

Larry McCay updated KNOX-1156:
--
Fix Version/s: (was: 1.0.0)
   1.1.0

> Disabled / Multiple Providers Yield Broken Deployment
> -
>
> Key: KNOX-1156
> URL: https://issues.apache.org/jira/browse/KNOX-1156
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.10.0, 0.11.0, 0.12.0, 0.13.0, 0.14.0
>Reporter: Rick Kellogg
>Assignee: Rick Kellogg
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: KNOX-1056.patch
>
>
> Within the topology XML file, the providers include an enabled element.  If 
> you include multiple providers with the same role the generated gateway.xml 
> file might not include the enabled providers. 
> In my specific example, I had two authentication providers.  The first of 
> which was disabled and the second was enabled.  The second provider was 
> ignored yielding no authentication provider in the gateway.xml and then 
> subsequent use of the identity provider failed with a missing Subject.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KNOX-1141) Coverity Issues Reported For AmbariConfigurationMonitor

[ASF subversion and git services (JIRA)]

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

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

Commit b006e1d404dfcb7558aaa2b9b9c4f4c578ab9749 in knox's branch 
refs/heads/v0.14.0 from [~pzampino]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=b006e1d ]

KNOX-1141 - Coverity Issues Reported For AmbariConfigurationMonitor


> Coverity Issues Reported For AmbariConfigurationMonitor
> ---
>
> Key: KNOX-1141
> URL: https://issues.apache.org/jira/browse/KNOX-1141
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1141.patch
>
>
> *** CID 1383538:  Null pointer dereferences  (NULL_RETURNS)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  436 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.getUpdatedConfigVersions(java.lang.String,
>  java.lang.String)()
> *** CID 1383537:  Resource leaks  (RESOURCE_LEAK)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  211 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.persist(java.util.Properties,
>  java.io.File)()
> *** CID 1383536:  Null pointer dereferences  (NULL_RETURNS)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  148 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.loadClusterVersionData()()
> *** CID 1383535:  Resource leaks  (RESOURCE_LEAK)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  119 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.loadDiscoveryConfiguration()()
> *** CID 1383534:  Resource leaks  (RESOURCE_LEAK)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  152 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.loadClusterVersionData()()



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1043) Ambari Service Discovery Support for HA-Enabled Services

[Phil Zampino (JIRA)]

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

Phil Zampino updated KNOX-1043:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Ambari Service Discovery Support for HA-Enabled Services
> 
>
> Key: KNOX-1043
> URL: https://issues.apache.org/jira/browse/KNOX-1043
> Project: Apache Knox
>  Issue Type: Sub-task
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
>  Labels: kip-8
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1043.patch
>
>
> Make sure that Ambari ServiceDiscovery correctly supports scenarios involving 
> HA-enabled Hadoop services.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KNOX-1043) Ambari Service Discovery Support for HA-Enabled Services

[ASF subversion and git services (JIRA)]

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

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

Commit 80b871f9c27356ef7bfb3b35b9da21fa4cb47fcf in knox's branch 
refs/heads/v0.14.0 from [~pzampino]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=80b871f ]

KNOX-1043 - Ambari Service Discovery Support for HA-Enabled Services


> Ambari Service Discovery Support for HA-Enabled Services
> 
>
> Key: KNOX-1043
> URL: https://issues.apache.org/jira/browse/KNOX-1043
> Project: Apache Knox
>  Issue Type: Sub-task
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
>  Labels: kip-8
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1043.patch
>
>
> Make sure that Ambari ServiceDiscovery correctly supports scenarios involving 
> HA-enabled Hadoop services.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

[ASF subversion and git services (JIRA)]

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

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

Commit 7a2e7eab16f28f5dce3a0f9e410e531186cc060b in knox's branch 
refs/heads/v0.14.0 from [~pzampino]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=7a2e7ea ]

KNOX-1144 - Provider Configuration Reference Relationships Aren't Established 
For Existing Descriptors at Gateway Startup


> Provider Configuration Reference Relationships Aren't Established For 
> Existing Descriptors at Gateway Startup
> -
>
> Key: KNOX-1144
> URL: https://issues.apache.org/jira/browse/KNOX-1144
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1144.patch, sandbox-providers.xml, 
> simple-sandbox.json
>
>
> Changes to existing provider configurations don't result in updates to the 
> existing descriptors which reference them.
> This is a consequence of changing the startup behavior wrt simple 
> descriptors. Now that existing simple descriptors no longer trigger topology 
> regeneration at startup (unless they've changed since shutdown), the 
> relationships between simple descriptors and the provider configurations they 
> reference are not being established.
> These relationships need to be established when the TopologyService is 
> initialized.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

[Phil Zampino (JIRA)]

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

Phil Zampino edited comment on KNOX-1137 at 1/3/18 10:23 PM:
-

Attached KNOX-1137.patch, which adds:

* list-provider-configs --registry-client CLIENT_NAME
* list-descriptors --registry-client CLIENT_NAME

Examples:

{noformat}
{GATEWAY_HOME}/bin/knoxcli.sh list-provider-configs --registry-client 
sandbox-zookeeper-client
Provider Configurations (@localhost:2181)
sandbox-providers.xml

{noformat}

{noformat}
{GATEWAY_HOME}/bin/knoxcli.sh list-descriptors --registry-client 
sandbox-zookeeper-client
Descriptors (@localhost:2181)
docker-sandbox.json

{noformat}



was (Author: pzampino):
Attached KNOX-1137.patch, which adds:

* list-provider-configs --registry-client CLIENT_NAME
* list-descriptors --registry-client CLIENT_NAME

Examples:

{noformat}
{GATEWAY_HOME}/bin/knoxcli.sh list-provider-configs --registry-name 
sandbox-zookeeper-client
Provider Configurations (@localhost:2181)
sandbox-providers.xml

{noformat}

{noformat}
{GATEWAY_HOME}/bin/knoxcli.sh list-descriptors --registry-name 
sandbox-zookeeper-client
Descriptors (@localhost:2181)
docker-sandbox.json

{noformat}


> KnoxCLI For Listing Provider Configurations and Descriptors in a Remote 
> Configuration Registry
> --
>
> Key: KNOX-1137
> URL: https://issues.apache.org/jira/browse/KNOX-1137
> Project: Apache Knox
>  Issue Type: Bug
>  Components: KnoxCLI
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1137.patch
>
>
> KNOX-1125 introduced Knox CLI commands for adding and removing provider 
> configurations and simple descriptors to a remote configuration registry 
> (e.g., ZooKeeper). It would be helpful to also have the ability to list the 
> provider configurations and descriptors that are in the registry.
> list-provider-configs --registry-client name
> list-descriptors --registry-client name



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

[ASF subversion and git services (JIRA)]

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

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

Commit 2ccb989c8b707c0bc9f4e99392783f0e26cf519c in knox's branch 
refs/heads/v0.14.0 from [~pzampino]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=2ccb989 ]

KNOX-1137 - KnoxCLI For Listing Provider Configurations and Descriptors in a 
Remote Configuration Registry


> KnoxCLI For Listing Provider Configurations and Descriptors in a Remote 
> Configuration Registry
> --
>
> Key: KNOX-1137
> URL: https://issues.apache.org/jira/browse/KNOX-1137
> Project: Apache Knox
>  Issue Type: Bug
>  Components: KnoxCLI
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1137.patch
>
>
> KNOX-1125 introduced Knox CLI commands for adding and removing provider 
> configurations and simple descriptors to a remote configuration registry 
> (e.g., ZooKeeper). It would be helpful to also have the ability to list the 
> provider configurations and descriptors that are in the registry.
> list-provider-configs --registry-client name
> list-descriptors --registry-client name



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KNOX-1151) Need Explicit curator-recipes dependency in pom

[ASF subversion and git services (JIRA)]

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

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

Commit f88cff28ec2173eb5cb6f7740977595bdae361e7 in knox's branch 
refs/heads/v0.14.0 from [~pzampino]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=f88cff2 ]

KNOX-1151 backport


> Need Explicit curator-recipes dependency in pom
> ---
>
> Key: KNOX-1151
> URL: https://issues.apache.org/jira/browse/KNOX-1151
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Build
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1151.patch
>
>
> In some cases, Maven is pulling versions of curator-recipes that are too old 
> to be compatible with curator-framework:4.0.0. Therefore, we must have an 
> explicit declaration for this dependency:
> org.apache.curator:curator-recipes:4.0.0



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KNOX-1043) Ambari Service Discovery Support for HA-Enabled Services

[ASF subversion and git services (JIRA)]

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

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

Commit 348c4d7def61f6296a7cf192ed00e38a8e5c3714 in knox's branch 
refs/heads/master from [~pzamp...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=348c4d7 ]

KNOX-1043


> Ambari Service Discovery Support for HA-Enabled Services
> 
>
> Key: KNOX-1043
> URL: https://issues.apache.org/jira/browse/KNOX-1043
> Project: Apache Knox
>  Issue Type: Sub-task
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
>  Labels: kip-8
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1043.patch
>
>
> Make sure that Ambari ServiceDiscovery correctly supports scenarios involving 
> HA-enabled Hadoop services.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

[Phil Zampino (JIRA)]

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

Phil Zampino updated KNOX-1144:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Provider Configuration Reference Relationships Aren't Established For 
> Existing Descriptors at Gateway Startup
> -
>
> Key: KNOX-1144
> URL: https://issues.apache.org/jira/browse/KNOX-1144
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1144.patch, sandbox-providers.xml, 
> simple-sandbox.json
>
>
> Changes to existing provider configurations don't result in updates to the 
> existing descriptors which reference them.
> This is a consequence of changing the startup behavior wrt simple 
> descriptors. Now that existing simple descriptors no longer trigger topology 
> regeneration at startup (unless they've changed since shutdown), the 
> relationships between simple descriptors and the provider configurations they 
> reference are not being established.
> These relationships need to be established when the TopologyService is 
> initialized.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1146) Document KNOX CLI Commands For Listing Provider Configs and Descriptors in Remote Registries

[Phil Zampino (JIRA)]

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

Phil Zampino updated KNOX-1146:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Document KNOX CLI Commands For Listing Provider Configs and Descriptors in 
> Remote Registries
> 
>
> Key: KNOX-1146
> URL: https://issues.apache.org/jira/browse/KNOX-1146
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: Site
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
> Attachments: KNOX-1146.patch
>
>
> KNOX-1137 adds commands for listing provider configurations and simple 
> descriptors in remote registries



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KNOX-1146) Document KNOX CLI Commands For Listing Provider Configs and Descriptors in Remote Registries

[ASF subversion and git services (JIRA)]

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

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

Commit 1820009 from [~pzampino]
[ https://svn.apache.org/r1820009 ]

KNOX-1146 CLI command updates

> Document KNOX CLI Commands For Listing Provider Configs and Descriptors in 
> Remote Registries
> 
>
> Key: KNOX-1146
> URL: https://issues.apache.org/jira/browse/KNOX-1146
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: Site
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
> Attachments: KNOX-1146.patch
>
>
> KNOX-1137 adds commands for listing provider configurations and simple 
> descriptors in remote registries



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

[ASF subversion and git services (JIRA)]

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

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

Commit a438bcc1e4dec613f078ecea25bb177a3904a3a7 in knox's branch 
refs/heads/master from [~pzamp...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=a438bcc ]

KNOX-1144


> Provider Configuration Reference Relationships Aren't Established For 
> Existing Descriptors at Gateway Startup
> -
>
> Key: KNOX-1144
> URL: https://issues.apache.org/jira/browse/KNOX-1144
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1144.patch, sandbox-providers.xml, 
> simple-sandbox.json
>
>
> Changes to existing provider configurations don't result in updates to the 
> existing descriptors which reference them.
> This is a consequence of changing the startup behavior wrt simple 
> descriptors. Now that existing simple descriptors no longer trigger topology 
> regeneration at startup (unless they've changed since shutdown), the 
> relationships between simple descriptors and the provider configurations they 
> reference are not being established.
> These relationships need to be established when the TopologyService is 
> initialized.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

[Phil Zampino (JIRA)]

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

Phil Zampino updated KNOX-1137:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> KnoxCLI For Listing Provider Configurations and Descriptors in a Remote 
> Configuration Registry
> --
>
> Key: KNOX-1137
> URL: https://issues.apache.org/jira/browse/KNOX-1137
> Project: Apache Knox
>  Issue Type: Bug
>  Components: KnoxCLI
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1137.patch
>
>
> KNOX-1125 introduced Knox CLI commands for adding and removing provider 
> configurations and simple descriptors to a remote configuration registry 
> (e.g., ZooKeeper). It would be helpful to also have the ability to list the 
> provider configurations and descriptors that are in the registry.
> list-provider-configs --registry-client name
> list-descriptors --registry-client name



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1141) Coverity Issues Reported For AmbariConfigurationMonitor

[Phil Zampino (JIRA)]

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

Phil Zampino updated KNOX-1141:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Coverity Issues Reported For AmbariConfigurationMonitor
> ---
>
> Key: KNOX-1141
> URL: https://issues.apache.org/jira/browse/KNOX-1141
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1141.patch
>
>
> *** CID 1383538:  Null pointer dereferences  (NULL_RETURNS)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  436 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.getUpdatedConfigVersions(java.lang.String,
>  java.lang.String)()
> *** CID 1383537:  Resource leaks  (RESOURCE_LEAK)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  211 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.persist(java.util.Properties,
>  java.io.File)()
> *** CID 1383536:  Null pointer dereferences  (NULL_RETURNS)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  148 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.loadClusterVersionData()()
> *** CID 1383535:  Resource leaks  (RESOURCE_LEAK)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  119 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.loadDiscoveryConfiguration()()
> *** CID 1383534:  Resource leaks  (RESOURCE_LEAK)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  152 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.loadClusterVersionData()()



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

[ASF subversion and git services (JIRA)]

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

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

Commit 7e03a9cf1714747df01c4fa4afc00615feafa8c5 in knox's branch 
refs/heads/master from [~pzamp...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=7e03a9c ]

KNOX-1137


> KnoxCLI For Listing Provider Configurations and Descriptors in a Remote 
> Configuration Registry
> --
>
> Key: KNOX-1137
> URL: https://issues.apache.org/jira/browse/KNOX-1137
> Project: Apache Knox
>  Issue Type: Bug
>  Components: KnoxCLI
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1137.patch
>
>
> KNOX-1125 introduced Knox CLI commands for adding and removing provider 
> configurations and simple descriptors to a remote configuration registry 
> (e.g., ZooKeeper). It would be helpful to also have the ability to list the 
> provider configurations and descriptors that are in the registry.
> list-provider-configs --registry-client name
> list-descriptors --registry-client name



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

list

[Philip Zampino]

subscribe

[jira] [Commented] (KNOX-1141) Coverity Issues Reported For AmbariConfigurationMonitor

[ASF subversion and git services (JIRA)]

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

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

Commit 7d42ffd065c66d810a52a90f8c2dace55f3aceed in knox's branch 
refs/heads/master from [~pzampino]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=7d42ffd ]

KNOX-1141


> Coverity Issues Reported For AmbariConfigurationMonitor
> ---
>
> Key: KNOX-1141
> URL: https://issues.apache.org/jira/browse/KNOX-1141
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1141.patch
>
>
> *** CID 1383538:  Null pointer dereferences  (NULL_RETURNS)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  436 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.getUpdatedConfigVersions(java.lang.String,
>  java.lang.String)()
> *** CID 1383537:  Resource leaks  (RESOURCE_LEAK)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  211 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.persist(java.util.Properties,
>  java.io.File)()
> *** CID 1383536:  Null pointer dereferences  (NULL_RETURNS)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  148 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.loadClusterVersionData()()
> *** CID 1383535:  Resource leaks  (RESOURCE_LEAK)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  119 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.loadDiscoveryConfiguration()()
> *** CID 1383534:  Resource leaks  (RESOURCE_LEAK)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  152 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.loadClusterVersionData()()



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Add Apache Knox Services

[larry mccay]

Interesting...

I see that it is resolving to the KNOX service role from the audit log.
That is the actual issue.

The KNOX service happens to be an odd implementation in that its path
assumes that it is deployed alone in the admin.xml topology.
Thus the URL is https://localhost:8443/gateway/admin/v1/... - note the lack
of an API context path there.
It seemed cleaner to implement that way than come up with some redundant
topology and api context path like "admin/knox" or "admin/admin".
As is often the case, the naming here was the hardest part and likely the
root of your issue.

Please remove the KNOX service from the sandbox topology.
You are getting a 404 because index.html is definitely not a resource in
the KNOX admin API.



On Wed, Jan 3, 2018 at 11:07 AM, Gareth Williams 
wrote:

> I touched the sandbox.xml topology file:
>
> 2018-01-03 16:00:12,237 INFO  hadoop.gateway (GatewayServer.java:
> internalDeactivateTopology(816)) - Deactivating topology sandbox
> 2018-01-03 16:00:30,568 INFO  hadoop.gateway 
> (DefaultGatewayServices.java:initializeContribution(201))
> - Credential store found for the cluster: sandbox - no need to create one.
> 2018-01-03 16:00:44,737 INFO  hadoop.gateway 
> (GatewayServer.java:internalActivateTopology(784))
> - Activating topology sandbox
> 2018-01-03 16:00:44,737 INFO  hadoop.gateway 
> (GatewayServer.java:internalActivateArchive(794))
> - Activating topology sandbox archive %2F
> 2018-01-03 16:00:46,703 INFO  hadoop.gateway (GatewayServer.java:
> cleanupTopologyDeployments(283)) - Deleting backup deployed topology
> C:\knox\bin\..\data\deployments\sandbox.topo.160bb92cbbd
>
> Same result, I am able to visit webhdfs via knox but not my newly created
> service.
>
> 18/01/03 16:06:34 ||22dc76f2-5b0f-4585-8620-157906f9977f|audit|0:0:0:0:0:
> 0:0:1|WEBHDFSaccess|uri|/gateway/sandbox/webhdfs/v1/?
> op=LISTSTATUS|unavailable|Request method: GET
> 18/01/03 16:06:34 ||22dc76f2-5b0f-4585-8620-157906f9977f|audit|0:0:0:0:0:
> 0:0:1|WEBHDFS|admin|||authentication|uri|/gateway/sandbox/webhdfs/v1/?op=
> LISTSTATUS|success|
> 18/01/03 16:06:34 ||22dc76f2-5b0f-4585-8620-157906f9977f|audit|0:0:0:0:0:
> 0:0:1|WEBHDFS|admin|||authentication|uri|/gateway/sandbox/webhdfs/v1/?op=LISTSTATUS|success|Groups:
> []
> 18/01/03 16:06:34 ||22dc76f2-5b0f-4585-8620-157906f9977f|audit|0:0:0:0:0:
> 0:0:1|WEBHDFS|admin|||dispatch|uri|http://localhost:50070/webhdfs/v1/?op=
> LISTSTATUS&user.name=admin|unavailable|Request method: GET
> 18/01/03 16:06:35 ||22dc76f2-5b0f-4585-8620-157906f9977f|audit|0:0:0:0:0:
> 0:0:1|WEBHDFS|admin|||dispatch|uri|http://localhost:50070/webhdfs/v1/?op=
> LISTSTATUS&user.name=admin|success|Response status: 200
> 18/01/03 16:06:35 ||22dc76f2-5b0f-4585-8620-157906f9977f|audit|0:0:0:0:0:
> 0:0:1|WEBHDFS|admin|||access|uri|/gateway/sandbox/webhdfs/
> v1/?op=LISTSTATUS|success|Response status: 200
> 18/01/03 16:06:41 ||8e1efbb0-8a1a-4c0c-8557-2d838fb61aae|audit|0:0:0:0:0:
> 0:0:1|KNOXaccess|uri|/gateway/sandbox/simple/index.html|unavailable|Request
> method: GET
> 18/01/03 16:06:41 ||8e1efbb0-8a1a-4c0c-8557-2d838fb61aae|audit|0:0:0:0:0:
> 0:0:1|KNOX|admin|||authentication|uri|/gateway/sandbox/simple/index.html|
> success|
> 18/01/03 16:06:41 ||8e1efbb0-8a1a-4c0c-8557-2d838fb61aae|audit|0:0:0:0:0:
> 0:0:1|KNOX|admin|||authentication|uri|/gateway/sandbox/simple/index.html|success|Groups:
> []
> 18/01/03 16:06:41 ||8e1efbb0-8a1a-4c0c-8557-2d838fb61aae|audit|0:0:0:0:0:
> 0:0:1|KNOX|admin|||access|uri|/gateway/sandbox/simple/index.html|success|Response
> status: 404
>
> Thanks,
>
> Gareth
>
> -Original Message-
> From: larry mccay [mailto:lmc...@apache.org]
> Sent: 03 January 2018 14:43
> To: dev@knox.apache.org
> Subject: Re: Add Apache Knox Services
>
> "Yes I edited the topology file after entering the service definitions and
> then I restarted the server."
>
> I interpret the above as:
>
> 1. added service definition to data directory 2. edited topology (which
> would deploy the new webapp without knowing about the service def) 3.
> restart server (which would make server aware of new service def for new
> topology deployments but the webapp still not)
>
> NOTE: webapps are not recreated on restart
>
> If the above is correct then you need to touch the topology so that it
> gets redeployed.
> If you haven't done that already then just do it and see if it works.
>
> On Wed, Jan 3, 2018 at 9:20 AM, Gareth Williams 
> wrote:
>
> > Yes I edited the topology file after entering the service definitions
> > and then I restarted the server.
> >
> > Any other suggestions?
> >
> > -Original Message-
> > From: larry mccay [mailto:lmc...@apache.org]
> > Sent: 03 January 2018 13:15
> > To: dev@knox.apache.org
> > Subject: Re: Add Apache Knox Services
> >
> > It all looks okay to me.
> > You may need to touch the sandbox.xml file.
> >
> > If you happen to have had it configured in the topology before you
> > added the service definition AND restarted then the generated we

RE: Add Apache Knox Services

[Gareth Williams]

I touched the sandbox.xml topology file:

2018-01-03 16:00:12,237 INFO  hadoop.gateway 
(GatewayServer.java:internalDeactivateTopology(816)) - Deactivating topology 
sandbox
2018-01-03 16:00:30,568 INFO  hadoop.gateway 
(DefaultGatewayServices.java:initializeContribution(201)) - Credential store 
found for the cluster: sandbox - no need to create one.
2018-01-03 16:00:44,737 INFO  hadoop.gateway 
(GatewayServer.java:internalActivateTopology(784)) - Activating topology sandbox
2018-01-03 16:00:44,737 INFO  hadoop.gateway 
(GatewayServer.java:internalActivateArchive(794)) - Activating topology sandbox 
archive %2F
2018-01-03 16:00:46,703 INFO  hadoop.gateway 
(GatewayServer.java:cleanupTopologyDeployments(283)) - Deleting backup deployed 
topology C:\knox\bin\..\data\deployments\sandbox.topo.160bb92cbbd

Same result, I am able to visit webhdfs via knox but not my newly created 
service.

18/01/03 16:06:34 
||22dc76f2-5b0f-4585-8620-157906f9977f|audit|0:0:0:0:0:0:0:1|WEBHDFSaccess|uri|/gateway/sandbox/webhdfs/v1/?op=LISTSTATUS|unavailable|Request
 method: GET
18/01/03 16:06:34 
||22dc76f2-5b0f-4585-8620-157906f9977f|audit|0:0:0:0:0:0:0:1|WEBHDFS|admin|||authentication|uri|/gateway/sandbox/webhdfs/v1/?op=LISTSTATUS|success|
18/01/03 16:06:34 
||22dc76f2-5b0f-4585-8620-157906f9977f|audit|0:0:0:0:0:0:0:1|WEBHDFS|admin|||authentication|uri|/gateway/sandbox/webhdfs/v1/?op=LISTSTATUS|success|Groups:
 []
18/01/03 16:06:34 
||22dc76f2-5b0f-4585-8620-157906f9977f|audit|0:0:0:0:0:0:0:1|WEBHDFS|admin|||dispatch|uri|http://localhost:50070/webhdfs/v1/?op=LISTSTATUS&user.name=admin|unavailable|Request
 method: GET
18/01/03 16:06:35 
||22dc76f2-5b0f-4585-8620-157906f9977f|audit|0:0:0:0:0:0:0:1|WEBHDFS|admin|||dispatch|uri|http://localhost:50070/webhdfs/v1/?op=LISTSTATUS&user.name=admin|success|Response
 status: 200
18/01/03 16:06:35 
||22dc76f2-5b0f-4585-8620-157906f9977f|audit|0:0:0:0:0:0:0:1|WEBHDFS|admin|||access|uri|/gateway/sandbox/webhdfs/v1/?op=LISTSTATUS|success|Response
 status: 200
18/01/03 16:06:41 
||8e1efbb0-8a1a-4c0c-8557-2d838fb61aae|audit|0:0:0:0:0:0:0:1|KNOXaccess|uri|/gateway/sandbox/simple/index.html|unavailable|Request
 method: GET
18/01/03 16:06:41 
||8e1efbb0-8a1a-4c0c-8557-2d838fb61aae|audit|0:0:0:0:0:0:0:1|KNOX|admin|||authentication|uri|/gateway/sandbox/simple/index.html|success|
18/01/03 16:06:41 
||8e1efbb0-8a1a-4c0c-8557-2d838fb61aae|audit|0:0:0:0:0:0:0:1|KNOX|admin|||authentication|uri|/gateway/sandbox/simple/index.html|success|Groups:
 []
18/01/03 16:06:41 
||8e1efbb0-8a1a-4c0c-8557-2d838fb61aae|audit|0:0:0:0:0:0:0:1|KNOX|admin|||access|uri|/gateway/sandbox/simple/index.html|success|Response
 status: 404

Thanks,

Gareth

-Original Message-
From: larry mccay [mailto:lmc...@apache.org] 
Sent: 03 January 2018 14:43
To: dev@knox.apache.org
Subject: Re: Add Apache Knox Services

"Yes I edited the topology file after entering the service definitions and then 
I restarted the server."

I interpret the above as:

1. added service definition to data directory 2. edited topology (which would 
deploy the new webapp without knowing about the service def) 3. restart server 
(which would make server aware of new service def for new topology deployments 
but the webapp still not)

NOTE: webapps are not recreated on restart

If the above is correct then you need to touch the topology so that it gets 
redeployed.
If you haven't done that already then just do it and see if it works.

On Wed, Jan 3, 2018 at 9:20 AM, Gareth Williams 
wrote:

> Yes I edited the topology file after entering the service definitions 
> and then I restarted the server.
>
> Any other suggestions?
>
> -Original Message-
> From: larry mccay [mailto:lmc...@apache.org]
> Sent: 03 January 2018 13:15
> To: dev@knox.apache.org
> Subject: Re: Add Apache Knox Services
>
> It all looks okay to me.
> You may need to touch the sandbox.xml file.
>
> If you happen to have had it configured in the topology before you 
> added the service definition AND restarted then the generated webapp 
> wouldn't have known about the service and it wouldn't have been added 
> to the gateway.xml file in the webapp.
>
> You can check that file - if you like or just touch the topology and 
> see if the new deployment works.
>
> On Wed, Jan 3, 2018 at 5:47 AM, Gareth Williams 
> 
> wrote:
>
> > I am unable to add new services to my Apache Knox installation. For 
> > example, I have created a tomcat site which hosts a static html file.
> > I have added it to Knox as a service called ‘Simple’.
> >
> > When I attempt to visit a page within one of the new services, I 
> > receive =
> > 404 page from jetty (not tomcat).
> >
> > I have attached my topology and services xml files and my log files.
> >
> > Thanks,
> >
> > Gareth
> >
>

[jira] [Updated] (KNOX-1151) Need Explicit curator-recipes dependency in pom

[Phil Zampino (JIRA)]

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

Phil Zampino updated KNOX-1151:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Need Explicit curator-recipes dependency in pom
> ---
>
> Key: KNOX-1151
> URL: https://issues.apache.org/jira/browse/KNOX-1151
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Build
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1151.patch
>
>
> In some cases, Maven is pulling versions of curator-recipes that are too old 
> to be compatible with curator-framework:4.0.0. Therefore, we must have an 
> explicit declaration for this dependency:
> org.apache.curator:curator-recipes:4.0.0



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KNOX-1151) Need Explicit curator-recipes dependency in pom

[ASF subversion and git services (JIRA)]

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

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

Commit 2b77fe102878f2c1e1e9831cfe1be3df75adfbd1 in knox's branch 
refs/heads/master from [~pzamp...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=2b77fe1 ]

KNOX-1151


> Need Explicit curator-recipes dependency in pom
> ---
>
> Key: KNOX-1151
> URL: https://issues.apache.org/jira/browse/KNOX-1151
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Build
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1151.patch
>
>
> In some cases, Maven is pulling versions of curator-recipes that are too old 
> to be compatible with curator-framework:4.0.0. Therefore, we must have an 
> explicit declaration for this dependency:
> org.apache.curator:curator-recipes:4.0.0



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Add Apache Knox Services

[larry mccay]

"Yes I edited the topology file after entering the service definitions and
then I restarted the server."

I interpret the above as:

1. added service definition to data directory
2. edited topology (which would deploy the new webapp without knowing about
the service def)
3. restart server (which would make server aware of new service def for new
topology deployments but the webapp still not)

NOTE: webapps are not recreated on restart

If the above is correct then you need to touch the topology so that it gets
redeployed.
If you haven't done that already then just do it and see if it works.

On Wed, Jan 3, 2018 at 9:20 AM, Gareth Williams 
wrote:

> Yes I edited the topology file after entering the service definitions and
> then I restarted the server.
>
> Any other suggestions?
>
> -Original Message-
> From: larry mccay [mailto:lmc...@apache.org]
> Sent: 03 January 2018 13:15
> To: dev@knox.apache.org
> Subject: Re: Add Apache Knox Services
>
> It all looks okay to me.
> You may need to touch the sandbox.xml file.
>
> If you happen to have had it configured in the topology before you added
> the service definition AND restarted then the generated webapp wouldn't
> have known about the service and it wouldn't have been added to the
> gateway.xml file in the webapp.
>
> You can check that file - if you like or just touch the topology and see
> if the new deployment works.
>
> On Wed, Jan 3, 2018 at 5:47 AM, Gareth Williams 
> wrote:
>
> > I am unable to add new services to my Apache Knox installation. For
> > example, I have created a tomcat site which hosts a static html file.
> > I have added it to Knox as a service called ‘Simple’.
> >
> > When I attempt to visit a page within one of the new services, I
> > receive =
> > 404 page from jetty (not tomcat).
> >
> > I have attached my topology and services xml files and my log files.
> >
> > Thanks,
> >
> > Gareth
> >
>

RE: Add Apache Knox Services

[Gareth Williams]

Yes I edited the topology file after entering the service definitions and then 
I restarted the server.

Any other suggestions?

-Original Message-
From: larry mccay [mailto:lmc...@apache.org] 
Sent: 03 January 2018 13:15
To: dev@knox.apache.org
Subject: Re: Add Apache Knox Services

It all looks okay to me.
You may need to touch the sandbox.xml file.

If you happen to have had it configured in the topology before you added the 
service definition AND restarted then the generated webapp wouldn't have known 
about the service and it wouldn't have been added to the gateway.xml file in 
the webapp.

You can check that file - if you like or just touch the topology and see if the 
new deployment works.

On Wed, Jan 3, 2018 at 5:47 AM, Gareth Williams 
wrote:

> I am unable to add new services to my Apache Knox installation. For 
> example, I have created a tomcat site which hosts a static html file.  
> I have added it to Knox as a service called ‘Simple’.
>
> When I attempt to visit a page within one of the new services, I 
> receive =
> 404 page from jetty (not tomcat).
>
> I have attached my topology and services xml files and my log files.
>
> Thanks,
>
> Gareth
>

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) 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 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 c65eee251600ac487fb2d5f7f749a0180ccf788b 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c65eee251600ac487fb2d5f7f749a0180ccf788b
Commit message: "KNOX-1145 - Upgrade Jackson due to CVE-2017-7525"
 > git rev-list c65eee251600ac487fb2d5f7f749a0180ccf788b # timeout=10
[Knox-master-patch-scan] $ /bin/bash /tmp/jenkins1991120998470368235.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:00:01 --:--:-- 0  0 
00 00 0  0  0 --:--:--  0:00:01 --:--:-- 0
curl: (52) Empty reply from server
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

Re: Add Apache Knox Services

[larry mccay]

It all looks okay to me.
You may need to touch the sandbox.xml file.

If you happen to have had it configured in the topology before you added
the service definition AND restarted then the generated webapp wouldn't
have known about the service and it wouldn't have been added to the
gateway.xml file in the webapp.

You can check that file - if you like or just touch the topology and see if
the new deployment works.

On Wed, Jan 3, 2018 at 5:47 AM, Gareth Williams 
wrote:

> I am unable to add new services to my Apache Knox installation. For
> example, I have created a tomcat site which hosts a static html file.  I
> have added it to Knox as a service called ‘Simple’.
>
> When I attempt to visit a page within one of the new services, I receive a
> 404 page from jetty (not tomcat).
>
> I have attached my topology and services xml files and my log files.
>
> Thanks,
>
> Gareth
>

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 


--
Started by timer
Started by timer
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) 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 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 c65eee251600ac487fb2d5f7f749a0180ccf788b 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c65eee251600ac487fb2d5f7f749a0180ccf788b
Commit message: "KNOX-1145 - Upgrade Jackson due to CVE-2017-7525"
 > git rev-list c65eee251600ac487fb2d5f7f749a0180ccf788b # timeout=10
[Knox-master-patch-scan] $ /bin/bash /tmp/jenkins5521207326177730969.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 --:--:-- --:--:-- --:--:-- 0100 
982960 982960 0  72722  0 --:--:--  0:00:01 --:--:-- 72704100  
255k0  255k0 0   119k  0 --:--:--  0:00:02 --:--:--  119k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure