Re: [onap-discuss] SO Error - ONAP 1.1

[Kapil Gupta (c)]

Hi,

We are still getting error "MSO Properties failed to initialize completely".

It will be really appreciated if someone help us on MSO errors.

Logs:-
2017-11-09 11:13:20,437||ServerService Thread Pool -- 
84|contextInitializedERROR|AvailabilityError|| MSO-RA-5210E Configuration 
error:Unknown. MSO Properties failed to initialize completely
2017-11-09 11:13:20,446||ServerService Thread Pool -- 
84|contextInitializedERROR|AvailabilityError|| MSO-GENERAL-9400E Exception: 
java.lang.NullPointerException -  at 
org.openecomp.mso.openstack.utils.CloudConfigInitializer.contextInitialized(CloudConfigInitializer.java:65)
 -at 
io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
 -at io



Thanks
Kapil
From: Gaurav Gupta (c)
Sent: 09 November 2017 14:24
To: Seshu m ; rd4...@att.com
Cc: Ramki Krishnan ; ISUKAPALLI, SASTRY S (SASTRY) 
(sas...@research.att.com) ; Sumit Verdi 
; Ramesh Tammana ; Kapil Gupta (c) 

Subject: Re: [onap-discuss] SO Error - ONAP 1.1


Rob

can you please help on this MSO Issue . Please be aware that Another windriver 
lab where ONAP is deployed on Vanila Openstack is also facing the same Error 
from MSO .



thanks
gaurav

From: Seshu m >
Sent: 08 November 2017 20:51
To: Gaurav Gupta (c); rd4...@att.com
Subject: RE: [onap-discuss] SO Error - ONAP 1.1

@Gaurav : We closed the meeting early today as the agendas were handled.
@ Rob : Could you please address the issue of Gaurav when you have time. Im 
just back from my business trip.

Best Regards,
Seshu
**
 This email and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained here in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: Gaurav Gupta (c) [guptagau...@vmware.com]
Sent: Wednesday, November 08, 2017 10:56 PM
To: Seshu m; rd4...@att.com
Subject: Re: [onap-discuss] SO Error - ONAP 1.1



Seshu , Rob



Did you have the SO Meeting today . I did not see any one when i joined  a 
little late .



Rob

would you need any more logs to check and let us know why is SO init is not 
getting completed



thanks

gaurav


From: Seshu m >
Sent: 08 November 2017 01:32:02
To: Gaurav Gupta (c); rd4...@att.com
Subject: Re: [onap-discuss] SO Error - ONAP 1.1

hi rob,
I'm on a business trip.
please help Gaurav in the issue.
Gaurav please join the so weekly meeting tomorrow. we can discuss further on 
this.

Sent from HUAWEI AnyOffice
From:Gaurav Gupta (c)
To:Radhika Kaslikar,Seshu m
Cc:onap-discuss@lists.onap.org
Date:2017-11-07 19:24:32
Subject:Re: [onap-discuss] SO Error - ONAP 1.1


Seshu , Radhika



We followed the  
https://jira.onap.org/browse/SO-208?src=confmacro
  . We pulled the Latest MSO Dockers from Nexus Repo but we are still seeing 
the error for MSO Indicating the Init not complete  .


2017-11-07 12:18:18,704||ServerService Thread Pool -- 
75|contextInitializedERROR|AvailabilityError|| MSO-RA-5210E Configuration 
error:Unknown. MSO Properties failed to initialize completely
2017-11-07 12:18:18,705||ServerService Thread Pool -- 
75|contextInitializedERROR|AvailabilityError|| MSO-GENERAL-9400E Exception: 
java.lang.NullPointerException -  at 
org.openecomp.mso.openstack.utils.CloudConfigInitializer.contextInitialized(CloudConfigInitializer.java:65)
 -at 
io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
 -at

Do let us know how to move forward on this .


thanks

gaurav




From: Radhika Kaslikar 
>
Sent: 07 November 2017 16:23
To: seshu.kuma...@huawei.com; Gaurav Gupta (c)
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] SO Error - ONAP 1.1


Hi 

[onap-discuss] Canceled event: [usecase] Subcommittee Weekly Meeting @ Mon Nov 13, 2017 7am - 8am (PST) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20171113T07
DTEND;TZID=America/Los_Angeles:20171113T08
DTSTAMP:20171110T011807Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:89b9frk2lpkddop9v7uvutev7k_r20170731t140...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=on
 ap-disc...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@lists.onap.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=al
 la.gold...@amdocs.com;X-NUM-GUESTS=0:mailto:alla.gold...@amdocs.com
