2.2 upgrage to 2.2.1 issue

[andy17612]

Preconditions

1. in magento2.2
2. php7,1

Steps to reproduce

1. I don't know why i in admin > setup upgradd >Update application is running ->will be show error upgrade. Did't suggest anything wrong?
2. i re-installed new 2.2.0 (no date) try to test, upgrade to 2.2.1. still have this problem in upgrade system

Expected result

1. How to solve this issue?

Actual result

1. Update application is not running

Error in Update!
Please refer to documentation Doc link to perform manual rollback.

To attempt automatic rollback, please click the "Rollback" button.

[Module 'Magento_******':
Running schema recurring...Source class "\SignifydAvsDefault" for "SignifydAvsDefaultMapper" generation does not exist.

[2017-11-10 11:19:32 UTC] Job "setup:upgrade {"command":"setup:upgrade"}" has been successfully completed
[2017-11-10 11:19:32 UTC] Job "setup:static:regenerate []" has started

[2017-11-10 11:19:32 UTC] Cleaning generated files...
[2017-11-10 11:19:32 UTC] Clearing cache...
[2017-11-10 11:20:12 UTC] Cleaning static view files
[2017-11-10 11:20:12 UTC] Job "setup:static:regenerate []" has been successfully completed
[2017-11-10 11:20:12 UTC] Job "setup:maintenance:disable []" has started
Disabled maintenance mode

[2017-11-10 11:20:12 UTC] Job "setup:maintenance:disable []" has been successfully completed

[amirhmoradi]

Same issue here. Tried to upgrade via cli, and I get this error:
Source class "\SignifydAvsDefault" for "SignifydAvsDefaultMapper" generation does not exist.

[andy17612]

@amirhmoradi
if you fixed it,please tell me

[andy17612]

im still stop and error in @amirhmoradi
[2017-11-11 08:36:19 UTC] Job "setup:maintenance:disable []" has been successfully completed

[andy17612]

i re-installed new 2.2.0 (no date) try to test, upgrade to 2.2.1. still have this issue in upgrade system @amirhmoradi

[evensis]

Delete generated folder.

[andy17612]

delete generated all folder ? @evensis

[evensis]

Yep, just take the entire thing out. Magento will regenerate it on compilation anyway.

[andy17612]

can't , i tryed in ftp delete the file. but the issuee still here.... @evensis
is run command rm -rf generated/* delete or use ftp delete?

Module 'Shopial_******':
Nothing to import.

[2017-11-13 17:36:32 UTC] Job "setup:upgrade {"command":"setup:upgrade"}" has been successfully completed
[2017-11-13 17:36:32 UTC] Job "setup:static:regenerate []" has started

[2017-11-13 17:36:32 UTC] Cleaning generated files...
[2017-11-13 17:36:32 UTC] Clearing cache...
[2017-11-13 17:36:32 UTC] Cleaning static view files
[2017-11-13 17:36:32 UTC] Job "setup:static:regenerate []" has been successfully completed
[2017-11-13 17:36:32 UTC] Job "setup:maintenance:disable []" has started
Disabled maintenance mode

[2017-11-13 17:36:32 UTC] Job "setup:maintenance:disable []" has been successfully completed

[evensis]

rm -rf generated/

I wouldn't ftp delete anything in that folder, paint would dry faster.

Soon as I did that the issue went away for me and I could continue upgrading. I did however have a few problems, so personally created a new git repo, sucked composer in, did a fresh 2.2.1 install via composer and then copied and pasted the app folder from my other repo over the top. Turned out it was Capistrano on my dev server causing the problems however. :-|

Although, the snippet you copied in looks like a successful deploy?

[andy17612]

But system upgrade FAIL on last step: maintenance disable it's made a rollback loop.
I installed new 2.2.0(no data) test to upgrade 2.2.1...same issuee..i dont know why... @evensis

[evensis]

Install fresh 2.2.1 via composer, copy and paste app folder into it from your primary repo (don't copy core Magento stuff if you used flat manual archive), delete generated folder and then run upgrade. See how you get on then, beyond that, deleting the generated folder worked for me (and by looks of it based on the thumbs up on the post, a few of others too).

[andy17612]

but the sql data is 2.2, is work ? @evensis

[evensis]

Yes, it will automatically run schema upgrades.

[andy17612]

but if system upgrade FAIL on last step is no problem too? look like work..but the step made a rollback loop. @evensis