Date   

Re: [OpenDaylight TSC] CSIT status in proposed topic:neon-mri ("Weather Item" TSC-132)

Michael Vorburger <vorburger@...>
 

-SFC but +aaa & Tom & Robert,

On Tue, Oct 9, 2018 at 6:35 PM Michael Vorburger <vorburger@...> wrote:
On Tue, Oct 9, 2018 at 6:18 PM Jamo Luhrsen <jluhrsen@...> wrote:
+netconf, +sfc

On 10/9/18 8:45 AM, Michael Vorburger wrote:
> [starting a new thread as we're now moving from netvirt to general, Cc TSC]
>
> With the build problem below in netvirt having been fixed a few ago today (by Stephen; thank you!), we have now finally
> reached the stage where we have a passing multipatch quick build for Neon-MRI in
> https://jira.opendaylight.org/browse/TSC-132, and can run CSIT on it. (We do not however have a passing full non-quick
> build just yet.)
>
> Jamo, https://jenkins.opendaylight.org/releng/view/integration/job/integration-multipatch-test-neon/62/ has a lot of red
> though, want to and add people/lists of any affected projects which should look at this now?

yeah, something basic is broken. from the CSIT level it looks like restconf
is broken, where there is no ability to open a connection on port 8181.

but, looking at a karaf.log, I think something even more basic is broken,
maybe in SFC?

2018-10-09T12:38:24,657 | ERROR | pool-1-thread-2  | BootFeaturesInstaller            | 8 -
org.apache.karaf.features.core - 4.1.5 | Error installing boot features
org.apache.karaf.features.internal.util.MultiException: Error:
        Unable to create resource for bundle mvn:org.opendaylight.sfc/sfc-sb-rest/0.9.0-SNAPSHOT

Caused by: org.osgi.framework.BundleException: Unable to build resource for mvn:org.opendaylight.sfc/sfc-sb-rest/0.9.0-SNAPSHOT: Duplicate import: org.opendaylight.yangtools.util.concurrent


This should have been seen by SFT when locally running (without -Pq) to prepare this... perhaps running CSIT on the quick build is actually premature, and what we really should do is focus on getting a full build to pass, and only then run CSIT? I'll kick a new one off shortly, and keep updating https://jira.opendaylight.org/browse/TSC-132.

Jamo and Ijust had a look at https://jenkins.opendaylight.org/releng/view/integration/job/integration-multipatch-test-neon/63/, and he from there finds https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/aaa-csit-1node-authn-all-neon/59/odl_1/odl1_karaf.log.gz with this new beauty, looks like some problem in AAA re. BouncyCastle version?! The SFT in AAA should have caught this, but apparently didn't... perhaps it only appears in an integration/distribution Karaf? Tom or Robert, is this something you would be willing to dig more into?
2018-10-09T19:48:59,694 | ERROR | pool-1-thread-2  | BootFeaturesInstaller            | 8 - org.apache.karaf.features.core - 4.1.5 | Error installing boot features
org.osgi.service.resolver.ResolutionException: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=odl-integration-compatible-with-all; type=karaf.feature; version="[0.10.0.SNAPSHOT,0.10.0.SNAPSHOT]"; filter:="(&(osgi.identity=odl-integration-compatible-with-all)(type=karaf.feature)(version>=0.10.0.SNAPSHOT)(version<=0.10.0.SNAPSHOT))" [caused by: Unable to resolve odl-integration-compatible-with-all/0.10.0.SNAPSHOT: missing requirement [odl-integration-compatible-with-all/0.10.0.SNAPSHOT] osgi.identity; osgi.identity=odl-sfc-ovs; type=karaf.feature; version="[0.9.0.SNAPSHOT,0.9.0.SNAPSHOT]" [caused by: Unable to resolve odl-sfc-ovs/0.9.0.SNAPSHOT: missing requirement [odl-sfc-ovs/0.9.0.SNAPSHOT] osgi.identity; osgi.identity=org.opendaylight.sfc.ovs; type=osgi.bundle; version="[0.9.0.SNAPSHOT,0.9.0.SNAPSHOT]"; resolution:=mandatory [caused by: Unable to resolve org.opendaylight.sfc.ovs/0.9.0.SNAPSHOT: missing requirement [org.opendaylight.sfc.ovs/0.9.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.opendaylight.ovsdb.southbound)(version>=1.8.0)(!(version>=2.0.0)))" [caused by: Unable to resolve org.opendaylight.ovsdb.southbound-impl/1.8.0.SNAPSHOT: missing requirement [org.opendaylight.ovsdb.southbound-impl/1.8.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.opendaylight.ovsdb.lib)(version>=1.8.0)(!(version>=2.0.0)))" [caused by: Unable to resolve org.opendaylight.ovsdb.library/1.8.0.SNAPSHOT: missing requirement [org.opendaylight.ovsdb.library/1.8.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.opendaylight.aaa.cert.api)(version>=0.9.0)(!(version>=1.0.0)))" [caused by: Unable to resolve org.opendaylight.aaa.cert/0.9.0.SNAPSHOT: missing requirement [org.opendaylight.aaa.cert/0.9.0.SNAPSHOT] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.bouncycastle.asn1)(version>=1.60.0)(!(version>=2.0.0)))"]]]]]]
	at org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42) ~[?:?]
	at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:391) ~[?:?]
	at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:377) ~[?:?]
	at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:349) ~[?:?]
	at org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:218) ~[?:?]
	at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:291) ~[?:?]
	at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1248) ~[?:?]
	at org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$1(FeaturesServiceImpl.java:1147) ~[?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?] 

from this log:
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/aaa-csit-1node-authn-all-neon/58/odl_1/odl1_karaf.log.gz

yeah, seeing the same thing in the netconf job.

JamO

