Bug 45510 – Upload of Activation license fails with "certificate verify failed (certificate is not yet valid)"

Bug 45510 - Upload of Activation license fails with "certificate verify failed (certificate is not yet valid)"


Summary:	Upload of Activation license fails with "certificate verify failed (certifica...

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	License
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.3-0-errata
Assigned To:	Erik Damrose
QA Contact:	Jürn Brodersen

URL:
Keywords:

Duplicates:	46098 (view as bug list)
Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-10-12 14:09 CEST by Nico Gulden
Modified:	2020-03-13 09:33 CET (History)
CC List:	2 users (show)

See Also:	50947
What kind of report is it?:	Bug Report
What type of bug is this?:	6: Setup Problem: Issue for the setup process
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	4: A User would return the product
User Pain:	0.411
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:	Yes
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2017092921000529, 2017092721000792, 2017092221000569, 2017102621000835, 2017102621000031, 2017101221000861, 2018020121000949, 2018013121000288, 2018012821000061, 2018021821000266, 2018021421001049, 2018032421000145, 2018032321000923, 2018032921000743
Bug group (optional):	Appliance, External feedback
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Nico Gulden

2017-10-12 14:09:18 CEST

There have been several feedback tickets with the following error message:

"""The following error occurred:

ldap_start_tls: Connect error (-11)
additional info: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed (certificate is not yet valid)"""

The error occurred during the upload of the activation license with an app appliance.

Comment 1 Nico Gulden

2017-10-12 14:13:25 CEST

First guess: The time on the machine does not match the current time.

Comment 2 Nico Gulden

2017-11-10 14:56:46 CET

Occurred again at Ticket#2017102621000835.

Comment 3 Nico Gulden

2017-11-10 15:01:34 CET

Occurred again on 26. Oct, see Ticket#2017102621000031.

Comment 4 Nico Gulden

2017-11-10 15:47:30 CET

Occurred again on 12. Oct, see Ticket#2017101221000861.

Comment 5 Nico Gulden

2018-02-05 17:24:02 CET

Occurred again: Ticket#2018020121000949

Comment 6 Nico Gulden

2018-02-06 15:14:09 CET

Occurred again: Ticket#2018013121000288

Comment 7 Nico Gulden

2018-02-06 20:14:52 CET

Occurred again at Ticket#2018012821000061.

Comment 9 Nico Gulden

2018-03-15 14:11:07 CET

Occurred again at Ticket#2018021821000266.

Comment 10 Nico Gulden

2018-03-15 14:41:20 CET

Occurred again at Ticket#2018021421001049.

Comment 11 Nico Gulden

2018-03-26 09:38:26 CEST

Occurred again Ticket#2018032421000145

Comment 12 Nico Gulden

2018-03-26 09:48:00 CEST

Occurred again: Ticket#2018032321000923

The same user also had Bug#46098 at Ticket#2018032321000932.

Comment 13 Jürn Brodersen

2018-03-28 17:32:22 CEST

How to reproduce:
Get a (real) Windows machine
Set the clock to UTC-X (I set it to UTC-7)
Setup the Owncloud appliance for virtualbox (Use the same timezone)
Reboot the appliance
Try to get a license -> bug 46098
Try to upload a license -> bug 45510


Workaround:
Open the settings for the appliance
Switch to "System"
Enable "Hardware Clock in UTC-time"

Maybe it's possible to set this option during appliance creation?

Comment 14 Jürn Brodersen

2018-03-28 17:45:30 CEST

VMware Player on Windows doesn't seem to have this problem.

Comment 15 Nico Gulden

2018-04-05 09:56:13 CEST

Occurred again Ticket#2018032921000743

Comment 16 Jürn Brodersen

2018-04-06 17:28:35 CEST

*** Bug 46098 has been marked as a duplicate of this bug. ***

Comment 17 Erik Damrose

2018-04-13 10:12:16 CEST

Only occured in Virtualbox. Fixed by creating the virtualbox appliances with preinstalled guest tools.

Appliance for testing
omar:/var/univention/buildsystem2/mirror/appcenter.test/univention-apps/current/owncloud/Univention-App-owncloud-virtualbox.ova

UCS appliances are beeing recreated, too.

Comment 18 Erik Damrose

2018-04-16 09:44:04 CEST

Reopen: Got feedback that the instance does not start on reboot. In my test, a black screen is shown instead of the welcome-screen

Comment 19 Erik Damrose

2018-04-16 14:41:34 CEST

Fixed by blacklisting vboxvideo module

Comment 20 Jürn Brodersen

2018-04-19 12:36:14 CEST

VMWare works -> OK
VirtualBox works -> OK
VritualBox with pacific time on windows works -> OK

-> Verified

Comment 21 Erik Damrose

2018-04-19 12:39:26 CEST

Internal script adaption, nothing to release -> closed