Re: Failing to download and install cloudstack-agent from deb-repository (Ubuntu 18.04)

2019-10-02 Thread Gabriel Beims Bräscher
Thanks for the update Chris, good news. Have fun ;) @Paul Angus That would be great. I can gather some of the commands and help with an automated way of building the packages. For building packages, I have been using two projects from Khosrow. They basically allow building DEB and RPM packages f

Re: Upgrade to 4.13 failed

2019-10-02 Thread Andrija Panic
- ake sure mgmt is stopped (you can leave it on 4.13 if not already downgraded), stop cloudstack-agents on KVM hosts. - Rollback DB with your SQL statements, that you shared a few emails ago (unfortunately after this 4.12 is NOT possible to work normally...) -Download the new systemVM template - i

Re: Failing to download and install cloudstack-agent from deb-repository (Ubuntu 18.04)

2019-10-02 Thread Christoffer Pedersen
Thank you guys, works like a charm now! Chris On Wed, Oct 2, 2019 at 1:25 AM Gabriel Beims Bräscher wrote: > Hello all, > > Cache has been cleaned up and (noredist) packages are now available also > for Ubuntu (16.04 and 18.04). > > Regards, > Gabriel > > Em seg, 30 de set de 2019 às 18:25, Gab

Re: Upgrade to 4.13 failed

2019-10-02 Thread Fariborz Navidan
I cannot rollback DB to 4.12. How can I download 4.11.3 and and register in DB? On Wed, Oct 2, 2019 at 9:43 PM Andrija Panic wrote: > There's a GitHub issue about this (perhaps you or some colleague?) > > Did you register 4.11.3 (not 4.13) systemVM template? Documentation has > just been updated

Re: Upgrade to 4.13 failed

2019-10-02 Thread Andrija Panic
There's a GitHub issue about this (perhaps you or some colleague?) Did you register 4.11.3 (not 4.13) systemVM template? Documentation has just been updated... Sorry for this. i..e. downgrade packages to 4.12, make sure your DB is rolled back, start 4.12 normally, register 4.11.3 systemVM templat

Re: Upgrade to 4.13 failed

2019-10-02 Thread Fariborz Navidan
Any idea? On Wed, Oct 2, 2019 at 3:59 PM Fariborz Navidan wrote: > Yes, It was clean 4.12 installation. > > On Wed, Oct 2, 2019 at 3:52 PM Andrija Panic > wrote: > >> "was this a clean 4.12 install, then later upgrade - or was it previously >> 4.11.x then 4.12 etc?" >> >> On Wed, 2 Oct 2019 at

Re: Upgrade to 4.13 failed

2019-10-02 Thread Fariborz Navidan
Yes, It was clean 4.12 installation. On Wed, Oct 2, 2019 at 3:52 PM Andrija Panic wrote: > "was this a clean 4.12 install, then later upgrade - or was it previously > 4.11.x then 4.12 etc?" > > On Wed, 2 Oct 2019 at 14:20, Fariborz Navidan > wrote: > > > Which question? > > > > I have sent past

Re: Upgrade to 4.13 failed

2019-10-02 Thread Andrija Panic
"was this a clean 4.12 install, then later upgrade - or was it previously 4.11.x then 4.12 etc?" On Wed, 2 Oct 2019 at 14:20, Fariborz Navidan wrote: > Which question? > > I have sent pastebin link. I lost 4.12 backup accidentally. I am trying to > make 4.13 upgrade successfully. I do run follow

Re: Upgrade to 4.13 failed

2019-10-02 Thread Fariborz Navidan
Which question? I have sent pastebin link. I lost 4.12 backup accidentally. I am trying to make 4.13 upgrade successfully. I do run following commands before upgrade retry: [root@fr-kvm1 ~]# cat rollback.sql delete from guest_os_hypervisor where guest_os_id >= 277; delete from guest_os where id >

Re: Upgrade to 4.13 failed