> Tx,
> M.
> --
> Michael Vorburger, Red Hat
> vorburger@... <mailto:vorburger@...> | IRC: vorburger @freenode | ~ = http://vorburger.ch
> <http://vorburger.ch/>
>
>
> ---------- Forwarded message ---------
> From: *Vishal Thapar* <vthapar@... <mailto:vthapar@...>>
> Date: Tue, Oct 9, 2018 at 7:52 AM
> Subject: Re: [netvirt-dev] NETVIRT-1425 netvirt build failure in proposed topic:neon-mri ("Weather Item" TSC-132)
> To: Michael Vorburger <vorburger@... <mailto:vorburger@...>>
> Cc: Sam Hague <shague@... <mailto:shague@...>>, Stephen Kitt <skitt@... <mailto:skitt@...>>,
> odl netvirt dev <netvirt-dev@... <mailto:netvirt-dev@...>>
>
>
>
>
> On Tue, Oct 9, 2018 at 7:00 AM Michael Vorburger <vorburger@... <mailto:vorburger@...>> wrote:
>
>     On Mon, Oct 8, 2018 at 10:25 PM Sam Hague <shague@... <mailto:shague@...>> wrote:
>
>         thanks Vishal! Do we want to remove the wip now?
>
>         Where do we stand on the full multipatch and not the fast? I know the OSGI patch never passed SFT since there
>         was always a missing injection somewhere.
>
>     Latest status now tracked on https://jira.opendaylight.org/browse/TSC-132 - summary: Until 1/2h ago, Neutron was
>     broken on Neon-MRI; that is now fixed (full details in NEUTRON-197
>     <https://jira.opendaylight.org/browse/NEUTRON-197> & NEUTRON-200 <https://jira.opendaylight.org/browse/NEUTRON-200>;
>     what a PITA), and if we could get a passing quick or even better full build, we should start running CSITs for
>     Neon-MRI to see how things are looking.
>
>         On Mon, Oct 8, 2018 at 6:50 AM Vishal Thapar <vthapar@... <mailto:vthapar@...>> wrote:
>
>             Netvirt passing now:
>
>             https://git.opendaylight.org/gerrit/#/c/76476/
>
>
>     but https://jenkins.opendaylight.org/releng/view/integration/job/integration-multipatch-test-neon/60/ failed, see
>     https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/integration-multipatch-test-neon/60/console.log.gz, it's
>     the blueprint-maven-plugin problem from https://jira.opendaylight.org/browse/ODLPARENT-167 hitting
>     neutronvpn-impl... odlparent 4.0.2 instead of 4.0.0 should have fixed that - huh?
>
>     I had a bit of a look, and noticed that it ran blueprint-maven-plugin:1.4.0 - that is wrong, it should be 1.10.0 ...
>     I can't quite see why though, because neutronvpn-impl uses org.opendaylight.mdsal:binding-parent, via
>     netvirt:binding-parent, which at 3.0.0-SNAPSHOT that
>     https://git.opendaylight.org/gerrit/#/c/76476/7/commons/binding-parent/pom.xml is on already has odlparent 4.0.2...
>     hm. BTW: You should switch mdsal 3.0.0-SNAPSHOT, but I don't think it will help for this problem (but it will avoid
>     others after we're past this).
>
> Answer to this question at least is in the very file yo mentioned which has following entry further down:
>            <!-- Support Blueprint XML construction using annotations -->
>            <groupId>org.apache.aries.blueprint</groupId>
>            <artifactId>blueprint-maven-plugin</artifactId>
>            <version>1.4.0</version>
>            <configuration>
> I tried with version removed and set to 1.10.0 both, neither helped with this particular failure.
>
>
>     Very curious though that the previous
>     https://jenkins.opendaylight.org/releng/job/integration-multipatch-test-neon/59/ passes - I can't quite explain that.
>
>             On Mon, Oct 8, 2018 at 2:03 PM Vishal Thapar <vthapar@... <mailto:vthapar@...>> wrote:
>
>                 Working on it. Revision needs to change. I'll also pull in Sam's OSGI-INF changes into this so we have
>                 single patch for all neon-mri changes.
>
>                 On Sun, Oct 7, 2018 at 5:18 AM Michael Vorburger <vorburger@... <mailto:vorburger@...>> wrote:
>
>                     Stephen, Sam,
>
>                     https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/integration-multipatch-test-neon/56/console.log.gz
>                     now fails in netvirt - will you look into and update https://git.opendaylight.org/gerrit/#/c/76476/ ?
>
>                     [ERROR] /w/workspace/integration-multipatch-test-neon/patch_tester/netvirt/aclservice/impl/src/main/java/org/opendaylight/netvirt/aclservice/listeners/AclInterfaceStateListener.java:[29,88] package org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.iana._if.type.rev140508 does not exist
>                     [ERROR] /w/workspace/integration-multipatch-test-neon/patch_tester/netvirt/aclservice/impl/src/main/java/org/opendaylight/netvirt/aclservice/listeners/AclInterfaceStateListener.java:[91,14] cannot find symbol
>                        symbol:   class L2vlan
>                        location: class org.opendaylight.netvirt.aclservice.listeners.AclInterfaceStateListener
>                     [ERROR] /w/workspace/integration-multipatch-test-neon/patch_tester/netvirt/aclservice/impl/src/main/java/org/opendaylight/netvirt/aclservice/listeners/AclInterfaceStateListener.java:[121,41] cannot find symbol
>                        symbol:   class L2vlan
>                        location: class org.opendaylight.netvirt.aclservice.listeners.AclInterfaceStateListener
>                     [ERROR] /w/workspace/integration-multipatch-test-neon/patch_tester/netvirt/aclservice/impl/src/main/java/org/opendaylight/netvirt/aclservice/listeners/AclInterfaceStateListener.java:[130,14] cannot find symbol
>                        symbol:   class L2vlan
>                        location: class org.opendaylight.netvirt.aclservice.listeners.AclInterfaceStateListener
>                     [INFO] 4 errors
>
>                     Tx,
>                     M.
>                     --
>                     Michael Vorburger, Red Hat
>                     vorburger@... <mailto:vorburger@...> | IRC: vorburger @freenode | ~ =
>                     http://vorburger.ch <http://vorburger.ch/>
>                     _______________________________________________
>                     netvirt-dev mailing list
>                     netvirt-dev@... <mailto:netvirt-dev@...>
>                     https://lists.opendaylight.org/mailman/listinfo/netvirt-dev
>
>
> _______________________________________________
> TSC mailing list
> TSC@...
> https://lists.opendaylight.org/mailman/listinfo/tsc


MoM from today's Kernel projects call

Michael Vorburger <vorburger@...>
 


MoM from today's Kernel projects call

Michael Vorburger <vorburger@...>
 


Re: [controller-dev] aaa build failure in proposed topic:neon-mri ("Weather Item" TSC-132)

Robert Varga
 

On 23/09/2018 17:33, Michael Vorburger wrote:
On Sun, Sep 23, 2018 at 3:21 PM Tom Pantelis <tompantelis@gmail.com
<mailto:tompantelis@gmail.com>> wrote:

On Sun, Sep 23, 2018 at 7:26 AM Michael Vorburger
<vorburger@redhat.com <mailto:vorburger@redhat.com>> wrote:

Dear maintainers of project aaa,

While verifying the proposed cross-projects changes on managed
topic:neon-mri together, your project failed to build; please
see
https://jenkins.opendaylight.org/releng/view/integration/job/integration-multipatch-test-neon/26/console.

IMHO this is blocking topic:neon-mri / TSC-132 and one of us
should see how we can sort this out:

Running org.opendaylight.odlparent.featuretest.SingleFeatureTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
315.015 sec <<< FAILURE! - in
org.opendaylight.odlparent.featuretest.SingleFeatureTest
installFeatureCatchAndLog(org.opendaylight.odlparent.featuretest.SingleFeatureTest)[repoUrl:
file:/w/workspace/integration-multipatch-test-neon/patch_tester/aaa/features/odl-aaa-password-service/target/feature/feature.xml,
Feature: odl-aaa-password-service 0.9.0.SNAPSHOT]  Time elapsed:
314.722 sec  <<< ERROR!
org.awaitility.core.ConditionTimeoutException: Condition with
alias 'checkBundleDiagInfos' didn't complete within 300 seconds
because lambda expression in
org.opendaylight.odlparent.bundlestest.lib.TestBundleDiag:
expected system either ready with all bundles Active, or
Stopping or Failure (but not still booting in GracePeriod,
Waiting, Starting, Unknown;but just Resolved and some
exceptional Installed OK) but was <diag: Booting {Installed=0,
Resolved=5, Unknown=0, GracePeriod=1, Waiting=0, Starting=0,
Active=101, Stopping=0, Failure=0}
1. NOK
org.opendaylight.aaa.password-service-impl:0.9.0.SNAPSHOT: OSGi
state = Active, Karaf bundleState = GracePeriod, due to: Blueprint
9/23/18 10:55 AM
Missing dependencies: 
(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://opendaylight.org/xmlns/blueprint/v1.0.0)) 
>.


This is b/c https://git.opendaylight.org/gerrit/#/c/74964/ moved the
aaa-password-service BP xml file under OSGI-INF/blueprint. However
the feature does not pull in the ODL blueprint bundles, either
directly or indirectly via odl-mdsal-broker-local. 
So it either needs to pull in odl-mdsal-broker-local or we create a
feature for the ODL blueprint bundle. For the short-term, that patch
doesn't need to
move  the BP xml file for the MRI version bumps so we could put it
back under org/opendaylight/blueprint for now and address it in
another patch.


I see. For the very short-term and to unblock topic:neon-mri (I'm
curious to see how far we can get the multipatch job to progress by all
working together this week!) I agree and too would go for the latter
and leave them in org/opendaylight/blueprint instead of moving them
to OSGI-INF/blueprint in c/74964 (NB not
just password-service-blueprint.xml but all BP XML).

Robert, as the author of c/74964 would you like to amend it to do so? If
you don't have time but confirm that you agree this is what should be
done, then I'm happy to do this as well, in order to unblock.
Done.

But given that we want to converge on OSGI-INF/blueprint (and explicitly
ask projects in the migration documentation on
https://wiki.opendaylight.org/view/Neon_platform_upgrade#Blueprint_declarations
...) I think it would be useful to do this uniformely soon-ish, so let's
make a plan for that as well, in parallel to fixing the short term? I
should be easy enough to raise a change in controller to have a new
odl-blueprint feature if that's what we want (and I'm happy to), but...
do we really want to? Would you then want to add that explicitly
to odl-aaa-password-service, and elsewhere where we hit this problem? I
don't really understand how it's possible for a bundle to use ODL
extensions in its BP XML yet not already depend on the feature that
currently brings it along (odl-mdsal-broker-local, from wha you write) -
what am I missing? You wouldn't want to just make
odl-aaa-password-service dependant on odl-mdsal-broker-local ?
Tom's email has the details. Yes, we want a new feature, no
odl-mdsal-broker-local is an overkill, yes, we want to move the
blueprints (because that change is good), no we do not need to do in in
the MRI window :)

