Bug 1490404 - [RFE] The engine should keep and expose hosts' public keys
Summary: [RFE] The engine should keep and expose hosts' public keys
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Martin Perina
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On: 1441528
Blocks: 1467898
TreeView+ depends on / blocked
 
Reported: 2017-09-11 13:33 UTC by Yedidyah Bar David
Modified: 2020-06-26 16:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-01 14:48:41 UTC
oVirt Team: Infra
Embargoed:
mperina: ovirt-4.5?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1441528 0 high CLOSED [RFE][Rebase] Rebase ovirt-engine on apache-sshd 2.1.0 2021-02-22 00:41:40 UTC

Internal Links: 1441528

Description Yedidyah Bar David 2017-09-11 13:33:03 UTC
Description of problem:

Currently, the engine keeps per-host its public key fingerprint, but does not keep the entire public key.

We want to use the public key for ansible.

This was attempted in the past [1] and abandoned, because it broke compatibility with v3 of the API.

We can now either decide we can break the API, or we can solve in a way that will not break the API - either by keeping both the full key and the fingerprint, and exposing both through the API, or by keeping only the full key, and expose both through the API, where the fingerprint is generated on-the-fly from the full key.

[1] https://gerrit.ovirt.org/50226

Comment 1 Martin Perina 2017-09-15 12:15:22 UTC
Due to capacity reasons moving to 4.2

Comment 2 Michal Skrivanek 2020-03-19 15:42:31 UTC
We didn't get to this bug for more than 2 years, and it's not being considered for the upcoming 4.4. It's unlikely that it will ever be addressed so I'm suggesting to close it.
If you feel this needs to be addressed and want to work on it please remove cond nack and target accordingly.

Comment 3 Michal Skrivanek 2020-04-01 14:48:41 UTC
Closing old bug. Please reopen if still relevant/you want to work on it.


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