Hi Slavka,

thank you for your explanations - really nice to have some insides of this
whole process.
Regarding your questions:

secondary stoage vm, console proxy were created with the same template.

So what has happend - i had som brief discussions with our admin team to
get things together:
Basically it seems that we have these problems since we tried to upgrade
the environment to 4.17 (from the information i have, the team tried to do
this before beeing aware of the advisory - otherwise i would have suggested
to skip 4.17 and wait for 4.17.1 / 4.18). How ever the upgrade process
failed for us and so we rolled back to 4.16.1. It seems that something went
wrong in this process - as the problems occured since then. The guys
responsible for performing the update meant, that some parts of the
upgrade-guide where not quiet clear - especially the part on how to deploy
the new systemvm templates since the changes made in 4.16 / 4.16.1.

The environment itself "was" build up as a testbed - sadly some people
where thinking that you can deploy services and make them useable in daily
work - meaning its now something i would call "semi-productive".... So i
can't just throw everything away and build it newly ...
That's why i hope to get around the corner on "fixing" the current
systemVM-Template / database and migrate as fast as possible to 4.17.1 -
making the current systemtemplate "obsolete".

Regards,
Chris

Am Fr., 5. Aug. 2022 um 10:16 Uhr schrieb Slavka Peleva <
[email protected]>:

