Bug 1105995 - neon does not build in 2019-09
Summary: neon does not build in 2019-09
Status: RESOLVED WONTFIX
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other (show other bugs)
Version: Current
Hardware: All openSUSE Factory
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Jason Sikes
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-25 20:00 UTC by Bernhard Wiedemann
Modified: 2018-09-20 17:03 UTC (History)
2 users (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Wiedemann 2018-08-25 20:00:12 UTC
Steps to Reproduce:
osc build --vm-type=kvm --noservice \
 "--build-opt=--vm-custom-opt=-rtc base=2019-09-01"

Actual Results:
ssl................... 55/65 FAIL - fail_nul_cn (verification flags were 22 not
4)
ssl................... 56/65 FAIL - fail_nul_san (verification flags were 22 not 4)

probably some builtin SSL cert expired then.

I wanted to file this upstream, but could not find it.
Comment 1 Jason Sikes 2018-09-09 22:52:58 UTC
Can I ask you to try again? I was working with neon, and after taking a break it now magically works again. I think some people were working on openssl which fixed the problems I was having.

And I, too, have been having trouble connecting to the upstream source. I'm not sure what to do about that.
Comment 2 Jason Sikes 2018-09-09 23:02:20 UTC
(In reply to Bernhard Wiedemann from comment #0)
> Steps to Reproduce:
> osc build --vm-type=kvm --noservice \
>  "--build-opt=--vm-custom-opt=-rtc base=2019-09-01"
> 
> Actual Results:
> ssl................... 55/65 FAIL - fail_nul_cn (verification flags were 22
> not
> 4)
> ssl................... 56/65 FAIL - fail_nul_san (verification flags were 22
> not 4)
> 
> probably some builtin SSL cert expired then.
> 
> I wanted to file this upstream, but could not find it.

Can I ask you to try again? I was working with neon, and after taking a break it now magically works again. I think some people were working on openssl which fixed the problems I was having.

And I, too, have been having trouble connecting to the upstream source. I'm not sure what to do about that.
Comment 3 Bernhard Wiedemann 2018-09-10 11:25:23 UTC
Still the same with current Factory.
Did you try the reproducer?
Comment 4 Jason Sikes 2018-09-11 00:51:50 UTC
(In reply to Bernhard Wiedemann from comment #3)
> Still the same with current Factory.
> Did you try the reproducer?

Not exactly, I removed "--vm-type=kvm" from the command because my system doesn't like kvm.

But this time I did temporarily set my system date to "01 September 2019" and got the same results as you.

You're right. A few built-in ssl certs do expire in August, 2019:
test/nulca.pem, test/nulcn.pem, test/nulsan.pem, and test/nulsan.pem.
Comment 5 Jason Sikes 2018-09-20 17:03:03 UTC
The certificates used in those two tests (fail_nul_cn and fail_nul_san) expire in September, 2019. They are specially-crafted with errors in them for those tests and are not used for anything else.

My suggestion is to disable the tests when the certificates expire.