December 2017 - Users - Ovirt List Archives

Re: [ovirt-users] ovirt 4.2 host not compatible

by Paul Dyer

It seems that I am using net_persistence = ifcfg, and that I have lost the definitions for the logical networks. I have recovered these, and was able to do setup logical networks. It is all working now. Paul On Fri, Dec 22, 2017 at 1:46 PM, Paul Dyer <pmdyermms(a)gmail.com> wrote: > My setup is RHEL 7.4, with the host separate from the engine. > > The ovirt-release42 rpm was added to the engine host, but not to the > virtualization host. The vhost was still running v4.1 rpms. I installed > ovirt-release42 on the vhost, then updated the rest of the rpms with "yum > update". I am still getting an error on activation of the vhost... > > Host parasol does not comply with the cluster Intel networks, the > following networks are missing on host: 'data30,data40,ovirtmgmt' > > It seems like the networks bridges are not there anymore?? > > Paul > > > > On Fri, Dec 22, 2017 at 12:46 PM, Paul Dyer <pmdyermms(a)gmail.com> wrote: > >> Hi, >> >> I have upgraded to ovirt 4.2 without issue. But I cannot find a way to >> upgrade the host compatibility in the new OVirt Manager. >> >> I get this error when activiating the host... >> >> host parasol is compatible with versions (3.6,4.0,4.1) and cannot join >> Cluster Intel which is set to version 4.2. >> >> Thanks, >> Paul >> >> >> -- >> Paul Dyer, >> Mercury Consulting Group, RHCE >> 504-302-8750 <(504)%20302-8750> >> > > > > -- > Paul Dyer, > Mercury Consulting Group, RHCE > 504-302-8750 <(504)%20302-8750> > -- Paul Dyer, Mercury Consulting Group, RHCE 504-302-8750

6 years, 12 months

2
1
0 / 0

Re: [ovirt-users] oVirt 4.2.0 is now generally available

by Gary Pedretty

Unable to upgrade a self-hosted engine installation to 4.2.0 due to the following error ovirt-engine-setup-plugin-ovirt-engine conflicts with ovirt-engine-4.0.6.3-1.el7.centos.noarch When trying to do the first step of updating the hosted engine vm Gary ------------------------------------------------------------------------ Gary Pedretty gary(a)ravnalaska.net Systems Manager www.flyravn.com Ravn Alaska /\ W 907-450-7251 5245 Airport Industrial Road / \/\ C 907-388-2247 Fairbanks, Alaska 99709 /\ / \ \ Second greatest commandment Serving All of Alaska / \/ /\ \ \/\ “Love your neighbor as White as far as the eye can see. Must be winter yourself” Matt 22:39 ------------------------------------------------------------------------

7 years

2
1
0 / 0

Info from 4.2 beta2 to 4.2

by Gianluca Cecchi

Hello, I have an host where I only installed ovirt-node-ng from iso of 4.2 beta2 and then I didn't run any deploy of hosted engine yet. If I want to start doing it but with the final 4.2 what is the correct step to do (other than starting from scratch with final 4.2 iso)? yum update (after installing 4.2 repo file) gives me what below and not a full image layer, is it correct? Thanks, Gianluca # yum update ... Dependencies Resolved ============================================================================================================================================================================================================================== Package Arch Version Repository Size ============================================================================================================================================================================================================================== Updating: ansible noarch 2.4.2.0-0.el7 ovirt-4.2-centos-ovirt42 7.6 M collectd x86_64 5.8.0-2.el7 ovirt-4.2-centos-opstools 624 k collectd-disk x86_64 5.8.0-2.el7 ovirt-4.2-centos-opstools 26 k collectd-netlink x86_64 5.8.0-2.el7 ovirt-4.2-centos-opstools 27 k collectd-write_http x86_64 5.8.0-2.el7 ovirt-4.2-centos-opstools 33 k gdeploy noarch 2.0.6-1.el7 ovirt-4.2-centos-gluster312 203 k glusterfs x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 558 k glusterfs-api x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 97 k glusterfs-cli x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 197 k glusterfs-client-xlators x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 854 k glusterfs-events x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 62 k glusterfs-fuse x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 141 k glusterfs-geo-replication x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 230 k glusterfs-libs x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 399 k glusterfs-rdma x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 64 k glusterfs-server x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 1.2 M openvswitch x86_64 1:2.7.3-1.1fc27.el7 ovirt-4.2-centos-ovirt42 4.6 M openvswitch-ovn-common x86_64 1:2.7.3-1.1fc27.el7 ovirt-4.2-centos-ovirt42 1.4 M openvswitch-ovn-host x86_64 1:2.7.3-1.1fc27.el7 ovirt-4.2-centos-ovirt42 802 k python2-gluster x86_64 3.12.3-1.el7 ovirt-4.2-centos-gluster312 39 k python2-openvswitch noarch 1:2.7.3-1.1fc27.el7 ovirt-4.2-centos-ovirt42 167 k qemu-img-ev x86_64 10:2.9.0-16.el7_4.11.1 ovirt-4.2-centos-qemu-ev 2.2 M qemu-kvm-common-ev x86_64 10:2.9.0-16.el7_4.11.1 ovirt-4.2-centos-qemu-ev 914 k qemu-kvm-ev x86_64 10:2.9.0-16.el7_4.11.1 ovirt-4.2-centos-qemu-ev 2.8 M Transaction Summary ============================================================================================================================================================================================================================== Upgrade 24 Packages Total download size: 25 M Is this ok [y/d/N]:

