Failing RSpec test doing certificate vaildation for Kubernetes
This job failure can be reproduced also on Heptapod-0.27.1
Extract:
Failures:
1) Clusters::Platforms::Kubernetes#kubeclient ca_pem is a chain includes chain of certificates
Failure/Error: expect(cert_store.verify(cert1)).to be true
expected true
got false
# ./spec/models/clusters/platforms/kubernetes_spec.rb:243:in `block (4 levels) in <top (required)>'
# ./spec/spec_helper.rb:413:in `block (3 levels) in <top (required)>'
# ./spec/support/sidekiq_middleware.rb:9:in `with_sidekiq_server_middleware'
# ./spec/spec_helper.rb:404:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:400:in `block (3 levels) in <top (required)>'
# ./lib/gitlab/application_context.rb:31:in `with_raw_context'
# ./spec/spec_helper.rb:400:in `block (2 levels) in <top (required)>'
# ./spec/support/database/prevent_cross_joins.rb:102:in `block (3 levels) in <main>'
# ./spec/support/database/prevent_cross_joins.rb:56:in `with_cross_joins_prevented'
# ./spec/support/database/prevent_cross_joins.rb:102:in `block (2 levels) in <main>'
Finished in 26.3 seconds (files took 18.41 seconds to load)
1 example, 1 failure
Failed examples:
rspec ./spec/models/clusters/platforms/kubernetes_spec.rb:231 # Clusters::Platforms::Kubernetes#kubeclient ca_pem is a chain includes chain of certificates
Of course, this test was passing normally at the time of the 0.27.1 release.
As certificate validation can depend on external factors, this is not a surprise. Since GitLab didn't fix it, it could simply mean that our base CI image gets more updated than theirs or something alike.