Re: Unable to login to GUI onto second management server

2022-08-03 Thread Harikrishna Patnala 
Glad that worked for you, Andrei.

Regards,
Harikrishna

From: Andrei Mikhailovsky 
Sent: Tuesday, August 2, 2022 8:12 PM
To: users 
Cc: Harikrishna Patnala 
Subject: Re: Unable to login to GUI onto second management server

I have followed the instructions from 
https://www.shapeblue.com/dynamic-roles-in-cloudstack/ and can confirm that 
after running the migration python script I was able to login to the new 
management server.

Perhaps the installation manuals for the multiple management server setup 
should mention the above instructions for the ACS servers that were crated 
before 4.9.x. In my case, I've installed ACS back in 2012 and didn't update the 
permissions structure

Thanks everyone for looking into this issue.

Andrei


 

- Original Message -
> From: "Andrei Mikhailovsky" 
> To: "users" 
> Cc: "Harikrishna Patnala" 
> Sent: Tuesday, 2 August, 2022 15:49:55
> Subject: Re: Unable to login to GUI onto second management server

> It seems that my issue is closely related to the issue discussed here:
> https://github.com/apache/cloudstack/issues/3200
>
> I will investigate this further
>
> Andrei
>
> - Original Message -
>> From: "Andrei Mikhailovsky" 
>> To: "Harikrishna Patnala" 
>> Cc: "users" 
>> Sent: Sunday, 31 July, 2022 22:56:31
>> Subject: Re: Unable to login to GUI onto second management server
>
>> Hi Harikrishna,
>>
>> Tried the below, but still have the same issue.
>>
>> also, after trying what you've suggested, I've started the old management 
>> server
>> and I was still able to login. not sure if the host setting does anything 
>> login
>> related...
>>
>> Andrei
>>
>>> From: "Harikrishna Patnala" 
>>> To: "Andrei Mikhailovsky" 
>>> Cc: "users" 
>>> Sent: Thursday, 28 July, 2022 09:54:39
>>> Subject: Re: Unable to login to GUI onto second management server
>>
>>> Hi Andrei,
>>
>>> Can you please also try the below steps? I'm just making sure all pointers 
>>> are
>>> to the new management server only.
>>
>>> 1. Keep only the new management server IP in the host configuration.
>>> 2. Stop the old management server
>>> 3. Restart the new management server
>>> Thanks,
>>> Harikrishna
>>
>>> From: Andrei Mikhailovsky 
>>> Sent: Wednesday, July 27, 2022 6:45 PM
>>> To: Harikrishna Patnala 
>>> Cc: users 
>>> Subject: Re: Unable to login to GUI onto second management server
>>> Hi Harikrishna,
>>
>>> I have added the new management server IP address into the host 
>>> configuration
>>> from the gui. It now shows:
>>
>>> host The ip address of management server. This can also accept 
>>> comma separated
>>> addresses.   Advanced
>>> 192.168.169.13,192.168.169.21
>>
>>> After that I've started the new management server and unfortunately, I still
>>> have the same issue.
>>
>>> I have also noticed that after starting the new management server, the table
>>> mshost has been updated to reflect the server status as Up.:
>>
>>>| 4 | 115129173025114 | 1658099918669 | ais-cloudhost13.csprdc.arhont.com |
>>>| 98405826-0861-11ea-a1da-8003fe80 | Up | 4.16.1.0 | 127.0.0.1 | 9090 |
>>> | 2022-07-27 13:10:05 | NULL | 0 |
>>>| 5 | 165004275141402 | 1658927302926 | ais-compute1.cloud.arhont.com |
>>>| 0d1522a5-5d08-46af-b59c-b577aa22e9bb | Up | 4.16.1.0 | 192.168.169.21 | 
>>>9090 |
>>> | 2022-07-27 13:08:32 | NULL | 0 |
>>
>>> Anything else I should try?
>>
>>> Thanks
>>
>>> Andrei
>>
 From: "Harikrishna Patnala" 
 To: "Andrei Mikhailovsky" , "users"
 
 Sent: Wednesday, 27 July, 2022 07:21:24
 Subject: Re: Unable to login to GUI onto second management server
>>
 Hi Andrei,
>>
 If the purpose of the second management server is about migration please 
 ignore
 the previous reply.
>>
 You have the right pointer to the procedure and I hope you have followed 
 it.
>>
 Please try to provide the following information.
>>
 1. Is the old management server also in the 4.16.1 version?
2. Which database.properties file you have changed to point to the new 
 database
 ?
3. Can you check the database table "configuration", what is the value 
 for the
 configuration with the name "host", is it your new MS host address ?
4. Also, check the "mshost" table in the database if it is pointing to 
 the new
 management server.
 Regards,
 Harikrishna