7 years

2
1
0 / 0

non-operational host issues following 4.2 upgrade

by Jason Brooks

Hi all, I upgraded my 4 host converged gluster/ovirt lab setup to 4.2 yesterday, and now 3 of my hosts won't connect to my main data domain, so they're non-operational when I try to activate them. Here's what seems like a relevant passage of vdsm.log: https://paste.fedoraproject.org/paste/JZuxul6-HZjjl8uHzgqL-w The hosts can mount the gluster storage just fine, I can mount to a test location on the hosts, and I can see that the hosts are mounting the storage in the usual place when they attempt to activate. Permissions look normal, too. I undeployed the hosted engine from the three problem machines, in case that was causing an issue. The hosts are running centos 7. Does any of this ring a bell for anyone? Thanks, Jason

7 years

2
3
0 / 0

two questions about 4.2 feature

by Nathanaël Blanchet

Hi all, On 4.2, it seems that it is not possible anymore to move a disk to an other storage domain through the vm disk tab (still possible from the storage disk tab). Secondly, while the new design is great, is there a possibility to keep the old one for any needs? -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

7 years

3
2
0 / 0

Ovirt 4.2 and host console

by Gianluca Cecchi

Hello, after upgrading engine and then plain CentOS 7.4 host from 4.1 to 4.2, I see in host section if I select line for the host, right click and host console... That tries to go to the typical 9090 cockpit Port of node-ng... Is this an error or in 4.2 the access to host console is for plain OS nodes too? In that case is there any service I have to enable on host? It seems indeed my host is not currently listening on 9090 Port.... Thanks, Gianluca

7 years

3
3
0 / 0

Re: [ovirt-users] Upgrade to 4.2 Postgresql Error

by Yaniv Kaul

On Dec 22, 2017 11:56 AM, "Gabriel Stein" <gabrielstein(a)gmail.com> wrote: Well, it worked, I could upgrade the hosted-engine changing the /etc/locale to en-US-UTF8. I deactivated puppet too, if someone are using puppet for provisioning. Now I'm having problems to update the host, but it's just this annoying bug from vsdm(you need to restart it....) Can you share more information? And the log, if possible. Y. Thanks a lot! Best Regards, Gabriel PS: Looking forward for the resolution in Bugzilla. Gabriel Stein ------------------------------ Gabriel Ferraz Stein Tel.: +49 (0) 170 2881531 2017-12-21 17:15 GMT+01:00 Simone Tiraboschi <stirabos(a)redhat.com>: > > > On Thu, Dec 21, 2017 at 4:30 PM, Simone Tiraboschi <stirabos(a)redhat.com> > wrote: > >> >> >> On Thu, Dec 21, 2017 at 8:41 AM, Sandro Bonazzola <sbonazzo(a)redhat.com> >> wrote: >> >>> >>> >>> 2017-12-20 16:07 GMT+01:00 Gabriel Stein <gabrielstein(a)gmail.com>: >>> >>>> Hi! >>>> >>>> well, I'm a update fever and I decided to update my ovirt to 4.2.0. >>>> >>> >>> Thanks for this valuable feedback! Simone has already replied and will >>> check your setup logs. >>> >>> >>> >>> >>>> >>>> How I'm doingi it? >>>> >>>> I'm following the rules! >>>> >>>> 1 - Global Maintenance Mode >>>> 2 - Yum Install ovirt-release-4.2 >>>> 3- yum update ovirt-setup*. >>>> >>>> But, by the engine-setup I have a conflict with the system collation >>>> and postgresql. Unfortunatelly I changed via puppet to the german >>>> collation(de_DE-UTF8) of ovirt-engine hosted vm(because it's a standard for >>>> us) but this was after the engine-setup and the DB Configuration from >>>> Postgresql. >>>> >>> >>> Adding also Didi >>> >>> >>>> >>>> I think that I can easily change the system collation to us-US-UFT8 but >>>> I'm afraid that I can "destroy" my hosted-engine VM with that change, is >>>> hosted-engine so sensible? >>>> >>>> How I know that error? The logs are saying that(and the error in on >>>> postgresql upgrade part of setup)! >>>> >>>> *Performing Consistency Checks* >>>> *-----------------------------* >>>> *Checking cluster versions ok* >>>> *Checking database user is the install user ok* >>>> *Checking database connection settings ok* >>>> *Checking for prepared transactions ok* >>>> *Checking for reg* system OID user data types ok* >>>> *Checking for contrib/isn with bigint-passing mismatch ok* >>>> *Checking for invalid "line" user columns ok* >>>> *Creating dump of global objects ok* >>>> *Creating dump of database schemas* >>>> * engine* >>>> * ovirt_engine_history* >>>> * postgres* >>>> * template1* >>>> * ok* >>>> >>>> *lc_collate values for database "postgres" do not match: old >>>> "en_US.UTF-8", new "de_DE.UTF-8"* >>>> *Failure, exiting* >>>> >>>> I would be thankful if someone could give me some hint about that! >>>> >>> >> OK, reproduced. >> The issue happens if and only if you changed system wide locales after >> having installed ovirt-engine but before upgrading it to 4.2. >> I'm going to open a bug to track it. >> > > https://bugzilla.redhat.com/show_bug.cgi?id=1528371 > > >> >> In engine-setup we are explicitly setting en_US.UTF-8 as the locale of >> the engine DB but we are not touching at all the locale of postgres own DB >> which match the system wide locale and your issue is indeed on the postgres >> DB, not on the engine one. >> pg_upgrade cannot change it on the fly on upgrades. >> >> I tried to find a working fix with env variables but unfortunately >> nothing I tired worked. >> The only workaround I was able to find is to temporary set the locale you >> had at first successful engine-setup execution time (en_US.UTF-8 in your >> case but it varies) under /etc/locale.conf and only then execute >> engine-setup to upgrade it to 4.2. >> After that you could safely switch back /etc/locale.conf to whatever you >> need. >> All the env variable I tried seams absolutely not relevant for this >> specific issue. >> >> >> >> >>> >>>> Best Regards, >>>> >>>> Gabriel >>>> PS: If I go to devconf in Brno I will pay a lot of beers to the >>>> developer of the engine-setup rollback! Saved my life! >>>> >>> >>> The specific developer won't be there, but you're welcome to reach oVirt >>> people there and share some beer :-) >>> >>> >>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Gabriel Stein >>>> ------------------------------ >>>> Gabriel Ferraz Stein >>>> Tel.: +49 (0) 170 2881531 >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> Users(a)ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/users >>>> >>>> >>> >>> >>> -- >>> >>> SANDRO BONAZZOLA >>> >>> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D >>> >>> Red Hat EMEA <https://www.redhat.com/> >>> <https://red.ht/sig> >>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >>> >> > _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

