Issue upgrading from 4.3 (Centos 7) to 4.4 (Centos 8)
Hello, I have been trying to upgrade my self-hosted engine from 4.3 to 4.4 but running into issue while performing hosted-engine deploy. Old hypervisor hosts are all running Centos 8 and old ovirt-engine is also running Centos 7. I created a brand new baremental node running Centos 8, Kernel 4.18.0-240.15.1.el8_3.x86_64 and the following engine versions: ovirt-hosted-engine-setup-2.4.9-1.el8.noarch ovirt-hosted-engine-ha-2.4.6-1.el8.noarch ovirt-engine-appliance-4.4-20210323171213.1.el8.x86_64 python3-ovirt-engine-sdk4-4.4.10-1.el8.x86_64 I have many VLANs in my environment. But on this host, I only have these network devices set up (eth0 is the main network, eth1 for storage): # nmcli con NAME UUID TYPE DEVICE ovirtmgmt 02f64861-d992-4e56-8cec-da1906bac09f bridge ovirtmgmt System eth1 bd9e565f-bdc3-4e43-bbd3-5875b9d7fed7 ethernet eth1 virbr0 78e6875d-70f6-4c89-89dd-180dbb9250b1 bridge virbr0 eth0 743b0e26-aae7-44b8-9215-3754a537e90b ethernet eth0 vnet0 bcfead6d-c5b6-4428-9f89-41589735be02 tun vnet0 When I run hosted-engine --deploy --restore-from-file=backup_050321.bck, it hangs after showing: [ INFO ] TASK [ovirt.ovirt.engine_setup : Copy yum configuration file] [ INFO ] changed: [localhost -> ovirt.safari.apple.com] [ INFO ] TASK [ovirt.ovirt.engine_setup : Set 'best' to false] [ INFO ] changed: [localhost -> ovirt.safari.apple.com] [ INFO ] TASK [ovirt.ovirt.engine_setup : Update all packages] virsh shows the VM is in paused state: # virsh list Id Name State ---------------------------------- 1 HostedEngineLocal paused I was able to ssh onto the VM until that point. Do I need to set up all the network connection for all the VLANs before running the deploy script? And how about engine storage domain? I have a new NFS mount ready but it did not ask me about which storage domain to use. Will it ask in later stage? Thanks.
On Wed, May 5, 2021 at 8:18 AM <ling@aliko.com> wrote:
Hello,
I have been trying to upgrade my self-hosted engine from 4.3 to 4.4 but running into issue while performing hosted-engine deploy. Old hypervisor hosts are all running Centos 8 and old ovirt-engine is also running Centos 7.
I created a brand new baremental node running Centos 8, Kernel 4.18.0-240.15.1.el8_3.x86_64 and the following engine versions: ovirt-hosted-engine-setup-2.4.9-1.el8.noarch ovirt-hosted-engine-ha-2.4.6-1.el8.noarch ovirt-engine-appliance-4.4-20210323171213.1.el8.x86_64 python3-ovirt-engine-sdk4-4.4.10-1.el8.x86_64
I have many VLANs in my environment. But on this host, I only have these network devices set up (eth0 is the main network, eth1 for storage): # nmcli con NAME UUID TYPE DEVICE ovirtmgmt 02f64861-d992-4e56-8cec-da1906bac09f bridge ovirtmgmt
Did you create ovirtmgmt manually, or let the deploy script create it?
System eth1 bd9e565f-bdc3-4e43-bbd3-5875b9d7fed7 ethernet eth1 virbr0 78e6875d-70f6-4c89-89dd-180dbb9250b1 bridge virbr0 eth0 743b0e26-aae7-44b8-9215-3754a537e90b ethernet eth0 vnet0 bcfead6d-c5b6-4428-9f89-41589735be02 tun vnet0
When I run hosted-engine --deploy --restore-from-file=backup_050321.bck, it hangs after showing: [ INFO ] TASK [ovirt.ovirt.engine_setup : Copy yum configuration file] [ INFO ] changed: [localhost -> ovirt.safari.apple.com] [ INFO ] TASK [ovirt.ovirt.engine_setup : Set 'best' to false] [ INFO ] changed: [localhost -> ovirt.safari.apple.com] [ INFO ] TASK [ovirt.ovirt.engine_setup : Update all packages]
You can disable this "Update all packages" by passing e.g.: hosted-engine --deploy --ansible-extra-vars=he_offline_deployment=true
virsh shows the VM is in paused state: # virsh list Id Name State ---------------------------------- 1 HostedEngineLocal paused
Any idea what made it become paused? Please check relevant logs (e.g. /var/log/messages, /var/log/libvirt/qemu/*, /var/log/vdsm/*).
I was able to ssh onto the VM until that point.
You mean, until it became paused? Or also after that?
Do I need to set up all the network connection for all the VLANs before running the deploy script?
In principle you should do nothing - just tell the process which NIC to use for ovirtmgmt, and it will configure ovirtmgmt for you. All the other network configuration you can/should do from inside the engine admin ui. If you have other networks marked "required", the deployment process will fail trying to add the host to the engine (because it can't know which NICs/VLANs should be used for which networks) and will pause, waiting for you to remove some lock file, letting you fix stuff manually. See also: https://bugzilla.redhat.com/1893385 .
And how about engine storage domain? I have a new NFS mount ready but it did not ask me about which storage domain to use. Will it ask in later stage?
Yes, storage is handled (also asked about) in a later stage, after the engine is up and the host added to it.. This is a change from <= 4.2, and was done so that we can use the engine (and vdsm) for this, instead of duplicating their functionality in the deploy code. Good luck and best regards, -- Didi
Hi, On Wed, May 5, 2021 1:40 am, Yedidyah Bar David wrote:
And how about engine storage domain? I have a new NFS mount ready but it did not ask me about which storage domain to use. Will it ask in later stage?
Yes, storage is handled (also asked about) in a later stage, after the engine is up and the host added to it.. This is a change from <= 4.2, and was done so that we can use the engine (and vdsm) for this, instead of duplicating their functionality in the deploy code.
Color me confused... How does this work? If I'm installing CentOS and then the Engine into the Hosted-Engine VM, don't I need a storage domain for that OS defined in order for me to install the OS into the VM? This sounds like a bootstrapping problem? Or do I install into some temporary storage and then once the Engine + VDSM are up and running I can assign the permanent storage and it will save/copy the temporary storage over to the permanent storage? But in the latter case, that would imply the ability to move the hosted-engine storage domain from one place to another? Or does 4.4 remove the ability to install the hosted-engine into a CentOS OS and instead one must always use a Hosted Engine appliance? NB: I installed back at 4.0 and have been upgrading ever since, so I've never had to re-install the engine from scratch; I know I will need to do that if I ever decide to upgrade from 4.3.10 to 4.4 (which, frankly, I am not looking forward to doing any time soon).
Good luck and best regards,
-derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
On Wed, May 5, 2021 at 4:20 PM Derek Atkins <derek@ihtfp.com> wrote:
Hi,
On Wed, May 5, 2021 1:40 am, Yedidyah Bar David wrote:
And how about engine storage domain? I have a new NFS mount ready but it did not ask me about which storage domain to use. Will it ask in later stage?
Yes, storage is handled (also asked about) in a later stage, after the engine is up and the host added to it.. This is a change from <= 4.2, and was done so that we can use the engine (and vdsm) for this, instead of duplicating their functionality in the deploy code.
Color me confused... How does this work?
Please review: https://www.ovirt.org/images/Hosted-Engine-4.3-deep-dive.pdf
If I'm installing CentOS and then the Engine into the Hosted-Engine VM, don't I need a storage domain for that OS defined in order for me to install the OS into the VM? This sounds like a bootstrapping problem?
Or do I install into some temporary storage and then once the Engine + VDSM are up and running I can assign the permanent storage and it will save/copy the temporary storage over to the permanent storage? But in the latter case, that would imply the ability to move the hosted-engine storage domain from one place to another?
Or does 4.4 remove the ability to install the hosted-engine into a CentOS OS and instead one must always use a Hosted Engine appliance?
NB: I installed back at 4.0 and have been upgrading ever since, so I've never had to re-install the engine from scratch; I know I will need to do that if I ever decide to upgrade from 4.3.10 to 4.4 (which, frankly, I am not looking forward to doing any time soon).
Good luck and best regards,
-derek
-- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
-- Didi
Hi, On Wed, May 5, 2021 9:24 am, Yedidyah Bar David wrote:
On Wed, May 5, 2021 at 4:20 PM Derek Atkins <derek@ihtfp.com> wrote:
Hi,
On Wed, May 5, 2021 1:40 am, Yedidyah Bar David wrote:
And how about engine storage domain? I have a new NFS mount ready but
it
did not ask me about which storage domain to use. Will it ask in later stage?
Yes, storage is handled (also asked about) in a later stage, after the engine is up and the host added to it.. This is a change from <= 4.2, and was done so that we can use the engine (and vdsm) for this, instead of duplicating their functionality in the deploy code.
Color me confused... How does this work?
Please review: https://www.ovirt.org/images/Hosted-Engine-4.3-deep-dive.pdf
Thanks. However nowhere in those slides does it talk about when one would install the Engine VM base OS. So my questions (quoted below) still apply.
If I'm installing CentOS and then the Engine into the Hosted-Engine VM, don't I need a storage domain for that OS defined in order for me to install the OS into the VM? This sounds like a bootstrapping problem?
Or do I install into some temporary storage and then once the Engine + VDSM are up and running I can assign the permanent storage and it will save/copy the temporary storage over to the permanent storage? But in the latter case, that would imply the ability to move the hosted-engine storage domain from one place to another?
Or does 4.4 remove the ability to install the hosted-engine into a CentOS OS and instead one must always use a Hosted Engine appliance?
NB: I installed back at 4.0 and have been upgrading ever since, so I've never had to re-install the engine from scratch; I know I will need to do that if I ever decide to upgrade from 4.3.10 to 4.4 (which, frankly, I am not looking forward to doing any time soon).
Good luck and best regards,
-derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
On Wed, May 5, 2021 at 8:47 PM Derek Atkins <derek@ihtfp.com> wrote:
Hi,
On Wed, May 5, 2021 9:24 am, Yedidyah Bar David wrote:
On Wed, May 5, 2021 at 4:20 PM Derek Atkins <derek@ihtfp.com> wrote:
Hi,
On Wed, May 5, 2021 1:40 am, Yedidyah Bar David wrote:
And how about engine storage domain? I have a new NFS mount ready but
it
did not ask me about which storage domain to use. Will it ask in later stage?
Yes, storage is handled (also asked about) in a later stage, after the engine is up and the host added to it.. This is a change from <= 4.2, and was done so that we can use the engine (and vdsm) for this, instead of duplicating their functionality in the deploy code.
Color me confused... How does this work?
Please review: https://www.ovirt.org/images/Hosted-Engine-4.3-deep-dive.pdf
Thanks. However nowhere in those slides does it talk about when one would install the Engine VM base OS. So my questions (quoted below) still apply.
You are most welcome to simply study the (ansible) sources: https://github.com/oVirt/ovirt-ansible-collection/tree/master/roles/hosted_e... Basically, the process: 1. Prompts for various details 2. Creates a local libvirt VM on local storage from the appliance image (+these details) 3. Starts this VM as HostedEngineLocal 4. Runs engine-setup, adds the host to the engine 5. Then prompts for storage details etc. 6. Creates the storage domain, edits the engine db a bit, shuts down the VM, edits it a bit further 7. Copies the VM's disk to the shared storage 8. Starts the HA daemons and let them start the engine vm I hope this clarifies.
If I'm installing CentOS and then the Engine into the Hosted-Engine VM, don't I need a storage domain for that OS defined in order for me to install the OS into the VM? This sounds like a bootstrapping problem?
Or do I install into some temporary storage and then once the Engine + VDSM are up and running I can assign the permanent storage and it will save/copy the temporary storage over to the permanent storage? But in the latter case, that would imply the ability to move the hosted-engine storage domain from one place to another?
See above. In theory, you can indeed manually update conf where needed to move the engine to another storage. In practice this was never considered important enough, and somewhat risky, so was never done. The documented way to do that is using engine-backup and hosted-engine --deploy --import-from-file.
Or does 4.4 remove the ability to install the hosted-engine into a CentOS OS and instead one must always use a Hosted Engine appliance?
This was done in 4.1, 4 years ago: https://bugzilla.redhat.com/1366183
NB: I installed back at 4.0 and have been upgrading ever since, so I've never had to re-install the engine from scratch; I know I will need to do that if I ever decide to upgrade from 4.3.10 to 4.4 (which, frankly, I am not looking forward to doing any time soon).
So this is indeed new to you. I hope that's ok :-). At first I was also somewhat hesitant about this, losing so much flexibility. But in practice, I can't remember even one case of someone asking to have this back. The appliance simply works, and works well, is far easier and faster to install than anything else (unless you had a very fine-tuned PXE installation system), and we still provide enough flexibility (IMO) using ansible hooks - see above link to the sources (github shows you the README in that directory). And, BTW, the appliance is not like ovirt-node - once you install it, it's just a plain normal CentOS machine - you upgrade stuff using 'dnf update' and 'engine-setup', etc. Best regards,
Good luck and best regards,
-derek
-- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
-- Didi
Didi, [snip] Thank you for all the details (which I cut from the reply). It's all useful information, and as you noticed, I've not had to install the engine in a while. Moreover....
And, BTW, the appliance is not like ovirt-node - once you install it, it's just a plain normal CentOS machine - you upgrade stuff using 'dnf update' and 'engine-setup', etc.
*THIS* truly answers my underlying question(s). I was concerned that the engine would be like the node, but this assures me it is not, it's just a "faster" way to build the engine VM, but it turns into (effectively) a standard CentOS+Engine VM post-install... Which SHOULD be good enough for what I want to do! (I have the engine running a few extra services, and wanted to make sure I could continue to do so). FWIW, I have a few extra services running on my host, too, but I think I would change that if I ever added additional hardware (currently running single-host). Thank you again for humoring me and answering my questions, even the ones I didn't explicitly ask!
Best regards,
-derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
On Fri, May 7, 2021 at 2:39 AM Derek Atkins <derek@ihtfp.com> wrote: [snip]
*THIS* truly answers my underlying question(s). I was concerned that the engine would be like the node, but this assures me it is not, it's just a "faster" way to build the engine VM, but it turns into (effectively) a standard CentOS+Engine VM post-install... Which SHOULD be good enough for what I want to do! (I have the engine running a few extra services, and wanted to make sure I could continue to do so).
OK. But in the mid term the problem will impact you anyway. What to do after 31/12/2021 with this system, as no new updates from CentOS repos? I think in the next months it would be nice to have at least a CentOS --> CentOS Stream migration path for the Hosted Engine VM or for an external engine that are now based on CentOS Or to confirm that the standard path described at https://centos.org/centos-stream/ works also for CentOS systems where oVirt repos are configured and active and engine packages installed. Currently it says: dnf swap centos-linux-repos centos-stream-repos dnf distro-sync Gianluca
HI, On Fri, May 7, 2021 2:55 am, Gianluca Cecchi wrote:
On Fri, May 7, 2021 at 2:39 AM Derek Atkins <derek@ihtfp.com> wrote: [snip]
*THIS* truly answers my underlying question(s). I was concerned that the engine would be like the node, but this assures me it is not, it's just a "faster" way to build the engine VM, but it turns into (effectively) a standard CentOS+Engine VM post-install... Which SHOULD be good enough for what I want to do! (I have the engine running a few extra services, and wanted to make sure I could continue to do so).
OK. But in the mid term the problem will impact you anyway. What to do after 31/12/2021 with this system, as no new updates from CentOS repos?
Umm, according to https://www.zdnet.com/article/red-hat-resets-centos-linux-and-users-are-angr... which links back to https://access.redhat.com/support/policy/updates/errata/#Life_Cycle_Dates which claims CentOS 7 will retain support through 2024-06-30. I think your 2021-12-31 date refers to EL8, not EL7.
I think in the next months it would be nice to have at least a CentOS --> CentOS Stream migration path for the Hosted Engine VM or for an external engine that are now based on CentOS
There is no "stream" for EL7.
Or to confirm that the standard path described at https://centos.org/centos-stream/ works also for CentOS systems where oVirt repos are configured and active and engine packages installed. Currently it says: dnf swap centos-linux-repos centos-stream-repos dnf distro-sync
Gianluca
-derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
On Fri, May 7, 2021 at 2:04 PM Derek Atkins <derek@ihtfp.com> wrote:
HI,
On Fri, May 7, 2021 2:55 am, Gianluca Cecchi wrote:
On Fri, May 7, 2021 at 2:39 AM Derek Atkins <derek@ihtfp.com> wrote: [snip]
*THIS* truly answers my underlying question(s). I was concerned that the engine would be like the node, but this assures me it is not, it's just a "faster" way to build the engine VM, but it turns into (effectively) a standard CentOS+Engine VM post-install... Which SHOULD be good enough for what I want to do! (I have the engine running a few extra services, and wanted to make sure I could continue to do so).
OK. But in the mid term the problem will impact you anyway. What to do after 31/12/2021 with this system, as no new updates from CentOS repos?
Umm, according to
https://www.zdnet.com/article/red-hat-resets-centos-linux-and-users-are-angr... which links back to https://access.redhat.com/support/policy/updates/errata/#Life_Cycle_Dates which claims CentOS 7 will retain support through 2024-06-30.
I think your 2021-12-31 date refers to EL8, not EL7.
yes, but as the thread was related to upgrade to 4.4 that needs version 8, I thought you were speaking about it. Even if version 7 of CentOS is supported through 2024, you are almost not getting any oVirt based update since June last year when the latest version of oVirt 4.3.x (4.3.10) has been released. RH EL for its 7.x version updates doesn't necessarily track incompatibilities with oVirt packages. So in my opinion iit s also risky to remain with a frozen 4.3 oVirt installation and to go with os overall updates for 3 years I would identify the reasons not allowing to pass to 4.4 and solve them in the meantime. YMMV
Hi Didi, Thanks a lot for taking the time to help!
On Wed, May 5, 2021 at 8:18 AM <ling(a)aliko.com> wrote:
Did you create ovirtmgmt manually, or let the deploy script create it? I created it manually.
So, last night, I removed ovirtmgmt I have created manually, and set up eth0 with Type Ethernet and ip address. This time it went way further, and the engine VM doesn't pause any more. Now I run into some other issues: [ ERROR ] ovirtsdk4.AuthError: Error during SSO authentication access_denied : Cannot authenticate user 'None@N/A': No valid profile found in credentials.. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error during SSO authentication access_denied : Cannot authenticate user 'None@N/A': No valid profile found in credentials.."} [snipped] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [snipped] [ ERROR ] fatal: [localhost]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host <my hostname> port 22: No route to host", "skip_reason": "Host localhost is unreachable", "unreachable": true} [snipped] [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20210505002924-q8il5m.log The Engine VM is still running and I could ssh into it. Connecting to the Management GUI, I am not able to log in using admin and password, or root and password I have given when running hosted-engine --deploy. I guess it' I have Kerberos configured for authentication and LDAP for authorization. Would restoring it this way work? Or should I remove the Kerberos and other SSO configuration, and do a backup and restoring again? Also, I do have other "required" networks. But though I answered "Yes" this time to the question "Pause the execution after adding this host to the engine?", I didn't get to this stage I think before
You can disable this "Update all packages" by passing e.g.:
hosted-engine --deploy --ansible-extra-vars=he_offline_deployment=true
Thanks for the option. Looks like I am not stuck here any more.
Any idea what made it become paused? Please check relevant logs (e.g. /var/log/messages, /var/log/libvirt/qemu/*, /var/log/vdsm/*).
You mean, until it became paused? Or also after that?
In principle you should do nothing - just tell the process which NIC to use for ovirtmgmt, and it will configure ovirtmgmt for you. All the other network configuration you can/should do from inside the engine admin ui. If you have other networks marked "required", the deployment process will fail trying to add the host to the engine (because it can't know which NICs/VLANs should be used for which networks) and will pause, waiting for you to remove some lock file, letting you fix stuff manually. See also: https://bugzilla.redhat.com/1893385 .
Yes, storage is handled (also asked about) in a later stage, after the engine is up and the host added to it.. This is a change from <= 4.2, and was done so that we can use the engine (and vdsm) for this, instead of duplicating their functionality in the deploy code.
Good luck and best regards,
... ling
On Wed, May 5, 2021 at 9:17 PM <ling@aliko.com> wrote:
Hi Didi,
Thanks a lot for taking the time to help!
On Wed, May 5, 2021 at 8:18 AM <ling(a)aliko.com> wrote:
Did you create ovirtmgmt manually, or let the deploy script create it? I created it manually.
So, last night, I removed ovirtmgmt I have created manually, and set up eth0 with Type Ethernet and ip address. This time it went way further, and the engine VM doesn't pause any more.
Now I run into some other issues: [ ERROR ] ovirtsdk4.AuthError: Error during SSO authentication access_denied : Cannot authenticate user 'None@N/A': No valid profile found in credentials.. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error during SSO authentication access_denied : Cannot authenticate user 'None@N/A': No valid profile found in credentials.."} [snipped] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [snipped] [ ERROR ] fatal: [localhost]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host <my hostname> port 22: No route to host", "skip_reason": "Host localhost is unreachable", "unreachable": true} [snipped] [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20210505002924-q8il5m.log The Engine VM is still running and I could ssh into it. Connecting to the Management GUI, I am not able to log in using admin and password, or root and password I have given when running hosted-engine --deploy. I guess it'
I have Kerberos configured for authentication and LDAP for authorization. Would restoring it this way work? Or should I remove the Kerberos and other SSO configuration, and do a backup and restoring again?
Do you make sure to backup and restore your conf? You can do this either using engine-backup itself, see e.g.: https://bugzilla.redhat.com/show_bug.cgi?id=1422980 , comment 15 in particular and also: https://www.ovirt.org/documentation/administration_guide/#Configuring_LDAP_a... and the specific mentions of engine-backup there, re what files it always includes, which we added in: https://bugzilla.redhat.com/show_bug.cgi?id=1693816 Alternatively, you can write custom ansible hooks, see my other reply (and search the net/bugzilla for examples - there are a few around).
Also, I do have other "required" networks. But though I answered "Yes" this time to the question "Pause the execution after adding this host to the engine?", I didn't get to this stage I think before
Indeed. Above failure happens before "Add host" (which fails if there are missing required networks). Best regards, -- Didi
Hi Didi, Thank you so much for your help! My SSO issue got resolved after reading one fo the bugs you included. My issue was on my old engine server, I have changed the config to point directly at /etc/krb5.keytab After copying /etc/krb5.keytab to /etc/http/http.keytab, redid the backup, the keytab got restored properly in the right place. I could have included /etc/krb5.keytab and a few other files in the backup according to one of the documentation, but it wasn't necessary. Since this is a one time process, I just manually logged on to the new engine VM and installed several RPMs needed for SSSD, KRB5 and corresponding configuration files. Everything else pretty much just worked, where it waited for me to add configure my networks, etc before removing the lock file. Also, I ran into small issues such as /rhev/data-center/mnt owned by root which should be vdsm:kvm, my new NFS volume for the new engine also need to be chown'ed to vdsm:kvm. And one my iscsci storage domain couldn't be mounted because I needed to add the initiator ID to my netapp filer. Hopefully it won't be that difficult going to 4.5 or newer versions in the future. ... ling
participants (4)
-
Derek Atkins -
Gianluca Cecchi -
ling＠aliko.com -
Yedidyah Bar David