Hi Brian,

Figured out the issue. Looks like when giving public net id in vFW env file, 
this issue comes.
I used internal network id instead and with it all 3 VMs are created and the VF 
module stack creation succeeds.
I then have to assign floating IP to 3 VMs manually though.

That said, still need to characterize the issue as a genuine bug or some local 
setup issue.

But importantly, passed step 5 of 6 :-)

Thanks,
Arun

________________________________
From: Arun Arora (c)
Sent: Friday, November 24, 2017 9:58:32 AM
To: FREEMAN, BRIAN D; [email protected]
Subject: Re: [onap-discuss] vFW Demo Stack Create Fails with ""Message: No 
valid host was found. There are not enough hosts available., Code: 500""


debugmso.log in VnfAdpater say the same error. Nothing more verbose in it 
w.r.t.  this error.


Arun

________________________________
From: FREEMAN, BRIAN D <[email protected]>
Sent: Friday, November 24, 2017 9:10:13 AM
To: Arun Arora (c); [email protected]
Subject: RE: [onap-discuss] vFW Demo Stack Create Fails with ""Message: No 
valid host was found. There are not enough hosts available., Code: 500""


I’ve only run into that when the Hosting platform didnt have enough memory or 
other resource (sometimes ports ) you’ll have to look at errors on the VMware 
side. Dont know if Marco or Kang have run into this particular message before.



Did debugmso.log in the VnfAdapter directory have any more details or was it 
the same No valid host was found message ?



Brian





From: [email protected] 
[mailto:[email protected]] On Behalf Of Arun Arora (c)
Sent: Thursday, November 23, 2017 9:24 AM
To: [email protected]
Subject: [onap-discuss] vFW Demo Stack Create Fails with ""Message: No valid 
host was found. There are not enough hosts available., Code: 500""



Hi All,



We are working to bring up the vFW demo on VIO 4.0. For that we run demo.sh 
init from robot VM and then service instantiation is done from VID.

We have reached a point where MSO sends the Heat Request to VIO for Demo Stack 
creation, however each time the stack creation fails with error ""Message: No 
valid host was found. There are not enough hosts available., Code: 500""



We have enough resources for the 3 VMs created as part of vFW demo. However, 
still receiving the following errors:



vsn_0<https://urldefense.proofpoint.com/v2/url?u=https-3A__10.110.209.230_project_stacks_stack_b7161f32-2D91cf-2D4f06-2Db4c3-2D3f5b5e1ab96c_vsn-5F0_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=gzKgE4TNJPXXTd0gyIIB1i9Me-bWT--wW7GqVISXrMI&s=JKQzrMkyWbTvis0j0UEpBDDzyNI0YO09YLhEHgfcGZY&e=>


7f5f2a96-065b-49d7-a6a4-281ff85df8db<https://urldefense.proofpoint.com/v2/url?u=https-3A__10.110.209.230_project_instances_7f5f2a96-2D065b-2D49d7-2Da6a4-2D281ff85df8db_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=gzKgE4TNJPXXTd0gyIIB1i9Me-bWT--wW7GqVISXrMI&s=37NPVDYMTeIn5gaxMZk8GZiQ8tld76TieX1YQMxweSE&e=>


OS::Nova::Server


14 minutes


Create Failed


ResourceInError: resources.vsn_0: Went to status ERROR due to "Message: No 
valid host was found. There are not enough hosts available., Code: 500"






vpg_0<https://urldefense.proofpoint.com/v2/url?u=https-3A__10.110.209.230_project_stacks_stack_b7161f32-2D91cf-2D4f06-2Db4c3-2D3f5b5e1ab96c_vpg-5F0_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=gzKgE4TNJPXXTd0gyIIB1i9Me-bWT--wW7GqVISXrMI&s=PboBWDIXmYMAAizjWOkS891HEl_xwSAUoftSr0yQ3xM&e=>


385d207f-97ff-4a3a-8107-c8a77c37b33b<https://urldefense.proofpoint.com/v2/url?u=https-3A__10.110.209.230_project_instances_385d207f-2D97ff-2D4a3a-2D8107-2Dc8a77c37b33b_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=gzKgE4TNJPXXTd0gyIIB1i9Me-bWT--wW7GqVISXrMI&s=qsyPLUDRYMNdqzIDWm-HT6mZpT5wBnu2O4Vzsye_1fg&e=>


OS::Nova::Server


14 minutes


Create Failed


ResourceInError: resources.vpg_0: Went to status ERROR due to "Message: No 
valid host was found. There are not enough hosts available., Code: 500"




I see that other resources creation is OK but the VMs creation fail. Attaching 
the topology snapshot for reference.



Has anyone seen this issue in your setup? Ayn pointers to fix this are highly 
appreciated.



Thanks,

Arun


_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to