7 years

2
1
0 / 0

Re: [ovirt-users] Ovirt-Log-Collector - Engine Crashes During

by Langley, Robert

--_000_BN1PR09MB02893630D6E0390EC4DC6FD387020BN1PR09MB0289namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Thank you for chiming in. I appreciate the help. The Engine's disk has 51GB available for /tmp of the 80GB disk. --_000_BN1PR09MB02893630D6E0390EC4DC6FD387020BN1PR09MB0289namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> <p class=3D"MsoPlainText">Thank you for chiming in. I appreciate the help.<= o:p></o:p></p> <p class=3D"MsoPlainText">The Engine’s disk has 51GB available for /t= mp of the 80GB disk.<o:p></o:p></p> </div> </body> </html> --_000_BN1PR09MB02893630D6E0390EC4DC6FD387020BN1PR09MB0289namp_--

7 years

1
0
0 / 0

Remove all traces of a host from oVirt Engine

by Vinícius Ferrão

Hello, I’m installing a brand new oVirt 4.2 infrastructure and for whatever reasons I don’t know one host got in an unstable state (due to misconfigurations of iSCSI networks) and it fails to be up. After giving up on the host I just reinstalled it and tried to add it again on the engine. To make me surprise, the problem persisted. So there’s an issue on the engine. The question is: how can I completely remove all traces os a given host on the ovirt engine? The server was removed gracefully from the web interface, but it appears that something nasty was keep in the engine. Thanks, V.

7 years

2
1
0 / 0

Re: [ovirt-users] Regarding Ovirt Installation

by Simone Tiraboschi

On Thu, Dec 21, 2017 at 1:59 PM, ruth john <gamerangerserver01(a)gmail.com> wrote: > Sir, buying nfs storage would cost me a lot. Can't I use it directly on > the provided storage? > We don't have anymore an all-in-one installation where the engine and vdsm runs altogether in the same machine; the proposed replacement is hosted-engine which doesn't work with local storage since it's supposed to be able to restart the engine VM somewhere else for HA reasons and the local storage is against that by definition. If you have three machines I'd suggest an hyperconverged gluster deployment with replica 3. If you want to try it on a single machine keep present that NFS in loop-back is discouraged so maybe you could try iSCSI or, maybe with a small hack, gluster in replica 1 in loopback > > > On Dec 21, 2017 1:25 PM, "Simone Tiraboschi" <stirabos(a)redhat.com> wrote: > > > > On Wed, Dec 20, 2017 at 10:45 PM, ruth john <gamerangerserver01(a)gmail.com> > wrote: > >> I am delighted with the interface and other features of the Ovirt but was >> never able to install it properly, is that true OVirt doesn't support >> Hetzner Dedicated and OVH dedicated? >> > > I personally know about a friend who is running it on an a couple of > dedicated OVH machines with NFS storage provided by OVH. > No idea about Hetzner. > > > >> if not can anyone please help me to install atleast on one to make me >> understand where am i doing the mistake. >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >> > >

7 years

4
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users December 2017