RECURRENCE-ID;TZID=America/Los_Angeles:20171113T07
CLASS:PUBLIC
CREATED:20170602T223917Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 2 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/655429955\n\nOr iPhone one-tap (US Toll):  +16465588656\,655429955# or 
 +14086380968\,655429955#\n\nOr Telephone:\nDial: +1 646 558 8656 (US To
 ll) or +1 408 638 0968 (US Toll)\nMeeting ID: 655 429 955\nInternat
 ional numbers available: https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfP
 HKBvf6Vslgcsn86\n\n
LAST-MODIFIED:20171110T011807Z
LOCATION:https://zoom.us/j/655429955
SEQUENCE:2
STATUS:CANCELLED
SUMMARY:[usecase] Subcommittee Weekly Meeting
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] VNF SDK 11-10-2017 Meeting - Developer Wiki - Confluence

[Tina Tsou]

Dear all,

Talk to you this Friday.

https://wiki.onap.org/display/DW/VNF+SDK+11-10-2017+Meeting


Thank you,
Tina
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP Helpdesk #45447] [integration] Maven repo precedence issue

[Gary Wu via RT]

Thanks Jess.

All teams:  Please make sure that you are no longer building against staging 
artifacts.  If you still have dependencies on staging artifacts, please contact 
the upstream teams to make sure that they formally release those artifacts.

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Thursday, November 09, 2017 11:51 AM
To: Gary Wu 
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence issue

Dear Gary, 

We have now removed the staging as an active profile from global-settings.xml 
now and the dependencies should now be downloaded from releases. 

Thanks!
Jess

