Correcting few typos:
There are 2 possibilities here
1. Since column reаson was added to table network_acl_item during the DB
schema upgrade from 4.11.2 to 4.12 this likely means that your upgrade failed
on a later step and you've tried to re-execute upgrade script. If so this is
not
There are 2 possibilities here
1. Since column reаson was added to table network_acl_item during the DB
schema upgrade from 4.11.12 to 4.12 this likely means that your upgrade failed
on a later step and you've tried to re-execute upgrade script. If so this is
not a right sequence of recoverin
You need to cleanup entry in vmware_data_center table e.g. assuming you have
unique vmware datacenter names:
delete from vmware_data_center where name='name_of_your_datacenter'
Thanks,
Sergey
On 7/18/20, 9:22 AM, "Rakesh v" wrote:
All the cloudstack management logs are stored in
/var/log
From the log, it looks like the column "reason" already exists in
network_acl_item table. Does this take suppose to have that field in 4.11?
Sent from my iPhone
> On 19-Jul-2020, at 9:30 AM, Ammad Syed wrote:
>
> Hi,
>
> I am trying to upgrade cloudstack from 4.11.3 to 4.13.1. I am having be
Hi,
I am trying to upgrade cloudstack from 4.11.3 to 4.13.1. I am having below
db upgrade error while upgrading. I think the upgrade is executing wrong
script i.e from 4.11.2 to 4.12.0. Please advise.
2020-07-13 20:29:37,650 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle]
(main:null) (logid:) Runni
Hi,
I am trying to upgrade cloudstack from 4.11.3 to 4.13.1. I am having below
db upgrade error while upgrading. I think the upgrade is executing wrong
script i.e from 4.11.2 to 4.12.0. Please advise.
2020-07-13 20:29:37,650 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle]
(main:null) (logid:) Runni
