[ovirt-users] Re: [ovrit-users] Anyone with Fiber Channel oVirt Storage Experience?
Sure ... I Will... Thanks... In time... Congrats for excellent work on oVirt 4.2 ... This new version are great !!! Em 17 de nov de 2018 12:53, "Nir Soffer" escreveu: On Fri, Nov 16, 2018, 00:37 Rogério Ceni Coelho I migrate from ovirt 4.0.5 to 4.2.6. > > You Just need to present luns to new servers, restart all nodes to > recognize all new disks, > Restart should not be needed. We perform scsi scan when creating a new domain or when managing an existing domain. New LUNs should be detected and apear in the domain dialog. If the system does not detect new LUNs without restart please file a bug. Nir import domain what can take long time if you have too many vms, import all > the vms and thats all. > > > > Em qua, 14 de nov de 2018 16:52, Rogério Ceni Coelho < > rogeriocenicoe...@gmail.com> escreveu: > >> If you use Snapshot or clone on Storage side you can Migrate vms on many >> steps Some vms each time... >> >> I use EMC VNX and EMC Unity and EMC Vplex. >> >> Good Luck >> >> Em qua, 14 de nov de 2018 às 15:27, Luca 'remix_tj' Lorenzetto < >> lorenzetto.l...@gmail.com> escreveu: >> >>> On Wed, Nov 14, 2018 at 4:39 PM Jacob Green wrote: >>> > >>> > I just have a few simple questions, have you migrated a fiber >>> > channel storage domain from one ovirt environment to another? And how >>> > did it go, did it just work aside from having to import all the vms and >>> > configure their settings was it any more difficult than that? >>> > >>> > We want to migrate our fiber channel storage with VM's intact from an >>> > oVirt 4.1 environment to a brand new oVirt 4.2 environment. >>> >>> Hello Jacob, >>> >>> we just did in our production environment using EMC VNX and EMC VPLEX >>> as storage backends. We simply zoned the new servers' hba with the >>> storage and on storage side we gave access to the same luns as the >>> older setup. >>> >>> Once done this we stopped all the vms on source side (4.1), detached >>> the storage domain and imported on the new one (4.2). Then, imported >>> all the vms. >>> >>> Please note that you MUST detach from source BEFORE attaching on >>> destination or you'll break everything. >>> >>> Nothing special required. The only simplification is using the same >>> network names on both sides, so is easier to import. >>> >>> We didn't automate anything, but you can do it for sure with ansible. >>> >>> Luca >>> -- >>> "E' assurdo impiegare gli uomini di intelligenza eccellente per fare >>> calcoli che potrebbero essere affidati a chiunque se si usassero delle >>> macchine" >>> Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) >>> >>> "Internet è la più grande biblioteca del mondo. >>> Ma il problema è che i libri sono tutti sparsi sul pavimento" >>> John Allen Paulos, Matematico (1945-vivente) >>> >>> Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , < >>> lorenzetto.l...@gmail.com> >>> ___ >>> Users mailing list -- users@ovirt.org >>> To unsubscribe send an email to users-le...@ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/HGFMMXGCSFPHRBDLBN7WE4FYVDRCABHQ/ >>> >> ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/TGI46QI4MZNUEYOL542H2MQSXXDWGXTD/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/6TYMVHFFJ46H4OKKMBDAZTJHZFD2XVBM/
[ovirt-users] Re: [ovrit-users] Anyone with Fiber Channel oVirt Storage Experience?
I migrate from ovirt 4.0.5 to 4.2.6. You Just need to present luns to new servers, restart all nodes to recognize all new disks, import domain what can take long time if you have too many vms, import all the vms and thats all. Em qua, 14 de nov de 2018 16:52, Rogério Ceni Coelho < rogeriocenicoe...@gmail.com> escreveu: > If you use Snapshot or clone on Storage side you can Migrate vms on many > steps Some vms each time... > > I use EMC VNX and EMC Unity and EMC Vplex. > > Good Luck > > Em qua, 14 de nov de 2018 às 15:27, Luca 'remix_tj' Lorenzetto < > lorenzetto.l...@gmail.com> escreveu: > >> On Wed, Nov 14, 2018 at 4:39 PM Jacob Green wrote: >> > >> > I just have a few simple questions, have you migrated a fiber >> > channel storage domain from one ovirt environment to another? And how >> > did it go, did it just work aside from having to import all the vms and >> > configure their settings was it any more difficult than that? >> > >> > We want to migrate our fiber channel storage with VM's intact from an >> > oVirt 4.1 environment to a brand new oVirt 4.2 environment. >> >> Hello Jacob, >> >> we just did in our production environment using EMC VNX and EMC VPLEX >> as storage backends. We simply zoned the new servers' hba with the >> storage and on storage side we gave access to the same luns as the >> older setup. >> >> Once done this we stopped all the vms on source side (4.1), detached >> the storage domain and imported on the new one (4.2). Then, imported >> all the vms. >> >> Please note that you MUST detach from source BEFORE attaching on >> destination or you'll break everything. >> >> Nothing special required. The only simplification is using the same >> network names on both sides, so is easier to import. >> >> We didn't automate anything, but you can do it for sure with ansible. >> >> Luca >> -- >> "E' assurdo impiegare gli uomini di intelligenza eccellente per fare >> calcoli che potrebbero essere affidati a chiunque se si usassero delle >> macchine" >> Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) >> >> "Internet è la più grande biblioteca del mondo. >> Ma il problema è che i libri sono tutti sparsi sul pavimento" >> John Allen Paulos, Matematico (1945-vivente) >> >> Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , < >> lorenzetto.l...@gmail.com> >> ___ >> Users mailing list -- users@ovirt.org >> To unsubscribe send an email to users-le...@ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/HGFMMXGCSFPHRBDLBN7WE4FYVDRCABHQ/ >> > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TGI46QI4MZNUEYOL542H2MQSXXDWGXTD/
[ovirt-users] Re: [ovrit-users] Anyone with Fiber Channel oVirt Storage Experience?
If you use Snapshot or clone on Storage side you can Migrate vms on many steps Some vms each time... I use EMC VNX and EMC Unity and EMC Vplex. Good Luck Em qua, 14 de nov de 2018 às 15:27, Luca 'remix_tj' Lorenzetto < lorenzetto.l...@gmail.com> escreveu: > On Wed, Nov 14, 2018 at 4:39 PM Jacob Green wrote: > > > > I just have a few simple questions, have you migrated a fiber > > channel storage domain from one ovirt environment to another? And how > > did it go, did it just work aside from having to import all the vms and > > configure their settings was it any more difficult than that? > > > > We want to migrate our fiber channel storage with VM's intact from an > > oVirt 4.1 environment to a brand new oVirt 4.2 environment. > > Hello Jacob, > > we just did in our production environment using EMC VNX and EMC VPLEX > as storage backends. We simply zoned the new servers' hba with the > storage and on storage side we gave access to the same luns as the > older setup. > > Once done this we stopped all the vms on source side (4.1), detached > the storage domain and imported on the new one (4.2). Then, imported > all the vms. > > Please note that you MUST detach from source BEFORE attaching on > destination or you'll break everything. > > Nothing special required. The only simplification is using the same > network names on both sides, so is easier to import. > > We didn't automate anything, but you can do it for sure with ansible. > > Luca > -- > "E' assurdo impiegare gli uomini di intelligenza eccellente per fare > calcoli che potrebbero essere affidati a chiunque se si usassero delle > macchine" > Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) > > "Internet è la più grande biblioteca del mondo. > Ma il problema è che i libri sono tutti sparsi sul pavimento" > John Allen Paulos, Matematico (1945-vivente) > > Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , < > lorenzetto.l...@gmail.com> > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/HGFMMXGCSFPHRBDLBN7WE4FYVDRCABHQ/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/2KRHL2SVB3FXJ4YVX6N3ZY5UTNA3WPEF/
[ovirt-users] Re: oVirt Node 4.2.7 upgrade fails with broken dependencies ?
Ovirt Engine with same problem. [root@nscovirt42prdpoa ~]# yum update Loaded plugins: fastestmirror, versionlock Loading mirror speeds from cached hostfile * base: centos.brnet.net.br * epel: mirror.ci.ifes.edu.br * extras: centos.brnet.net.br * ovirt-4.2: mirror.linux.duke.edu * ovirt-4.2-epel: mirror.ci.ifes.edu.br * updates: centos.brnet.net.br Resolving Dependencies --> Running transaction check ---> Package collectd.x86_64 0:5.8.0-6.1.el7 will be updated --> Processing Dependency: collectd(x86-64) = 5.8.0-6.1.el7 for package: collectd-disk-5.8.0-6.1.el7.x86_64 --> Processing Dependency: collectd(x86-64) = 5.8.0-6.1.el7 for package: collectd-write_http-5.8.0-6.1.el7.x86_64 ---> Package collectd.x86_64 0:5.8.1-1.el7 will be an update ---> Package collectd-postgresql.x86_64 0:5.8.0-6.1.el7 will be updated ---> Package collectd-postgresql.x86_64 0:5.8.1-1.el7 will be an update ---> Package ovirt-engine-extensions-api-impl.noarch 0:4.2.7.4-1.el7 will be updated ---> Package ovirt-engine-extensions-api-impl.noarch 0:4.2.7.5-1.el7 will be an update ---> Package ovirt-engine-lib.noarch 0:4.2.7.4-1.el7 will be updated ---> Package ovirt-engine-lib.noarch 0:4.2.7.5-1.el7 will be an update ---> Package ovirt-engine-setup.noarch 0:4.2.7.4-1.el7 will be updated ---> Package ovirt-engine-setup.noarch 0:4.2.7.5-1.el7 will be an update ---> Package ovirt-engine-setup-base.noarch 0:4.2.7.4-1.el7 will be updated ---> Package ovirt-engine-setup-base.noarch 0:4.2.7.5-1.el7 will be an update ---> Package ovirt-engine-setup-plugin-ovirt-engine.noarch 0:4.2.7.4-1.el7 will be updated ---> Package ovirt-engine-setup-plugin-ovirt-engine.noarch 0:4.2.7.5-1.el7 will be an update ---> Package ovirt-engine-setup-plugin-ovirt-engine-common.noarch 0:4.2.7.4-1.el7 will be updated ---> Package ovirt-engine-setup-plugin-ovirt-engine-common.noarch 0:4.2.7.5-1.el7 will be an update ---> Package ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch 0:4.2.7.4-1.el7 will be updated ---> Package ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch 0:4.2.7.5-1.el7 will be an update ---> Package ovirt-engine-setup-plugin-websocket-proxy.noarch 0:4.2.7.4-1.el7 will be updated ---> Package ovirt-engine-setup-plugin-websocket-proxy.noarch 0:4.2.7.5-1.el7 will be an update ---> Package ovirt-engine-vmconsole-proxy-helper.noarch 0:4.2.7.4-1.el7 will be updated ---> Package ovirt-engine-vmconsole-proxy-helper.noarch 0:4.2.7.5-1.el7 will be an update ---> Package ovirt-engine-websocket-proxy.noarch 0:4.2.7.4-1.el7 will be updated ---> Package ovirt-engine-websocket-proxy.noarch 0:4.2.7.5-1.el7 will be an update ---> Package ovirt-release42.noarch 0:4.2.7-1.el7 will be updated ---> Package ovirt-release42.noarch 0:4.2.7.1-1.el7 will be an update --> Finished Dependency Resolution Error: Package: collectd-write_http-5.8.0-6.1.el7.x86_64 (@ovirt-4.2-centos-opstools) Requires: collectd(x86-64) = 5.8.0-6.1.el7 Removing: collectd-5.8.0-6.1.el7.x86_64 (@ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-6.1.el7 Updated By: collectd-5.8.1-1.el7.x86_64 (epel) collectd(x86-64) = 5.8.1-1.el7 Available: collectd-5.7.2-1.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.7.2-1.el7 Available: collectd-5.7.2-3.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.7.2-3.el7 Available: collectd-5.8.0-2.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-2.el7 Available: collectd-5.8.0-3.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-3.el7 Available: collectd-5.8.0-5.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-5.el7 Error: Package: collectd-disk-5.8.0-6.1.el7.x86_64 (@ovirt-4.2-centos-opstools) Requires: collectd(x86-64) = 5.8.0-6.1.el7 Removing: collectd-5.8.0-6.1.el7.x86_64 (@ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-6.1.el7 Updated By: collectd-5.8.1-1.el7.x86_64 (epel) collectd(x86-64) = 5.8.1-1.el7 Available: collectd-5.7.2-1.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.7.2-1.el7 Available: collectd-5.7.2-3.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.7.2-3.el7 Available: collectd-5.8.0-2.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-2.el7 Available: collectd-5.8.0-3.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-3.el7 Available: collectd-5.8.0-5.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-5.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@nsco
[ovirt-users] oVirt Node 4.2.7 upgrade fails with broken dependencies ?
Hi all ! Broken dependencies ? [root@nscovirtkvm41prdpoa ~]# yum update Loaded plugins: enabled_repos_upload, fastestmirror, package_upload, product-id, search-disabled-repos, subscription-manager, vdsmupgrade This system is not registered with an entitlement server. You can use subscription-manager to register. Loading mirror speeds from cached hostfile * base: mirror.ufscar.br * epel: mirror.ci.ifes.edu.br * extras: centos.brnet.net.br * ovirt-4.2: www.gtlib.gatech.edu * ovirt-4.2-epel: mirror.ci.ifes.edu.br * updates: mirror.ufscar.br Resolving Dependencies --> Running transaction check ---> Package collectd.x86_64 0:5.8.0-6.1.el7 will be updated --> Processing Dependency: collectd(x86-64) = 5.8.0-6.1.el7 for package: collectd-disk-5.8.0-6.1.el7.x86_64 --> Processing Dependency: collectd(x86-64) = 5.8.0-6.1.el7 for package: collectd-write_http-5.8.0-6.1.el7.x86_64 ---> Package collectd.x86_64 0:5.8.1-1.el7 will be an update ---> Package collectd-netlink.x86_64 0:5.8.0-6.1.el7 will be updated ---> Package collectd-netlink.x86_64 0:5.8.1-1.el7 will be an update ---> Package collectd-virt.x86_64 0:5.8.0-6.1.el7 will be updated ---> Package collectd-virt.x86_64 0:5.8.1-1.el7 will be an update ---> Package ovirt-hosted-engine-setup.noarch 0:2.2.30-1.el7 will be updated ---> Package ovirt-hosted-engine-setup.noarch 0:2.2.32-1.el7 will be an update --> Finished Dependency Resolution Error: Package: collectd-write_http-5.8.0-6.1.el7.x86_64 (@ovirt-4.2-centos-opstools) Requires: collectd(x86-64) = 5.8.0-6.1.el7 Removing: collectd-5.8.0-6.1.el7.x86_64 (@ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-6.1.el7 Updated By: collectd-5.8.1-1.el7.x86_64 (epel) collectd(x86-64) = 5.8.1-1.el7 Available: collectd-5.7.2-1.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.7.2-1.el7 Available: collectd-5.7.2-3.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.7.2-3.el7 Available: collectd-5.8.0-2.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-2.el7 Available: collectd-5.8.0-3.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-3.el7 Available: collectd-5.8.0-5.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-5.el7 Error: Package: collectd-disk-5.8.0-6.1.el7.x86_64 (@ovirt-4.2-centos-opstools) Requires: collectd(x86-64) = 5.8.0-6.1.el7 Removing: collectd-5.8.0-6.1.el7.x86_64 (@ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-6.1.el7 Updated By: collectd-5.8.1-1.el7.x86_64 (epel) collectd(x86-64) = 5.8.1-1.el7 Available: collectd-5.7.2-1.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.7.2-1.el7 Available: collectd-5.7.2-3.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.7.2-3.el7 Available: collectd-5.8.0-2.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-2.el7 Available: collectd-5.8.0-3.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-3.el7 Available: collectd-5.8.0-5.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-5.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Uploading Enabled Repositories Report Loaded plugins: fastestmirror, product-id, subscription-manager This system is not registered with an entitlement server. You can use subscription-manager to register. Cannot upload enabled repos report, is this client registered? [root@nscovirtkvm41prdpoa ~]# yum repolist Loaded plugins: enabled_repos_upload, fastestmirror, package_upload, product-id, search-disabled-repos, subscription-manager, vdsmupgrade This system is not registered with an entitlement server. You can use subscription-manager to register. Loading mirror speeds from cached hostfile * base: mirror.ufscar.br * epel: mirror.ci.ifes.edu.br * extras: centos.brnet.net.br * ovirt-4.2: www.gtlib.gatech.edu * ovirt-4.2-epel: mirror.ci.ifes.edu.br * updates: mirror.ufscar.br repo id repo name status base/7/x86_64 CentOS-7 - Base 9,911 centos-sclo-rh-release/x86_64 CentOS-7 - SCLo rh 8,099 epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 12,708 extras/7/x86_64 CentOS-7 - Extras 434 ovirt-4.2/7 Latest oVirt 4.2 Release 2,439
[ovirt-users] The number of LVs on the domain VPLEX_DATA_DOMAIN exceeded 300, you are approaching the limit where performance may degrade.
Hi oVirt Admins, I have two data domains using FC SAN, with 150 VMs. Each VM have 3 or 4 disks. A few time ago i saw the above message on Events. What can i do ? What are the alternatives ? What can i do ? The number of LVs on the domain VPLEX_DATA_DOMAIN exceeded 300, you are approaching the limit where performance may degrade. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] New oVirt Node 4.0.6.1 network problem with bond and many vlans - Network.service timeout failed
To install 4.1.1 node i need to update ovirt engine ? Em Sáb, 6 de mai de 2017 13:07, Sandro Bonazzola <sbona...@redhat.com> escreveu: > > > Il 04/Mag/2017 20:02, "Rogério Ceni Coelho" <rogeriocenicoe...@gmail.com> > ha scritto: > > Hi oVirt admins, > > Yesterday, i install a new node 4.0.6.1 > > > I would suggest to go with 4.1.1 nodes since 4.0 is not supported anymore. > > > and after config network bond (1) + vlans ( about 50 ), network.service > failed with timeout as above. All my old and working fine oVirt nodes run > 4.0.5 and have the same 5 min timeout on systemd. > > When i try to run vms on this new server, some networks are ok and some > not. > > I install oVirt Node with 4.0.3 on same server and this problem do not > occur. > > How can i workaround or change timeout to network.service ? > > In time, there are any way to update oVirt Node to 4.0.5 from 4.0.3 > install iso ? > > [root@prd-rbs-ovirt-kvm21-poa ~]# systemctl status network.service > â— network.service - LSB: Bring up/down networking >Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled) >Active: failed (Result: timeout) since Thu 2017-05-04 11:29:43 BRT; 3h > 12min ago > Docs: man:systemd-sysv-generator(8) > Process: 7574 ExecStart=/etc/rc.d/init.d/network start (code=killed, > signal=TERM) > > May 04 11:29:12 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: > Bringing up interface o_p_s_a_lb_758: [ OK ] > May 04 11:29:18 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: > Bringing up interface o_p_sites_a_755: [ OK ] > May 04 11:29:23 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: > Bringing up interface o_prod_app_757: [ OK ] > May 04 11:29:28 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: > Bringing up interface o_prod_db_756: [ OK ] > May 04 11:29:38 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: > Bringing up interface ovirtmgmt: [ OK ] > *May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br > <http://prd-rbs-ovirt-kvm21-poa.rbs.com.br> systemd[1]: network.service > start operation timed out. Terminating.* > May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: Failed to > start LSB: Bring up/down networking. > May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: Unit > network.service entered failed state. > May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: > network.service failed. > May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: > Bringing up interface paas_1305: > [root@prd-rbs-ovirt-kvm21-poa ~]# > > [root@prd-rbs-ovirt-kvm21-poa ~]# systemctl restart network.service > Job for network.service failed because a timeout was exceeded. See > "systemctl status network.service" and "journalctl -xe" for details. > [root@prd-rbs-ovirt-kvm21-poa ~]# systemctl status network.service > â— network.service - LSB: Bring up/down networking >Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled) >Active: failed (Result: timeout) since Thu 2017-05-04 14:55:34 BRT; > 4min 46s ago > Docs: man:systemd-sysv-generator(8) > Process: 40810 ExecStart=/etc/rc.d/init.d/network start (code=killed, > signal=TERM) > > May 04 14:55:21 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]: [ OK > ] > May 04 14:55:23 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]: > Bringing up interface o_hlg_db_766: RTNETLINK answers: File exists > May 04 14:55:26 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]: [ OK > ] > May 04 14:55:28 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]: > Bringing up interface o_p_s_a_lb_758: RTNETLINK answers: File exists > May 04 14:55:31 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]: [ OK > ] > May 04 14:55:33 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]: > Bringing up interface o_p_sites_a_755: RTNETLINK answers: File exists > May 04 14:55:34 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: > network.service start operation timed out. Terminating. > May 04 14:55:34 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: Failed to > start LSB: Bring up/down networking. > May 04 14:55:34 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: Unit > network.service entered failed state. > May 04 14:55:34 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: > network.service failed. > [root@prd-rbs-ovirt-kvm21-poa ~]# > > > > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] New oVirt Node install on oVirt Cluster 4.0.5 - How can I install oVirt Node with same 4.0.5 version ???
::(_findDomain) looking for unfetched domain f9e051a9-6660-4e49-a3f1-354583501610 Thread-37::ERROR::2017-05-05 10:39:12,431::sdc::157::Storage.StorageDomainCache::(_findUnfetchedDomain) looking for domain f9e051a9-6660-4e49-a3f1-354583501610 Thread-37::DEBUG::2017-05-05 10:39:12,432::lvm::288::Storage.Misc.excCmd::(cmd) /usr/bin/taskset --cpu-list 0-31 /usr/bin/sudo -n /usr/sbin/lvm vgs --config ' devices { preferred_names = ["^/dev/mapper/"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter = [ '\''a|/dev/mapper/3600014400010206a1c589de93966|/dev/mapper/3600014400010206a1c589de939b1|/dev/mapper/3600014400010206a1c589de93a4d|/dev/mapper/3600601600f7025006828c2f47c7be611|'\'', '\''r|.*|'\'' ] } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 use_lvmetad=0 } backup { retain_min = 50 retain_days = 0 } ' --noheadings --units b --nosuffix --separator '|' --ignoreskippedcluster -o uuid,name,attr,size,free,extent_size,extent_count,free_count,tags,vg_mda_size,vg_mda_free,lv_count,pv_count,pv_name f9e051a9-6660-4e49-a3f1-354583501610 (cwd None) Thread-37::DEBUG::2017-05-05 10:39:12,591::lvm::288::Storage.Misc.excCmd::(cmd) FAILED: = ' WARNING: Not using lvmetad because config setting use_lvmetad=0.\n WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).\n Volume group "f9e051a9-6660-4e49-a3f1-354583501610" not found\n Cannot process volume group f9e051a9-6660-4e49-a3f1-354583501610\n'; = 5 Thread-37::WARNING::2017-05-05 10:39:12,597::lvm::376::Storage.LVM::(_reloadvgs) lvm vgs failed: 5 [] [' WARNING: Not using lvmetad because config setting use_lvmetad=0.', ' WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).', ' Volume group "f9e051a9-6660-4e49-a3f1-354583501610" not found', ' Cannot process volume group f9e051a9-6660-4e49-a3f1-354583501610'] *Thread-37::ERROR::2017-05-05 10:39:12,602::sdc::146::Storage.StorageDomainCache::(_findDomain) domain f9e051a9-6660-4e49-a3f1-354583501610 not found* Traceback (most recent call last): File "/usr/share/vdsm/storage/sdc.py", line 144, in _findDomain dom = findMethod(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 174, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) StorageDomainDoesNotExist: Storage domain does not exist: (u'f9e051a9-6660-4e49-a3f1-354583501610',) Thread-37::ERROR::2017-05-05 10:39:12,602::monitor::328::Storage.Monitor::(_setupLoop) Setting up monitor for f9e051a9-6660-4e49-a3f1-354583501610 failed Traceback (most recent call last): File "/usr/share/vdsm/storage/monitor.py", line 325, in _setupLoop self._setupMonitor() File "/usr/share/vdsm/storage/monitor.py", line 348, in _setupMonitor self._produceDomain() File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 405, in wrapper value = meth(self, *a, **kw) File "/usr/share/vdsm/storage/monitor.py", line 366, in _produceDomain self.domain = sdCache.produce(self.sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 101, in produce domain.getRealDomain() File "/usr/share/vdsm/storage/sdc.py", line 53, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 125, in _realProduce domain = self._findDomain(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 144, in _findDomain dom = findMethod(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 174, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) StorageDomainDoesNotExist: Storage domain does not exist: (u'f9e051a9-6660-4e49-a3f1-354583501610',) jsonrpc.Executor/3::DEBUG::2017-05-05 10:39:13,057::__init__::530::jsonrpc.JsonRpcServer::(_handle_request) Calling 'Host.getAllVmStats' in bridge with {} jsonrpc.Executor/3::DEBUG::2017-05-05 10:39:13,081::__init__::555::jsonrpc.JsonRpcServer::(_handle_request) Return 'Host.getAllVmStats' in bridge with (suppressed) jsonrpc.Executor/3::INFO::2017-05-05 10:39:13,088::__init__::513::jsonrpc.JsonRpcServer::(_serveRequest) RPC call Host.getAllVmStats succeeded in 0.03 seconds Em sex, 5 de mai de 2017 às 14:40, Yuval Turgeman <yuv...@redhat.com> escreveu: > I take it updating everything to 4.0.6 is not an option ? > > Thanks, > Yuval > > On May 5, 2017 6:16 PM, "Rogério Ceni Coelho" <rogeriocenicoe...@gmail.com> > wrote: > >> I can think in two ways. Please let me know if have a change to go ok. >> >> First, download ovirt-node-ng-image-update and ovirt-node-ng-image from >> 4.0.5 version and run yum localinstall. >> >> Second, create a rpm list from other 4.0.5 node, do an diff agains my >> 4.0.3 node and use the diff to download packages from 4.0.5 version and run >> yum localintall.
[ovirt-users] New oVirt Node install on oVirt Cluster 4.0.5 - How can I install oVirt Node with same 4.0.5 version ???
Hi oVirt Troopers, I have two segregated oVirt Clusters running 4.0.5 ( DEV and PROD enviroments). Now i need to install a new oVirt Node Server (Dell PowerEdge M620), but i see that does not exist an 4.0.5 iso on http://resources.ovirt.org/pub/ovirt-4.0/iso/ovirt-node-ng-installer/ , only 4.0.3 and 4.0.6. How can i install this new server and go to the same version of all 20 others ??? There is a way to install 4.0.3 and update to 4.0.5 only ? Thanks in advance. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] New oVirt Node 4.0.6.1 network problem with bond and many vlans - Network.service timeout failed
Hi again oVirt Admins, After dig some time, i adjust network.service (/etc/rc.d/init.d/network) timeout to zero creating a custom timeout.conf file for systemctl. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818676 https://www.turnkeylinux.org/blog/debugging-systemd-sysv-init-compat https://unix.stackexchange.com/questions/233468/how-does-systemd-use-etc-init-d-scripts [root@prd-rbs-ovirt-kvm21-poa system]# systemctl show network.service | grep -i timeout TimeoutStartUSec=5min TimeoutStopUSec=5min Result=timeout JobTimeoutUSec=0 JobTimeoutAction=none [root@prd-rbs-ovirt-kvm21-poa system]# pwd /usr/lib/systemd/system [root@prd-rbs-ovirt-kvm21-poa system]# mkdir network.service.d [root@prd-rbs-ovirt-kvm21-poa system]# cd network.service.d/ [root@prd-rbs-ovirt-kvm21-poa network.service.d]# vi timeout.conf [Service] TimeoutSec=0 TimeoutStartUSec=0 [root@prd-rbs-ovirt-kvm21-poa system]# systemctl daemon-reload [root@prd-rbs-ovirt-kvm21-poa system]# systemctl show network.service | grep -i timeout TimeoutStartUSec=0 TimeoutStopUSec=0 Result=timeout DropInPaths=/usr/lib/systemd/system/network.service.d/timeout.conf JobTimeoutUSec=0 JobTimeoutAction=none [root@prd-rbs-ovirt-kvm21-poa system]# [root@prd-rbs-ovirt-kvm21-poa ~]# systemctl restart network.service [root@prd-rbs-ovirt-kvm21-poa ~]# systemctl status network.service â— network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/network.service.d └─timeout.conf Active: active (exited) since Thu 2017-05-04 15:22:12 BRT; 5min ago Docs: man:systemd-sysv-generator(8) Process: 345 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=0/SUCCESS) May 04 15:21:39 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[345]: Bringing up interface rede_5: [ OK ] May 04 15:21:44 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[345]: Bringing up interface rede_6: [ OK ] May 04 15:21:48 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[345]: Bringing up interface server_lb_7: [ OK ] May 04 15:21:50 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[345]: Bringing up interface srv_1056: RTNETLINK answers: File exists May 04 15:21:53 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[345]: [ OK ] May 04 15:21:58 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[345]: Bringing up interface streaming_106: [ OK ] May 04 15:22:02 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[345]: Bringing up interface tef_100: [ OK ] May 04 15:22:07 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[345]: Bringing up interface telecom_25: [ OK ] May 04 15:22:12 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[345]: Bringing up interface zh_32: [ OK ] May 04 15:22:12 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: Started LSB: Bring up/down networking. [root@prd-rbs-ovirt-kvm21-poa ~]# Em qui, 4 de mai de 2017 às 15:01, Rogério Ceni Coelho < rogeriocenicoe...@gmail.com> escreveu: > Hi oVirt admins, > > Yesterday, i install a new node 4.0.6.1 and after config network bond (1) > + vlans ( about 50 ), network.service failed with timeout as above. All my > old and working fine oVirt nodes run 4.0.5 and have the same 5 min timeout > on systemd. > > When i try to run vms on this new server, some networks are ok and some > not. > > I install oVirt Node with 4.0.3 on same server and this problem do not > occur. > > How can i workaround or change timeout to network.service ? > > In time, there are any way to update oVirt Node to 4.0.5 from 4.0.3 > install iso ? > > [root@prd-rbs-ovirt-kvm21-poa ~]# systemctl status network.service > â— network.service - LSB: Bring up/down networking >Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled) >Active: failed (Result: timeout) since Thu 2017-05-04 11:29:43 BRT; 3h > 12min ago > Docs: man:systemd-sysv-generator(8) > Process: 7574 ExecStart=/etc/rc.d/init.d/network start (code=killed, > signal=TERM) > > May 04 11:29:12 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: > Bringing up interface o_p_s_a_lb_758: [ OK ] > May 04 11:29:18 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: > Bringing up interface o_p_sites_a_755: [ OK ] > May 04 11:29:23 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: > Bringing up interface o_prod_app_757: [ OK ] > May 04 11:29:28 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: > Bringing up interface o_prod_db_756: [ OK ] > May 04 11:29:38 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: > Bringing up interface ovirtmgmt: [ OK ] > *May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br > <http://prd-rbs-ovirt-kvm21-poa.rbs.com.br> systemd[1]: network.service > start operation timed out. Terminating.* > May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: Failed to > start LSB: Bring up/down networking. > May 04 11:29:43 prd-rbs-ovirt
Re: [ovirt-users] EMC Unity 300
Hi ! I will use Unity 400 with oVirt in next week with FC SAN. Em Seg, 10 de abr de 2017 09:27, Colin Coeescreveu: > Hi all > > We are contemplating moving away from our current iSCSI SAN to Dell/EMC > Unity 300. > > I've seen one thread where the 300F is problematic and no resolution is > posted. > > Is anyone else using tis with RHEV/oVirt? Any war stories? > > Thanks > > CC > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Passing VLAN trunk to VM
I think you define vlans on vm virtual nic OS like you do as usual. Monday i will try and share results. Bye. Em Dom, 12 de mar de 2017 10:40, FERNANDO FREDIANI < fernando.fredi...@upx.com> escreveu: > Great ! > > What about a range of VLANs, is it also supported ? > > 2017-03-11 17:47 GMT-03:00 Edward Haas <eh...@redhat.com>: > > Passing a trunk to the vnic is supported long ago. > Just create a network over a nic/bond that is connected to a trunk port > and do not define any VLAN (we call it non vlan network). > In oVirt, a non-vlan network will ignore the VLAN tag and will forward the > packets as is onward. > It is up to the VM vnic to define vlans or use a promisc mode to see > everything. > > OVS can add a layer of security over the existing, by defining explicitly > which vlans are allowed for a specific vnic, but it is not > currently available. > > > On Thu, Mar 9, 2017 at 11:40 PM, Simon Vincent <s...@srvincent.co.uk> wrote: > > I was wondering if open vswitch will get round this problem. Has anyone > tried it? > > On 9 Mar 2017 7:41 pm, "Rogério Ceni Coelho" <rogeriocenicoe...@gmail.com> > wrote: > > Hi, > > Ovirt user interface does not allow to input 4095 as a tag vlan number ... > Only values between 0 and 4094. > > This is useful to me too. Maybe any other way ? > > Em qui, 9 de mar de 2017 às 16:15, FERNANDO FREDIANI < > fernando.fredi...@upx.com> escreveu: > > Have you tried use Vlan 4095 ? On VMware it used to be the way to pass all > Vlans from a vSwitch to a Vlan in a single port. And yes I have used it > also for pfSense. > > Fernando > > On 09/03/2017 16:09, Simon Vincent wrote: > > Is it possible to pass multiple VLANs to a VM (pfSense) using a single > virtual NIC? All my existing oVirt networks are setup as a single tagged > VLAN. I know this didn't used to be supported but wondered if this has > changed. My other option is to pass each VLAN as a separate NIC to the VM > however if I needed to add a new VLAN I would have to add a new interface > and reboot the VM as hot-add of NICs is not supported by pfSense. > > > > > ___ > Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Passing VLAN trunk to VM
Hi, Ovirt user interface does not allow to input 4095 as a tag vlan number ... Only values between 0 and 4094. This is useful to me too. Maybe any other way ? Em qui, 9 de mar de 2017 às 16:15, FERNANDO FREDIANI < fernando.fredi...@upx.com> escreveu: > Have you tried use Vlan 4095 ? On VMware it used to be the way to pass all > Vlans from a vSwitch to a Vlan in a single port. And yes I have used it > also for pfSense. > > Fernando > > On 09/03/2017 16:09, Simon Vincent wrote: > > Is it possible to pass multiple VLANs to a VM (pfSense) using a single > virtual NIC? All my existing oVirt networks are setup as a single tagged > VLAN. I know this didn't used to be supported but wondered if this has > changed. My other option is to pass each VLAN as a separate NIC to the VM > however if I needed to add a new VLAN I would have to add a new interface > and reboot the VM as hot-add of NICs is not supported by pfSense. > > > > > ___ > Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Recommended Ovirt Implementation on Active-Active Datacenters (Site 1 and Site2) - Same Cluster
Hi oVirt Masters !!! I create Affinity Rules with sucess using REST API as Martin Sivak wrote on https://www.ovirt.org/blog/2016/07/affinity-labels I only want to tell him ( and all others users ) that the URL to check on his blog is not right ( or at least nomore ). Wrong way : ( Do not list hosts on affinitylabels - Original as wrote on Martin Blogs - $ cengine -f http://localhost:8080/ovirt-engine/api/affinitylabels | jq -r '.affinity_label[] | {id, name, vms, hosts}') [root@hlg-rbs-ovirt01-poa ~]# cengine -f https://hlg-rbs-ovirt01-poa.rbs.com.br/ovirt-engine/api/affinitylabels { "affinity_label" : [ { "read_only" : "false", "name" : "DATACENTER_TV", "href" : "/ovirt-engine/api/affinitylabels/37f59ae4-2c63-46ac-a126-aa75b5be3437", "id" : "37f59ae4-2c63-46ac-a126-aa75b5be3437", "link" : [ { "href" : "/ovirt-engine/api/affinitylabels/37f59ae4-2c63-46ac-a126-aa75b5be3437/hosts", "rel" : "hosts" }, { "href" : "/ovirt-engine/api/affinitylabels/37f59ae4-2c63-46ac-a126-aa75b5be3437/vms", "rel" : "vms" } ] }, { "read_only" : "false", "name" : "DATACENTER_CORP", "href" : "/ovirt-engine/api/affinitylabels/cecf7ac2-3128-443a-8d90-26f90bfca99d", "id" : "cecf7ac2-3128-443a-8d90-26f90bfca99d", "link" : [ { "href" : "/ovirt-engine/api/affinitylabels/cecf7ac2-3128-443a-8d90-26f90bfca99d/hosts", "rel" : "hosts" }, { "href" : "/ovirt-engine/api/affinitylabels/cecf7ac2-3128-443a-8d90-26f90bfca99d/vms", "rel" : "vms" } ] } ] For me the right way are : [root@hlg-rbs-ovirt01-poa ~]# export DATACENTER_CORP=cecf7ac2-3128-443a-8d90-26f90bfca99d [root@hlg-rbs-ovirt01-poa ~]# cengine -f https://hlg-rbs-ovirt01-poa.rbs.com.br/ovirt-engine/api/affinitylabels/ $DATACENTER_CORP/hosts { "host" : [ { "href" : "/ovirt-engine/api/hosts/f527f077-dd27-46d2-bd39-3f157177277e", "id" : "f527f077-dd27-46d2-bd39-3f157177277e" }, { "href" : "/ovirt-engine/api/hosts/f9c9d929-b460-4102-bb29-de1e6ad6ad72", "id" : "f9c9d929-b460-4102-bb29-de1e6ad6ad72" }, { "href" : "/ovirt-engine/api/hosts/02ead14e-0208-4a74-b1c2-4c19383820f9", "id" : "02ead14e-0208-4a74-b1c2-4c19383820f9" }, { "href" : "/ovirt-engine/api/hosts/ffde7cb6-30db-4d77-872d-ef4e1b3d1a8e", "id" : "ffde7cb6-30db-4d77-872d-ef4e1b3d1a8e" }, { "href" : "/ovirt-engine/api/hosts/5feddfba-d7b2-423e-a946-ac2bf36906fa", "id" : "5feddfba-d7b2-423e-a946-ac2bf36906fa" }, { "href" : "/ovirt-engine/api/hosts/7d9cab91-703d-432d-b5da-91e122950794", "id" : "7d9cab91-703d-432d-b5da-91e122950794" }, { "href" : "/ovirt-engine/api/hosts/cd5e5f1d-6c8b-49ad-a9ab-4f2fc3fedbb8", "id" : "cd5e5f1d-6c8b-49ad-a9ab-4f2fc3fedbb8" }, { "href" : "/ovirt-engine/api/hosts/45b93272-7bfd-4d9a-b934-75c4a9b9514e", "id" : "45b93272-7bfd-4d9a-b934-75c4a9b9514e" }, { "href" : "/ovirt-engine/api/hosts/0ccedcb2-33ab-43be-9218-7743d711bc18", "id" : "0ccedcb2-33ab-43be-9218-7743d711bc18" } ] I am using oVirt 4.0.6. Thanks. Em qui, 24 de nov de 2016 às 13:01, Roy Golan <rgo...@redhat.com> escreveu: > Affinity labels [1] will allow you to label the hosts and vms to site1 and > site2 and that should be it. > > - create label per site > - add the redpective label to each vm and host > > Unfortunately there is no UI for that but with SDK or rest it's easy > > [1] https://www.ovirt.org/blog/2016/07/affinity-labels/ > > On Nov 24, 2016 3:12 PM, "Rogério Ceni Coelho" < > rogeriocenicoe...@gmail.com> wrote: > > Hi Ovirt Jedi´s !!! > > First of all, congrats about the product !!! I love Ovirt !!! > > I am using Ovirt 4.0.4 with 10 hosts and 58 virtual machines on two > Active-Active Datacenters using two EMC Vplex + two EMC VNX5500 + eight > Dell Blades + 8 Dell PowerEdge M610 and two M620 Servers. > > Half servers are on Site 1 and Half servers on Site 2. The same with VMs. > All Sites work as one and have redundant network, storage, power, etc etc > etc ... > > I want to know what is the best way to set that VM number 1 runs on Site 1 > and VM number 2 runs on Site 2 ? > > On Vmware 5.1 we use DRS Group Manager and on Hyper-V we use Custom > Properties on hosts and on VMs. What we use on oVirt without segregate on > two different Datacenters or two different clusters ? > > Thanks in advance. > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] oVirt Engine 4.0.5 and CentOS 7.3 Instability
I found https://bugzilla.redhat.com/show_bug.cgi?id=1393714 which seem to be the same problem that occour with me ... Em sex, 6 de jan de 2017 às 16:28, Rogério Ceni Coelho < rogeriocenicoe...@gmail.com> escreveu: > Pavel, > > Take a look ... > > [root@prd-rbs-ovirt01-poa ~]# grep -i error > /var/log/ovirt-engine/engine.log | grep -v > org.ovirt.engine.core.vdsbroker.HostDevListByCapsVDSCommand | tail -50 > 2017-01-06 16:20:06,897 ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] > (DefaultQuartzScheduler6) [a6fc972] Command > 'GetAllVmStatsVDSCommand(HostName = prd-rbs-ovirt-kvm10-poa.rbs.com.br, > VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', > hostId='8b4bc7dc-af8c-4415-a2ef-bccc11ddf23a', vds='Host[ > prd-rbs-ovirt-kvm10-poa.rbs.com.br,8b4bc7dc-af8c-4415-a2ef-bccc11ddf23a]'})' > execution failed: VDSGenericException: VDSNetworkException: Heartbeat > exceeded > 2017-01-06 16:20:06,899 ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] > (DefaultQuartzScheduler10) [19b85a77] Command > 'GetAllVmStatsVDSCommand(HostName = prd-rbs-ovirt-kvm17-poa.rbs.com.br, > VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', > hostId='795b917b-ea5b-499d-80c5-aa3aad4f2537', vds='Host[ > prd-rbs-ovirt-kvm17-poa.rbs.com.br,795b917b-ea5b-499d-80c5-aa3aad4f2537]'})' > execution failed: VDSGenericException: VDSNetworkException: Heartbeat > exceeded > 2017-01-06 16:20:06,901 ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] > (DefaultQuartzScheduler8) [1bccfc8a] Command > 'GetAllVmStatsVDSCommand(HostName = prd-rbs-ovirt-kvm19-poa.rbs.com.br, > VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', > hostId='887b6e35-1fd1-4cd6-9e78-05bcab12a417', vds='Host[ > prd-rbs-ovirt-kvm19-poa.rbs.com.br,887b6e35-1fd1-4cd6-9e78-05bcab12a417]'})' > execution failed: VDSGenericException: VDSNetworkException: Heartbeat > exceeded > 2017-01-06 16:23:26,020 ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] > (DefaultQuartzScheduler1) [7771902b] Command > 'GetAllVmStatsVDSCommand(HostName = prd-rbs-ovirt-kvm06-poa.rbs.com.br, > VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', > hostId='23b750ed-4ba6-4782-a9bd-c018c0f36e44', vds='Host[ > prd-rbs-ovirt-kvm06-poa.rbs.com.br,23b750ed-4ba6-4782-a9bd-c018c0f36e44]'})' > execution failed: VDSGenericException: VDSNetworkException: Heartbeat > exceeded > 2017-01-06 16:23:26,043 ERROR > [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able > to update response for "e5f7a478-841d-413c-baa1-d63632be7748" > 2017-01-06 16:24:32,480 ERROR > [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able > to update response for "75bf7e9a-fb5f-4253-bdf6-ff0fcbf8c876" > 2017-01-06 16:24:32,485 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (DefaultQuartzScheduler6) [35cc958c] Correlation ID: null, Call Stack: > null, Custom Event ID: -1, Message: VDSM > prd-rbs-ovirt-kvm06-poa.rbs.com.br command failed: Heartbeat exceeded > 2017-01-06 16:24:32,485 ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand] > (DefaultQuartzScheduler6) [35cc958c] Command 'SpmStatusVDSCommand(HostName > = prd-rbs-ovirt-kvm06-poa.rbs.com.br, > SpmStatusVDSCommandParameters:{runAsync='true', > hostId='23b750ed-4ba6-4782-a9bd-c018c0f36e44', > storagePoolId='0001-0001-0001-0001-0198'})' execution failed: > VDSGenericException: VDSNetworkException: Heartbeat exceeded > 2017-01-06 16:24:32,524 WARN > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (DefaultQuartzScheduler6) [152cde35] Correlation ID: 152cde35, Call Stack: > null, Custom Event ID: -1, Message: Invalid status on Data Center RBS. > Setting Data Center status to Non Responsive (On host > prd-rbs-ovirt-kvm06-poa.rbs.com.br, Error: Network error during > communication with the Host.). > 2017-01-06 16:25:37,493 ERROR > [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] > Internal server error: null > 2017-01-06 16:25:37,494 ERROR > [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] > Internal server error: null > 2017-01-06 16:25:37,494 ERROR > [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] > Internal server error: null > 2017-01-06 16:25:37,494 ERROR > [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] > Internal server error: null > 2017-01-06 16:25:37,494 ERROR > [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] > Internal server error: null > 2017-01-06 16:25:37,494 ERROR > [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] > I
Re: [ovirt-users] oVirt Engine 4.0.5 and CentOS 7.3 Instability
AndVdsVDSCommandParametersBase:{runAsync='true', hostId='f7842244-646c-400a-9736-f8d4aa9b1cef', vds='Host[ prd-rbs-ovirt-kvm03-poa.rbs.com.br,f7842244-646c-400a-9736-f8d4aa9b1cef]'})' execution failed: VDSGenericException: VDSNetworkException: Heartbeat exceeded 2017-01-06 16:27:49,666 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (DefaultQuartzScheduler7) [68fa51f0] Command 'GetAllVmStatsVDSCommand(HostName = prd-rbs-ovirt-kvm11-poa.rbs.com.br, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', hostId='d3c5cf1f-b203-4818-9767-5249387e3553', vds='Host[ prd-rbs-ovirt-kvm11-poa.rbs.com.br,d3c5cf1f-b203-4818-9767-5249387e3553]'})' execution failed: VDSGenericException: VDSNetworkException: Heartbeat exceeded 2017-01-06 16:27:49,667 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (DefaultQuartzScheduler11) [2d5a3838] Command 'GetAllVmStatsVDSCommand(HostName = prd-rbs-ovirt-kvm19-poa.rbs.com.br, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', hostId='887b6e35-1fd1-4cd6-9e78-05bcab12a417', vds='Host[ prd-rbs-ovirt-kvm19-poa.rbs.com.br,887b6e35-1fd1-4cd6-9e78-05bcab12a417]'})' execution failed: VDSGenericException: VDSNetworkException: Heartbeat exceeded 2017-01-06 16:27:49,682 ERROR [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able to update response for "edd8b375-4598-4671-a2cf-0d62fc9bdd0a" Em sex, 6 de jan de 2017 às 15:16, Rogério Ceni Coelho < rogeriocenicoe...@gmail.com> escreveu: > After apply the new vdsm-json package ? Yes, restart hole vm. :-( > > [root@prd-rbs-ovirt01-poa ~]# rpm -q > vdsm-jsonrpc-java-1.2.10-1.20161211091707.gitaf70e3f.el7.centos.noarch > vdsm-jsonrpc-java-1.2.10-1.20161211091707.gitaf70e3f.el7.centos.noarch > > [root@prd-rbs-ovirt01-poa ~]# rpm -qi > vdsm-jsonrpc-java-1.2.10-1.20161211091707.gitaf70e3f.el7.centos.noarch > Name: vdsm-jsonrpc-java > Version : 1.2.10 > Release : 1.20161211091707.gitaf70e3f.el7.centos > Architecture: noarch > Install Date: Fri Jan 6 09:57:25 2017 > Group : Development/Libraries > Size: 144305 > License : LGPLv2+ > Signature : (none) > Source RPM : > vdsm-jsonrpc-java-1.2.10-1.20161211091707.gitaf70e3f.el7.centos.src.rpm > Build Date : Sun Dec 11 07:17:40 2016 > Build Host : vm0065.workers-phx.ovirt.org > Relocations : (not relocatable) > URL : http://www.ovirt.org > Summary : JsonRpc java client (vdsm-jsonrpc-java) for oVirt > Description : > vdsm jsonrpc java > [root@prd-rbs-ovirt01-poa ~]# uptime > 15:15:11 up 19 min, 1 user, load average: 0.50, 0.46, 0.37 > [root@prd-rbs-ovirt01-poa ~]# last | head > rogerio_ pts/010.40.134.150Fri Jan 6 15:06 still logged in > > reboot system boot 3.10.0-514.2.2.e Fri Jan 6 14:56 - 15:15 (00:19) > > rogerio_ pts/010.40.134.150Fri Jan 6 14:46 - 14:55 (00:08) > > reboot system boot 3.10.0-514.2.2.e Fri Jan 6 10:11 - 14:55 (04:44) > > rogerio_ pts/010.40.134.150Fri Jan 6 09:56 - 10:10 (00:14) > > reboot system boot 3.10.0-514.2.2.e Fri Jan 6 09:55 - 10:11 (00:15) > > rogerio_ pts/010.40.134.150Fri Jan 6 09:53 - 09:53 (00:00) > > reboot system boot 3.10.0-514.2.2.e Thu Jan 5 10:00 - 10:11 (1+00:10) > > rogerio_ pts/010.40.134.150Thu Jan 5 09:59 - 09:59 (00:00) > > reboot system boot 3.10.0-514.2.2.e Wed Jan 4 14:53 - 10:11 (1+19:18) > > [root@prd-rbs-ovirt01-poa ~]# > > > Em sex, 6 de jan de 2017 às 15:12, Pavel Gashev <p...@acronis.com> > escreveu: > > Rogério, > > > > Did you restart the engine? > > > > *From: *Rogério Ceni Coelho <rogeriocenicoe...@gmail.com> > *Date: *Friday 6 January 2017 at 19:56 > *To: *Pavel Gashev <p...@acronis.com>, users <users@ovirt.org> > *Subject: *Re: [ovirt-users] oVirt Engine 4.0.5 and CentOS 7.3 Instability > > > > Pavel and oVirt Admins, > > > > Problem still the same ... Take a look ... > > > > [image: asted1] > > [root@prd-rbs-ovirt01-poa ~]# tail -f /var/log/ovirt-engine/engine.log > > 2017-01-06 14:24:48,145 WARN [org.ovirt.engine.core.vdsbroker.VdsManager] > (org.ovirt.thread.pool-6-thread-34) [] Host ' > prd-rbs-ovirt-kvm19-poa.rbs.com.br' is not responding. It will stay in > Connecting state for a grace period of 62 seconds and after that an attempt > to fence the host will be issued. > > 2017-01-06 14:24:48,168 WARN > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (org.ovirt.thread.pool-6-thread-34) [] Correlation ID: null, Call Stack: > null, Custom Event ID: -1, Message: Host > prd-rbs-ovirt-kvm19-poa.rbs.com.br is not responding. It will stay in > Connecting state for a grace period of 62
Re: [ovirt-users] oVirt Engine 4.0.5 and CentOS 7.3 Instability
Hi Pavel and oVirt Elves, Today, I install vdsm-jsonrpc-java. Take a look. Let´s see if problem are solve. Thanks again. [root@hlg-rbs-ovirt01-poa ~]# rpm -qa | grep -i vdsm-jsonrpc vdsm-jsonrpc-java-1.2.7-1.el7.centos.noarch [root@hlg-rbs-ovirt01-poa ~]# wget http://resources.ovirt.org/pub/ovirt-4.0-snapshot/rpm/el7/noarch/vdsm-jsonrpc-java-1.2.10-1.20161211091707.gitaf70e3f.el7.centos.noarch.rpm --2017-01-05 17:52:51-- http://resources.ovirt.org/pub/ovirt-4.0-snapshot/rpm/el7/noarch/vdsm-jsonrpc-java-1.2.10-1.20161211091707.gitaf70e3f.el7.centos.noarch.rpm Resolving resources.ovirt.org (resources.ovirt.org)... 66.187.230.28 Connecting to resources.ovirt.org (resources.ovirt.org)|66.187.230.28|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 123420 (121K) [application/x-rpm] Saving to: 'vdsm-jsonrpc-java-1.2.10-1.20161211091707.gitaf70e3f.el7.centos.noarch.rpm' 100%[=>] 123,420 202KB/s in 0.6s 2017-01-05 17:52:52 (202 KB/s) - 'vdsm-jsonrpc-java-1.2.10-1.20161211091707.gitaf70e3f.el7.centos.noarch.rpm' saved [123420/123420] [root@hlg-rbs-ovirt01-poa ~]# ll vdsm-jsonrpc-java-1.2.10-1.20161211091707.gitaf70e3f.el7.centos.noarch.rpm -rw-r--r--. 1 root root 123420 Jan 4 22:39 vdsm-jsonrpc-java-1.2.10-1.20161211091707.gitaf70e3f.el7.centos.noarch.rpm [root@hlg-rbs-ovirt01-poa ~]# rpm -Uvh vdsm-jsonrpc-java-1.2.10-1.20161211091707.gitaf70e3f.el7.centos.noarch.rpm Preparing... # [100%] Updating / installing... 1:vdsm-jsonrpc-java-1.2.10-1.201612# [ 50%] Cleaning up / removing... 2:vdsm-jsonrpc-java-1.2.7-1.el7.cen# [100%] [root@hlg-rbs-ovirt01-poa ~]# Em qua, 4 de jan de 2017 às 17:17, Rogério Ceni Coelho < rogeriocenicoe...@gmail.com> escreveu: > Wonderfull ... Seems to be the original problem with me on 4.0.5 ... I > will try this and do some feedback about soon ... > > Thanks > > Em qua, 4 de jan de 2017 às 17:08, Pavel Gashev <p...@acronis.com> > escreveu: > > Rogério, > > > > It looks like https://bugzilla.redhat.com/show_bug.cgi?id=1401585 > > > > Please try to install the following package, and restart the engine. > > > http://resources.ovirt.org/pub/ovirt-4.0-snapshot/rpm/el7/noarch/vdsm-jsonrpc-java-1.2.10-1.20161211091707.gitaf70e3f.el7.centos.noarch.rpm > > > > > > *From: *<users-boun...@ovirt.org> on behalf of Rogério Ceni Coelho < > rogeriocenicoe...@gmail.com> > *Date: *Monday 2 January 2017 at 21:51 > *To: *users <users@ovirt.org> > *Subject: *[ovirt-users] oVirt Engine 4.0.5 and CentOS 7.3 Instability > > > > Hi oVirt Gurus, > > > > Happy new year to everyone !!! > > > > I update oVirt Engine to 4.0.5 from 4.0.4 and Centos to 7.3 from 7.2 last > week and after that I have instability four times. Every time ovirt engine > seems to loose communication with one or more node servers like this image > below. Every time I rebooted oVirt engine server and everything came back > to normal. > > > > Anyone with this kind of problem ??? > > > > [image: asted1] > > > > After reboot : > > > > [image: asted2] > > > > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] PLEASE HELP - oVirt 4.0.5 Instability + Best way to rollback to 4.0.4
Oh my god ... This option means a lot of work ... But thanks anyway ... I think in this case are more easy to clone this six new VMs (that does not exist on ovirt engine database 4.0.4) to another Storage Domain with NFS or oVirt Production enviroment and recreate them after checkpoint rollback. Do you think ovirt-engine database restore are really not an option from 4.0.5 to 4.0.4 ? Thanks. Em qua, 4 de jan de 2017 às 15:55, Pavel Zhukov <pzhu...@redhat.com> escreveu: > Hello oVirt Padawan, > You can install new engine machine and import existing storage domains > there. > https://www.ovirt.org/develop/release-management/features/storage/importstoragedomain/ > Please read restrictions and limitations. > I think it's more safe way to go in such kind of situations. > > On Wed, Jan 4, 2017 at 6:40 PM, Rogério Ceni Coelho < > rogeriocenicoe...@gmail.com> wrote: > > Hi oVirt ObiWan´s, > > Today i try to rollback 4.0.5 to 4.0.4 because some instability with the > following method and i crash on a problem. :-( > > I shutdown oVirt Engine and make checkpoint on Engine VM ( Runs on > Hyper-V, don´t ask me way ... ). Rollback vm checkpoint to point in time > before 4.0.5 update process and power up ovirt engine vm. Everything ok > but, six virtual machines that i create before this point in time does not > exist on oVirt Engine Database and all came with external-VMNAME and i can > not do nothing on them. I really think (only in my dreams ) that when ovirt > engine goes up and talk with ovirt nodes, all new vm will be automatically > discovered again. The worst thing are that i use SAN Storage Domain and > oVirt use LVM to storage VM disks, so i don´t know how to find vm disks > that ovirt engine does not recognize (external-VMNAME). > > After all that, i rollback again to 4.0.5 and every vm are ok now again, > but i want to test this rollback process to 4.0.4 and do this on Production. > > I think the right steps are : > > 1. Run engine-backup /bin/engine-backup --mode=backup --scope=all > --file=/root/ovirt/`hostname`.`date +%d%m%Y.%H%M%S`.ovirt-engine.bkp > --log=/tmp/ovirt-engine_backup.log > 2. Shutdown ovirt engine vm. > 3. Make new checkpoint to rollback with something goes wrong > 4. Rollback to checkpoint witch 4.0.4 > 5. Restore engine-backup (from version 4.0.5) > 6. Start everything and check if all are ok > > This is the right way to rollback from one sub release to another ( 4.0.5 > to 4.0.4 ) ??? > This checkpoints/snapshots of ovirt-engine VM are the best way to rollback > in time ??? > > Thanks in advance. > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > > > -- > Pavel Zhukov > Software Engineer > RHEV Devops > IRC: landgraf > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] PLEASE HELP - oVirt 4.0.5 Instability + Best way to rollback to 4.0.4
Hi oVirt ObiWan´s, Today i try to rollback 4.0.5 to 4.0.4 because some instability with the following method and i crash on a problem. :-( I shutdown oVirt Engine and make checkpoint on Engine VM ( Runs on Hyper-V, don´t ask me way ... ). Rollback vm checkpoint to point in time before 4.0.5 update process and power up ovirt engine vm. Everything ok but, six virtual machines that i create before this point in time does not exist on oVirt Engine Database and all came with external-VMNAME and i can not do nothing on them. I really think (only in my dreams ) that when ovirt engine goes up and talk with ovirt nodes, all new vm will be automatically discovered again. The worst thing are that i use SAN Storage Domain and oVirt use LVM to storage VM disks, so i don´t know how to find vm disks that ovirt engine does not recognize (external-VMNAME). After all that, i rollback again to 4.0.5 and every vm are ok now again, but i want to test this rollback process to 4.0.4 and do this on Production. I think the right steps are : 1. Run engine-backup /bin/engine-backup --mode=backup --scope=all --file=/root/ovirt/`hostname`.`date +%d%m%Y.%H%M%S`.ovirt-engine.bkp --log=/tmp/ovirt-engine_backup.log 2. Shutdown ovirt engine vm. 3. Make new checkpoint to rollback with something goes wrong 4. Rollback to checkpoint witch 4.0.4 5. Restore engine-backup (from version 4.0.5) 6. Start everything and check if all are ok This is the right way to rollback from one sub release to another ( 4.0.5 to 4.0.4 ) ??? This checkpoints/snapshots of ovirt-engine VM are the best way to rollback in time ??? Thanks in advance. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Recommended Ovirt Implementation on Active-Active Datacenters (Site 1 and Site2) - Same Cluster
Hi Ovirt Jedi´s !!! First of all, congrats about the product !!! I love Ovirt !!! I am using Ovirt 4.0.4 with 10 hosts and 58 virtual machines on two Active-Active Datacenters using two EMC Vplex + two EMC VNX5500 + eight Dell Blades + 8 Dell PowerEdge M610 and two M620 Servers. Half servers are on Site 1 and Half servers on Site 2. The same with VMs. All Sites work as one and have redundant network, storage, power, etc etc etc ... I want to know what is the best way to set that VM number 1 runs on Site 1 and VM number 2 runs on Site 2 ? On Vmware 5.1 we use DRS Group Manager and on Hyper-V we use Custom Properties on hosts and on VMs. What we use on oVirt without segregate on two different Datacenters or two different clusters ? Thanks in advance. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Replace Engine Self-Signed Certificate
Take a look. Documentation imcomplete. https://bugzilla.redhat.com/show_bug.cgi?id=1336838 Em seg, 10 de out de 2016 às 12:17, Alan Griffithsescreveu: > Hi, > > I'm trying to replace the self-signed certificate in the engine. > > I updated the four files listed here > > http://www.ovirt.org/develop/release-management/features/infra/pki/ > > But on restarting Apache and logging in I get the following error, > "sun.security.validator.ValidatorException: PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target" > > What am I missing? > > Thanks, > > Alan > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] oVirt Node Network conf X DNS
Thanks! Em Qui, 15 de set de 2016 09:04, Simone Tiraboschi <stira...@redhat.com> escreveu: > On Wed, Sep 14, 2016 at 11:16 PM, Rogério Ceni Coelho < > rogeriocenicoe...@gmail.com> wrote: > >> Hi oVirt Users and Admins !!! >> >> I am installing ovirt 4.0.3 and do above conf on my OVirt Node using bond >> and vlan. >> >> When I add this host to ovirt engine and associate ovirtmgmt network with >> same tag vlan number 1051, DNS conf was overwrited by vdsm. >> > > > It's a know issue: https://bugzilla.redhat.com/1160423 > please set you DNSs in /etc/resolv.conf instead of the interface file cfg > with DNS1 and DNS2. > You can also try this: > https://bugzilla.redhat.com/show_bug.cgi?id=1160423#c44 > > >> >> So, as i do not find any way to set DNS on ovirt engine network conf i >> think that for ovirt nodes i need to use another network that i do not plan >> to use with virtual machines ( because if i add a new network on ovirt >> engine with same tag vlan number the ovirt node conf will be overwrited by >> vdsm ). >> >> Before add to ovirt engine : >> >> [root@prd-rbs-ovirt-kvm01-poa ~]# ip addr >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >> >> inet 127.0.0.1/8 scope host lo >> >>valid_lft forever preferred_lft forever >> >> inet6 ::1/128 scope host >> >>valid_lft forever preferred_lft forever >> >> 2: em1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master >> bond0 state UP qlen 1000 >> >> link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff >> >> 3: em2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master >> bond0 state UP qlen 1000 >> >> link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff >> >> 4: p3p1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master >> bond0 state UP qlen 1000 >> >> link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff >> >> 5: p3p2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master >> bond0 state UP qlen 1000 >> >> link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff >> >> 6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue >> state UP >> >> link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff >> >> inet6 fe80::5e26:aff:fefd:acc/64 scope link >> >>valid_lft forever preferred_lft forever >> >> 7: bond0.1051@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc >> noqueue state UP >> >> link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff >> >> inet 10.151.252.222/22 brd 10.151.255.255 scope global bond0.1051 >> >>valid_lft forever preferred_lft forever >> >> inet6 fe80::5e26:aff:fefd:acc/64 scope link >> >>valid_lft forever preferred_lft forever >> >> [root@prd-rbs-ovirt-kvm01-poa ~]# cat /etc/resolv.conf >> >> # Generated by NetworkManager >> >> search rbs.com.br rbs.net clicrbs.com.br srvr.rbs.net >> >> nameserver 10.236.68.62 >> >> nameserver 10.1.1.40 >> >> nameserver 10.155.33.154 >> >> >> After : >> >> >> [root@prd-rbs-ovirt-kvm01-poa ~]# ip addr >> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN >> >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >> >> inet 127.0.0.1/8 scope host lo >> >>valid_lft forever preferred_lft forever >> >> inet6 ::1/128 scope host >> >>valid_lft forever preferred_lft forever >> >> 2: em1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master >> bond0 state UP qlen 1000 >> >> link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff >> >> 3: em2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master >> bond0 state UP qlen 1000 >> >> link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff >> >> 4: p3p1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master >> bond0 state UP qlen 1000 >> >> link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff >> >> 5: p3p2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master >> bond0 state UP qlen 1000 >> >> link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff >> >> 6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu
[ovirt-users] oVirt Node Network conf X DNS
Hi oVirt Users and Admins !!! I am installing ovirt 4.0.3 and do above conf on my OVirt Node using bond and vlan. When I add this host to ovirt engine and associate ovirtmgmt network with same tag vlan number 1051, DNS conf was overwrited by vdsm. So, as i do not find any way to set DNS on ovirt engine network conf i think that for ovirt nodes i need to use another network that i do not plan to use with virtual machines ( because if i add a new network on ovirt engine with same tag vlan number the ovirt node conf will be overwrited by vdsm ). Before add to ovirt engine : [root@prd-rbs-ovirt-kvm01-poa ~]# ip addr 1: lo:mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: em1: mtu 1500 qdisc mq master bond0 state UP qlen 1000 link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff 3: em2: mtu 1500 qdisc mq master bond0 state UP qlen 1000 link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff 4: p3p1: mtu 1500 qdisc mq master bond0 state UP qlen 1000 link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff 5: p3p2: mtu 1500 qdisc mq master bond0 state UP qlen 1000 link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff 6: bond0: mtu 1500 qdisc noqueue state UP link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff inet6 fe80::5e26:aff:fefd:acc/64 scope link valid_lft forever preferred_lft forever 7: bond0.1051@bond0: mtu 1500 qdisc noqueue state UP link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff inet 10.151.252.222/22 brd 10.151.255.255 scope global bond0.1051 valid_lft forever preferred_lft forever inet6 fe80::5e26:aff:fefd:acc/64 scope link valid_lft forever preferred_lft forever [root@prd-rbs-ovirt-kvm01-poa ~]# cat /etc/resolv.conf # Generated by NetworkManager search rbs.com.br rbs.net clicrbs.com.br srvr.rbs.net nameserver 10.236.68.62 nameserver 10.1.1.40 nameserver 10.155.33.154 After : [root@prd-rbs-ovirt-kvm01-poa ~]# ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: em1: mtu 1500 qdisc mq master bond0 state UP qlen 1000 link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff 3: em2: mtu 1500 qdisc mq master bond0 state UP qlen 1000 link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff 4: p3p1: mtu 1500 qdisc mq master bond0 state UP qlen 1000 link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff 5: p3p2: mtu 1500 qdisc mq master bond0 state UP qlen 1000 link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff 6: bond0: mtu 1500 qdisc noqueue state UP link/ether 5c:26:0a:fd:0a:cc brd ff:ff:ff:ff:ff:ff 7: bond0.1051@bond0: mtu 1500 qdisc noqueue master ovirtmgmt state UP link/ether fa:d3:c0:cd:dd:a3 brd ff:ff:ff:ff:ff:ff 8: ;vdsmdummy;: mtu 1500 qdisc noop state DOWN link/ether b2:8b:94:d9:d9:83 brd ff:ff:ff:ff:ff:ff 9: ovirtmgmt: mtu 1500 qdisc noqueue state UP link/ether fa:d3:c0:cd:dd:a3 brd ff:ff:ff:ff:ff:ff inet 10.151.252.222/22 brd 10.151.255.255 scope global ovirtmgmt valid_lft forever preferred_lft forever [root@prd-rbs-ovirt-kvm01-poa ~]# cat /etc/resolv.conf # Generated by NetworkManager search rbs.com.br # No nameservers found; try putting DNS servers into your # ifcfg files in /etc/sysconfig/network-scripts like so: # # DNS1=xxx.xxx.xxx.xxx # DNS2=xxx.xxx.xxx.xxx # DOMAIN=lab.foo.com bar.foo.com [root@prd-rbs-ovirt-kvm01-poa ~]# cat /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt # Generated by VDSM version 4.18.11-1.el7.centos DEVICE=ovirtmgmt TYPE=Bridge DELAY=0 STP=off ONBOOT=yes IPADDR=10.151.252.222 NETMASK=255.255.252.0 GATEWAY=10.151.252.1 BOOTPROTO=none MTU=1500 DEFROUTE=yes NM_CONTROLLED=no IPV6INIT=no [root@prd-rbs-ovirt-kvm01-poa ~]# ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users