> Hi Christopher,
>
> Just for understanding:
>> When deploying a new "systemvm"-template, which i normally would do while
>> upgardeing mi CS-Environment, the values of the template.properties will be
>> transfaired into DB. The management server will then make use of the values
>> which are stored in the DB?
>
>
> Yes. When the system VM template is seeded, CS (or you do it manually)
> executes a script which creates the `template.properties` file and fills it
> with the information you shared. Then it takes from it the data and updates
> the DB. In your `template.properties` file, the `virtualsize` is empty.
> Probably something happened while the `qemu-img info` (from that script)
> was executed.
>
> I can't advise you on how to proceed because I don't know what steps you
> made before. Is this a test setup?
>
> Are the system VMs (secondary storage/console proxy VMs) created with the
> same template? Can you check when they are deployed, and are there any
> updates on this template? You can find the info for the template in the
> template_store_ref table -> created and last_updated columns.
>
> Best regards,
> Slavka
>
> On Thu, Aug 4, 2022 at 9:50 PM [email protected] <[email protected]> wrote:
>
>> hi slavka,
>> i checked the log and didn't found anything like "failed to read from
>> template.properties".
>>
>> Just for understanding:
>> When deploying a new "systemvm"-template, which i normally would do while
>> upgardeing mi CS-Environment, the values of the template.properties will be
>> transfaired into DB. The management server will then make use of the values
>> which are stored in the DB?
>>
>> i destroyed the "stopped" router in my installation and triggered a
>> re-deployment. The term "template" is mentioned inside the logs only for
>> two reasons:
>> 1. Successfull router health check of the running router (the primary one
>> of my vpc)
>> 2. In the mentioned error log
>> " at
>> org.apache.cloudstack.storage.datastore.db.TemplateDataStoreVO.getSize(TemplateDataStoreVO.java:280)
>>         at
>> com.cloud.template.TemplateManagerImpl.getTemplateSize(TemplateManagerImpl.java:2009)
>> "
>>
>> so the question for me is  - can i manually place the missing values in
>> the DB, so that the template is useable again? Or will i wait until i
>> upgrade to 4.17.1 - which might bring a new systemVM template which will
>> then be seeded again ?
>>
>> Regards,
>> Chris
>>
>> Am Do., 4. Aug. 2022 um 19:10 Uhr schrieb Slavka Peleva <
>> [email protected]>:
>>
>>> Hi Christopher,
>>>
>>> For some reason, these fields' values are empty, which probably
>>> happened while you seed the system VM template.
>>>
>>>> qcow2.virtualsize=
>>>> virtualsize=
>>>> qcow2.size=
>>>
>>>
>>> From the DB record, the only option for the values of physical_size = 0
>>> and size=Null, is that CS couldn't read the `template.properties` file. Can
>>> you search in the management log file for a message like "Failed to read
>>> from template.properties"? It should contain more detailed information
>>> about the failure.
>>>
>>> Best regards,
>>> Slavka
>>>
>>> On Thu, Aug 4, 2022 at 7:13 PM [email protected] <[email protected]> wrote:
>>>
>>>> Hi everyone -
>>>>
>>>> @Gary
>>>> thanks for your input
>>>>
>>>> @Wei ZHOU <[email protected]>
>>>> Yes, the image is completely downloaded to the imagestore. I also
>>>> checked
>>>> the availeabilty on the storage beneath - everything seems to be in
>>>> place
>>>> like it should
>>>>
>>>> Following the values out ouf the db you requested:
>>>> id= 18
>>>> store_id = 1
>>>> download_pct = 100
>>>> size = "NULL"
>>>> store_role = Image
>>>> physical_size = 0
>>>> download_state = DOWNLOADED
>>>> state = READY
>>>> install_path =
>>>> /template/tmpl/1/212/0573ec70-0a30-4e2a-be9e-4675bf755cf2.qcow2
>>>>
>>>> @Slavka
>>>> Following the information of the 'template.properties'
>>>>
>>>> filename=0573ec70-0a30-4e2a-be9e-4675bf755cf2.qcow2
>>>> description=SystemVM Template ( kvm )
>>>> hvm=false
>>>> size=460067328
>>>> qcow2=true
>>>> id=212
>>>> public=true
>>>> qcow2.filename=0573ec70-0a30-4e2a-be9e-4675bf755cf2.qcow2
>>>> uniquename=routing-212
>>>> qcow2.virtualsize=
>>>> virtualsize=
>>>> qcow2.size=
>>>>
>>>> Regards,
>>>> Chris
>>>>
>>>> Am Do., 4. Aug. 2022 um 12:05 Uhr schrieb Slavka Peleva
>>>> <[email protected]>:
>>>>
>>>> > Hi Christopher,
>>>> >
>>>> > Can you share the information of the `template.properties` file
>>>> located on
>>>> > your secondary storage, where the template file is downloaded? You
>>>> can find
>>>> > the path in the template_store_ref tabled - install_path.
>>>> >
>>>> > Best regards,
>>>> > Slavka
>>>> >
>>>> > On Thu, Aug 4, 2022 at 12:41 PM Gary Dixon <[email protected]
>>>> > .invalid>
>>>> > wrote:
>>>> >
>>>> > > Hi Christopher
>>>> > >
>>>> > > My values show :
>>>> > > size=2621440000 physical size=375471104 and this is for a 4.15.1
>>>> systemVM
>>>> > > template
>>>> > >
>>>> > > BR
>>>> > > Gary
>>>> > >
>>>> > > Gary Dixon​
>>>> > > Senior Technical Consultant
>>>> > > T:  *0161 537 4980* <0161%20537%204980>
>>>> > > W: www.quadris.co.uk
>>>> > > The information contained in this e-mail from Quadris may be
>>>> confidential
>>>> > > and privileged for the private use of the named recipient.  The
>>>> contents
>>>> > of
>>>> > > this e-mail may not necessarily represent the official views of
>>>> Quadris.
>>>> > > If you have received this information in error you must not copy,
>>>> > > distribute or take any action or reliance on its contents.  Please
>>>> > destroy
>>>> > > any hard copies and delete this message.
>>>> > > -----Original Message-----
>>>> > > From: [email protected] <[email protected]>
>>>> > > Sent: 04 August 2022 09:40
>>>> > > To: [email protected]; Wei ZHOU <[email protected]>
>>>> > > Subject: Re: VR for VPC won't start anymore
>>>> > >
>>>> > > I forgot to ask - might anyone take a quick look into the database
>>>> and
>>>> > can
>>>> > > give a hind if the fields are indeed "filled" with values
>>>> > > (template_store_res.size / template_store_res.physical_size)?
>>>> > > Another question for understanding would be the difference of the
>>>> values
>>>> > -
>>>> > > physical size is the actual amount of data on a datasystemlevel -
>>>> but
>>>> > what
>>>> > > represents the value of "size"?
>>>> > >
>>>> > > Regards,
>>>> > > Christopher
>>>> > >
>>>> > > Am Mi., 3. Aug. 2022 um 23:14 Uhr schrieb [email protected] <
>>>> [email protected]>:
>>>> > >
>>>> > > > Wei, seems like you are heading twards the right direction - like
>>>> > always.
>>>> > > >
>>>> > > > i took a look into the "template_store_res" table... and guess:
>>>> There
>>>> > > > is a entry for the current systemvmtemplate-4.16.1. How ever: The
>>>> > > > field for "size" ist "null" and "physical_size" is "0".
>>>> > > >
>>>> > > > Might this be the reason for the "
>>>> java.lang.NullPointerException" ?
>>>> > > >
>>>> > > > Regards,
>>>> > > > Chris
>>>> > > >
>>>> > > > Am Mi., 3. Aug. 2022 um 21:56 Uhr schrieb Wei ZHOU
>>>> > > > <[email protected]
>>>> > > > >:
>>>> > > >
>>>> > > >> It looks there is no entry in template_store_ref table for the
>>>> > > >> systemvm template
>>>> > > >>
>>>> > > >> -Wei
>>>> > > >>
>>>> > > >> On Wed, 3 Aug 2022 at 21:43, [email protected] <[email protected]>
>>>> wrote:
>>>> > > >>
>>>> > > >> > Hi everyone,
>>>> > > >> >
>>>> > > >> > faceing currently some challanges regarding my network
>>>> > > >> > configuration in
>>>> > > >> CS
>>>> > > >> > 4.16.1.
>>>> > > >> >
>>>> > > >> > Setup:
>>>> > > >> > VPC with redundant routers and some tiers as well as an private
>>>> > > gateway.
>>>> > > >> >
>>>> > > >> > Today i wanted to restart the whole VPC - sadly only one
>>>> vrouter
>>>> > > >> > "survived" .... Currently i can't depoly any networks in or
>>>> outside
>>>> > > >> > the VPC. Also the second router shall be delployed but keeps
>>>> in the
>>>> > > >> > stopped state.
>>>> > > >> > I really dont have a clue where to look at first...
>>>> > > >> >
>>>> > > >> > here the logfile from the Management-Server:
>>>> > > >> >
>>>> > > >> > 2022-08-03 20:35:48,768 DEBUG [c.c.n.r.NetworkHelperImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating the VR with id=74 in datacenter Zone {"id": "1",
>>>> "name":
>>>> > > >> > "xxxxxxxxxx", "uuid": "48e2e928-3300-43b5-8e3a-d>
>>>> > > >> > 2022-08-03 20:35:48,776 DEBUG [c.c.n.r.NetworkHelperImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Adding nic for Virtual Router in Control network
>>>> > > >> > 2022-08-03 20:35:48,781 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Found existing network configuration for offering [Network
>>>> Offering
>>>> > > >> > [3-Control-System-Control-Network]: Ntwk[202|>
>>>> > > >> > 2022-08-03 20:35:48,781 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Releasing lock for
>>>> > > >> > Acct[60bddbd5-1d8a-11ec-83ce-525400c9c662-system] -- Account
>>>> {"id":
>>>> > > >> > 1, "name": "system", "uuid>
>>>> > > >> > 2022-08-03 20:35:48,785 DEBUG [c.c.n.r.NetworkHelperImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Adding nic for Virtual Router in Public network
>>>> > > >> > 2022-08-03 20:35:48,789 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Found existing network configuration for offering [Network
>>>> Offering
>>>> > > >> > [1-Public-System-Public-Network]: Ntwk[200|Pu>
>>>> > > >> > 2022-08-03 20:35:48,789 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Releasing lock for
>>>> > > >> > Acct[60bddbd5-1d8a-11ec-83ce-525400c9c662-system] -- Account
>>>> {"id":
>>>> > > >> > 1, "name": "system", "uuid>
>>>> > > >> > 2022-08-03 20:35:48,793 INFO [c.c.n.r.NetworkHelperImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Use same MAC as previous RvR, the MAC is 1e:00:59:00:00:b2
>>>> > > >> > 2022-08-03 20:35:48,793 DEBUG [c.c.n.r.NetworkHelperImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Adding nic for Virtual Router in Guest network
>>>> Ntwk[249|Guest|30]
>>>> > > >> > 2022-08-03 20:35:48,801 DEBUG [c.c.u.d.T.Transaction]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Rolling back the transaction: Time = 0 Name =
>>>> API-Job-Executor-60;
>>>> > > >> called
>>>> > > >> > by -TransactionLegacy.rollback:888-PrivateIpDa>
>>>> > > >> > 2022-08-03 20:35:48,808 DEBUG [c.c.n.NetworkModelImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Service SecurityGroup is not supported in the network id=236
>>>> > > >> > 2022-08-03 20:35:48,851 INFO [c.c.v.VirtualMachineManagerImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > allocating virtual machine from
>>>> > > >> > template:0573ec70-0a30-4e2a-be9e-4675bf755cf2 with
>>>> hostname:r-74-VM
>>>> > > >> > and
>>>> > > >> 12
>>>> > > >> > netw>
>>>> > > >> > 2022-08-03 20:35:48,852 DEBUG [c.c.v.VirtualMachineManagerImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating entries for VM: VM instance {id: "74", name:
>>>> "r-74-VM",
>>>> > > uuid:
>>>> > > >> > "09dc644b-76a2-404a-82fd-aecc8d5799c3">
>>>> > > >> > 2022-08-03 20:35:48,857 DEBUG [c.c.v.VirtualMachineManagerImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating nics for VM instance {id: "74", name: "r-74-VM",
>>>> uuid:
>>>> > > >> > "09dc644b-76a2-404a-82fd-aecc8d5799c3", type=>
>>>> > > >> > 2022-08-03 20:35:48,858 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating nic for vm VM instance {id: "74", name: "r-74-VM",
>>>> uuid:
>>>> > > >> > "09dc644b-76a2-404a-82fd-aecc8d5799c3", type=>
>>>> > > >> > 2022-08-03 20:35:48,866 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating nic for vm VM instance {id: "74", name: "r-74-VM",
>>>> uuid:
>>>> > > >> > "09dc644b-76a2-404a-82fd-aecc8d5799c3", type=>
>>>> > > >> > 2022-08-03 20:35:48,886 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating nic for vm VM instance {id: "74", name: "r-74-VM",
>>>> uuid:
>>>> > > >> > "09dc644b-76a2-404a-82fd-aecc8d5799c3", type=>
>>>> > > >> > 2022-08-03 20:35:48,904 DEBUG [c.c.n.NetworkModelImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Service SecurityGroup is not supported in the network id=249
>>>> > > >> > 2022-08-03 20:35:48,907 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating nic for vm VM instance {id: "74", name: "r-74-VM",
>>>> uuid:
>>>> > > >> > "09dc644b-76a2-404a-82fd-aecc8d5799c3", type=>
>>>> > > >> > 2022-08-03 20:35:48,917 DEBUG [c.c.n.NetworkModelImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Service SecurityGroup is not supported in the network id=236
>>>> > > >> > 2022-08-03 20:35:48,920 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating nic for vm VM instance {id: "74", name: "r-74-VM",
>>>> uuid:
>>>> > > >> > "09dc644b-76a2-404a-82fd-aecc8d5799c3", type=>
>>>> > > >> > 2022-08-03 20:35:48,939 DEBUG [c.c.n.NetworkModelImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Service SecurityGroup is not supported in the network id=240
>>>> > > >> > 2022-08-03 20:35:48,942 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating nic for vm VM instance {id: "74", name: "r-74-VM",
>>>> uuid:
>>>> > > >> > "09dc644b-76a2-404a-82fd-aecc8d5799c3", type=>
>>>> > > >> > 2022-08-03 20:35:48,959 DEBUG [c.c.n.NetworkModelImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Service SecurityGroup is not supported in the network id=241
>>>> > > >> > 2022-08-03 20:35:48,962 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating nic for vm VM instance {id: "74", name: "r-74-VM",
>>>> uuid:
>>>> > > >> > "09dc644b-76a2-404a-82fd-aecc8d5799c3", type=>
>>>> > > >> > 2022-08-03 20:35:48,985 DEBUG [c.c.n.NetworkModelImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Service SecurityGroup is not supported in the network id=242
>>>> > > >> > 2022-08-03 20:35:48,987 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating nic for vm VM instance {id: "74", name: "r-74-VM",
>>>> uuid:
>>>> > > >> > "09dc644b-76a2-404a-82fd-aecc8d5799c3", type=>
>>>> > > >> > 2022-08-03 20:35:49,004 DEBUG [c.c.n.NetworkModelImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Service SecurityGroup is not supported in the network id=243
>>>> > > >> > 2022-08-03 20:35:49,008 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating nic for vm VM instance {id: "74", name: "r-74-VM",
>>>> uuid:
>>>> > > >> > "09dc644b-76a2-404a-82fd-aecc8d5799c3", type=>
>>>> > > >> > 2022-08-03 20:35:49,026 DEBUG [c.c.n.NetworkModelImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Service SecurityGroup is not supported in the network id=244
>>>> > > >> > 2022-08-03 20:35:49,029 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating nic for vm VM instance {id: "74", name: "r-74-VM",
>>>> uuid:
>>>> > > >> > "09dc644b-76a2-404a-82fd-aecc8d5799c3", type=>
>>>> > > >> > 2022-08-03 20:35:49,046 DEBUG [c.c.n.NetworkModelImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Service SecurityGroup is not supported in the network id=245
>>>> > > >> > 2022-08-03 20:35:49,049 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating nic for vm VM instance {id: "74", name: "r-74-VM",
>>>> uuid:
>>>> > > >> > "09dc644b-76a2-404a-82fd-aecc8d5799c3", type=>
>>>> > > >> > 2022-08-03 20:35:49,065 DEBUG [c.c.n.NetworkModelImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Service SecurityGroup is not supported in the network id=246
>>>> > > >> > 2022-08-03 20:35:49,068 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating nic for vm VM instance {id: "74", name: "r-74-VM",
>>>> uuid:
>>>> > > >> > "09dc644b-76a2-404a-82fd-aecc8d5799c3", type=>
>>>> > > >> > 2022-08-03 20:35:49,085 DEBUG [c.c.n.NetworkModelImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Service SecurityGroup is not supported in the network id=247
>>>> > > >> > 2022-08-03 20:35:49,088 DEBUG [c.c.v.VirtualMachineManagerImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Allocating disks for VM instance {id: "74", name: "r-74-VM",
>>>> uuid:
>>>> > > >> > "09dc644b-76a2-404a-82fd-aecc8d5799c3", type>
>>>> > > >> > 2022-08-03 20:35:49,088 INFO [o.a.c.e.o.VolumeOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > adding disk object ROOT-74 to r-74-VM
>>>> > > >> > 2022-08-03 20:35:49,091 DEBUG [c.c.u.d.T.Transaction]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Rolling back the transaction: Time = 234 Name =
>>>> > > >> > API-Job-Executor-60; called by
>>>> > > >> > -TransactionLegacy.rollback:888-Transacti>
>>>> > > >> > 2022-08-03 20:35:49,099 WARN [o.a.c.e.o.NetworkOrchestrator]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Failed to implement network Ntwk[249|Guest|30] elements and
>>>> > > >> > resources
>>>> > > >> as a
>>>> > > >> > part of network restart due to
>>>> > > >> > java.lang.NullPointerException
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.apache.cloudstack.storage.datastore.db.TemplateDataStoreVO.getSiz
>>>> > > >> e(TemplateDataStoreVO.java:280)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> com.cloud.template.TemplateManagerImpl.getTemplateSize(TemplateManage
>>>> > > >> rImpl.java:2009)
>>>> > > >> > at
>>>> > > >> >
>>>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Nat
>>>> > > >> > ive
>>>> > > >> > Method)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Native
>>>> > > >> MethodAccessorImpl.java:62)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(De
>>>> > > >> legatingMethodAccessorImpl.java:43)
>>>> > > >> > at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
>>>> > > >> on(AopUtils.java:344)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
>>>> > > >> inpoint(ReflectiveMethodInvocation.java:198)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
>>>> > > >> ReflectiveMethodInvocation.java:163)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invok
>>>> > > >> e(ExposeInvocationInterceptor.java:97)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
>>>> > > >> ReflectiveMethodInvocation.java:186)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
>>>> > > >> cAopProxy.java:215)
>>>> > > >> > at com.sun.proxy.$Proxy201.getTemplateSize(Unknown Source)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.allocat
>>>> > > >> eTemplatedVolume(VolumeOrchestrator.java:834)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.allocat
>>>> > > >> eTemplatedVolumes(VolumeOrchestrator.java:954)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> com.cloud.vm.VirtualMachineManagerImpl$1.doInTransactionWithoutResult
>>>> > > >> (VirtualMachineManagerImpl.java:496)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTrans
>>>> > > >> action(TransactionCallbackWithExceptionNoReturn.java:25)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTrans
>>>> > > >> action(TransactionCallbackWithExceptionNoReturn.java:21)
>>>> > > >> > at com.cloud.utils.db.Transaction.execute(Transaction.java:40)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> com.cloud.vm.VirtualMachineManagerImpl.allocate(VirtualMachineManager
>>>> > > >> Impl.java:471)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> com.cloud.vm.VirtualMachineManagerImpl.allocate(VirtualMachineManager
>>>> > > >> Impl.java:528)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> com.cloud.network.router.VpcNetworkHelperImpl.reallocateRouterNetwork
>>>> > > >> s(VpcNetworkHelperImpl.java:169)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> com.cloud.network.router.NetworkHelperImpl.deployRouter(NetworkHelper
>>>> > > >> Impl.java:520)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.cloud.network.router.deployment.VpcRouterDeploymentDefinition.dep
>>>> > > >> loyAllVirtualRouters(VpcRouterDeploymentDefinition.java:178)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.cloud.network.router.deployment.RouterDeploymentDefinition.execut
>>>> > > >> eDeployment(RouterDeploymentDefinition.java:377)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.cloud.network.router.deployment.RouterDeploymentDefinition.findOr
>>>> > > >> DeployVirtualRouter(RouterDeploymentDefinition.java:239)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.cloud.network.router.deployment.VpcRouterDeploymentDefinition.fin
>>>> > > >> dOrDeployVirtualRouter(VpcRouterDeploymentDefinition.java:140)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.cloud.network.router.deployment.RouterDeploymentDefinition.deploy
>>>> > > >> VirtualRouter(RouterDeploymentDefinition.java:205)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> com.cloud.network.element.VpcVirtualRouterElement.implement(VpcVirtua
>>>> > > >> lRouterElement.java:215)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implem
>>>> > > >> entNetworkElements(NetworkOrchestrator.java:1488)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implem
>>>> > > >> entNetworkElementsAndResources(NetworkOrchestrator.java:1423)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.restar
>>>> > > >> tNetwork(NetworkOrchestrator.java:3302)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> com.cloud.network.NetworkServiceImpl.restartNetwork(NetworkServiceImp
>>>> > > >> l.java:2068)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> com.cloud.network.NetworkServiceImpl.restartNetwork(NetworkServiceImp
>>>> > > >> l.java:2089)
>>>> > > >> > at
>>>> > > >> >
>>>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Nat
>>>> > > >> > ive
>>>> > > >> > Method)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Native
>>>> > > >> MethodAccessorImpl.java:62)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(De
>>>> > > >> legatingMethodAccessorImpl.java:43)
>>>> > > >> > at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
>>>> > > >> on(AopUtils.java:344)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
>>>> > > >> inpoint(ReflectiveMethodInvocation.java:198)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
>>>> > > >> ReflectiveMethodInvocation.java:163)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.apache.cloudstack.network.contrail.management.EventUtils$EventInt
>>>> > > >> erceptor.invoke(EventUtils.java:107)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
>>>> > > >> ReflectiveMethodInvocation.java:175)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.
>>>> > > >> java:51)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
>>>> > > >> ReflectiveMethodInvocation.java:175)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invok
>>>> > > >> e(ExposeInvocationInterceptor.java:97)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
>>>> > > >> ReflectiveMethodInvocation.java:186)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
>>>> > > >> cAopProxy.java:215)
>>>> > > >> > at com.sun.proxy.$Proxy168.restartNetwork(Unknown Source)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.apache.cloudstack.api.command.user.network.RestartNetworkCmd.exec
>>>> > > >> ute(RestartNetworkCmd.java:98)
>>>> > > >> > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java
>>>> > > >> :108)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runIn
>>>> > > >> Context(AsyncJobManagerImpl.java:620)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(Ma
>>>> > > >> nagedContextRunnable.java:48)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$
>>>> 1.ca
>>>> > > >> ll(DefaultManagedContext.java:55)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.call
>>>> > > >> WithContext(DefaultManagedContext.java:102)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runW
>>>> > > >> ithContext(DefaultManagedContext.java:52)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(Mana
>>>> > > >> gedContextRunnable.java:45)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(A
>>>> > > >> syncJobManagerImpl.java:568)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executo
>>>> > > >> rs.java:515)
>>>> > > >> > at
>>>> > > >> >
>>>> java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoo
>>>> > > >> lExecutor.java:1128)
>>>> > > >> > at
>>>> > > >> >
>>>> > > >>
>>>> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPo
>>>> > > >> olExecutor.java:628)
>>>> > > >> > at java.base/java.lang.Thread.run(Thread.java:829)
>>>> > > >> > 2022-08-03 20:35:49,100 WARN [c.c.n.NetworkServiceImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342 ctx-150e61a2)
>>>> > > >> (logid:6b6b9867)
>>>> > > >> > Network id=249 failed to restart.
>>>> > > >> > 2022-08-03 20:35:49,111 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342) (logid:6b6b9867)
>>>> > > >> > Complete
>>>> > > >> async
>>>> > > >> > job-3342, jobStatus: FAILED, resultCode: 530, result:
>>>> > > >> > org.apache.cloudstack.api.response.ExceptionResponse/nu>
>>>> > > >> > 2022-08-03 20:35:49,112 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342) (logid:6b6b9867)
>>>> > > >> > Publish
>>>> > > >> async
>>>> > > >> > job-3342 complete on message bus
>>>> > > >> > 2022-08-03 20:35:49,112 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342) (logid:6b6b9867)
>>>> Wake
>>>> > > >> > up
>>>> > > >> jobs
>>>> > > >> > related to job-3342
>>>> > > >> > 2022-08-03 20:35:49,112 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342) (logid:6b6b9867)
>>>> Update
>>>> > > >> > db status for job-3342
>>>> > > >> > 2022-08-03 20:35:49,114 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342) (logid:6b6b9867)
>>>> Wake
>>>> > > >> > up
>>>> > > >> jobs
>>>> > > >> > joined with job-3342 and disjoin all subjobs created from job-
>>>> 3342
>>>> > > >> > 2022-08-03 20:35:49,119 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
>>>> > > >> > (API-Job-Executor-60:ctx-a9f63190 job-3342) (logid:6b6b9867)
>>>> Done
>>>> > > >> executing
>>>> > > >> >
>>>> org.apache.cloudstack.api.command.user.network.RestartNetworkCmd
>>>> > > >> > for
>>>> > > >> > job-3342
>>>> > > >> >
>>>> > > >> > Regards,
>>>> > > >> > Chris
>>>> > > >> >
>>>> > > >>
>>>> > > >
>>>> > >
>>>> >
>>>>
>>>

Reply via email to