On Wed, Jun 13, 2018 at 11:03 AM, Yedidyah Bar David <didi(a)redhat.com> wrote:
Hi all,
I am working on some bugs [1][2] related to the ovirt-engine-rename tool [3].
I want to hopefully cover all needed changes since I last worked on
this tool, so did this:
Ran engine-setup, kept a list of files it added/changed
Ran rename, checked which of above files still contain the old name.
This is the result:
ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf
- that's [1]
pki/ovirt-engine/certs/engine.cer
- that's ok, we do not rename the engine (engine<->hosts comm)
pki/ovirt-engine/certs/imageio-proxy.cer
- that's [2]
pki/ovirt-engine/certs/jboss.cer
- ok (used only to access jboss directly without httpd proxy)
pki/ovirt-engine/certs/ovirt-provider-ovn.cer
pki/ovirt-engine/certs/ovn-ndb.cer
pki/ovirt-engine/certs/ovn-sdb.cer
- [1]
pki/ovirt-engine/certs/reports.cer
- ok (not used anymore since 4.0)
pki/ovirt-engine/certs/vmconsole-proxy-helper.cer
pki/ovirt-engine/certs/vmconsole-proxy-host.cer
pki/ovirt-engine/certs/vmconsole-proxy-user.cer
- This is the first reason I am sending this email, adding Francesco.
- Should it be changed on rename? I guess so, not sure - and no-one
opened a bug (that I know of)
We did have, though:
https://bugzilla.redhat.com/show_bug.cgi?id=1290088
and that I already noted this there... So can I assume that's enough,
and we do not need to touch vmconsole pki?
--
Didi