Regards,
Robert


Re: [controller-dev] aaa build failure in proposed topic:neon-mri ("Weather Item" TSC-132)

Tom Pantelis
 



On Sun, Sep 23, 2018 at 11:34 AM Michael Vorburger <vorburger@...> wrote:
On Sun, Sep 23, 2018 at 3:21 PM Tom Pantelis <tompantelis@...> wrote:
On Sun, Sep 23, 2018 at 7:26 AM Michael Vorburger <vorburger@...> wrote:
Dear maintainers of project aaa,

While verifying the proposed cross-projects changes on managed topic:neon-mri together, your project failed to build; please see https://jenkins.opendaylight.org/releng/view/integration/job/integration-multipatch-test-neon/26/console.

IMHO this is blocking topic:neon-mri / TSC-132 and one of us should see how we can sort this out:

Running org.opendaylight.odlparent.featuretest.SingleFeatureTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 315.015 sec <<< FAILURE! - in org.opendaylight.odlparent.featuretest.SingleFeatureTest
installFeatureCatchAndLog(org.opendaylight.odlparent.featuretest.SingleFeatureTest)[repoUrl: file:/w/workspace/integration-multipatch-test-neon/patch_tester/aaa/features/odl-aaa-password-service/target/feature/feature.xml, Feature: odl-aaa-password-service 0.9.0.SNAPSHOT]  Time elapsed: 314.722 sec  <<< ERROR!
org.awaitility.core.ConditionTimeoutException: Condition with alias 'checkBundleDiagInfos' didn't complete within 300 seconds because lambda expression in org.opendaylight.odlparent.bundlestest.lib.TestBundleDiag: expected system either ready with all bundles Active, or Stopping or Failure (but not still booting in GracePeriod, Waiting, Starting, Unknown;but just Resolved and some exceptional Installed OK) but was <diag: Booting {Installed=0, Resolved=5, Unknown=0, GracePeriod=1, Waiting=0, Starting=0, Active=101, Stopping=0, Failure=0}
1. NOK org.opendaylight.aaa.password-service-impl:0.9.0.SNAPSHOT: OSGi state = Active, Karaf bundleState = GracePeriod, due to: Blueprint
9/23/18 10:55 AM
Missing dependencies: 
(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://opendaylight.org/xmlns/blueprint/v1.0.0)) 
>.

This is b/c https://git.opendaylight.org/gerrit/#/c/74964/ moved the aaa-password-service BP xml file under OSGI-INF/blueprint. However the feature does not pull in the ODL blueprint bundles, either directly or indirectly via odl-mdsal-broker-local. 
So it either needs to pull in odl-mdsal-broker-local or we create a feature for the ODL blueprint bundle. For the short-term, that patch doesn't need to
move  the BP xml file for the MRI version bumps so we could put it back under org/opendaylight/blueprint for now and address it in another patch.

I see. For the very short-term and to unblock topic:neon-mri (I'm curious to see how far we can get the multipatch job to progress by all working together this week!) I agree and too would go for the latter and leave them in org/opendaylight/blueprint instead of moving them to OSGI-INF/blueprint in c/74964 (NB not just password-service-blueprint.xml but all BP XML).

Robert, as the author of c/74964 would you like to amend it to do so? If you don't have time but confirm that you agree this is what should be done, then I'm happy to do this as well, in order to unblock.
 
But given that we want to converge on OSGI-INF/blueprint (and explicitly ask projects in the migration documentation on https://wiki.opendaylight.org/view/Neon_platform_upgrade#Blueprint_declarations ...) I think it would be useful to do this uniformely soon-ish, so let's make a plan for that as well, in parallel to fixing the short term?

I started that a while ago in mdsal https://git.opendaylight.org/gerrit/#/c/75528/. But it needed odlparent 4.0.0 to remove the Import{Export}-Service headers. I also have a controller draft patch to follow. However that is running into the same issue with the missing ODL BP NamespaceHandler. It's interesting that we didn't see an issue before with the files under org/opendaylight/blueprint b/c there was no BP extender triggered to try to load them, which wasn't good b/c we weren't actually testing the BP wiring during SFT.
 
I should be easy enough to raise a change in controller to have a new odl-blueprint feature if that's what we want (and I'm happy to), but... do we really want to? Would you then want to add that explicitly to odl-aaa-password-service, and elsewhere where we hit this problem? I don't really understand how it's possible for a bundle to use ODL extensions in its BP XML yet not already depend on the feature that currently brings it along (odl-mdsal-broker-local, from wha you write) - what am I missing? You wouldn't want to just make odl-aaa-password-service dependant on odl-mdsal-broker-local ?

We're going to have to separate the ODL blueprint bundle to it's own feature and move it out of the controller so mdsal can use it - either it's own project or move it into mdsal. But first, in the ODL blueprint bundle, we need to remove the dependencies on the controller APIs. 
 


Re: [controller-dev] aaa build failure in proposed topic:neon-mri ("Weather Item" TSC-132)

Michael Vorburger <vorburger@...>
 

On Sun, Sep 23, 2018 at 3:21 PM Tom Pantelis <tompantelis@...> wrote:
On Sun, Sep 23, 2018 at 7:26 AM Michael Vorburger <vorburger@...> wrote:
Dear maintainers of project aaa,

While verifying the proposed cross-projects changes on managed topic:neon-mri together, your project failed to build; please see https://jenkins.opendaylight.org/releng/view/integration/job/integration-multipatch-test-neon/26/console.

IMHO this is blocking topic:neon-mri / TSC-132 and one of us should see how we can sort this out:

Running org.opendaylight.odlparent.featuretest.SingleFeatureTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 315.015 sec <<< FAILURE! - in org.opendaylight.odlparent.featuretest.SingleFeatureTest
installFeatureCatchAndLog(org.opendaylight.odlparent.featuretest.SingleFeatureTest)[repoUrl: file:/w/workspace/integration-multipatch-test-neon/patch_tester/aaa/features/odl-aaa-password-service/target/feature/feature.xml, Feature: odl-aaa-password-service 0.9.0.SNAPSHOT]  Time elapsed: 314.722 sec  <<< ERROR!
org.awaitility.core.ConditionTimeoutException: Condition with alias 'checkBundleDiagInfos' didn't complete within 300 seconds because lambda expression in org.opendaylight.odlparent.bundlestest.lib.TestBundleDiag: expected system either ready with all bundles Active, or Stopping or Failure (but not still booting in GracePeriod, Waiting, Starting, Unknown;but just Resolved and some exceptional Installed OK) but was <diag: Booting {Installed=0, Resolved=5, Unknown=0, GracePeriod=1, Waiting=0, Starting=0, Active=101, Stopping=0, Failure=0}
1. NOK org.opendaylight.aaa.password-service-impl:0.9.0.SNAPSHOT: OSGi state = Active, Karaf bundleState = GracePeriod, due to: Blueprint
9/23/18 10:55 AM
Missing dependencies: 
(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://opendaylight.org/xmlns/blueprint/v1.0.0)) 
>.

This is b/c https://git.opendaylight.org/gerrit/#/c/74964/ moved the aaa-password-service BP xml file under OSGI-INF/blueprint. However the feature does not pull in the ODL blueprint bundles, either directly or indirectly via odl-mdsal-broker-local. 
So it either needs to pull in odl-mdsal-broker-local or we create a feature for the ODL blueprint bundle. For the short-term, that patch doesn't need to
move  the BP xml file for the MRI version bumps so we could put it back under org/opendaylight/blueprint for now and address it in another patch.

I see. For the very short-term and to unblock topic:neon-mri (I'm curious to see how far we can get the multipatch job to progress by all working together this week!) I agree and too would go for the latter and leave them in org/opendaylight/blueprint instead of moving them to OSGI-INF/blueprint in c/74964 (NB not just password-service-blueprint.xml but all BP XML).

Robert, as the author of c/74964 would you like to amend it to do so? If you don't have time but confirm that you agree this is what should be done, then I'm happy to do this as well, in order to unblock.
 
But given that we want to converge on OSGI-INF/blueprint (and explicitly ask projects in the migration documentation on https://wiki.opendaylight.org/view/Neon_platform_upgrade#Blueprint_declarations ...) I think it would be useful to do this uniformely soon-ish, so let's make a plan for that as well, in parallel to fixing the short term? I should be easy enough to raise a change in controller to have a new odl-blueprint feature if that's what we want (and I'm happy to), but... do we really want to? Would you then want to add that explicitly to odl-aaa-password-service, and elsewhere where we hit this problem? I don't really understand how it's possible for a bundle to use ODL extensions in its BP XML yet not already depend on the feature that currently brings it along (odl-mdsal-broker-local, from wha you write) - what am I missing? You wouldn't want to just make odl-aaa-password-service dependant on odl-mdsal-broker-local ?


Re: [controller-dev] aaa build failure in proposed topic:neon-mri ("Weather Item" TSC-132)

Tom Pantelis
 



On Sun, Sep 23, 2018 at 7:26 AM Michael Vorburger <vorburger@...> wrote:
Dear maintainers of project aaa,

While verifying the proposed cross-projects changes on managed topic:neon-mri together, your project failed to build; please see https://jenkins.opendaylight.org/releng/view/integration/job/integration-multipatch-test-neon/26/console.

IMHO this is blocking topic:neon-mri / TSC-132 and one of us should see how we can sort this out:

Running org.opendaylight.odlparent.featuretest.SingleFeatureTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 315.015 sec <<< FAILURE! - in org.opendaylight.odlparent.featuretest.SingleFeatureTest
installFeatureCatchAndLog(org.opendaylight.odlparent.featuretest.SingleFeatureTest)[repoUrl: file:/w/workspace/integration-multipatch-test-neon/patch_tester/aaa/features/odl-aaa-password-service/target/feature/feature.xml, Feature: odl-aaa-password-service 0.9.0.SNAPSHOT]  Time elapsed: 314.722 sec  <<< ERROR!
org.awaitility.core.ConditionTimeoutException: Condition with alias 'checkBundleDiagInfos' didn't complete within 300 seconds because lambda expression in org.opendaylight.odlparent.bundlestest.lib.TestBundleDiag: expected system either ready with all bundles Active, or Stopping or Failure (but not still booting in GracePeriod, Waiting, Starting, Unknown;but just Resolved and some exceptional Installed OK) but was <diag: Booting {Installed=0, Resolved=5, Unknown=0, GracePeriod=1, Waiting=0, Starting=0, Active=101, Stopping=0, Failure=0}
1. NOK org.opendaylight.aaa.password-service-impl:0.9.0.SNAPSHOT: OSGi state = Active, Karaf bundleState = GracePeriod, due to: Blueprint
9/23/18 10:55 AM
Missing dependencies: 
(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://opendaylight.org/xmlns/blueprint/v1.0.0)) 
>.

This is b/c https://git.opendaylight.org/gerrit/#/c/74964/ moved the aaa-password-service BP xml file under OSGI-INF/blueprint. However the feature does not pull in the ODL blueprint bundles, either directly or indirectly via odl-mdsal-broker-local. 
So it either needs to pull in odl-mdsal-broker-local or we create a feature for the ODL blueprint bundle. For the short-term, that patch doesn't need to
move  the BP xml file for the MRI version bumps so we could put it back under org/opendaylight/blueprint for now and address it in another patch.
 
_______________________________________________
controller-dev mailing list
controller-dev@...
https://lists.opendaylight.org/mailman/listinfo/controller-dev


aaa build failure in proposed topic:neon-mri ("Weather Item" TSC-132)

Michael Vorburger <vorburger@...>
 

Dear maintainers of project aaa,

While verifying the proposed cross-projects changes on managed topic:neon-mri together, your project failed to build; please see https://jenkins.opendaylight.org/releng/view/integration/job/integration-multipatch-test-neon/26/console.

IMHO this is blocking topic:neon-mri / TSC-132 and one of us should see how we can sort this out:

Running org.opendaylight.odlparent.featuretest.SingleFeatureTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 315.015 sec <<< FAILURE! - in org.opendaylight.odlparent.featuretest.SingleFeatureTest
installFeatureCatchAndLog(org.opendaylight.odlparent.featuretest.SingleFeatureTest)[repoUrl: file:/w/workspace/integration-multipatch-test-neon/patch_tester/aaa/features/odl-aaa-password-service/target/feature/feature.xml, Feature: odl-aaa-password-service 0.9.0.SNAPSHOT]  Time elapsed: 314.722 sec  <<< ERROR!
org.awaitility.core.ConditionTimeoutException: Condition with alias 'checkBundleDiagInfos' didn't complete within 300 seconds because lambda expression in org.opendaylight.odlparent.bundlestest.lib.TestBundleDiag: expected system either ready with all bundles Active, or Stopping or Failure (but not still booting in GracePeriod, Waiting, Starting, Unknown;but just Resolved and some exceptional Installed OK) but was <diag: Booting {Installed=0, Resolved=5, Unknown=0, GracePeriod=1, Waiting=0, Starting=0, Active=101, Stopping=0, Failure=0}
1. NOK org.opendaylight.aaa.password-service-impl:0.9.0.SNAPSHOT: OSGi state = Active, Karaf bundleState = GracePeriod, due to: Blueprint
9/23/18 10:55 AM
Missing dependencies: 
(&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://opendaylight.org/xmlns/blueprint/v1.0.0)) 
>.

Yours sincerely,





Re: Migrate AAA docs to AAA project

Thanh Ha <thanh.ha@...>
 

On Sat, Sep 8, 2018 at 8:27 PM Thanh Ha <thanh.ha@...> wrote:
Hi aaa-dev,

I've submitted a few patches to migrate the AAA documentation into the AAA project under the aaa-docs topic here:


Once merged we can activate the project specific docs job. This allows project specific docs to exist directly inside of their project repo and the ODL docs project can link to the docs via intersphinx linking. This should make the documentation process more simplified moving forward.

Thanks for merging those patches. AAA docs are now available at this location https://docs.opendaylight.org/projects/aaa and the documentation will link to that moving forward.

I've submitted a patch to releng/builder to activate the aaa jobs here https://git.opendaylight.org/gerrit/75956

Finally aaa's RTD project is located at https://readthedocs.org/dashboard/odl-aaa if any aaa committers would like to be added as a maintainer in RTD please privately email me your RTD userid.

Cheers,
Thanh


Migrate AAA docs to AAA project

Thanh Ha <thanh.ha@...>
 

Hi aaa-dev,

I've submitted a few patches to migrate the AAA documentation into the AAA project under the aaa-docs topic here:


Once merged we can activate the project specific docs job. This allows project specific docs to exist directly inside of their project repo and the ODL docs project can link to the docs via intersphinx linking. This should make the documentation process more simplified moving forward.

Regards,
Thanh


MoM from today's Kernel Projects call

Michael Vorburger <vorburger@...>
 

Hello,

Here are the MoM from today's Kernel Projects call :

* Meeting ended Tue Sep  4 16:28:39 2018 UTC

We also had a question: Ryan used to used to record the Zoom meeting, AFAIK. I'm not sure if anyone ever listened to any those (nor how to actually do recordings). I certainly never did. AFAIK, no other weekly ODL project meetings do this either (or not anymore). Therefore, does anyone object to ditching that practice, and not record the weekly kernel project meeting anymore? We of course still will, diligently, keep minutes (and send them out in weekly emails like this one).

Tx,
M.
--
Michael Vorburger, Red Hat
vorburger@... | IRC: vorburger @freenode | ~ = http://vorburger.ch


Re: master of c/73991 Subscribe to authorization information instead of reading it

Michael Vorburger <vorburger@...>
 

On Tue, Jul 31, 2018 at 4:06 PM Tom Pantelis <tompantelis@...> wrote:
On Tue, Jul 31, 2018 at 8:36 AM, Michael Vorburger <vorburger@...> wrote:
Tom,

I was just looking over https://git.opendaylight.org/gerrit/#/c/73991/ and noticed it's on Oxygen but on Gerrit has no link to a change on master ... was it (a) separately sumbited and is just not linked; (b) is already done differently on master; (c) still needs to be ported?

I had to manually backport it as the code in master has diverged a bit.

 
Tx,
M.
--
Michael Vorburger, Red Hat
vorburger@... | IRC: vorburger @freenode | ~ = http://vorburger.ch


Re: master of c/73991 Subscribe to authorization information instead of reading it

Tom Pantelis
 



On Tue, Jul 31, 2018 at 8:36 AM, Michael Vorburger <vorburger@...> wrote:
Tom,

I was just looking over https://git.opendaylight.org/gerrit/#/c/73991/ and noticed it's on Oxygen but on Gerrit has no link to a change on master ... was it (a) separately sumbited and is just not linked; (b) is already done differently on master; (c) still needs to be ported?

I had to manually backport it as the code in master has diverged a bit.
 

Tx,
M.
--
Michael Vorburger, Red Hat
vorburger@... | IRC: vorburger @freenode | ~ = http://vorburger.ch


master of c/73991 Subscribe to authorization information instead of reading it

Michael Vorburger <vorburger@...>
 

Tom,

I was just looking over https://git.opendaylight.org/gerrit/#/c/73991/ and noticed it's on Oxygen but on Gerrit has no link to a change on master ... was it (a) separately sumbited and is just not linked; (b) is already done differently on master; (c) still needs to be ported?

Tx,
M.
--
Michael Vorburger, Red Hat
vorburger@... | IRC: vorburger @freenode | ~ = http://vorburger.ch


Re: Getting 401 for newly created users using aaa-cli-jar

Ryan Goulding <ryandgoulding@...>
 

Awesome, glad it works well with the updated version.

Regards,

Ryan Goulding

On Wed, Jul 18, 2018 at 12:28 PM, Naveen Kumar Verma <naveen.kumar.verma@...> wrote:

Hi Ryan,

 

I too was about to mail you that we were using 0.5 version, were as current version is 0.8.

 

I have updated that and it’s working fine now.

 

Thanks for that.

And the reason for not using  idmtool is that it uses REST and we want to configure user before starting karaf.

 

 

Thanks,

Naveen

 

From: Ryan Goulding [mailto:ryandgoulding@gmail.com]
Sent: Wednesday, July 18, 2018 8:25 PM


To: Naveen Kumar Verma <naveen.kumar.verma@ericsson.com>
Cc: aaa-dev@...
Subject: Re: [Aaa-dev] Getting 401 for newly created users using aaa-cli-jar

 

Which version of code are you running?  We changed the password hashing algorithm in master, and you are using an ancient version of the cli jar that is incompatible with master.


Regards,

Ryan Goulding

 

On Tue, Jul 17, 2018 at 2:12 PM, Naveen Kumar Verma <naveen.kumar.verma@ericsson.com> wrote:

Hi Ryan,

 

I am doing just that, As I mentioned in my initial mail, I am using -a option to create the new user…

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --nu naveen -a -p naveen

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

New user created, as admin: naveen

 

Still I am getting 401.

It use to work earlier but not sure if recently something has been changed.

 

Thanks,

Naveen

 

From: Ryan Goulding [mailto:ryandgoulding@gmail.com]
Sent: Tuesday, July 17, 2018 11:38 PM


To: Naveen Kumar Verma <naveen.kumar.verma@ericsson.com>
Cc: aaa-dev@...
Subject: Re: [Aaa-dev] Getting 401 for newly created users using aaa-cli-jar

 

This tool was written for a very specific OpenStack OOO use case.  You will want to probably make the user an admin with the tool if you continue to use it (i.e., use the "-a" flag when you do newUser).  If you are using for generic interaction, use bin/idmtool.

 

Best,

Ryan


Regards,

Ryan Goulding

 

On Tue, Jul 17, 2018 at 2:06 PM, Naveen Kumar Verma <naveen.kumar.verma@ericsson.com> wrote:

Hi Ryan,

Aaa-cli-jar doesn’t specify any option to create grant or list it.

 

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --help

Unrecognized options: [--help]

Option                       Description

------                       -----------

-?, -h                       Show help

-X, --debug                  Produce execution debug output

-a                           New User(s) added with 'admin' role

--changeUser, --cu <String>  Existing user name to change password

--dbd <File: path>           databaseDirectory (default: .)

--deleteUser, --du <String>  Existing user name to delete

-l, --listUsers              List all existing users

--newUser, --nu <String>     New user to create

-p, --passwd <String>        New password

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

 

When I tried using idmtool (first time user), it got hanged when I tried to list the users itself:

 

# ~/odl_repo/integration-distribution (master)

$ /c/Python27/python.exe karaf/target/assembly/bin/idmtool admin list-users

 

 

Is there any REST uri where can I can grants existing in the system?

 

Thanks,
Naveen

 

From: Ryan Goulding [mailto:ryandgoulding@gmail.com]
Sent: Tuesday, July 17, 2018 10:42 PM
To: Naveen Kumar Verma <naveen.kumar.verma@ericsson.com>
Cc: aaa-dev@...
Subject: Re: [Aaa-dev] Getting 401 for newly created users using aaa-cli-jar

 

Have you created a grant for the user?  Otherwise, it should return 401…

 

 

On Jul 17, 2018, at 12:37 PM, Naveen Kumar Verma <naveen.kumar.verma@ericsson.com> wrote:

 

Hi all, 

 

I am trying to create users using aaa-cli-jar, the users are getting created but I am getting 401 when I try to use that user.

 

Did anything changed recently?

 

Any idea what I am doing wrong:

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . -l

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

User names:

admin

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --nu naveen -a -p naveen

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

New user created, as admin: naveen

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . -l

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

User names:

admin

naveen

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

 

# ~

$ curl -u naveen:naveen  -v -H 'Content-type: application/json' -X GET http://localhost:8181/auth/v1/users | python -mjson.tool

Note: Unnecessary use of -X or --request, GET is already inferred.

* timeout on name lookup is not supported

*   Trying ::1...

* TCP_NODELAY set

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to localhost (::1) port 8181 (#0)

* Server auth using Basic with user 'naveen'

> GET /auth/v1/users HTTP/1.1

> Host: localhost:8181

> Authorization: Basic bmF2ZWVuOm5hdmVlbg==

> User-Agent: curl/7.51.0

> Accept: */*

> Content-type: application/json

< HTTP/1.1 401 Unauthorized

< Set-Cookie: rememberMe=deleteMe; Path=/; Max-Age=0; Expires=Mon, 16-Jul-2018 16:29:04 GMT

* Authentication problem. Ignoring this.

< WWW-Authenticate: BASIC realm="application"

< Content-Length: 0

* Curl_http_done: called premature == 0

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

* Connection #0 to host localhost left intact

Expecting value: line 1 column 1 (char 0)

 

# ~

 

 

 

Thanks,

Naveen

 

 

 

 

_______________________________________________
aaa-dev mailing list
aaa-dev@...
https://lists.opendaylight.org/mailman/listinfo/aaa-dev

 

 

 



Re: Getting 401 for newly created users using aaa-cli-jar

Naveen Kumar Verma
 

Hi Ryan,

 

I too was about to mail you that we were using 0.5 version, were as current version is 0.8.

 

I have updated that and it’s working fine now.

 

Thanks for that.

And the reason for not using  idmtool is that it uses REST and we want to configure user before starting karaf.

 

 

Thanks,

Naveen

 

From: Ryan Goulding [mailto:ryandgoulding@...]
Sent: Wednesday, July 18, 2018 8:25 PM
To: Naveen Kumar Verma <naveen.kumar.verma@...>
Cc: aaa-dev@...
Subject: Re: [Aaa-dev] Getting 401 for newly created users using aaa-cli-jar

 

Which version of code are you running?  We changed the password hashing algorithm in master, and you are using an ancient version of the cli jar that is incompatible with master.


Regards,

Ryan Goulding

 

On Tue, Jul 17, 2018 at 2:12 PM, Naveen Kumar Verma <naveen.kumar.verma@...> wrote:

Hi Ryan,

 

I am doing just that, As I mentioned in my initial mail, I am using -a option to create the new user…

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --nu naveen -a -p naveen

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

New user created, as admin: naveen

 

Still I am getting 401.

It use to work earlier but not sure if recently something has been changed.

 

Thanks,

Naveen

 

From: Ryan Goulding [mailto:ryandgoulding@...]
Sent: Tuesday, July 17, 2018 11:38 PM


To: Naveen Kumar Verma <naveen.kumar.verma@...>
Cc: aaa-dev@...
Subject: Re: [Aaa-dev] Getting 401 for newly created users using aaa-cli-jar

 

This tool was written for a very specific OpenStack OOO use case.  You will want to probably make the user an admin with the tool if you continue to use it (i.e., use the "-a" flag when you do newUser).  If you are using for generic interaction, use bin/idmtool.

 

Best,

Ryan


Regards,

Ryan Goulding

 

On Tue, Jul 17, 2018 at 2:06 PM, Naveen Kumar Verma <naveen.kumar.verma@...> wrote:

Hi Ryan,

Aaa-cli-jar doesn’t specify any option to create grant or list it.

 

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --help

Unrecognized options: [--help]

Option                       Description

------                       -----------

-?, -h                       Show help

-X, --debug                  Produce execution debug output

-a                           New User(s) added with 'admin' role

--changeUser, --cu <String>  Existing user name to change password

--dbd <File: path>           databaseDirectory (default: .)

--deleteUser, --du <String>  Existing user name to delete

-l, --listUsers              List all existing users

--newUser, --nu <String>     New user to create

-p, --passwd <String>        New password

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

 

When I tried using idmtool (first time user), it got hanged when I tried to list the users itself:

 

# ~/odl_repo/integration-distribution (master)

$ /c/Python27/python.exe karaf/target/assembly/bin/idmtool admin list-users

 

 

Is there any REST uri where can I can grants existing in the system?

 

Thanks,
Naveen

 

From: Ryan Goulding [mailto:ryandgoulding@...]
Sent: Tuesday, July 17, 2018 10:42 PM
To: Naveen Kumar Verma <naveen.kumar.verma@...>
Cc: aaa-dev@...
Subject: Re: [Aaa-dev] Getting 401 for newly created users using aaa-cli-jar

 

Have you created a grant for the user?  Otherwise, it should return 401…

 

 

On Jul 17, 2018, at 12:37 PM, Naveen Kumar Verma <naveen.kumar.verma@...> wrote:

 

Hi all, 

 

I am trying to create users using aaa-cli-jar, the users are getting created but I am getting 401 when I try to use that user.

 

Did anything changed recently?

 

Any idea what I am doing wrong:

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . -l

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

User names:

admin

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --nu naveen -a -p naveen

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

New user created, as admin: naveen

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . -l

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

User names:

admin

naveen

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

 

# ~

$ curl -u naveen:naveen  -v -H 'Content-type: application/json' -X GET http://localhost:8181/auth/v1/users | python -mjson.tool

Note: Unnecessary use of -X or --request, GET is already inferred.

* timeout on name lookup is not supported

*   Trying ::1...

* TCP_NODELAY set

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to localhost (::1) port 8181 (#0)

* Server auth using Basic with user 'naveen'

> GET /auth/v1/users HTTP/1.1

> Host: localhost:8181

> Authorization: Basic bmF2ZWVuOm5hdmVlbg==

> User-Agent: curl/7.51.0

> Accept: */*

> Content-type: application/json

< HTTP/1.1 401 Unauthorized

< Set-Cookie: rememberMe=deleteMe; Path=/; Max-Age=0; Expires=Mon, 16-Jul-2018 16:29:04 GMT

* Authentication problem. Ignoring this.

< WWW-Authenticate: BASIC realm="application"

< Content-Length: 0

* Curl_http_done: called premature == 0

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

* Connection #0 to host localhost left intact

Expecting value: line 1 column 1 (char 0)

 

# ~

 

 

 

Thanks,

Naveen

 

 

 

 

_______________________________________________
aaa-dev mailing list
aaa-dev@...
https://lists.opendaylight.org/mailman/listinfo/aaa-dev

 

 

 


Re: Getting 401 for newly created users using aaa-cli-jar

Ryan Goulding <ryandgoulding@...>
 

Which version of code are you running?  We changed the password hashing algorithm in master, and you are using an ancient version of the cli jar that is incompatible with master.

Regards,

Ryan Goulding

On Tue, Jul 17, 2018 at 2:12 PM, Naveen Kumar Verma <naveen.kumar.verma@...> wrote:

Hi Ryan,

 

I am doing just that, As I mentioned in my initial mail, I am using -a option to create the new user…

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --nu naveen -a -p naveen

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

New user created, as admin: naveen

 

Still I am getting 401.

It use to work earlier but not sure if recently something has been changed.

 

Thanks,

Naveen

 

From: Ryan Goulding [mailto:ryandgoulding@gmail.com]
Sent: Tuesday, July 17, 2018 11:38 PM


To: Naveen Kumar Verma <naveen.kumar.verma@ericsson.com>
Cc: aaa-dev@...
Subject: Re: [Aaa-dev] Getting 401 for newly created users using aaa-cli-jar

 

This tool was written for a very specific OpenStack OOO use case.  You will want to probably make the user an admin with the tool if you continue to use it (i.e., use the "-a" flag when you do newUser).  If you are using for generic interaction, use bin/idmtool.

 

Best,

Ryan


Regards,

Ryan Goulding

 

On Tue, Jul 17, 2018 at 2:06 PM, Naveen Kumar Verma <naveen.kumar.verma@ericsson.com> wrote:

Hi Ryan,

Aaa-cli-jar doesn’t specify any option to create grant or list it.

 

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --help

Unrecognized options: [--help]

Option                       Description

------                       -----------

-?, -h                       Show help

-X, --debug                  Produce execution debug output

-a                           New User(s) added with 'admin' role

--changeUser, --cu <String>  Existing user name to change password

--dbd <File: path>           databaseDirectory (default: .)

--deleteUser, --du <String>  Existing user name to delete

-l, --listUsers              List all existing users

--newUser, --nu <String>     New user to create

-p, --passwd <String>        New password

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

 

When I tried using idmtool (first time user), it got hanged when I tried to list the users itself:

 

# ~/odl_repo/integration-distribution (master)

$ /c/Python27/python.exe karaf/target/assembly/bin/idmtool admin list-users

 

 

Is there any REST uri where can I can grants existing in the system?

 

Thanks,
Naveen

 

From: Ryan Goulding [mailto:ryandgoulding@gmail.com]
Sent: Tuesday, July 17, 2018 10:42 PM
To: Naveen Kumar Verma <naveen.kumar.verma@ericsson.com>
Cc: aaa-dev@...
Subject: Re: [Aaa-dev] Getting 401 for newly created users using aaa-cli-jar

 

Have you created a grant for the user?  Otherwise, it should return 401…

 

 

On Jul 17, 2018, at 12:37 PM, Naveen Kumar Verma <naveen.kumar.verma@ericsson.com> wrote:

 

Hi all, 

 

I am trying to create users using aaa-cli-jar, the users are getting created but I am getting 401 when I try to use that user.

 

Did anything changed recently?

 

Any idea what I am doing wrong:

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . -l

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

User names:

admin

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --nu naveen -a -p naveen

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

New user created, as admin: naveen

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . -l

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

User names:

admin

naveen

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

 

# ~

$ curl -u naveen:naveen  -v -H 'Content-type: application/json' -X GET http://localhost:8181/auth/v1/users | python -mjson.tool

Note: Unnecessary use of -X or --request, GET is already inferred.

* timeout on name lookup is not supported

*   Trying ::1...

* TCP_NODELAY set

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to localhost (::1) port 8181 (#0)

* Server auth using Basic with user 'naveen'

> GET /auth/v1/users HTTP/1.1

> Host: localhost:8181

> Authorization: Basic bmF2ZWVuOm5hdmVlbg==

> User-Agent: curl/7.51.0

> Accept: */*

> Content-type: application/json

< HTTP/1.1 401 Unauthorized

< Set-Cookie: rememberMe=deleteMe; Path=/; Max-Age=0; Expires=Mon, 16-Jul-2018 16:29:04 GMT

* Authentication problem. Ignoring this.

< WWW-Authenticate: BASIC realm="application"

< Content-Length: 0

* Curl_http_done: called premature == 0

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

* Connection #0 to host localhost left intact

Expecting value: line 1 column 1 (char 0)

 

# ~

 

 

 

Thanks,

Naveen

 

 

 

 

_______________________________________________
aaa-dev mailing list
aaa-dev@...
https://lists.opendaylight.org/mailman/listinfo/aaa-dev

 

 



Re: Getting 401 for newly created users using aaa-cli-jar

Naveen Kumar Verma
 

Hi Ryan,

 

I am doing just that, As I mentioned in my initial mail, I am using -a option to create the new user…

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --nu naveen -a -p naveen

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

New user created, as admin: naveen

 

Still I am getting 401.

It use to work earlier but not sure if recently something has been changed.

 

Thanks,

Naveen

 

From: Ryan Goulding [mailto:ryandgoulding@...]
Sent: Tuesday, July 17, 2018 11:38 PM
To: Naveen Kumar Verma <naveen.kumar.verma@...>
Cc: aaa-dev@...
Subject: Re: [Aaa-dev] Getting 401 for newly created users using aaa-cli-jar

 

This tool was written for a very specific OpenStack OOO use case.  You will want to probably make the user an admin with the tool if you continue to use it (i.e., use the "-a" flag when you do newUser).  If you are using for generic interaction, use bin/idmtool.

 

Best,

Ryan


Regards,

Ryan Goulding

 

On Tue, Jul 17, 2018 at 2:06 PM, Naveen Kumar Verma <naveen.kumar.verma@...> wrote:

Hi Ryan,

Aaa-cli-jar doesn’t specify any option to create grant or list it.

 

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --help

Unrecognized options: [--help]

Option                       Description

------                       -----------

-?, -h                       Show help

-X, --debug                  Produce execution debug output

-a                           New User(s) added with 'admin' role

--changeUser, --cu <String>  Existing user name to change password

--dbd <File: path>           databaseDirectory (default: .)

--deleteUser, --du <String>  Existing user name to delete

-l, --listUsers              List all existing users

--newUser, --nu <String>     New user to create

-p, --passwd <String>        New password

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

 

When I tried using idmtool (first time user), it got hanged when I tried to list the users itself:

 

# ~/odl_repo/integration-distribution (master)

$ /c/Python27/python.exe karaf/target/assembly/bin/idmtool admin list-users

 

 

Is there any REST uri where can I can grants existing in the system?

 

Thanks,
Naveen

 

From: Ryan Goulding [mailto:ryandgoulding@...]
Sent: Tuesday, July 17, 2018 10:42 PM
To: Naveen Kumar Verma <naveen.kumar.verma@...>
Cc: aaa-dev@...
Subject: Re: [Aaa-dev] Getting 401 for newly created users using aaa-cli-jar

 

Have you created a grant for the user?  Otherwise, it should return 401…

 

 

On Jul 17, 2018, at 12:37 PM, Naveen Kumar Verma <naveen.kumar.verma@...> wrote:

 

Hi all, 

 

I am trying to create users using aaa-cli-jar, the users are getting created but I am getting 401 when I try to use that user.

 

Did anything changed recently?

 

Any idea what I am doing wrong:

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . -l

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

User names:

admin

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --nu naveen -a -p naveen

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

New user created, as admin: naveen

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . -l

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

User names:

admin

naveen

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

 

# ~

$ curl -u naveen:naveen  -v -H 'Content-type: application/json' -X GET http://localhost:8181/auth/v1/users | python -mjson.tool

Note: Unnecessary use of -X or --request, GET is already inferred.

* timeout on name lookup is not supported

*   Trying ::1...

* TCP_NODELAY set

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to localhost (::1) port 8181 (#0)

* Server auth using Basic with user 'naveen'

> GET /auth/v1/users HTTP/1.1

> Host: localhost:8181

> Authorization: Basic bmF2ZWVuOm5hdmVlbg==

> User-Agent: curl/7.51.0

> Accept: */*

> Content-type: application/json

< HTTP/1.1 401 Unauthorized

< Set-Cookie: rememberMe=deleteMe; Path=/; Max-Age=0; Expires=Mon, 16-Jul-2018 16:29:04 GMT

* Authentication problem. Ignoring this.

< WWW-Authenticate: BASIC realm="application"

< Content-Length: 0

* Curl_http_done: called premature == 0

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

* Connection #0 to host localhost left intact

Expecting value: line 1 column 1 (char 0)

 

# ~

 

 

 

Thanks,

Naveen

 

 

 

 

_______________________________________________
aaa-dev mailing list
aaa-dev@...
https://lists.opendaylight.org/mailman/listinfo/aaa-dev

 

 


Re: Getting 401 for newly created users using aaa-cli-jar

Ryan Goulding <ryandgoulding@...>
 

This tool was written for a very specific OpenStack OOO use case.  You will want to probably make the user an admin with the tool if you continue to use it (i.e., use the "-a" flag when you do newUser).  If you are using for generic interaction, use bin/idmtool.

Best,
Ryan

Regards,

Ryan Goulding

On Tue, Jul 17, 2018 at 2:06 PM, Naveen Kumar Verma <naveen.kumar.verma@...> wrote:

Hi Ryan,

Aaa-cli-jar doesn’t specify any option to create grant or list it.

 

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --help

Unrecognized options: [--help]

Option                       Description

------                       -----------

-?, -h                       Show help

-X, --debug                  Produce execution debug output

-a                           New User(s) added with 'admin' role

--changeUser, --cu <String>  Existing user name to change password

--dbd <File: path>           databaseDirectory (default: .)

--deleteUser, --du <String>  Existing user name to delete

-l, --listUsers              List all existing users

--newUser, --nu <String>     New user to create

-p, --passwd <String>        New password

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

 

When I tried using idmtool (first time user), it got hanged when I tried to list the users itself:

 

# ~/odl_repo/integration-distribution (master)

$ /c/Python27/python.exe karaf/target/assembly/bin/idmtool admin list-users

 

 

Is there any REST uri where can I can grants existing in the system?

 

Thanks,
Naveen

 

From: Ryan Goulding [mailto:ryandgoulding@gmail.com]
Sent: Tuesday, July 17, 2018 10:42 PM
To: Naveen Kumar Verma <naveen.kumar.verma@ericsson.com>
Cc: aaa-dev@...
Subject: Re: [Aaa-dev] Getting 401 for newly created users using aaa-cli-jar

 

Have you created a grant for the user?  Otherwise, it should return 401…

 

 

On Jul 17, 2018, at 12:37 PM, Naveen Kumar Verma <naveen.kumar.verma@ericsson.com> wrote:

 

Hi all, 

 

I am trying to create users using aaa-cli-jar, the users are getting created but I am getting 401 when I try to use that user.

 

Did anything changed recently?

 

Any idea what I am doing wrong:

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . -l

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

User names:

admin

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --nu naveen -a -p naveen

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

New user created, as admin: naveen

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . -l

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

User names:

admin

naveen

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

 

# ~

$ curl -u naveen:naveen  -v -H 'Content-type: application/json' -X GET http://localhost:8181/auth/v1/users | python -mjson.tool

Note: Unnecessary use of -X or --request, GET is already inferred.

* timeout on name lookup is not supported

*   Trying ::1...

* TCP_NODELAY set

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to localhost (::1) port 8181 (#0)

* Server auth using Basic with user 'naveen'

> GET /auth/v1/users HTTP/1.1

> Host: localhost:8181

> Authorization: Basic bmF2ZWVuOm5hdmVlbg==

> User-Agent: curl/7.51.0

> Accept: */*

> Content-type: application/json

< HTTP/1.1 401 Unauthorized

< Set-Cookie: rememberMe=deleteMe; Path=/; Max-Age=0; Expires=Mon, 16-Jul-2018 16:29:04 GMT

* Authentication problem. Ignoring this.

< WWW-Authenticate: BASIC realm="application"

< Content-Length: 0

* Curl_http_done: called premature == 0

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

* Connection #0 to host localhost left intact

Expecting value: line 1 column 1 (char 0)

 

# ~

 

 

 

Thanks,

Naveen

 

 

 

 

_______________________________________________
aaa-dev mailing list
aaa-dev@...
https://lists.opendaylight.org/mailman/listinfo/aaa-dev

 



Re: Getting 401 for newly created users using aaa-cli-jar

Naveen Kumar Verma
 

Hi Ryan,

Aaa-cli-jar doesn’t specify any option to create grant or list it.

 

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --help

Unrecognized options: [--help]

Option                       Description

------                       -----------

-?, -h                       Show help

-X, --debug                  Produce execution debug output

-a                           New User(s) added with 'admin' role

--changeUser, --cu <String>  Existing user name to change password

--dbd <File: path>           databaseDirectory (default: .)

--deleteUser, --du <String>  Existing user name to delete

-l, --listUsers              List all existing users

--newUser, --nu <String>     New user to create

-p, --passwd <String>        New password

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

 

When I tried using idmtool (first time user), it got hanged when I tried to list the users itself:

 

# ~/odl_repo/integration-distribution (master)

$ /c/Python27/python.exe karaf/target/assembly/bin/idmtool admin list-users

 

 

Is there any REST uri where can I can grants existing in the system?

 

Thanks,
Naveen

 

From: Ryan Goulding [mailto:ryandgoulding@...]
Sent: Tuesday, July 17, 2018 10:42 PM
To: Naveen Kumar Verma <naveen.kumar.verma@...>
Cc: aaa-dev@...
Subject: Re: [Aaa-dev] Getting 401 for newly created users using aaa-cli-jar

 

Have you created a grant for the user?  Otherwise, it should return 401…

 

 

On Jul 17, 2018, at 12:37 PM, Naveen Kumar Verma <naveen.kumar.verma@...> wrote:

 

Hi all, 

 

I am trying to create users using aaa-cli-jar, the users are getting created but I am getting 401 when I try to use that user.

 

Did anything changed recently?

 

Any idea what I am doing wrong:

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . -l

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

User names:

admin

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . --nu naveen -a -p naveen

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

New user created, as admin: naveen

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

$ java -jar ~/Downloads/aaa-cli-jar-0.5.0-20170522.110416-143.jar -dbd . -l

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Checking if default entries must be created in IDM store

[main] INFO org.opendaylight.aaa.api.StoreBuilder - Found default domain in IDM store, skipping insertion of default data

User names:

admin

naveen

 

# ~/odl_repo/integration-distribution/karaf/target/assembly/data (master)

 

# ~

$ curl -u naveen:naveen  -v -H 'Content-type: application/json' -X GET http://localhost:8181/auth/v1/users | python -mjson.tool

Note: Unnecessary use of -X or --request, GET is already inferred.

* timeout on name lookup is not supported

*   Trying ::1...

* TCP_NODELAY set

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected to localhost (::1) port 8181 (#0)

* Server auth using Basic with user 'naveen'

> GET /auth/v1/users HTTP/1.1

> Host: localhost:8181

> Authorization: Basic bmF2ZWVuOm5hdmVlbg==

> User-Agent: curl/7.51.0

> Accept: */*

> Content-type: application/json

< HTTP/1.1 401 Unauthorized

< Set-Cookie: rememberMe=deleteMe; Path=/; Max-Age=0; Expires=Mon, 16-Jul-2018 16:29:04 GMT

* Authentication problem. Ignoring this.

< WWW-Authenticate: BASIC realm="application"

< Content-Length: 0

* Curl_http_done: called premature == 0

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

* Connection #0 to host localhost left intact

Expecting value: line 1 column 1 (char 0)

 

# ~

 

 

 

Thanks,

Naveen

 

 

 

 

_______________________________________________
aaa-dev mailing list
aaa-dev@...
https://lists.opendaylight.org/mailman/listinfo/aaa-dev

 

81 - 100 of 1823