2019-10-02 Thread Andrija Panic
It was not designed to rollback on its own, you are expected to rollback DB yourself (DB restore) and try again if needed. But you have not answered my question. On Wed, 2 Oct 2019, 13:50 Fariborz Navidan, wrote: > In my experience, if DB upgrade fails, it does not fully rolls back > remaining

Re: clouds stack constantly failed on Centos 7

2019-10-02 Thread Andrija Panic
This is agent log,l. Send management-server.log please. On Wed, 2 Oct 2019, 09:29 Tikk, wrote: > Dear Andrija > > > Please check log file attached in this email. > > > Regards > > Tikk > > > On 10/2/2019 1:03 PM, Andrija Panic wrote: > > Please send management server logs. > > > > Andrija > > >

Re: Upgrade to 4.13 failed

2019-10-02 Thread Fariborz Navidan
In my experience, if DB upgrade fails, it does not fully rolls back remaining 4.13's schema upgraded partially and upon next restart it does not check existence of 4.13's table or columns causing SQL errors complaining about tables or columns already exists. On Wed, Oct 2, 2019 at 3:14 PM Andrija

Re: Upgrade to 4.13 failed

2019-10-02 Thread Andrija Panic
was this a clean 4.12 install, then later upgrade - or was it previously 4.11.x then 4.12 etc? On Wed, 2 Oct 2019 at 12:21, Fariborz Navidan wrote: > https://pastebin.com/2EFm0jaW > > On Wed, Oct 2, 2019 at 1:19 PM Andrija Panic > wrote: > > > (backup, backup, backup...) > > > > Can you send th

Re: Upgrade to 4.13 failed

2019-10-02 Thread Fariborz Navidan
https://pastebin.com/2EFm0jaW On Wed, Oct 2, 2019 at 1:19 PM Andrija Panic wrote: > (backup, backup, backup...) > > Can you send the full logs (passtebin or similar please, not in email) ? > > Andrija >

Re: Failed to move vm

2019-10-02 Thread Andrija Panic
You have to perform the API as admin - are you doing so? On Wed, 2 Oct 2019 at 11:34, Ugo Vasi wrote: > Hi all, > I need to move a VM created by admin user of the ROOT domain to a new > account of sub-account (Test-2/user01) but the procedure fails with this > error message: > > Failed to move v

Re: Upgrade to 4.13 failed

2019-10-02 Thread Andrija Panic
(backup, backup, backup...) Can you send the full logs (passtebin or similar please, not in email) ? Andrija

Failed to move vm

2019-10-02 Thread Ugo Vasi
Hi all, I need to move a VM created by admin user of the ROOT domain to a new account of sub-account (Test-2/user01) but the procedure fails with this error message: Failed to move vm Acct[0efe4d3e...] does not have permission to operate within domain id=165f090c-... Here it is the Manageme

Upgrade to 4.13 failed

2019-10-02 Thread Fariborz Navidan
Hello, Upgrade to 4.13 was failed and downgrade to 4.12 does not work due to datbase modifications and failing to roll back. I failed to take backup of database as well. I have created a rollback sql based on error log step by step after running manual rollback commands. I do run this sql before e

Re: [DISCUSS] Primate - new UI for CloudStack?

2019-10-02 Thread Rohit Yadav
All, Thank you all for your positive support so far. I just want to share that I will start a voting thread on Monday next week, in case there are any further feedback, objections and concerns on the proposal before that. Regards. Regards, Rohit Yadav From: Sy

Re: clouds stack constantly failed on Centos 7

2019-10-02 Thread Tikk
Dear Andrija Please check log file attached in this email. Regards Tikk On 10/2/2019 1:03 PM, Andrija Panic wrote: Please send management server logs. Andrija On Wed, 2 Oct 2019, 03:42 Tikk, wrote: Hi All I have install cloud stack agent on Centos7 VM (vmwareworkstation, 1 vcpu, 2 G