1 Reply Latest reply on May 26, 2017 4:46 AM by Devendra Dehadaraya

    Error in VM Provisioning: Management NIC not found

    Jyoti Wakchaure
      Share This:

      Hello,

       

      we are getting below error while VM provisioning that management NIC not found.....Where in IP addresses are available.

       

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

      VM Creation Failed

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

      success

      Linux3.13.0-36-genericsuccesspython /home/aouser/aws/vm_create.py  -u "company26may@mailinator.com" -p "12a985fb3922"  -t "company26may" -o "AGIT VMWare Windows Server 2008 R2" -s "vww12at2"  -n "vww12at2"  -q 1 -d 0  --vm-user "rizky" --vm-pass  "P@ssw0rd123"  --vm-options '{}'257660successhttp://172.30.167.59:7070/csm/task/e1011144-aba3-41c6-b926-7e948d8150ec/statusQUEUED

       

       

       

       

      http://172.30.167.59:7070/csm/task/e1011144-aba3-41c6-b926-7e948d8150ec/status

       

      ServiceOfferingInstancecom.bmc.cloud.model.beans.Task2017/05/26 14:08:54 ICT2017/05/26 14:06:47 ICTcom.bmc.cloud.model.beans.TaskErrorPlease contact System Administrator.Error while executing bulk create in Service Offering Instance.BMC-CLMT-104002011a43f7fe-d4b4-4ce9-979b-ba30fd0296cd172.30.167.59com.bmc.cloud.model.beans.CloudErrorPlease contact System Administrator.Error creating Service Offering Instance with name vww12at2 from  Service Offering AGIT VMWare Windows Server 2008 R2.BMC-CLMT-10400061021bead2-54ce-4244-b62c-39e816c5f5ac172.30.167.59com.bmc.cloud.model.beans.CloudErrorPlease contact System Administrator.Error creating Service Offering Instance with name vww12at2 from  Service Offering AGIT VMWare Windows Server 2008 R2.BMC-CLMT-10400061d2a665be-65eb-49fb-a9f3-26df30411dba172.30.167.59com.bmc.cloud.model.beans.CloudErrorPlease contact System Administrator.Error occurred while creating one or more resource sets.BMC-CLMT-10500029ae428f5e-2aaf-424b-bec8-7a720363f24e172.30.167.59com.bmc.cloud.model.beans.CloudErrorPlease contact System Administrator.Error occurred while creating resource set Microsoft Windows Server 2008.BMC-CLMT-10500027899b64aa-061c-4278-9c36-98151b5b88b5172.30.167.59com.bmc.cloud.model.beans.CloudErrorPlease contact System Administrator.Error creating Virtual ComputeContainer vww12at2-1.BMC-CLMT-1080033095c38180-ce4d-457f-b8ba-5ff851570e0f172.30.167.59com.bmc.cloud.model.beans.CloudErrorPlease contact System Administrator.VG creation failed:Management NIC was not provided in the VirtualGuest object.BMC-CLMT-10100019java.lang.IllegalArgumentException: Management NIC was not provided in the VirtualGuest object

      at com.bmc.cloud.provider.bbsaprovider.task.VMWareVirtualGuestConstructorExecHelper.updateVMWareNetworkSettings(VMWareVirtualGuestConstructorExecHelper.java:322)

      at com.bmc.cloud.provider.bbsaprovider.task.VMWareVirtualGuestConstructorExecHelper.updateVMWareInfo(VMWareVirtualGuestConstructorExecHelper.java:199)

      at com.bmc.cloud.provider.bbsaprovider.task.VMWareVirtualGuestConstructorExecHelper.updatePlatformInfo(VMWareVirtualGuestConstructorExecHelper.java:154)

      at com.bmc.cloud.provider.bbsaprovider.task.VirtualGuestTaskExecHelper.createVGJobConfig(VirtualGuestTaskExecHelper.java:642)

      at com.bmc.cloud.provider.bbsaprovider.task.VirtualGuestTaskExecHelper.createFile(VirtualGuestTaskExecHelper.java:575)

      at com.bmc.cloud.provider.bbsaprovider.task.VirtualGuestTaskExecHelper.execute(VirtualGuestTaskExecHelper.java:143)

      at com.bmc.cloud.provider.bbsaprovider.task.VirtualGuestTaskExecHelper.execute(VirtualGuestTaskExecHelper.java:120)

      at com.bmc.cloud.provider.bbsaprovider.task.VirtualGuestConstructorExecHelper.execute(VirtualGuestConstructorExecHelper.java:63)

      at com.bmc.cloud.task.scxml.actions.ExecAction.doExecute(ExecAction.java:74)

      at com.bmc.cloud.task.scxml.actions.CSMBaseAction.execute(CSMBaseAction.java:106)

      at org.apache.commons.scxml.semantics.SCXMLSemanticsImpl.executeActions(SCXMLSemanticsImpl.java:239)

      at org.apache.commons.scxml.SCXMLExecutor.reset(SCXMLExecutor.java:252)

      at org.apache.commons.scxml.SCXMLExecutor.go(SCXMLExecutor.java:351)

      at com.bmc.cloud.task.impl.SCXMLTaskImpl.executeTask(SCXMLTaskImpl.java:148)

      at com.bmc.cloud.task.impl.TaskImpl.fireEvent(TaskImpl.java:643)

      at com.bmc.cloud.taskmanager.impl.SCXMLEventWorker.process(SCXMLEventWorker.java:58)

      at com.bmc.cloud.taskmanager.impl.SCXMLEventWorker.process(SCXMLEventWorker.java:17)

      at com.bmc.cloud.worker.WorkQueue$WorkerThread.run(WorkQueue.java:430)

      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

      at java.util.concurrent.FutureTask.run(FutureTask.java:262)

      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

      at java.lang.Thread.run(Thread.java:745)

      9245352a-7da7-4539-acee-df2d6edb9eb3172.30.167.59CRITICAL080ad10a-9ea4-433a-a8bb-c5ff181f7c19CRITICAL080ad10a-9ea4-433a-a8bb-c5ff181f7c19CRITICAL080ad10a-9ea4-433a-a8bb-c5ff181f7c19CRITICAL080ad10a-9ea4-433a-a8bb-c5ff181f7c19CRITICAL080ad10a-9ea4-433a-a8bb-c5ff181f7c19CRITICAL080ad10a-9ea4-433a-a8bb-c5ff181f7c19CRITICALe1011144-aba3-41c6-b926-7e948d8150ec080ad10a-9ea4-433a-a8bb-c5ff181f7c19bbd4217f-feb8-4878-ac6f-5785689c95c3falsetruefalsevww12at2bulkcreatee1011144-aba3-41c6-b926-7e948d8150ec100.0FAILEDhttp://172.30.167.59:7070/csm/task/e1011144-aba3-41c6-b926-7e948d8150ec/statustask_fail080ad10a-9ea4-433a-a8bb-c5ff181f7c19

       

       

      Kindly help on above.

       

      Regards,

      Jyoti

        • 1. Re: Error in VM Provisioning: Management NIC not found
          Devendra Dehadaraya

          Hello,

           

          In CLM we expect that that VM that you are provisioning should have at least 1 management NIC. Which means that when you are designing your service blueprint, you need to tag the network component with same Tag that has been placed on a management network of the network container.(Management network can be at POD level or network container level depending upon the network topology that you are following in your infrastructure)

           

          To view the type of the network (Management/Customer), you will need to view the network container from BNA console.

           

          Thanks,

          Devendra

          1 of 1 people found this helpful