>>
 From: Andrei Mikhailovsky 
 Sent: Monday, July 25, 2022 7:46 PM
 To: users 
 Cc: Harikrishna Patnala 
 Subject: Re: Unable to login to GUI onto second management server
>>
 Hi Harikrishna,
>>
 Having read the links that you've sent I am not sure that my issues are 
 related.
 Perhaps I should have explained my current set up / intensions a bit more. 
 My
 main reasons for adding the multiple management servers is not to provide 
 the
 HA / load balancing, but rather to migrate the current management server 
 from
 old hardw

Re: VR for VPC won't start anymore

2022-08-03 Thread vas...@gmx.de 
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 :

> It looks there is no entry in template_store_ref table for the systemvm
> template
>
> -Wei
>
> On Wed, 3 Aug 2022 at 21:43, vas...@gmx.de  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":
> > "xx", "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

Re: VR for VPC won't start anymore

2022-08-03 Thread Wei ZHOU 
It looks there is no entry in template_store_ref table for the systemvm
template

-Wei

On Wed, 3 Aug 2022 at 21:43, vas...@gmx.de  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":
> "xx", "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

VR for VPC won't start anymore

2022-08-03 Thread vas...@gmx.de 
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":
"xx", "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)

Re: [PROPOSE] CloudStack 4.17.1.0 release and RM

2022-08-03 Thread Nicolas Vazquez 
LGTM thanks Abhishek!

Regards,
Nicolas Vazquez


From: Nux 
Date: Wednesday, 3 August 2022 at 13:31
To: d...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: Re: [PROPOSE] CloudStack 4.17.1.0 release and RM
+1, thanks for volunteering Abhishek. You'll do a great job.

---
Nux
www.nux.ro

