Certificate verify failed after enabling the force_https option in astute
Bug #1675701 reported by
Ilya Bumarskov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Ilya Bumarskov |
Bug Description
Fuel 10 build# 1501
Steps to reproduce:
On master node:
echo -e '"SSL":\n "force_https": "true"' >> /etc/fuel/
puppet apply /etc/puppet/
systemctl restart nailgun
Then try to execute any cli command:
[root@nailgun ~]# fuel2 release list
[SSL: CERTIFICATE_
Changed in fuel: | |
importance: | Undecided → High |
milestone: | none → 10.1 |
Changed in fuel: | |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
tags: | added: swarm-fail |
Changed in fuel: | |
status: | New → Confirmed |
tags: | added: area-python |
Changed in fuel: | |
assignee: | Fuel Sustaining (fuel-sustaining-team) → Stanislaw Bogatkin (sbogatkin) |
Changed in fuel: | |
assignee: | Stanislaw Bogatkin (sbogatkin) → Ilya Bumarskov (ibumarskov) |
Changed in fuel: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
I suppose that in our case there is much easier to add this certificate to trusted as we do for slave nodes. So, in test we need to place it in /etc/pki/ ca-trust/ source/ anchors/ <cert_name> .pem, then run "update-ca-trust force-enable" and then "update- ca-certificates ". After this test should pass.