-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Core updating logs shows empty messages in some scenarios. #423
Comments
weird, looks like a bug. we should fix this before 0.3.0 is out I think |
fix must PR onto release-0.3.0 branch |
@davitol should I use the market shipped with 10.0.10 for the env? |
@VicDeo no I think it was discovered while testing market 0.3.0, see #417 (comment) for the tarball |
As already clarified via Rocket.Chat, the market app used in this specific scenario was the one included in ownCloud daily master tarball |
@davitol it's not related to the password policy update path... Here are my steps:
result
|
@VicDeo Which password_policy version did you get after the core upgrade? |
may be I need to remove |
The same when the app code is missing
|
@davitol 1.0.3, as per your report |
@VicDeo Then there's definitely something different in our tests due to I got the 2.11. Later I will retest and post here the results |
@davitol I mean that I start with v1.0.3
|
@VicDeo retested and keeps happening to me from 10.0.10 to daily master using tarballs
|
Comment that previously i run a "non-success" upgrade due to I had to disable
|
Ok, i'll recheck with |
@davitol the results are still not the same in yours.
|
@davitol in your case |
@VicDeo I have just reproduced it again, and i think I don't miss nothing in the steps above. If you want we can have an screensharing and I will show how i tested it |
let's defer this, it's not a regression |
Initial stateconfig.php
Enabled apps
occ status
occ upgrade
apps after upgrade
|
@davitol could it be a connectivity issue in your case?
For me it is just
|
moving to backlog for now, not critical |
Description
Core updating logs shows empty messages in some scenarios.
Steps to reproduce
1 . Having an oC 10.0.10 server, install password policy v1.0.3 using a tarball
2. Upgrade oC server to daily master
Expected result
Upgrade Logs should show the version Password Policy was upgraded
Current behavior
The app gets updated from 1.0.3 to 2.11 when I make a oC major update but the upgrade output shows like an exception with an empty message.
Note: There was a password policy major version only available for master (max-version 11) that is the one that is finally updated, different from the major version of 10.0.10.
Before update:
After update:
@VicDeo
The text was updated successfully, but these errors were encountered: