[QA] upgrade from 2.0.0 to 2.1.0 disconnects the elastic host

[jnweiger]

Seen with 2.1.0 on owncloud 10.9.1

• configure 2.0.0 in the admin settings search. There is only one text field, input the elastic server address there '172.17.0.3:9200`

• the connection icon turns from red to green.

• occ search:index:update indexes all my 9 files.
  

• upgrade the app to version 2.1.0

• run occ upgrade

• the search engine becomes defunct. The search host in the admin UI is replaced with the string on
  

Expected behaviour:

• the config is preserved.
• having no username and password is accepted, as it was acceptable before.

Workaround:

• re-enter host:port
• enter random username and password.

[jnweiger]

The output from occ upgrade is

 occ upgrade
ownCloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
2022-02-18T17:31:56+00:00 Set log level to debug
2022-02-18T17:31:56+00:00 Turned on maintenance mode
2022-02-18T17:31:56+00:00 Repair step: Upgrade app code from the marketplace
2022-02-18T17:31:56+00:00 Repair step: Repair MySQL database engine
2022-02-18T17:31:56+00:00 Repair step: Repair MySQL collation
2022-02-18T17:31:56+00:00 Repair info: Change collation for oc_migrations ...
2022-02-18T17:31:56+00:00 Repair step: Repair SQLite autoincrement
2022-02-18T17:31:56+00:00 Repair step: Repair orphaned reshare
2022-02-18T17:31:56+00:00 Repair step: Repair duplicate entries in oc_lucene_status
2022-02-18T17:31:56+00:00 Repair info: lucene_status table does not exist -> nothing to do
2022-02-18T17:31:56+00:00 Updating database schema
2022-02-18T17:31:56+00:00 Updated database
2022-02-18T17:31:57+00:00 Updating <search_elastic> ...
2022-02-18T17:31:57+00:00 Updated <search_elastic> to 2.1.0
2022-02-18T17:31:57+00:00 Repair step: Repair mime types
2022-02-18T17:31:57+00:00 Repair step: Detect file cache entries with path that does not match parent-child relationships
2022-02-18T17:31:57+00:00 Repair step: Generate ETags for file where no ETag is present.
2022-02-18T17:31:57+00:00 Repair info: ETags have been fixed for 0 files/folders.
2022-02-18T17:31:57+00:00 Repair step: Clean tags and favorites
2022-02-18T17:31:57+00:00 Repair info: 0 tags of deleted users have been removed.
2022-02-18T17:31:57+00:00 Repair info: 0 tags for delete files have been removed.
2022-02-18T17:31:57+00:00 Repair info: 0 tag entries for deleted tags have been removed.
2022-02-18T17:31:57+00:00 Repair info: 0 tags with no entries have been removed.
2022-02-18T17:31:57+00:00 Repair step: Drop old database tables
2022-02-18T17:31:57+00:00 Repair step: Drop old background jobs
2022-02-18T17:31:57+00:00 Repair step: Remove getetag entries in properties table
2022-02-18T17:31:57+00:00 Repair info: Removed 0 unneeded "{DAV:}getetag" entries from properties table.
2022-02-18T17:31:57+00:00 Repair step: Repair invalid shares
2022-02-18T17:31:57+00:00 Repair step: Repair sub shares
2022-02-18T17:31:57+00:00 Repair step: Remove old share propagation app entries
2022-02-18T17:31:57+00:00 Repair step: Move user avatars outside the homes to the new location
2022-02-18T17:31:57+00:00 Repair info: No action required
2022-02-18T17:31:57+00:00 Repair step: Fix user avatars location
2022-02-18T17:31:57+00:00 Repair info: No action required
2022-02-18T17:31:57+00:00 Repair step: Remove shares of a users root folder
2022-02-18T17:31:57+00:00 Repair step: Repair unmerged shares
2022-02-18T17:31:57+00:00 Repair step: Disable extra themes
2022-02-18T17:31:57+00:00 Starting code integrity check...
2022-02-18T17:32:18+00:00 Finished code integrity check
2022-02-18T17:32:18+00:00 Update successful
2022-02-18T17:32:18+00:00 Turned off maintenance mode
2022-02-18T17:32:18+00:00 Reset log level

[hodyroff]

Yes, the olf config must be preserverd.
It must still be possible to work unauthenticated.

[pmaier1]

Blocker for the search_elastic 2.1.0 release.
@ahherrera can you check, please?

[jnweiger]

Alberto cannot reproduce. And I cannot reproduce either.
We both can upgrade just fine now... hmm.

Trying things:

• Refresh bbrowser before occ upgrade,
• Switch external storages checkbox before refreshing.
• Have te Settings-Search page open while running occ refresh,
• After installing the new version, click elsewhere, so that the blue refresh popup comes up, then run occ refresh.
  None of this reproduces the error.

Sorry for the spurious alert. Closing.