Any idea? On Wed, Oct 2, 2019 at 3:59 PM Fariborz Navidan <[email protected]> wrote:
> Yes, It was clean 4.12 installation. > > On Wed, Oct 2, 2019 at 3:52 PM Andrija Panic <[email protected]> > 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 <[email protected]> >> 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 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 >= 277; >> > SET FOREIGN_KEY_CHECKS=0; >> > drop table direct_download_certificate; >> > drop table vpc_offering_details; >> > drop table direct_download_certificate_host_map; >> > drop table template_ovf_properties; >> > SET FOREIGN_KEY_CHECKS=1; >> > alter table data_center drop column sort_key; >> > alter table vpc_offerings drop column sort_key; >> > alter table disk_offering add column domain_id int(32) not null; >> > alter table service_offering_details add constraint >> > uk_service_offering_id_name unique (id); >> > alter table network_offering_details DROP COLUMN `display`; >> > ALTER TABLE `cloud_usage`.`usage_vmsnapshot` DROP COLUMN >> `vm_snapshot_id`; >> > ALTER TABLE `cloud_usage`.`usage_snapshot_on_primary` DROP COLUMN >> > `vm_snapshot_id`; >> > [root@fr-kvm1 ~]# >> > >> > However I don't understand the error I showed you on log in pastebin. >> > Please check and let me know what does it mean. >> > >> > On Wed, Oct 2, 2019 at 3:27 PM Andrija Panic <[email protected]> >> > wrote: >> > >> > > 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, <[email protected]> >> > wrote: >> > > >> > > > 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 Panic < >> [email protected]> >> > > > 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 12:21, Fariborz Navidan < >> [email protected] >> > > >> > > > > wrote: >> > > > > >> > > > > > https://pastebin.com/2EFm0jaW >> > > > > > >> > > > > > On Wed, Oct 2, 2019 at 1:19 PM Andrija Panic < >> > > [email protected]> >> > > > > > wrote: >> > > > > > >> > > > > > > (backup, backup, backup...) >> > > > > > > >> > > > > > > Can you send the full logs (passtebin or similar please, not >> in >> > > > email) >> > > > > ? >> > > > > > > >> > > > > > > Andrija >> > > > > > > >> > > > > > >> > > > > >> > > > > >> > > > > -- >> > > > > >> > > > > Andrija Panić >> > > > > >> > > > >> > > >> > >> >> >> -- >> >> Andrija Panić >> >
