On Thu, Jul 30, 2020 at 12:42 PM Alex K <rightkickt...@gmail.com> wrote: > > > > On Thu, Jul 30, 2020 at 12:01 PM Yedidyah Bar David <d...@redhat.com> wrote: >> >> On Thu, Jul 30, 2020 at 11:30 AM Alex K <rightkickt...@gmail.com> wrote: >>> >>> >>> >>> On Tue, Jul 28, 2020 at 11:51 AM Anton Louw via Users <users@ovirt.org> >>> wrote: >>>> >>>> >>>> >>>> Hi All, >>>> >>>> >>>> >>>> Does somebody perhaps know the process of changing the Hosted Engine IP >>>> address? I see that it is possible, I am just not sure if it is a straight >>>> forward process using ‘nmtui’ or editing the network config file. I have >>>> also ensured that everything was configured using the FQDN. >>> >>> Since the FQDN is not changing you should not have issues just updating >>> your DNS then changing manually the engine IP from the ifcfg-ethx files >>> then restart networking. >>> What i find difficult and perhaps impossible is to change engine FQDN, as >>> one will need to regenerate all certs from scratch (otherwise you will have >>> issues with several services: imageio proxy, OVN, etc) and there is no such >>> procedure documented/or supported. >> >> >> I wonder - how/what did you search for, that led you to this conclusion? Or >> perhaps you even found it explicitly written somewhere? > > Searching around and testing in LAB. I am testing 4.3 though not 4.4. I used > engine-rename tool and although was able to change fqdn for hosts and engine, > I observed that some certificates were left out (for example OVN was still > complaining about certificate issue with subject name not agreeing with the > new FQDN - checking/downloading the relevant cert was still showing the > previous FQDN). I do not deem successful the renaming of not all services are > functional.
Very well. I'd find your above statement less puzzling if you wrote instead "... and the procedure for doing this is buggy/broken/incomplete"... >> >> >> There actually is: >> >> >> https://www.ovirt.org/documentation/administration_guide/#sect-The_oVirt_Engine_Rename_Tool > > > At this same link it reads: > While the ovirt-engine-rename command creates a new certificate for the web > server on which the Engine runs, it does not affect the certificate for the > Engine or the certificate authority. Due to this, there is some risk involved > in using the ovirt-engine-rename command, particularly in environments that > have been upgraded from Red Hat Enterprise Virtualization 3.2 and earlier. > Therefore, changing the fully qualified domain name of the Engine by running > engine-cleanup and engine-setup is recommended where possible. > explaining my above findings from the tests. No. These are two different things: 1. Bugs. All software has bugs. Hopefully we fix them over time. If you find one, please file it. 2. Inherent design (or other) problems - the software works as intended, but that's not what you want... See also: https://www.ovirt.org/develop/networking/changing-engine-hostname.html >> >> >> That said, it indeed was somewhat broken for some time now - some fixed were >> only added quite recently, and are available only in current 4.4: > > This is interesting and needed for migration scenarios. Can you please elaborate? If it's DR migration, perhaps you want storage export/import, as is done using the DR tool: https://www.ovirt.org/documentation/disaster-recovery-guide/disaster-recovery-guide.html If you just want to use a new name, but do not need to completely forget the old one, you can add it using SSO_ALTERNATE_ENGINE_FQDNS. > Also I am wondering if I can change in some way the management network and > make from untagged to VLAN tagged. Sorry, no idea. Perhaps start a different thread about this. Best regards, >> >> >> https://github.com/oVirt/ovirt-engine/commits/master/packaging/setup/plugins/ovirt-engine-rename >> >> I do not think I am aware of currently still-open bugs. If you find one, >> please file it in bugzilla. Thanks! >> >>> >>> I might be able to soon test this engine IP change in a virtual environment >>> and let you know. >> >> >> Thanks and good luck! >> -- >> Didi > > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/R5ZWCNEL3HPK5VGTTR6TJ7HMIJ5YCV4M/ -- Didi _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/HADIKTQLYKFFA5K3AE6LP2G7I3SDJMF6/