On Mon Nov 06 13:43:31 2017, gary.i...@huawei.com wrote:
> Hi Jessica,
> 
> Thanks for the investigation.  At this point in the release cycle, I 
> think the better solution now is to just completely remove staging 
> from settings.xml.  All teams should be formally releasing their 
> artifacts by now, and we should no longer be having any build 
> dependencies on staging artifacts.  This would completely eliminate 
> the precedence issue.
> 
> Thanks,
> Gary
> 
> -Original Message-
>  From: Jessica Wagantall via RT [mailto:onap- 
> helpd...@rt.linuxfoundation.org]
> Sent: Friday, November 03, 2017 6:21 PM
> To: Gary Wu 
> Cc: onap-discuss@lists.onap.org
> Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence 
> issue
> 
> Dear Gary,
> 
> I was briefly talking with Andy about this ticket.
> 
> I made a test in the sandbox in where I am changing the values that 
> global-settings have as the active profiles. Basically, this file has 
> the releases, staging, snapshot active profiles described in that 
> order. This file controls the precedence of the repos where is going 
> to do the downloads.
> 
> Here is a run on the job with that described global settings:
> https://jenkins.onap.org/sandbox/job/integration-master-version-
> manifest-release-version-java-daily/2/console
> This job downloaded the release version of oparent: 00:53:19 [INFO]
> Downloaded:
> https://nexus.onap.org/content/repositories/releases/org/onap/oparent/
> oparent/0.1.1/oparent-
> 0.1.1.pom (21 KB at 430.4 KB/sec)
> 
> I did a small test in which I removed the releases profile and the 
> download happened from the public repo:
> https://jenkins.onap.org/sandbox/job/integration-master-version-
> manifest-release-version-java-daily/6/console
> 
> Another thing that Andy mentioned, is that whenever this download 
> fails, the log will report the last place where it looked for the 
> binaries. For example, if we ask the job to look into releases and 
> then staging, if it fails it will report the failure while looking 
> into staging making the log look like it didn't looked in releases 
> even though it actually did. It just happens that maven will report 
> the failure making reference to the last profile it looked into.
> 
> Let me know if you would like to make more tests with my setup, I can 
> place the jobs in the Sandbox for us to experiment more.
> 
> Thanks!
> Jess
> 
> On Tue Oct 24 00:29:23 2017, gary.i...@huawei.com wrote:
> > This issue is still occurring and still needs LF resolution.
> >
> > Thanks,
> > Gary
> >
> > -Original Message-
> >  From: Kenny Paul via RT [mailto:onap- 
> > helpd...@rt.linuxfoundation.org]
> > Sent: Sunday, October 22, 2017 7:43 PM
> > To: Gary Wu 
> > Cc: onap-discuss@lists.onap.org
> >  Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence 
> > issue
> >
> > I’m reviewing all of the tickets in the LF IT queue that are open.
> >  Is this still an issue that needs support from IT or can this 
> > ticket be closed?
> >
> > Thanks!
> > -kenny
> >
> > On Wed Sep 06 17:18:23 2017, gary.i...@huawei.com wrote:
> > > I just noticed the issue today, but I suspect it's been happening 
> > > for a long time.
> > >
> > > Thanks,
> > > Gary
> > >
> > > -Original Message-
> > >From: Jessica Wagantall via RT [mailto:onap- 
> > > helpd...@rt.linuxfoundation.org]
> > > Sent: Wednesday, September 06, 2017 2:10 PM
> > > To: Gary Wu 
> > > Cc: onap-discuss@lists.onap.org
> > >   Subject: [ONAP Helpdesk #45447] [integration] Maven repo 
> > > precedence issue
> > >
> > > Hey Gary, quick question.. did you saw this happening the time we 
> > > released oparent 0.1.0?
> > >
> > > Thanks!
> > > Jess
> >
> >
> >
> 
> 
> 




___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [ONAP Helpdesk #45447] [integration] Maven repo precedence issue

[Jessica Wagantall via RT]

Dear Gary, 

We have now removed the staging as an active profile from global-settings.xml 
now and the dependencies should now be downloaded from releases. 

Thanks!
Jess

On Mon Nov 06 13:43:31 2017, gary.i...@huawei.com wrote:
> Hi Jessica,
> 
> Thanks for the investigation.  At this point in the release cycle, I
> think the better solution now is to just completely remove staging
> from settings.xml.  All teams should be formally releasing their
> artifacts by now, and we should no longer be having any build
> dependencies on staging artifacts.  This would completely eliminate
> the precedence issue.
> 
> Thanks,
> Gary
> 
> -Original Message-
>  From: Jessica Wagantall via RT [mailto:onap-
> helpd...@rt.linuxfoundation.org]
> Sent: Friday, November 03, 2017 6:21 PM
> To: Gary Wu 
> Cc: onap-discuss@lists.onap.org
> Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence
> issue
> 
> Dear Gary,
> 
> I was briefly talking with Andy about this ticket.
> 
> I made a test in the sandbox in where I am changing the values that
> global-settings have as the active profiles. Basically, this file has
> the releases, staging, snapshot active profiles described in that
> order. This file controls the precedence of the repos where is going
> to do the downloads.
> 
> Here is a run on the job with that described global settings:
> https://jenkins.onap.org/sandbox/job/integration-master-version-
> manifest-release-version-java-daily/2/console
> This job downloaded the release version of oparent: 00:53:19 [INFO]
> Downloaded:
> https://nexus.onap.org/content/repositories/releases/org/onap/oparent/oparent/0.1.1/oparent-
> 0.1.1.pom (21 KB at 430.4 KB/sec)
> 
> I did a small test in which I removed the releases profile and the
> download happened from the public repo:
> https://jenkins.onap.org/sandbox/job/integration-master-version-
> manifest-release-version-java-daily/6/console
> 
> Another thing that Andy mentioned, is that whenever this download
> fails, the log will report the last place where it looked for the
> binaries. For example, if we ask the job to look into releases and
> then staging, if it fails it will report the failure while looking
> into staging making the log look like it didn't looked in releases
> even though it actually did. It just happens that maven will report
> the failure making reference to the last profile it looked into.
> 
> Let me know if you would like to make more tests with my setup, I can
> place the jobs in the Sandbox for us to experiment more.
> 
> Thanks!
> Jess
> 
> On Tue Oct 24 00:29:23 2017, gary.i...@huawei.com wrote:
> > This issue is still occurring and still needs LF resolution.
> >
> > Thanks,
> > Gary
> >
> > -Original Message-
> >  From: Kenny Paul via RT [mailto:onap-
> > helpd...@rt.linuxfoundation.org]
> > Sent: Sunday, October 22, 2017 7:43 PM
> > To: Gary Wu 
> > Cc: onap-discuss@lists.onap.org
> >  Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence
> > issue
> >
> > I’m reviewing all of the tickets in the LF IT queue that are open.
> >  Is this still an issue that needs support from IT or can this ticket
> > be closed?
> >
> > Thanks!
> > -kenny
> >
> > On Wed Sep 06 17:18:23 2017, gary.i...@huawei.com wrote:
> > > I just noticed the issue today, but I suspect it's been happening
> > > for a long time.
> > >
> > > Thanks,
> > > Gary
> > >
> > > -Original Message-
> > >From: Jessica Wagantall via RT [mailto:onap-
> > > helpd...@rt.linuxfoundation.org]
> > > Sent: Wednesday, September 06, 2017 2:10 PM
> > > To: Gary Wu 
> > > Cc: onap-discuss@lists.onap.org
> > >   Subject: [ONAP Helpdesk #45447] [integration] Maven repo
> > > precedence
> > > issue
> > >
> > > Hey Gary, quick question.. did you saw this happening the time we
> > > released oparent 0.1.0?
> > >
> > > Thanks!
> > > Jess
> >
> >
> >
> 
> 
> 



___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [OOM] Request for new committer on OOM - Borislav Glozman

[Alexis de Talhouët]

+1 

Well deserved! Thanks for the major contribution.

> On Nov 9, 2017, at 12:16 PM, Jessica Wagantall 
>  wrote:
> 
> (Adding Yury)
> 
> Dear OOM committers, 
> 
> Please let us know if this request looks good to you so that David can help 
> us bringing this to the TSC members. 
> 
> Thansk!
> Jess
> 
> On Wed, Nov 8, 2017 at 5:19 AM, Sauvageau, David  > wrote:
> Dear OOM committers, 
> 
> This is a request to promote Borislav as a committer on the OOM project. I 
> would need all OOM committers to vote on Borislav’s promotion by replying +1, 
> 0 or –1 on this email. If we get a majority of +1, I will then bring the 
> request to the TSC. 
> 
> Thanks!
> 
> From: Borislav Glozman  >
> Date: Sunday, November 5, 2017 at 2:48 AM
> To: David Sauvageau >
> Cc: Alla Goldner >
> Subject: ONAP OOM committer for Borislav Glozman
> 
> Hi David,
> 
>  
> 
> I would like to officially become OOM committer.
> 
> I fix defects, commit code, participate in meetings, participate in design of 
> features, participated in Paris ONAP event and presented there.
> 
> I also lead a team of developers who work on OOM.
> 
>  
> 
> Could you please assist me in becoming a committer in OOM project so that I 
> could actively participate in Beijing release in OOM?
> 
> Please let me know what is the process.
> 
>  
> 
> Thanks,
> 
> Borislav Glozman
> 
> O:+972.9.776.1988 
> M:+972.52.2835726 
>  
> 
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> you may review at https://www.amdocs.com/about/email-disclaimer 
> 
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org 
> https://lists.onap.org/mailman/listinfo/onap-discuss 
> 
> 
> 
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [aai] failing aai-common stage-site Jenkins build

[Tian Lee]

Hi Jimmy,

Regarding the failing aai-common stage-site Jenkins build: 
https://jenkins.onap.org/view/aai/job/aai-aai-common-master-stage-site-java/

I think the first thing to do is to try and find someone who has access to the 
Jenkins server's provided settings files. The pom changes we are making appear 
to have no effect, which leads me to believe that the settings files in the 
Jenkins configuration is overriding our pom config.

When I look at an equivalent aai-resources build log, I see that it's trying to 
download from the onap staging, snapshots, releases, public and other nexus 
repos. When I look at the failing aai-common build log, it is only ever trying 
to download from releases and public.

If the global or user settings configured for the aai-commons Jenkins job 
(global-settings, aai-aai-common-settings respectively) do not contain an entry 
for the staging nexus repository, then this could explain the error that we are 
seeing.

Regards,
Tian Lee
Software Design Expert
Amdocs Technology
ONAP committer for AAI

+44 (0)1225 32 7522

[amdocs-a]

Read the latest on Amdocs.com and the Amdocs blog 
network - and follow us on 
Facebook, Twitter, 
LinkedIn and 
YouTube.

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [multicloud] Please cancel this week's Multi Cloud weekly call

[Xinhui Li]

Hi Kenny,

Please help to cancel this week’s Multi Cloud weekly meeting for OpenStack 
Summit in Sydney

Xinhui Li

PTL of Multi VIM/Cloud

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] SO Error - ONAP 1.1

[Kapil Gupta (c)]

Hi,

Anyone have  update on error "MSO Properties failed to initialize".

Thanks
Kapil
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gaurav Gupta (c)
Sent: 07 November 2017 19:24
To: Radhika Kaslikar ; seshu.kuma...@huawei.com
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SO Error - ONAP 1.1


Seshu , Radhika



We followed the  
https://jira.onap.org/browse/SO-208?src=confmacro
  . We pulled the Latest MSO Dockers from Nexus Repo but we are still seeing 
the error for MSO Indicating the Init not complete  .


2017-11-07 12:18:18,704||ServerService Thread Pool -- 
75|contextInitializedERROR|AvailabilityError|| MSO-RA-5210E Configuration 
error:Unknown. MSO Properties failed to initialize completely
2017-11-07 12:18:18,705||ServerService Thread Pool -- 
75|contextInitializedERROR|AvailabilityError|| MSO-GENERAL-9400E Exception: 
java.lang.NullPointerException -  at 
org.openecomp.mso.openstack.utils.CloudConfigInitializer.contextInitialized(CloudConfigInitializer.java:65)
 -at 
io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
 -at

Do let us know how to move forward on this .


thanks

gaurav




From: Radhika Kaslikar 
>
Sent: 07 November 2017 16:23
To: seshu.kuma...@huawei.com; Gaurav Gupta (c)
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] SO Error - ONAP 1.1


Hi Seshu,



We are facing the same issue with MSO.

On running health check, MSO is failing

Basic MSO Health Check| FAIL |

503 != 200






And on checking the logs I see the following error :

2017-11-06 19:14:21,766||ServerService Thread Pool -- 
75|contextInitializedERROR|AvailabilityError|| MSO-RA-5210E Configuration 
error:Unknown. MSO Properties failed to initialize completely

2017-11-06 19:14:21,786||ServerService Thread Pool -- 
75|contextInitializedERROR|AvailabilityError|| MSO-GENERAL-9400E Exception: 
java.lang.NullPointerException - at 
org.openecomp.mso.openstack.utils.CloudConfigInitializer.contextInitialized(CloudConfigInitializer.java:65)
 -




Can you please tell us how can we solve this.



Thanks and Regards,

Radhika.




From: Pranay Nawghare [prana...@gmail.com]
Sent: Tuesday, November 07, 2017 4:09 PM
To: Radhika Kaslikar
Subject: Fwd: [onap-discuss] SO Error - ONAP 1.1
-- Forwarded message --
From: "Gaurav Gupta (c)" >
Date: 06-Nov-2017 11:19 PM
Subject: [onap-discuss] SO Error - ONAP 1.1
To: "Seshu m" >
Cc: "onap-discuss@lists.onap.org" 
>


Seshu



We needed some help in SO due to some unexplained error seen . Also can you 
also help us with what are the important configuration file in 
/etc/mso/config.d files and what should be the good value in those files .



Error seen in SO .



at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
-  at java.lang.Thread.run(Thread.java:748) -  at 
org.jboss.threads.JBossThread.run(JBossThread.java:320) -

2017-11-03 01:45:00,002||EJB default - 
2|reloadMsoPropertiesERROR|PermissionError|| MSO-GENERAL-5412E Missing or 
invalid properties file: /etc/mso/config.d/mso.vfc.properties
2017-11-03 01:45:00,003||EJB default - 
2|reloadMsoPropertiesERROR|PermissionError|| MSO-GENERAL-9400E Exception: 
java.io.FileNotFoundException: /etc/mso/config.d/mso.vfc.properties (No such 
file or directory) -  at java.io.FileInputStream.open0(Native Method) -  at 
java.io.FileInputStream.open(FileInputStream.java:195) -  at 
java.io.FileInputStream.(FileInputStream.java:138) -  at



.after we copied mso.vnf.properties  to mso.vfc.properties and restart mso test 
lab container

the error changes to



2017-11-06 12:37:31,707||ServerService Thread Pool -- 
82|contextInitializedERROR|AvailabilityError|| MSO-RA-5210E Configuration 
error:Unknown. MSO Properties failed to initialize completely

2017-11-06 12:37:31,729||ServerService Thread Pool -- 
82|contextInitializedERROR|AvailabilityError|| MSO-GENERAL-9400E Exception: 
java.lang.NullPointerException





with best regards

Gaurav





___
onap-discuss mailing list
onap-discuss@lists.onap.org