On 2022-08-02 18:37, Abhishek Kumar wrote:
> Hi all,
>
> I would like to propose and put myself forward as the release manager
> for the 4.17.1.0 release. My colleague Nicolas Vazquez will support me
> as the co-RM for the PR reviews/tests/merges, and others are welcome
> to support as well.
> We can keep the scope limited to include only bugs, critical issues
> and fixes for a stable release. I see about 89 closed issues/PRs
> already on the 4.17.1.0 milestone[1] and some 24 items are remaining.
>
> I propose the following timeline, aiming to cut the first RC around
> the end of August.
>  - ~3 weeks from now till late August 2022 (Ongoing): Accept all
> bugs, issues and minor improvements allowed in LTS [2]
>  - 1 week: Accept only critical/blocker fixes, stabilize 4.17
> branch
>  - end-August 2022 and onwards: Cut 4.17.1.0 RC1 and further RCs
> if necessary, start/conclude vote, and finish release work
>
> Please let me know if you have any thoughts/comments.
>
> [1] https://github.com/apache/cloudstack/milestone/25
> [2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
>
> Regards,
> Abhishek

Re: Terraform Cloudstack module

2022-08-03 Thread Niclas Lindblom 
And of course as soon as I posted this I realised my own stupidity, but I 
thought I share it.

I store some static key pair values in Consul that are retrieved by the Consul 
Terraform module where there was a case sensitivity mismatch

Large Instance (Cloudstack) was retrieved as Large instance from the key store 
triggering the Terraform change

However

disk_offering I had as “custom” which is what the documentation states, but 
should be “Custom” for Terraform to match and not trigger a disk change

Niclas 

> On 3 Aug 2022, at 18:46, Niclas Lindblom  
> wrote:
> 
> Hello,
> 
> I am not sure if the Cloudstack Terraform module is community supported 
> through this forum, but I have an issue which I am not sure if it is with the 
> module or with Terraform itself. When I deploy a virtual machine and 
> create/attach a disk it works fine on the first run and the resources are 
> created. However, when I run Terraform again without any code changes, 
> Terraform detects that the resources needs to be upgraded (which isn’t the 
> case) and then fails with the message in my case:
> 
> Error changing the service offering for instance 
> VM-c3a9b229-f817-47ea-8f8b-99fe13dbf003: CloudStack API error 431 
> (CSExceptionErrorCode: 4350): Not upgrading vm VM instance {id: "64", name: 
> "i-2-64-VM", uuid: "c3a9b229-f817-47ea-8f8b-99fe13dbf003", type="User"} since 
> it already has the requested service offering (Large Instance)
> 
> Has anyone seen this before and have any advise to offer ? 
> 
> Terraform version: 1.2.6
> Cloudstack version: 4.17.0
> Terraform Cloudstack Module: 0.4.0
> 
> Regards
> 
> Niclas



smime.p7s
Description: S/MIME cryptographic signature

Terraform Cloudstack module

2022-08-03 Thread Niclas Lindblom 
Hello,

I am not sure if the Cloudstack Terraform module is community supported through 
this forum, but I have an issue which I am not sure if it is with the module or 
with Terraform itself. When I deploy a virtual machine and create/attach a disk 
it works fine on the first run and the resources are created. However, when I 
run Terraform again without any code changes, Terraform detects that the 
resources needs to be upgraded (which isn’t the case) and then fails with the 
message in my case:

Error changing the service offering for instance 
VM-c3a9b229-f817-47ea-8f8b-99fe13dbf003: CloudStack API error 431 
(CSExceptionErrorCode: 4350): Not upgrading vm VM instance {id: "64", name: 
"i-2-64-VM", uuid: "c3a9b229-f817-47ea-8f8b-99fe13dbf003", type="User"} since 
it already has the requested service offering (Large Instance)

Has anyone seen this before and have any advise to offer ? 

Terraform version: 1.2.6
Cloudstack version: 4.17.0
Terraform Cloudstack Module: 0.4.0

Regards

Niclas

smime.p7s
Description: S/MIME cryptographic signature

Re: [PROPOSE] CloudStack 4.17.1.0 release and RM

2022-08-03 Thread Nux 

+1, thanks for volunteering Abhishek. You'll do a great job.

---
Nux
www.nux.ro

On 2022-08-02 18:37, Abhishek Kumar wrote:

Hi all,

I would like to propose and put myself forward as the release manager
for the 4.17.1.0 release. My colleague Nicolas Vazquez will support me
as the co-RM for the PR reviews/tests/merges, and others are welcome
to support as well.
We can keep the scope limited to include only bugs, critical issues
and fixes for a stable release. I see about 89 closed issues/PRs
already on the 4.17.1.0 milestone[1] and some 24 items are remaining.

I propose the following timeline, aiming to cut the first RC around
the end of August.
 - ~3 weeks from now till late August 2022 (Ongoing): Accept all
bugs, issues and minor improvements allowed in LTS [2]
 - 1 week: Accept only critical/blocker fixes, stabilize 4.17 
branch

 - end-August 2022 and onwards: Cut 4.17.1.0 RC1 and further RCs
if necessary, start/conclude vote, and finish release work

Please let me know if you have any thoughts/comments.

[1] https://github.com/apache/cloudstack/milestone/25
[2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS

Regards,
Abhishek

Re: Usage service issue on Ubuntu

2022-08-03 Thread Vivek Kumar 
Hello Folks,

Can anyone help me on this ?


Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 28-Jul-2022, at 10:55 PM, Vivek Kumar  wrote:
> 
> Hello Wei, 
> 
> Any suggestion on below issue ?
> 
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> TechOps | Indiqus Technologies
> 
> vivek.ku...@indiqus.com 
>   www.indiqus.com 
> 
> 
> 
> 
>> On 22-Jul-2022, at 1:52 PM, Vivek Kumar > > wrote:
>> 
>> Hello Wei, 
>> 
>> Thanks for the response..! Please find the content below - 
>> 
>> 
>> 
>> 
>> 
>> 
>> http://jakarta.apache.org/log4j/ 
>> " debug="false">
>> 
>>
>>
>>
>> 
>>
>>   
>>   
>> 
>>   
>>  
>>   
>>
>> 
>>
>>
>>
>> 
>>
>>> class="org.apache.log4j.rolling.RollingFileAppender">
>>   
>>   
>>   
>> > value="/var/log/cloudstack/usage/usage.log.%d{-MM-dd}{GMT}.gz"/>
>> > value="/var/log/cloudstack/usage/usage.log"/>
>>   
>> 
>>   
>>  
>>   
>>
>> 
>>
>>
>>
>> 
>>
>>  
>>
>> 
>>
>>
>>   
>>
>> 
>>
>>   
>>
>> 
>>
>>  
>>
>> 
>>
>>
>>
>> 
>>
>>   
>>   
>>   
>>
>> 
>> 
>> 
>> 
>> Vivek Kumar
>> Sr. Manager - Cloud & DevOps
>> TechOps | Indiqus Technologies
>> 
>> vivek.ku...@indiqus.com 
>>  www.indiqus.com 
>> 
>> 
>> 
>> 
>>> On 22-Jul-2022, at 1:47 PM, Wei ZHOU >> > wrote:
>>> 
>>> Hi Vivek,
>>> 
>>> Can you share the log4j conf file `/etc/cloudstack/usage/log4j-cloud.xml` ?
>>> 
>>> -Wei
>>> 
>>> On Fri, 22 Jul 2022 at 08:31, Vivek Kumar >> >
>>> wrote:
>>> 
 Hello Folks,
 
 Can anyone help me on this ?
 
 
 Vivek Kumar
 Sr. Manager - Cloud & DevOps
 TechOps | Indiqus Technologies
 
 vivek.ku...@indiqus.com  
 >
www.indiqus.com  >
 
 
 
 
> On 14-Jul-2022, at 12:41 PM, Vivek Kumar  >
 wrote:
> 
> Hello Folks,
> We have deployed cloudstack 4.16.1 on ubuntu OS. Management service is
 working fine but getting error with cloudstack-usage. This is a clean new
 installation. Can someone help me out ? Pasting the details below -
> 
> 
> 
> root@SPRPVTCLDACS02:~# systemctl status cloudstack-usage
> ● cloudstack-usage.service - CloudStack Usage Server
> Loaded: loaded (/lib/systemd/system/cloudstack-usage.service;
 enabled; vendor preset: enabled)
> Active: activating (auto-restart) (Result: exit-code) since Thu
 2022-07-14 11:17:16 IST; 3s ago
>   Docs: http://www.cloudstack.org/  
> >
>Process: 294817 ExecStart=/bin/sh -ec /usr/bin/java
 -Dpid=${JAVA_PID} $JAVA_OPTS $JAVA_DEBUG -cp $CLASSPATH $JAVA_CLASS
 (code=exited, status=1/FAILURE)
>   Main PID: 294817 (code=exited, status=1/FAILURE)
> 
> Jul 14 11:17:27 SPRPVTCLDACS02 systemd[1]: cloudstack-usage.service:
 Scheduled restart job, restart counter is at 4970.
> Jul 14 11:17:27 SPRPVTCLDACS02 systemd[1]: Stopped CloudStack Usage
 Server.
> Jul 14 11:17:27 SPRPVTCLDACS02 systemd[1]: Started CloudStack Usage
 Server.
> Jul 14 11:17:27 SPRPVTCLDACS02 sh[294878]: log4j:WARN No appenders could
 be found for logger (com.cloud.utils.LogUtils).
> Jul 14 11:17:27 SPRPVTCLDACS02 sh[294878]: log4j:WARN Please initialize
 the log4j system properly.
> Jul 14 11:17:27 SPRPVTCLDACS02 sh[294878]: log4j:WARN See
 http://logging.apache.org/log4j/1.2/faq.html#noconfig 
  <
 http://logging.apache.org/log4j/1.2/faq.html#noconfig 
 > for more info.
> Jul 14 11:17:28 SPRPVTCLDACS02 sh[294878]: SLF4J: Failed to load class
 "org.slf4j.impl.StaticLoggerBinder".
> Jul 14 11:17:28 SPRPVTCLDACS02 sh[294878]: SLF4J: Defaulting to
 no-operation (NOP) logger implementation
> Jul 14 11:17:28 SPRPVTCLDACS02 sh[294878]: SLF4J: See
 http://www.slf4j.org/codes.html#StaticLoggerBinder 
  <
 http://www.slf4j.org/codes.html#StaticLoggerBinder 
 > for further details.
> Jul 14 11:17:30 SPRPVTCLDACS02 sh[294878

kubertes tables CS 4.15.2

2022-08-03 Thread Olivier GUIN 

Hello,

Following a restoration of my database, I no longer have the kubernetes_ 
tables.


I am using CS 4.15.2Do you know how I can import the definitions of 
these tables?


I was not using Kubernetes so the tables are normally empty!


Thank you,

Best regards,
Olivier

Re: [PROPOSE] CloudStack 4.17.1.0 release and RM

2022-08-03 Thread Rohit Yadav 
+1 thanks for volunteering, looks good to me.

Regards.

Regards.

From: Harikrishna Patnala 
Sent: Wednesday, August 3, 2022 6:57:35 AM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: [PROPOSE] CloudStack 4.17.1.0 release and RM

Looks good Abhishek and thanks for volunteering.

Regards,
Harikrishna

From: Abhishek Kumar 
Sent: Tuesday, August 2, 2022 11:07 PM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: [PROPOSE] CloudStack 4.17.1.0 release and RM

Hi all,

I would like to propose and put myself forward as the release manager for the 
4.17.1.0 release. My colleague Nicolas Vazquez will support me as the co-RM for 
the PR reviews/tests/merges, and others are welcome to support as well.
We can keep the scope limited to include only bugs, critical issues and fixes 
for a stable release. I see about 89 closed issues/PRs already on the 4.17.1.0 
milestone[1] and some 24 items are remaining.

I propose the following timeline, aiming to cut the first RC around the end of 
August.
 - ~3 weeks from now till late August 2022 (Ongoing): Accept all bugs, 
issues and minor improvements allowed in LTS [2]
 - 1 week: Accept only critical/blocker fixes, stabilize 4.17 branch
 - end-August 2022 and onwards: Cut 4.17.1.0 RC1 and further RCs if 
necessary, start/conclude vote, and finish release work

Please let me know if you have any thoughts/comments.

[1] https://github.com/apache/cloudstack/milestone/25
[2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS

Regards,
Abhishek