Skip to content
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

Settings view shows upgrade that matches existing version (14 rc2) #10953

Closed
vwbusguy opened this issue Aug 31, 2018 · 5 comments
Closed

Settings view shows upgrade that matches existing version (14 rc2) #10953

vwbusguy opened this issue Aug 31, 2018 · 5 comments
Labels

Comments

@vwbusguy
Copy link

vwbusguy commented Aug 31, 2018

Steps to reproduce

  1. Upgrade to version 14rc2 from 14rc1 (via "Beta" channel)
  2. Open Settings->Administration->Overview
  3. Observe current version is "14.0.0 RC2" and an update is available for "14.0.0 RC2" (See screenshot in next comment)

Expected behaviour

Nextcloud should report that install is at latest version for channel when installed version matches latest in channel.

Actual behaviour

Nextcloud offers an upgrade for version install is already on.

Server configuration

Operating system: Fedora 28

Web server: Apache 2.4.24

Database: MariaDB 10.2.16

PHP version: 7.2.9

Nextcloud version: 14.0.0 RC2

Updated from an older Nextcloud/ownCloud or fresh install: Updated from 14.0.0 RC1

Where did you install Nextcloud from: Initially from tarball from Nextcloud website

Signing status:

Signing status No errors have been found.

List of activated apps:

App list ok 100 OK federation user_ldap systemtags files_texteditor files_pdfviewer serverinfo survey_client accessibility theming user_external gallery files_trashbin files_videoplayer admin_audit support files_sharing password_policy comments sharebymail files_external nextcloud_announcements updatenotification files_versions logreader encryption notifications firstrunwizard activity files_markdown passman bruteforcesettings calendar external deck ocsms contacts socialsharing_facebook notes tasks richdocuments files_automatedtagging files_downloadactivity spreed socialsharing_twitter bookmarks socialsharing_email audioplayer

Nextcloud configuration:

Config report
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder

or 

Insert your config.php content here. 
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)

Are you using external storage, if yes which one: no

Are you using encryption: no

Are you using an external user-backend, if yes which one: no

Client configuration

Browser: Firefox 61.0.2

Operating system: Fedora 28

@vwbusguy
Copy link
Author

screenshot from 2018-08-31 11-27-21

@nextcloud-bot
Copy link
Member

GitMate.io thinks possibly related issues are #2270 (Skipping major versions during upgrade), #2785 (after upgrade theme setting is gone), #2072 (Settings section shows a scrollbar ), #2898 (Upgrade Issue), and #9795 (Upgrade error).

@vwbusguy vwbusguy changed the title Settings view shows upgrade that matched existing version (14 rc2) Settings view shows upgrade that matches existing version (14 rc2) Aug 31, 2018
@vwbusguy
Copy link
Author

Interestingly, I kept checking back while I was trying to figure out why and it eventually went away after about an hour:
screenshot from 2018-08-31 12-26-28

@tflidd
Copy link
Contributor

tflidd commented Sep 2, 2018

I have seen this as well in the NC 14.0.0 RC 1 release. I also got a notification that a new version is available, this is very confusing since I thought to have upgraded just before.

@MorrisJobke
Copy link
Member

I have seen this as well in the NC 14.0.0 RC 1 release. I also got a notification that a new version is available, this is very confusing since I thought to have upgraded just before.

That is weird - usually I can only explain this, that the internal version number has updated, but the readable version was the same.

This is then only a config issue on the updater_server and not in the server I will close this for now. Thanks for the feedback anyways. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants