[ovirt-users] Re: Using third-party certificate: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

2021-09-30 Thread Edward Berger
I have an engine with a similar issue.
You might want to revert to the old self signed cert created by
installation, and then follow the instructions at
   https://ovirt.org/documentation/administration_guide/index.html
to try re-installing the third party cert after you're sure the original
cert is working properly.

My temp fix for this (didn't survive an engine VM reboot) was to cat the
cert I was installing with its intermediate-root cert into
a file named full.crt and then running a command as root like...

keytool -import -trustcacerts -keystore /etc/pki/java/cacerts -storepass
changeit -alias "$YOURALIAS" -import -file full.crt
and then systemctl restart ovirt-engine #to pick up the change.

Still trying to track down what's different on this one vs others that
work.
  key size is larger
  cert has alternative name.


On Thu, Sep 30, 2021 at 4:47 PM Nicolás  wrote:

> Please, any help with this?
>
> El 29/9/21 a las 13:21, nico...@devels.es escribió:
> > Hi,
> >
> > I'm making a bare metal oVirt installation, version 4.4.8.
> > 'ovirt-engine' command ends well, however, we're using a third-party
> > certificate (from LetsEncrypt) both for the apache server and the
> > ovirt-websocket-proxy. So we changed configuration files regarding
> > httpd and ovirt-websocket-proxy.
> >
> > Once changed the configurations, if I try to log in to the oVirt
> > engine, I get a "PKIX path building failed:
> > sun.security.provider.certpath.SunCertPathBuilderException: unable to
> > find valid certification path to requested target" error.
> >
> > In prior versions we used to add the chain to the
> > /etc/pki/ovirt-engine/.truststore file, however, simply listing the
> > current certificates seems not to be working on 4.4.8.
> >
> >   # LANG=C keytool -list -keystore /etc/pki/ovirt-engine/.truststore
> > -alias intermedia_le -storepass mypass
> >   keytool error: java.io.IOException: Invalid keystore format
> >
> > Is there something I'm missing here?
> >
> > Thank
> > ___
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to users-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> >
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/5VWVBQGIWJSPWVTV5UK2I2VXBNDV6GSS/
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/VKYBE6TJZFMAXX2G6GPMXIQYW7F5LABY/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/K7Q2WDCSCZPSKL2IHJA6C2BIFGYLH3IZ/


[ovirt-users] Re: host upgrade problems galore

2021-09-15 Thread Edward Berger
In case you decide to try again or for other oVirt users, who see similar
issues

When 'required' networks for the cluster aren't there, or shared storage is
unreachable, the host is put into non-operational state.

oVirt engine wants to handle the network configs for the hypervisors.
The required networks should be configured in the engine's "setup host
networks" for the new host.

When you add a new hypervisor host to the oVirt cluster, by default it
doesn't set up 'required networks',
and doing things behind the engine's back isn't a good idea because it
doesn't know which logical network
should be connected to which network interface.

If you forget to tell your shared storage to allow access from the new host
it will also cause non-operational state.





On Wed, Sep 15, 2021 at 3:32 PM Diggy Mc  wrote:

> You can now discard this thread !!!
>
> Prior to creating this thread, I also tried to copy the networks from
> another functioning host thinking that might be needed.  Did not get any
> errors for the copy function, but the networks were not copied.
>
> That's when started this thread.
>
> Since then, I said, "fck it" and decided to try something while waiting
> for help.
>
> I manually added the networks to the rebuilt host.  Suddenly (and
> apparently magically) it is now in Up state.
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/EZSSMERYDSUS25TRLTEKXD26CQZWY65U/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/IWROC4DXB2X7G6NNO5IBYG3OQLTHPAHQ/


[ovirt-users] Re: cannot add host to cluster - libvirt.libvirtError: internal error: unknown feature amd-sev-es

2021-08-30 Thread Edward Berger
Somewhere along the way in oVirt old CPU support was dropped for windows
compatibility reasons.
Nehalems were dropped, and westmeres would report as nehalems and then fail
if AES wasn't turned on in the bios.
So this is a case of ERROR_CPU_TOO_OLD.  (They're also power hungry
compared to modern CPUs)

As you're trying standalone, I'd suggest a basic KVM host if it was the
only server I had.

On Mon, Aug 30, 2021 at 5:48 AM marek  wrote:

> ovirt 4.4.8 standalone
>
> cluster cpu type: nehalem family
>
> ovirt host centos 8 stream
>
> ovirt gui info: Host CPU type is not supported in this cluster
> compatibility version or is not supported at all.
>
> vdsm.log
>
> 2021-08-30 11:30:58,600+0200 ERROR (jsonrpc/4) [root] Error while
> getting domain capabilities (machinetype:92)
> Traceback (most recent call last):
>File "/usr/lib/python3.6/site-packages/vdsm/common/cache.py", line
> 41, in __call__
>  return self.cache[args]
> KeyError: ()
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>File "/usr/lib/python3.6/site-packages/vdsm/machinetype.py", line 90,
> in _get_domain_capabilities
>  domcaps = conn.getDomainCapabilities(None, arch, None, virt_type, 0)
>File
> "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py",
> line 131, in wrapper
>  ret = f(*args, **kwargs)
>File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line
> 94, in wrapper
>  return func(inst, *args, **kwargs)
>File "/usr/lib64/python3.6/site-packages/libvirt.py", line 4493, in
> getDomainCapabilities
>  raise libvirtError('virConnectGetDomainCapabilities() failed')
> libvirt.libvirtError: internal error: unknown feature amd-sev-es
> 2021-08-30 11:30:58,650+0200 ERROR (jsonrpc/4) [root] Error while
> getting CPU features: no domain capabilities found (machinetype:188)
>
> model name  : Intel(R) Xeon(R) CPU   E5504  @ 2.00GHz
>
> cat /sys/devices/cpu/caps/pmu_name
> nehalem
>
>   grep -E 'svm|vmx' /proc/cpuinfo | grep nx
>
> flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall
> nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
> nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3
> cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm pti ssbd ibrs ibpb stibp
> tpr_shadow vnmi flexpriority ept vpid dtherm flush_l1d
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/EXS5BJYDCALBFG4FOK6T4UT43WTQOFRZ/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/IULRXEUOOHY2FDGSAIH4VX2CMQUR5AEA/


[ovirt-users] Re: Is there a way to support Mellanox OFED with oVirt/RHV?

2021-08-05 Thread Edward Berger
The ovirt node-ng installer iso creates imgbased systems with baseos and
appstream repos disabled,
not something you would have with a regular base OS installed system with
added oVirt repos...

so with node, 'dnf install foo' usually fails if not adding an extra
--enablerepo flag, which seems to change with the OS version.

here's some old notes I had.

download latest mlnx ofed archive
tar xfvz *.tgz
cd *64

# mount -o loop MLNX*iso /mnt
# cd /mnt

#./mlnxinstall requires more RPMS to be installed
# note: some versions of CentOS use different case reponames, look at
contents of /etc/yum.repos.d files
yum --enablerepo baseos install perl-Term-ANSIColor
yum --enablerepo baseos --enablerepo appstream install
perl-Getopt-Long tcl gcc-gfortran tcsh tk make
./mlnxinstall


On Thu, Aug 5, 2021 at 3:32 PM Vinícius Ferrão 
wrote:

> Hi Edward, it seems that running mlnxofedinstall would do the job.
> Although I've some questions.
>
> You mentioned the --enable-repo option but I didn't find it. There's a
> disable one, so I'm assuming that it's enabled by default. Anyway there's
> no repos added after the script.
>
> I've run the script with the arguments: ./mlnxofedinstall --with-nfsrdma
> -vvv; and everything went fine:
>
> [root@rhvepyc2 mnt]# /etc/init.d/openibd status
>
>   HCA driver loaded
>
> Configured IPoIB devices:
> ib0
>
> Currently active IPoIB devices:
> ib0
> Configured Mellanox EN devices:
>
> Currently active Mellanox devices:
> ib0
>
> The following OFED modules are loaded:
>
>   rdma_ucm
>   rdma_cm
>   ib_ipoib
>   mlx5_core
>   mlx5_ib
>   ib_uverbs
>   ib_umad
>   ib_cm
>   ib_core
>   mlxfw
>
> [root@rhvepyc2 mnt]# rpm -qa | grep -i mlnx
> libibverbs-54mlnx1-1.54103.x86_64
> infiniband-diags-54mlnx1-1.54103.x86_64
> mlnx-ethtool-5.10-1.54103.x86_64
> rdma-core-54mlnx1-1.54103.x86_64
> dapl-utils-2.1.10.1.mlnx-OFED.4.9.0.1.4.54103.x86_64
> kmod-mlnx-nfsrdma-5.4-OFED.5.4.1.0.3.1.rhel8u4.x86_64
> dapl-2.1.10.1.mlnx-OFED.4.9.0.1.4.54103.x86_64
> mlnx-tools-5.2.0-0.54103.x86_64
> libibumad-54mlnx1-1.54103.x86_64
> opensm-5.9.0.MLNX20210617.c9f2ade-0.1.54103.x86_64
> kmod-kernel-mft-mlnx-4.17.0-1.rhel8u4.x86_64
> ibacm-54mlnx1-1.54103.x86_64
> dapl-devel-static-2.1.10.1.mlnx-OFED.4.9.0.1.4.54103.x86_64
> ar_mgr-1.0-5.9.0.MLNX20210617.g5dd71ee.54103.x86_64
> mlnx-ofa_kernel-5.4-OFED.5.4.1.0.3.1.rhel8u4.x86_64
> rdma-core-devel-54mlnx1-1.54103.x86_64
> opensm-static-5.9.0.MLNX20210617.c9f2ade-0.1.54103.x86_64
> srp_daemon-54mlnx1-1.54103.x86_64
> sharp-2.5.0.MLNX20210613.83fe753-1.54103.x86_64
> mlnx-iproute2-5.11.0-1.54103.x86_64
> kmod-knem-1.1.4.90mlnx1-OFED.5.1.2.5.0.1.rhel8u4.x86_64
> librdmacm-54mlnx1-1.54103.x86_64
> opensm-libs-5.9.0.MLNX20210617.c9f2ade-0.1.54103.x86_64
> mlnx-ofa_kernel-devel-5.4-OFED.5.4.1.0.3.1.rhel8u4.x86_64
> dapl-devel-2.1.10.1.mlnx-OFED.4.9.0.1.4.54103.x86_64
> dump_pr-1.0-5.9.0.MLNX20210617.g5dd71ee.54103.x86_64
> mlnxofed-docs-5.4-1.0.3.0.noarch
> opensm-devel-5.9.0.MLNX20210617.c9f2ade-0.1.54103.x86_64
> knem-1.1.4.90mlnx1-OFED.5.1.2.5.0.1.rhel8u4.x86_64
> librdmacm-utils-54mlnx1-1.54103.x86_64
> mlnx-fw-updater-5.4-1.0.3.0.x86_64
> kmod-mlnx-ofa_kernel-5.4-OFED.5.4.1.0.3.1.rhel8u4.x86_64
> libibverbs-utils-54mlnx1-1.54103.x86_64
> ibutils2-2.1.1-0.136.MLNX20210617.g4883fca.54103.x86_64
>
> As a final question, did you selected the option: --add-kernel-support on
> the script? I couldn't find the difference between enabling it or not.
>
> Thank you.
>
> On 5 Aug 2021, at 15:20, Vinícius Ferrão 
> wrote:
>
> Hmmm. Running the mlnx_ofed_install.sh script is a pain. But I got your
> idea. I'll do this test right now and report back. Ideally using the repo
> would guarantee an easy upgrade path between release, but Mellanox is
> lacking on this part.
>
> And yes Edward, I want to use the virtual Infiniband interfaces too.
>
> Thank you.
>
> On 5 Aug 2021, at 10:52, Edward Berger  wrote:
>
> I don't know if you can just remove the gluster-rdma rpm.
>
> I'm using mlnx ofed on some 4.4 ovirt node hosts by installing it via the
> mellanox tar/iso and
> running the mellanox install script after adding the required dependencies
> with --enable-repo,
> which isn't the same as adding a repository and 'dnf install'.  So I would
> try that on a test host.
>
> I use it for the 'virtual infiniband' interfaces that get attached to VMs
> as 'host device passthru'.
>
> I'll note the node versions of gluster are 7.8 (node 4.4.4.0/CentOS8.3)
> and 7.9 (node 4.4.4.1/CentOS8.3).
> unlike your glusterfs version 6.0.x
>
> I'll be trying to install mellanox ofed on node 4.4.7.1 (CentOS 8 stream)
> soon to see how that works out.
>
>
>
> On Wed, Aug 

[ovirt-users] Re: Is there a way to support Mellanox OFED with oVirt/RHV?

2021-08-05 Thread Edward Berger
 I don't know if you can just remove the gluster-rdma rpm.

I'm using mlnx ofed on some 4.4 ovirt node hosts by installing it via the
mellanox tar/iso and
running the mellanox install script after adding the required dependencies
with --enable-repo,
which isn't the same as adding a repository and 'dnf install'.  So I would
try that on a test host.

I use it for the 'virtual infiniband' interfaces that get attached to VMs
as 'host device passthru'.

I'll note the node versions of gluster are 7.8 (node 4.4.4.0/CentOS8.3) and
7.9 (node 4.4.4.1/CentOS8.3).
unlike your glusterfs version 6.0.x

I'll be trying to install mellanox ofed on node 4.4.7.1 (CentOS 8 stream)
soon to see how that works out.



On Wed, Aug 4, 2021 at 10:04 PM Vinícius Ferrão via Users 
wrote:

> Hello,
>
> Is there a way to keep Mellanox OFED and oVirt/RHV playing nice with each
> other?
>
> The real issue is regarding GlusterFS. It seems to be a Mellanox issue,
> but I would like to know if there's something that we can do make both play
> nice on the same machine:
>
> [root@rhvepyc2 ~]# dnf update --nobest
> Updating Subscription Management repositories.
> Last metadata expiration check: 0:14:25 ago on Wed 04 Aug 2021 02:01:11 AM
> -03.
> Dependencies resolved.
>
>  Problem: both package mlnx-ofed-all-user-only-5.4-1.0.3.0.rhel8.4.noarch
> and mlnx-ofed-all-5.4-1.0.3.0.rhel8.4.noarch obsolete glusterfs-rdma
>   - cannot install the best update candidate for package
> glusterfs-rdma-6.0-49.1.el8.x86_64
>   - package ovirt-host-4.4.7-1.el8ev.x86_64 requires glusterfs-rdma, but
> none of the providers can be installed
>   - package mlnx-ofed-all-5.4-1.0.3.0.rhel8.4.noarch obsoletes
> glusterfs-rdma provided by glusterfs-rdma-6.0-49.1.el8.x86_64
>   - package glusterfs-rdma-3.12.2-40.2.el8.x86_64 requires
> glusterfs(x86-64) = 3.12.2-40.2.el8, but none of the providers can be
> installed
>   - package glusterfs-rdma-6.0-15.el8.x86_64 requires glusterfs(x86-64) =
> 6.0-15.el8, but none of the providers can be installed
>   - package glusterfs-rdma-6.0-20.el8.x86_64 requires glusterfs(x86-64) =
> 6.0-20.el8, but none of the providers can be installed
>   - package glusterfs-rdma-6.0-37.el8.x86_64 requires glusterfs(x86-64) =
> 6.0-37.el8, but none of the providers can be installed
>   - package glusterfs-rdma-6.0-37.2.el8.x86_64 requires glusterfs(x86-64)
> = 6.0-37.2.el8, but none of the providers can be installed
>   - cannot install both glusterfs-3.12.2-40.2.el8.x86_64 and
> glusterfs-6.0-49.1.el8.x86_64
>   - cannot install both glusterfs-6.0-15.el8.x86_64 and
> glusterfs-6.0-49.1.el8.x86_64
>   - cannot install both glusterfs-6.0-20.el8.x86_64 and
> glusterfs-6.0-49.1.el8.x86_64
>   - cannot install both glusterfs-6.0-37.el8.x86_64 and
> glusterfs-6.0-49.1.el8.x86_64
>   - cannot install both glusterfs-6.0-37.2.el8.x86_64 and
> glusterfs-6.0-49.1.el8.x86_64
>   - cannot install the best update candidate for package
> ovirt-host-4.4.7-1.el8ev.x86_64
>   - cannot install the best update candidate for package
> glusterfs-6.0-49.1.el8.x86_64
>
> =
>  PackageArchitectureVersion
>Repository
>   Size
>
> =
> Installing dependencies:
>  openvswitchx86_64
> 2.14.1-1.54103mlnx_ofed_5.4-1.0.3.0_base
> 17 M
>  ovirt-openvswitch  noarch  2.11-1.el8ev
> rhv-4-mgmt-agent-for-rhel-8-x86_64-rpms
>   8.7 k
>  replacing  rhv-openvswitch.noarch 1:2.11-7.el8ev
>  unboundx86_64  1.7.3-15.el8
> rhel-8-for-x86_64-appstream-rpms
>  895 k
> Skipping packages with conflicts:
> (add '--best --allowerasing' to command line to force their upgrade):
>  glusterfs  x86_64
> 3.12.2-40.2.el8   rhel-8-for-x86_64-baseos-rpms
> 558 k
>  glusterfs  x86_64  6.0-15.el8
> rhel-8-for-x86_64-baseos-rpms
>   658 k
>  glusterfs  x86_64  6.0-20.el8
> rhel-8-for-x86_64-baseos-rpms
>   659 k
>  glusterfs  x86_64  6.0-37.el8
> rhel-8-for-x86_64-baseos-rpms
>   663 k
>  glusterfs  x86_64  6.0-37.2.el8
> rhel-8-for-x86_64-baseos-rpms
>   662 k
> Skipping packages with broken dependencies:
>  glusterfs-rdma x86_64
> 3.12.2-40.2.el8   rhel-8-for-x86_64-baseos-rpms
>  49 k
>  glusterfs-rdma  

[ovirt-users] Re: Why cannot connect to KVM Libvirtd using oVirt ??

2021-06-21 Thread Edward Berger
oVirt runs as user vdsm@ovirt so security settings prevent other users
including root from seeing it by default.

root should be able to see it as in readonly

 virsh -r list

You can either run the command on hypervisor like this alias

alias virsh='virsh -c
qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf'

 or you can lookup the default vdsm@ovirt password online and then login
with those credentials and see it.

#root account on 'oVirt node' hosts can't connect to ovirt's details
#login as vdsm@ovirt instead
#
# virsh -c qemu:///system
# user: vdsm@ovirt
# pass: shibboleth




On Mon, Jun 21, 2021 at 1:20 PM tommy  wrote:

> The error log is :
>
>
>
> VDSM olvms3 command GetVmsNamesFromExternalProviderVDS failed: Cannot recv
> data: Host key verification failed.: Connection reset by peer
>
>
>
> But if I use the virsh, it can connect.
>
>
>
> [root@olvms1 ~]# virsh -c qemu+ssh://root@192.168.10.175/system
>
> root@192.168.10.175's password:
>
> Welcome to virsh, the virtualization interactive terminal.
>
>
>
> Type:  'help' for help with commands
>
>'quit' to quit
>
>
>
> virsh #
>
> virsh #
>
> virsh # list
>
> Id   Name   State
>
> 
>
>
>
> virsh #
>
> virsh #
>
> virsh # list --all
>
> Id   NameState
>
> 
>
> -1.vm1   shut off
>
>
>
> virsh #
>
>
>
>
>
> Why ??
>
>
>
>
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/SLSQVFOWWGX44PZPIFB4VZKSBW76FOQP/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/N2SB4WKO6BNWGG3HUXEJKCRARWRWMAKA/


[ovirt-users] Re: hosted-engine --vm-start not working

2021-06-21 Thread Edward Berger
I would see this if the engine VM storage was not accessible.
In my case a targetd iscsi server for the hosted storage wouldn't serve it
after rebooting from a power outage.
More specifically, the iscsi host had let LVM startup scan the device,
which prevented targetd from serving it.




On Mon, Jun 21, 2021 at 12:21 PM Harry O  wrote:

> Hi,
> When i run: hosted-engine --vm-start I get this:
> VM exists and is Down, cleaning up and restarting
> VM in WaitForLaunch
>
> But the VM never starts:
> virsh list --all
>  Id   Name   State
> ---
>  -HostedEngine   shut off
>
>
> systemctl status -l ovirt-ha-agent
> ● ovirt-ha-agent.service - oVirt Hosted Engine High Availability
> Monitoring Agent
>Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-agent.service;
> disabled; vendor preset: disabled)
>Active: active (running) since Wed 2021-06-16 13:27:27 CEST; 3min 26s
> ago
>  Main PID: 79702 (ovirt-ha-agent)
> Tasks: 2 (limit: 198090)
>Memory: 28.3M
>CGroup: /system.slice/ovirt-ha-agent.service
>└─79702 /usr/libexec/platform-python
> /usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent
>
> Jun 16 13:27:27 hej1.5ervers.lan systemd[1]: ovirt-ha-agent.service:
> Succeeded.
> Jun 16 13:27:27 hej1.5ervers.lan systemd[1]: Stopped oVirt Hosted Engine
> High Availability Monitoring Agent.
> Jun 16 13:27:27 hej1.5ervers.lan systemd[1]: Started oVirt Hosted Engine
> High Availability Monitoring Agent.
> Jun 16 13:29:42 hej1.5ervers.lan ovirt-ha-agent[79702]: ovirt-ha-agent
> ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine ERROR Engine VM
> stopped on localhost
>
>
>
>
>
> hosted-engine --vm-status
>
>
> --== Host hej1.5ervers.lan (id: 1) status ==--
>
> Host ID: 1
> Host timestamp : 3547
> Score  : 3400
> Engine status  : {"vm": "down", "health": "bad",
> "detail": "Down", "reason": "bad vm status"}
> Hostname   : hej1.5ervers.lan
> Local maintenance  : False
> stopped: False
> crc32  : f35899f8
> conf_on_shared_storage : True
> local_conf_timestamp   : 3547
> Status up-to-date  : True
> Extra metadata (valid at timestamp):
> metadata_parse_version=1
> metadata_feature_version=1
> timestamp=3547 (Wed Jun 16 13:32:12 2021)
> host-id=1
> score=3400
> vm_conf_refresh_time=3547 (Wed Jun 16 13:32:12 2021)
> conf_on_shared_storage=True
> maintenance=False
> state=EngineDown
> stopped=False
>
>
> --== Host hej2.5ervers.lan (id: 2) status ==--
>
> Host ID: 2
> Host timestamp : 94681
> Score  : 0
> Engine status  : {"vm": "down_unexpected", "health":
> "bad", "detail": "Down", "reason": "bad vm status"}
> Hostname   : hej2.5ervers.lan
> Local maintenance  : False
> stopped: False
> crc32  : 40a3f809
> conf_on_shared_storage : True
> local_conf_timestamp   : 94681
> Status up-to-date  : True
> Extra metadata (valid at timestamp):
> metadata_parse_version=1
> metadata_feature_version=1
> timestamp=94681 (Wed Jun 16 13:32:05 2021)
> host-id=2
> score=0
> vm_conf_refresh_time=94681 (Wed Jun 16 13:32:05 2021)
> conf_on_shared_storage=True
> maintenance=False
> state=EngineUnexpectedlyDown
> stopped=False
> timeout=Fri Jan  2 03:23:40 1970
>
>
> --== Host hej3.5ervers.lan (id: 3) status ==--
>
> Host ID: 3
> Host timestamp : 94666
> Score  : 0
> Engine status  : {"vm": "down_unexpected", "health":
> "bad", "detail": "Down", "reason": "bad vm status"}
> Hostname   : hej3.5ervers.lan
> Local maintenance  : False
> stopped: False
> crc32  : a50c2b3e
> conf_on_shared_storage : True
> local_conf_timestamp   : 94666
> Status up-to-date  : True
> Extra metadata (valid at timestamp):
> metadata_parse_version=1
> metadata_feature_version=1
> timestamp=94666 (Wed Jun 16 13:32:09 2021)
> host-id=3
> score=0
> vm_conf_refresh_time=94666 (Wed Jun 16 13:32:09 2021)
> conf_on_shared_storage=True
> maintenance=False
> state=EngineUnexpectedlyDown
> stopped=False
> timeout=Fri Jan  2 03:23:16 1970
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> 

[ovirt-users] Re: How to handle broken NFS storage?

2021-06-05 Thread Edward Berger
I could be mistaken, but I think the issue is that ovirt engine believes
the NFS domain is mandatory for all hypervisor hosts unless you put the
storage domain into 'maintenance' mode.
It will notice its down and start trying to fence the offending hypervisors
which in turn tries to migrate VMs to other hypervisors that also are
marked bad because they can't reach the storage domain either. That's what
I recall once seeing when I thought it was safe to temporarily take down an
ISO NFS domain a few years ago.

On Fri, Jun 4, 2021 at 5:11 AM David White via Users 
wrote:

> I'm trying to figure out how to keep a "broken" NFS mount point from
> causing the entire HCI cluster to crash.
>
> HCI is working beautifully.
> Last night, I finished adding some NFS storage to the cluster - this is
> storage that I don't necessarily need to be HA, and I was hoping to store
> some backups and less-important VMs on, since my Gluster (sssd) storage
> availability is pretty limited.
>
> But as a test, after I got everything setup, I stopped the nfs-server.
> This caused the entire cluster to go down, and several VMs - that are not
> stored on the NFS storage - went belly up.
>
> Once I started the NFS server process again, HCI did what it was supposed
> to do, and was able to automatically recover.
> My concern is that NFS is a single point of failure, and if VMs that don't
> even rely on that storage are affected if the NFS storage goes away, then I
> don't want anything to do with it.
> On the other hand, I'm still struggling to come up with a good way to run
> on-site backups and snapshots without using up more gluster space on my
> (more expensive) sssd storage.
>
> Is there any way to setup NFS storage for a Backup Domain - as well as a
> Data domain (for lesser important VMs) - such that, if the NFS server
> crashed, all of my non-NFS stuff would be unaffected?
>
>
> Sent with ProtonMail  Secure Email.
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/7PEJUNBDBD72TMSPIQFQGHF2ZFNT6UYX/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/D6KDJ7VB2Q7QXJSJ3KYZNLQYPJOFWE6A/


[ovirt-users] Re: Cluster stuck in maintenance - Hosts not upgrading as expected

2021-05-22 Thread Edward Berger
I'm saw something similar on a test cluster on CentOS 8.3.
You can take it out of global maintenance mode by navigating the engine UI
to edit cluster -> scheduling policy and turn off global maintenance there.

Not sure what else is going on.  It wants me to put all three hosts into
maintenance mode which is impossible.


On Sat, May 22, 2021 at 8:36 PM David White via Users 
wrote:

> I have a 3-node hyperconverged cluster with Gluster filesystem running on
> RHEL 8.3 hosts.
>
> It's been stable on oVirt 4.5.
> Today, I just upgraded the Engine to v4.6.
>
> [image: Screenshot from 2021-05-22 20-29-23.png]
>
> I then logged into the oVirt manager, navigated to Compute -> Clusters,
> and clicked on Upgrade.
> The Status of the cluster does have an exclamation mark that says "Upgrade
> Cluster Compatibility Level", but my understanding is, I shouldn't do that
> until all 3 of my hosts have been upgraded.
>
> Looking at active tasks, I see that the first host in my cluster is stuck
> in "Upgrading".
> It's now been like this for 3 hours, without any visible progress.
>
> If I try to launch a VM that is not configured for high availability, the
> VM fails to launch, and I get a message about the cluster being in
> "Maintenance Mode" and that none of the hosts satisfies current scheduling
> restraints.
> How do I
> a) Cancel / clear the upgrade and take the cluster out of "maintenance
> mode"
> b) Properly upgrade the cluster, since clicking the "Upgrade" button
> clearly didn't work?
>
> Thanks,
> David
>
>
> Sent with ProtonMail  Secure Email.
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/4JIRYDSSKBPBJBIIQMRTNGSASBOQIR6I/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CC4J7AGJ7TKSSLKTBRXJN3YOXTPLGKCR/


[ovirt-users] Re: How to create new users other than admin

2021-05-19 Thread Edward Berger
 For specific users local to the ovirt engine
https://ovirt.org/documentation/administration_guide/index.html#sect-Administering_User_Tasks_From_the_commandline
OK for an emergency admin user or perhaps external system user, but this
doesn't scale very well.

But generally you might want to setup LDAP logins with
https://ovirt.org/documentation/administration_guide/index.html#sect-Configuring_an_External_LDAP_Provider
and manage users externally across multiple machines.

On Wed, May 19, 2021 at 5:59 AM  wrote:

> Hello everyone, I am new to ovirt and would like to apologise if this has
> been asked before.
> When I created a cluster of ovirt 4.3, I was presented with the option of
> creating an admin user.
> However, we would like to assign different login credentials for our
> employees with different set of rules.
>
> I was able to view the users menu under the Administration > Users.
> Currently we only have an admin user with internal-authz. When clicking on
> the add button, I only see "internal-authz" and "*" under namespace.
> Clicking on Go button simply shows admin user again.
>
> I created a new role under the Administration > Configure > Roles,
> however, there is no option to add new user anywhere.
>
> Can you please point me to the right steps for adding new users?
>
> Thanks
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/E7GHE4DRMTWWJJYGOQD4B6GPOKIJLVBT/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/Z2JVYBVGNXMJD3ZG35M3KWKIFOI3WTFW/


[ovirt-users] Re: Unable start self hosted engine after accidental shut down

2021-05-18 Thread Edward Berger
With all the other VMs paused, I would guess all the VM disk image storage
is offline or unreachable
from the hypervisor.

login to this hypervisor host. df -kh to see whats mounted

check the fileserving from hosts there.



On Tue, May 18, 2021 at 4:33 PM Eugène Ngontang  wrote:

> Hi,
>
> Our self hosted engine has been accidentally shut down by a teammate and
> now I'm trying hard to get it back up without success.
>
> I've tried the --vm-start command but it says the VM is in WaitForLaunch
> status.
>
> I've set the global maintenance mode but it does nothing.
>
> root@milhouse-main ~]# hosted-engine --vm-start
> VM exists and is down, cleaning up and restarting
> VM in WaitForLaunch
>
> [root@milhouse-main ~]# hosted-engine --set-maintenance --mode=global
> [root@milhouse-main ~]# hosted-engine --vm-status
>
>
> !! Cluster is in GLOBAL MAINTENANCE mode !!
>
>
>
> --== Host milhouse-main.envrmnt.local (id: 1) status ==--
>
> conf_on_shared_storage : True
> Status up-to-date  : False
> Hostname   : milhouse-main.envrmnt.local
> Host ID: 1
> Engine status  : unknown stale-data
> Score  : 3400
> stopped: False
> Local maintenance  : False
> crc32  : 931b2db9
> local_conf_timestamp   : 1642052
> Host timestamp : 1642052
> Extra metadata (valid at timestamp):
>   metadata_parse_version=1
>   metadata_feature_version=1
>   timestamp=1642052 (Tue May 18 19:52:59 2021)
>   host-id=1
>   score=3400
>   vm_conf_refresh_time=1642052 (Tue May 18 19:53:00 2021)
>   conf_on_shared_storage=True
>   maintenance=False
>   state=EngineDown
>   stopped=False
>
>
> !! Cluster is in GLOBAL MAINTENANCE mode !!
>
> You have new mail in /var/spool/mail/root
> [root@milhouse-main ~]# hosted-engine --vm-start
> VM exists and is down, cleaning up and restarting
> VM in WaitForLaunch
>
> [root@milhouse-main ~]#
>
> And when I list all vms, I can see the hosted engine is in the Shut Off 
> status and the managed vms are all paused
>
>
> [root@milhouse-main ~]# virsh -r list --all
> setlocale: No such file or directory
>  IdName   State
> 
>  2 hp_gpu-node11  paused
>  3 fp_gpu-node5   paused
>  4 hp_gpu-node10  paused
>  5 hp_gpu-node7   paused
>  6 cpu-node3  paused
>  7 hp_gpu-node5   paused
>  8 fp_gpu-node1   paused
>  9 fp_gpu-node0   paused
>  10cpu-node1  paused
>  11fp_gpu-node6   paused
>  12hp_gpu-node8   paused
>  13fp_gpu-node10  paused
>  14fp_gpu-node4   paused
>  15fp_gpu-node9   paused
>  16hp_gpu-node4   paused
>  17fp_gpu-node15  paused
>  18fp_gpu-node8   paused
>  19hp_gpu-node0   paused
>  20fp_gpu-node14  paused
>  21fp_gpu-node2   paused
>  22fp_gpu-node11  paused
>  23hp_gpu-node9   paused
>  24cpu-node2  paused
>  25hp_gpu-node1   paused
>  26hp_gpu-node2   paused
>  27fp_gpu-node12  paused
>  28hp_gpu-node3   paused
>  29hp_gpu-node6   paused
>  30infra-vm   paused
>  31cpu-node0  paused
>  32fp_gpu-node3   paused
>  33fp_gpu-node7   paused
>  34fp_gpu-node13  paused
>  35bigip-16.1x-milhouse   paused
>  - HostedEngine   shut off
>
> [root@milhouse-main ~]#
>
>
> I don't want to reboot the host server, cause I could loose all my VMs.
>
> Can someone help here please?
>
> Thanks.
>
> Regards,
> Eugène NG
> --
> LesCDN 
> engont...@lescdn.com
> 
> *Aux hommes il faut un chef, et au*
>
> * chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te
> voit on te juge!*
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZA7FHNC3K7TXF3P47LZP7JNKNO4QCB4M/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe 

[ovirt-users] Re: unable to login cockpit using root after upgrading to 4.4.6

2021-05-18 Thread Edward Berger
I swapped out the /etc/authselect login and system files and It seems to be
that the
updated node 4.6 pam stack is calling /usr/sbin/chkpwd and that fails for
all cockpit users, root and otherwise.

for root
May 18 13:03:02 br014 unix_chkpwd[14186]: check pass; user unknown
May 18 13:03:02 br014 unix_chkpwd[14187]: check pass; user unknown
May 18 13:03:02 br014 unix_chkpwd[14187]: password check failed for user
(root)

for local user account >1000 UID
May 18 13:03:28 br014 unix_chkpwd[14309]: could not obtain user info
(e##)


On Tue, May 18, 2021 at 12:02 PM Edward Berger  wrote:

> /etc/pam.d/cockpit under node 4.4.6 is the same as you posted.
> Something else changed.
>
> #%PAM-1.0
> # this MUST be first in the "auth" stack as it sets PAM_USER
> # user_unknown is definitive, so die instead of ignore to avoid subsequent
> modules mess up the error code
> -auth  [success=done new_authtok_reqd=done user_unknown=die
> default=ignore]   pam_cockpit_cert.so
> auth   required pam_sepermit.so
> auth   substack password-auth
> auth   include  postlogin
> auth   optional pam_ssh_add.so
> accountrequired pam_nologin.so
> accountinclude  password-auth
> password   include  password-auth
> # pam_selinux.so close should be the first session rule
> sessionrequired pam_selinux.so close
> sessionrequired pam_loginuid.so
> # pam_selinux.so open should only be followed by sessions to be executed
> in the user context
> sessionrequired pam_selinux.so open env_params
> sessionoptional pam_keyinit.so force revoke
> sessionoptional pam_ssh_add.so
> sessioninclude  password-auth
> sessioninclude  postlogin
>
>
> On Tue, May 18, 2021 at 11:50 AM Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> On Tue, May 18, 2021 at 4:50 PM Glenn Farmer 
>> wrote:
>>
>>> The current thread is about 4.4.6 - nice that you can login to your
>>> 4.4.5.
>>>
>>
>> The subject of the thread says it all... ;-)
>> My point was to ask if you see differences in /etc/pam.d/cockpit in your
>> 4.4.6, in respect with the version I pasted for my 4.4.5 or if they are the
>> same.
>> I cannot compare as I have not yet 4.4.6 installed
>>
>>
>>> I changed the admin password on the engine - still cannot access the
>>> Cockpit GUI on any of my hosts.
>>>
>>
>> The cockpit gui for the host is accessed through users defined on the
>> hosts, not on engine side. It is not related to the admin engine web admi
>> gui...
>> I think you can configure a normal user on your hypervisor host and see
>> if you can use it to connect to the cockpit gui or if you receive error.
>> Do you need any particular functionality to use the root user?
>>
>> HIH,
>> Gianluca
>>
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/VSM4BLBD36MFNXR5OXS4QWWHHGQXXZIP/
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/QADZ4TFIUNUKCCCBXE7LT6MHFXDNVARG/


[ovirt-users] Re: unable to login cockpit using root after upgrading to 4.4.6

2021-05-18 Thread Edward Berger
/etc/pam.d/cockpit under node 4.4.6 is the same as you posted.
Something else changed.

#%PAM-1.0
# this MUST be first in the "auth" stack as it sets PAM_USER
# user_unknown is definitive, so die instead of ignore to avoid subsequent
modules mess up the error code
-auth  [success=done new_authtok_reqd=done user_unknown=die
default=ignore]   pam_cockpit_cert.so
auth   required pam_sepermit.so
auth   substack password-auth
auth   include  postlogin
auth   optional pam_ssh_add.so
accountrequired pam_nologin.so
accountinclude  password-auth
password   include  password-auth
# pam_selinux.so close should be the first session rule
sessionrequired pam_selinux.so close
sessionrequired pam_loginuid.so
# pam_selinux.so open should only be followed by sessions to be executed in
the user context
sessionrequired pam_selinux.so open env_params
sessionoptional pam_keyinit.so force revoke
sessionoptional pam_ssh_add.so
sessioninclude  password-auth
sessioninclude  postlogin


On Tue, May 18, 2021 at 11:50 AM Gianluca Cecchi 
wrote:

> On Tue, May 18, 2021 at 4:50 PM Glenn Farmer 
> wrote:
>
>> The current thread is about 4.4.6 - nice that you can login to your 4.4.5.
>>
>
> The subject of the thread says it all... ;-)
> My point was to ask if you see differences in /etc/pam.d/cockpit in your
> 4.4.6, in respect with the version I pasted for my 4.4.5 or if they are the
> same.
> I cannot compare as I have not yet 4.4.6 installed
>
>
>> I changed the admin password on the engine - still cannot access the
>> Cockpit GUI on any of my hosts.
>>
>
> The cockpit gui for the host is accessed through users defined on the
> hosts, not on engine side. It is not related to the admin engine web admi
> gui...
> I think you can configure a normal user on your hypervisor host and see if
> you can use it to connect to the cockpit gui or if you receive error.
> Do you need any particular functionality to use the root user?
>
> HIH,
> Gianluca
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/VSM4BLBD36MFNXR5OXS4QWWHHGQXXZIP/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/4ZXGJTICEWBOLFZJ2FLQULS3BZE4CP5G/


[ovirt-users] Re: unable to login cockpit using root after upgrading to 4.4.6

2021-05-18 Thread Edward Berger
I see the same thing on a test cluster.  I presumed it was due to using
sssd and kerberos for local user logins.
Here's an example of what gets written to /var/log/secure when root login
to cockpit fails.
May 18 11:29:07 br014 unix_chkpwd[26429]: check pass; user unknown
May 18 11:29:07 br014 unix_chkpwd[26430]: check pass; user unknown
May 18 11:29:07 br014 unix_chkpwd[26430]: password check failed for user
(root)
May 18 11:29:07 br014 cockpit-session[26427]: pam_unix(cockpit:auth):
authentication failure; logname= uid=993 euid=993 tty= ruser=
rhost=:::128.182.79.36  user=root
May 18 11:29:07 br014 cockpit-session[26427]: pam_succeed_if(cockpit:auth):
requirement "uid >= 1000" not met by user "root"

The uid test is obviously an issue. not sure why check pass seems to always
give user unknown errors. tried putting selinux in permissive same issue.


On Tue, May 18, 2021 at 10:50 AM Glenn Farmer 
wrote:

> The current thread is about 4.4.6 - nice that you can login to your 4.4.5.
>
> I changed the admin password on the engine - still cannot access the
> Cockpit GUI on any of my hosts.
>
> Do I have to reboot them?  Restart Cockpit - tried that - failed.
>
> Cannot access Cockpit on all hosts in a cluster after upgrading to 4.4.6
> really should be considered a bug.
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/VZPGTQUWDUPJWVRHFNUARRSB3EDX7PLX/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BCPXOJ2GKWEEONMQ53775H6RD2FXFOWP/


[ovirt-users] Re: Error while deploying Hyperconverged oVirt 4.3.3(el7) + GlusterFS

2021-05-13 Thread Edward Berger
4.3.10 is the latest version of oVirt 4.3, not sure why you'd want to try
installing an older version.

These types of installer errors are usually caused by either the device
'sdb' is smaller than you're trying to allocate
or
has some previous partition formatting on it (installer presumes a
non-formatted drive, and stops to protect data)
or
the system has lvm or multipathd filtering out the drive /dev/sdb
In the second case usually wipefs can be used to make /dev/sdb clean for
script to work.
for the third case, you may need to edit the /etc/multipathd.conf or
lvm.conf and reboot to make
the device available to the installer.



On Thu, May 13, 2021 at 7:23 AM techbreak--- via Users 
wrote:

> As title, we want to use 3 hosts with hyperconverged solution of oVirt. We
> installed oVirt and Gluster as reported in the guide
> https://www.ovirt.org/documentation/gluster-hyperconverged/chap-Deploying_Hyperconverged.html
> When we try to deploy, we get some errors which we cannot figure out.
>
> ==
> gdeploy creates as configuration rules:
> hc_nodes:
>   hosts:
> virtnodetest-0-0:
>   gluster_infra_volume_groups:
> - vgname: gluster_vg_sdb
>   pvname: /dev/sdb
>   gluster_infra_mount_devices:
> - path: /gluster_bricks/engine
>   lvname: gluster_lv_engine
>   vgname: gluster_vg_sdb
> - path: /gluster_bricks/isostorage
>   lvname: gluster_lv_isostorage
>   vgname: gluster_vg_sdb
> - path: /gluster_bricks/vmstorage
>   lvname: gluster_lv_vmstorage
>   vgname: gluster_vg_sdb
>   gluster_infra_thick_lvs:
> - vgname: gluster_vg_sdb
>   lvname: gluster_lv_engine
>   size: 150G
>   gluster_infra_thinpools:
> - vgname: gluster_vg_sdb
>   thinpoolname: gluster_thinpool_gluster_vg_sdb
>   poolmetadatasize: 16G
>   gluster_infra_lv_logicalvols:
> - vgname: gluster_vg_sdb
>   thinpool: gluster_thinpool_gluster_vg_sdb
>   lvname: gluster_lv_isostorage
>   lvsize: 250G
> - vgname: gluster_vg_sdb
>   thinpool: gluster_thinpool_gluster_vg_sdb
>   lvname: gluster_lv_vmstorage
>   lvsize: 3500G
> virtnodetest-0-1:
>   gluster_infra_volume_groups:
> - vgname: gluster_vg_sdb
>   pvname: /dev/sdb
>   gluster_infra_mount_devices:
> - path: /gluster_bricks/engine
>   lvname: gluster_lv_engine
>   vgname: gluster_vg_sdb
> - path: /gluster_bricks/isostorage
>   lvname: gluster_lv_isostorage
>   vgname: gluster_vg_sdb
> - path: /gluster_bricks/vmstorage
>   lvname: gluster_lv_vmstorage
>   vgname: gluster_vg_sdb
>   gluster_infra_thick_lvs:
> - vgname: gluster_vg_sdb
>   lvname: gluster_lv_engine
>   size: 150G
>   gluster_infra_thinpools:
> - vgname: gluster_vg_sdb
>   thinpoolname: gluster_thinpool_gluster_vg_sdb
>   poolmetadatasize: 16G
>   gluster_infra_lv_logicalvols:
> - vgname: gluster_vg_sdb
>   thinpool: gluster_thinpool_gluster_vg_sdb
>   lvname: gluster_lv_isostorage
>   lvsize: 250G
> - vgname: gluster_vg_sdb
>   thinpool: gluster_thinpool_gluster_vg_sdb
>   lvname: gluster_lv_vmstorage
>   lvsize: 3500G
> virtnodetest-0-2:
>   gluster_infra_volume_groups:
> - vgname: gluster_vg_sdb
>   pvname: /dev/sdb
>   gluster_infra_mount_devices:
> - path: /gluster_bricks/engine
>   lvname: gluster_lv_engine
>   vgname: gluster_vg_sdb
> - path: /gluster_bricks/isostorage
>   lvname: gluster_lv_isostorage
>   vgname: gluster_vg_sdb
> - path: /gluster_bricks/vmstorage
>   lvname: gluster_lv_vmstorage
>   vgname: gluster_vg_sdb
>   gluster_infra_thick_lvs:
> - vgname: gluster_vg_sdb
>   lvname: gluster_lv_engine
>   size: 150G
>   gluster_infra_thinpools:
> - vgname: gluster_vg_sdb
>   thinpoolname: gluster_thinpool_gluster_vg_sdb
>   poolmetadatasize: 16G
>   gluster_infra_lv_logicalvols:
> - vgname: gluster_vg_sdb
>   thinpool: gluster_thinpool_gluster_vg_sdb
>   lvname: gluster_lv_isostorage
>   lvsize: 250G
> - vgname: gluster_vg_sdb
>   thinpool: gluster_thinpool_gluster_vg_sdb
>   lvname: gluster_lv_vmstorage
>   lvsize: 3500G
>   vars:
> gluster_infra_disktype: JBOD
> gluster_set_selinux_labels: true
> gluster_infra_fw_ports:
>   - 2049/tcp
>   - 54321/tcp
>   - 5900/tcp
>   - 5900-6923/tcp
>   - 5666/tcp
>   - 16514/tcp
> gluster_infra_fw_permanent: true
> gluster_infra_fw_state: enabled
> gluster_infra_fw_zone: public
> gluster_infra_fw_services:
>   - 

[ovirt-users] Re: How to update ovirt-sdk

2021-04-20 Thread Edward Berger
You are looking at very old repos.
One normally does something like..


yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm

yum install python-ovirt-engine-sdk4


On Tue, Apr 20, 2021 at 11:46 AM Miguel Garcia 
wrote:

> BTW...
> Already followed instruction as described in
> https://pypi.org/project/ovirt-engine-sdk-python/4.2.4/
>
> https://www.ovirt.org/develop/release-management/features/infra/python-sdk.html
>
> but the problem persists.
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/HYYNFS3PHTXOMZUDVYJ3YJ4NJOZI2COH/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VBRUWPWH7YL7KYYL2ZPYHLR7QXDFY7FG/


[ovirt-users] Re: What do some of the terms mean in the documentation?

2021-03-21 Thread Edward Berger
oVirt node is a dedicated hypervisor imgbased installer distro for oVirt
that handles upgrades all at once with a rollback feature, whereas an
Enterprise Linux Host would do the same thing but you would partition your
disks however you saw fit and manually install RPMs to get the same
functionality as a node-ng host.  No need to have both type of hypervisor
hosts.  The engine is sometimes a VM itself which provides the Web GUI and
databases needed to manage a cluster of virtualization hosts and VMs
therein.


On Sun, Mar 21, 2021 at 10:31 AM  wrote:

> So in the documentation it says that the oVirt Engine is a user interface
> and a REST API endpoint. Ok, that's clear enough.
>
> As far as the oVirt hosts there are two types Enterprise Linux hosts and
> oVirt Nodes. Do the Enterprise Linux hosts run the VMs for my apps or the
> oVirt nodes?
>
> What are their respective roles? Do I need both?
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/C24YO2HVDZYPJ46OEJZJ4YDFN6B5N3SN/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/KD7GTXX3RTXR2MJHHAWDVO5XTW4LTAPB/


[ovirt-users] Re: Which Operating System to choose

2021-03-07 Thread Edward Berger
 If you're content with the current RHEL licensing terms, its a great
choice for now.
Noone can tell you the future with certainty.

If you're just creating a virtualization cluster with external storage, why
not use the node-ng installer iso.
It will be updated as necessary for each new released version of oVirt.
Today it is CentOS8.3 based, but it will easily be changed once oVirt on
Stream is ready.












On Sun, Mar 7, 2021 at 5:27 AM  wrote:

> I want to set up a small cluster consisting of 2 Hypervisor nodes
> (self-hosted engine) with shared storage (SAN, ISCSI).
>
> According to https://www.ovirt.org/download/ the following Operating
> Systems are supported with the latest oVirt version (4.4.4):
> - Red Hat Enterprise Linux 8.3
> - CentOS Linux 8.3
> - CentOS Stream (Tech Preview)
>
> My doubts are:
> - RHEL 8.3 is free to use up tp 16 hosts, but until when? Red Hat can
> decide at anytime to change their subscription program.
> - CentOS Linux is no more, support will stop at the end of 2021.
> - CentOS Stream is in Tech Preview. I don't like running production
> environments on "tech preview / beta" versions.
>
> I would say CentOS 7, it will receive maintenance updates up to 2024, and
> switch to RHEL in 2024 if the free-to-use program is still active.
> Unfortunately, CentOS 7 seems not to be supported.
>
> On what Operating System are you running oVirt 4.4.4 and why? Any feedback
> and advice is welcome. Thanks!
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/2XHHPDCQTEMAFQQNMESEY2KVCLSLFM7A/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HYKCUVNDO37M2EW626JTGSSJXHTLUYRG/


[ovirt-users] Re: ERROR: Installing oVirt Node & Hosted-Engine on one physical server

2021-03-07 Thread Edward Berger
 > Question 1: In General, can i install oVirt Node and hosted-engine on
one physical server?
Yes and single node hyperconverged is suggested for single node deployments.

> Question 2: What domain names should I specify in the DNS server and
which ones IP should I reserve?
You can use any domain name you have ownership of and control the DNS for,
as seen to and from your host and VMs
not localhost.

You want two hostnames that resolve to the same network/netmask, one for
the hypervisor, one for the engine VM.
The installer will create a network bridge for the engine VM off the host's
ethernet which the two will communicate over
and it will be available for any other VMs you deploy later with that
network..

This network must be reachable via your web browser, so it is usually a
public network address,
For updates, installation needs, etc. both host and engine will want to
reach out to the internet.
If you're planning on adding more storage servers, another network as a
private network and hostname that
resolves to it would be suggested, but it isn't necessary in the single
host case.

> Question 3: "Failed to connect to the host via ssh: ssh: connect to host
ovirt-engine-01.local port 22: No route to host" - Who and where is trying
to establish a connection via SSH?
The host will try to ssh to the engine VM and the engine VM will will try
to communicate to the host.
The main accounts are root and vdsm.  I'm not sure of others.





On Sun, Mar 7, 2021 at 2:17 AM  wrote:

> oVirt node 4.4.4
>
> Question 1: In General, can i install oVirt Node and hosted-engine on one
> physical server?
>
> Question 2: What domain names should I specify in the DNS server and which
> ones IP should I reserve?
>
> Question 3: "Failed to connect to the host via ssh: ssh: connect to host
> ovirt-engine-01.local port 22: No route to host" - Who and where is trying
> to establish a connection via SSH?
>
> Can someone reply to questions 1-3 above? Any help will be much
> appreciated.
>
> Thanks for the help,
> Ivan.
>
> Logs:
> ERROR otopi.ovirt_hosted_engine_setup.ansible_utils
> ansible_utils._process_output:109 fatal: [localhost]: FAILED! =>
> {"attempts": 180, "changed": true, "cmd": ["hosted-engine", "--vm-status",
> "--json"], "delta": "0:00:00.565239", "end": "2021-03-03 13:36:54.775239",
> "rc": 0, "start": "2021-03-03 13:36:54.21", "stderr": "",
> "stderr_lines": [], "stdout": "{\"1\": {\"host-id\": 1, \"host-ts\": 16377,
> \"score\": 3400, \"engine-status\": {\"vm\": \"up\", \"health\": \"bad\",
> \"detail\": \"Up\", \"reason\": \"failed liveliness check\"}, \"hostname\":
> \"mng-ovirt-engine-01.local\", \"maintenance\": false, \"stopped\": false,
> \"crc32\": \"2b3ee5d1\", \"conf_on_shared_storage\": true,
> \"local_conf_timestamp\": 16377, \"extra\":
> \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=16377
> (Wed Mar  3 13:36:48
> 2021)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=16377 (Wed Mar  3
> 13:36:48
> 2021)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=
>  False\\n\", \"live-data\": true}, \"global_maintenance\": false}",
> "stdout_lines": ["{\"1\": {\"host-id\": 1, \"host-ts\": 16377, \"score\":
> 3400, \"engine-status\": {\"vm\": \"up\", \"health\": \"bad\", \"detail\":
> \"Up\", \"reason\": \"failed liveliness check\"}, \"hostname\":
> \"mng-ovirt-engine-01.local\", \"maintenance\": false, \"stopped\": false,
> \"crc32\": \"2b3ee5d1\", \"conf_on_shared_storage\": true,
> \"local_conf_timestamp\": 16377, \"extra\":
> \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=16377
> (Wed Mar  3 13:36:48
> 2021)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=16377 (Wed Mar  3
> 13:36:48
> 2021)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\",
> \"live-data\": true}, \"global_maintenance\": false}"]}
>
> ERROR otopi.ovirt_hosted_engine_setup.ansible_utils
> ansible_utils._process_output:109 fatal: [localhost]: FAILED! =>
> {"changed": false, "msg": "Engine VM IP address is  while the engine's
> he_fqdn ovirt-engine-01.local resolves to 10.0.2.250. If you are using
> DHCP, check your DHCP reservation configuration"}
>
> ERROR otopi.ovirt_hosted_engine_setup.ansible_utils
> ansible_utils._process_output:109 fatal: [localhost]: UNREACHABLE! =>
> {"changed": false, "msg": "Failed to connect to the host via ssh: ssh:
> connect to host ovirt-engine-01.local port 22: No route to host",
> "skip_reason": "Host localhost is unreachable", "unreachable": true}
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLNLHUJLKQ4SAJY6UJ4IBC3IIWXLP3WW/
>

[ovirt-users] Re: oVirt 4.2 cluster upgrade

2021-02-26 Thread Edward Berger
The upgrade selection would only upgrade you to the last version of 4.2 if
that is even out there for it to download.
4.2 has been end of life for a long time now.

You need to upgrade the engine itself to at least 4.3.10 to upgrade to 4.4,.
So much has changed internally with 4.2 to 4.3 to 4.4, (4.4 is based on
CentOS8, etc.) that a simple yum
update won't do it.  For that big of a jump you might want to save off the
VM images somewhere external
and redeploy as a new 4.4 cluster and import the images into the new
cluster.


On Fri, Feb 26, 2021 at 6:06 AM Fedele Stabile 
wrote:

> I have a 3 node oVirt 4.2.1 cluster,
> i'm using a self-hosted engine architecture and
> storage-engine is on a glusterfs replica 3
> of the cluster.
> The oldest CPU is SandyBridge family (E5-2609)
> and incidentally I have connectivity problems with IPMI NIC of one node,
> but Hosted Engine HA is enabled and working.
> Is it safe to upgrade to the last oVirt 4.4 without a down of vm running
> on the cluster?
> May I just click on the button
> Upgrade
> that appears on the host page?
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/MLDMLBTKPM4PNJB7KV5M5N4ELIK3AWGR/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BAANZ457K6JD6OIUMUCGVEO5JHI76M7M/


[ovirt-users] 4.3 to 4.4 engine upgrade missing log analyzer tool

2021-02-26 Thread Edward Berger
I have an oVirt 4.3 to 4.4 engine upgrade upcoming, so I decided to start
reading up on the procedure at
https://www.ovirt.org/documentation/upgrade_guide/#SHE_Upgrading_from_4-3

I'm stuck at "4.2 Analyzing the environment" which says to install some RPM
that isn't found
and the closest sounding "ovirt-log-collector" doesn't seem to have the
--live option as used there.

yum install rhv-log-collector-analyzer
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LEQCIUHWHY3RBKBCWSVHCCT6Q3K3UPQO/


[ovirt-users] Re: Building new cluster today - OS recommendations

2021-02-16 Thread Edward Berger
The ovirt-node-ng-installer iso imbased installs will have the dependency
issues worked out when they move it to CentOS8 Stream.
Its the simplest way to go. Its going to be tested as a whole before you
touch it. It version locks a lot of things, but some packages
can be added afterwards with something like
  'yum --enablerepo baseos --enablerepo appstream install packagename', and
you can run most other things you wanted on a VM anyway.

The largest issue I see with complex systems like oVirt and openstack being
installed 'by hand' on base CentOS is all the
inter-dependencies between separate open source projects.

Occasionally someone thinks its a good idea to update a package somewhere
like in  EPEL, or elsewhere in the project's dependency
tree and it breaks some previously working assumptions so the software you
wanted now fails to install or work correctly as
it was tested under different circumstances at a different time.








On Tue, Feb 16, 2021 at 8:39 AM Gervais de Montbrun 
wrote:

> Hi All,
>
> I've been testing with a single server "cluster" running oVirt w/Gluster
> and am about to build my in house cluster using three Dell servers. I was
> planing on putting CentOS 8 on these servers and building oVirt on top.
> With the recent changes to CentOS changing to CentOS Stream, I have
> concerns.
>
> I'm tempted to build my cluster with CentOS 8 (as this is what I tested
> on) and assume that there will be some official word from oVirt as to how
> to proceed come end of year. Any suggestions from folks here? Any one know
> if there is anything out from oVirt crew already around this?
>
> Cheers,
> Gervais
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/6ZPWKPOKCC4MAVNHYJVSGN657BEANAIV/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/AEQMYXIG6LB7PPK22UDFFSSOP2HXADYH/


[ovirt-users] Re: [ANN] oVirt 4.4.5 Fifth Release Candidate is now available for testing

2021-02-15 Thread Edward Berger
I'm seeing a bug with disk type showing up as preallocated in VM portal for
a template disk, when it should be thin-provisioned.
All storage domains are NFS.
I setup a 4.4.5 RC engine with hosts both 4.4.5 RC and 4.4.4 on the admin
portal as 'admin@internal'
I created a small CentOS 7.9 VM on NFS domain vmstore (thin provisioned
storage).
I created a template from said VM, and chose 'QCOW' Disk type at that
stage, default said RAW.
logout of admin portal.
login to vm portal as admin@internal
Create VM button, and create from said template created above with a name.
Continue to this part.
[image: preallocated disk vm-portal.JPG]
Note the wrong disk type displayed.  Trying to continue on fails to create
VM due to 'preallocated not supported by storage domain'.
Since I never asked for 'Preallocated', I don't know why its showing up
here like this.



On Thu, Feb 11, 2021 at 3:41 PM Konstantin Shalygin  wrote:

> Is there any plans to fix [1] and [2] in 4.4? After no feedback (from dec
> 2020) from oVirt team I decide to drop oVirt 4.4 engine, and revert to 4.3.
> Current cinder integration broken broken in 4.4, but marked for
> deprecation only in 4.5 [3]
>
>
> Thanks,
> k
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1904669
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1905113
> [3] https://bugzilla.redhat.com/show_bug.cgi?id=1899453
>
>
> On 11 Feb 2021, at 18:24, Lev Veyde  wrote:
>
> oVirt 4.4.5 Fifth Release Candidate is now available for testing
> The oVirt Project is pleased to announce the availability of oVirt 4.4.5
> Fifth Release Candidate for testing, as of February 11th, 2021.
>
> This update is the fifth in a series of stabilization updates to the 4.4
> series.
> How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1
> Note: Upgrading from 4.4.2 GA or later should not require re-doing these
> steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
> are only required to be done once.
>
> Due to Bug 1837864 
> - Host enter emergency mode after upgrading to latest build
> If you have your root file system on a multipath device on your hosts you
> should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your
> host entering emergency mode.
> In order to prevent this be sure to upgrade oVirt Engine first, then on
> your hosts:
>
>1. Remove the current lvm filter while still on 4.4.1, or in emergency
>mode (if rebooted).
>2. Reboot.
>3. Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5).
>4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in
>place.
>5. Only if not using oVirt Node:
>- run "dracut --force --add multipath” to rebuild initramfs with the
>correct filter configuration
>6. Reboot.
>
> Documentation
>
>- If you want to try oVirt as quickly as possible, follow the
>instructions on the Download  page.
>- For complete installation, administration, and usage instructions,
>see the oVirt Documentation .
>- For upgrading from a previous version, see the oVirt Upgrade Guide
>.
>- For a general overview of oVirt, see About oVirt
>.
>
> Important notes before you try it
> Please note this is a pre-release build.
> The oVirt Project makes no guarantees as to its suitability or usefulness.
> This pre-release must not be used in production.
> Installation instructions
> For installation instructions and additional information please refer to:
> https://ovirt.org/documentation/
>
> This release is available now on x86_64 architecture for:
> * Red Hat Enterprise Linux 8.3 or newer
> * CentOS Linux (or similar) 8.3 or newer
>
> This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
> for:
> * Red Hat Enterprise Linux 8.3 or newer
> * CentOS Linux (or similar) 8.3 or newer
> * oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only)
>
> See the release notes [1] for installation instructions and a list of new
> features and bugs fixed.
>
> Notes:
> - oVirt Appliance is already available for CentOS Linux 8
> - oVirt Node NG is already available for CentOS Linux 8
> - We found a few issues while testing on CentOS Stream so we are still
> basing oVirt 4.4.5 Node and Appliance on CentOS Linux.
>
> Additional Resources:
> * Read more about the oVirt 4.4.5 release highlights:
> http://www.ovirt.org/release/4.4.5/
> * Get more oVirt project updates on Twitter: https://twitter.com/ovirt
> * Check out the latest project news on the oVirt blog:
> http://www.ovirt.org/blog/
>
>
> [1] http://www.ovirt.org/release/4.4.5/
> [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/
>
> --
>
> Lev Veyde
>
> Senior Software Engineer, RHCE | RHCVA | MCITP
> Red Hat Israel
>
> 
>
> l...@redhat.com | 

[ovirt-users] Re: strange behavior of fresh ovirt setup..

2021-02-13 Thread Edward Berger
I recall some earlier ovirt users list postings with similar issues with
the NAS.
One thought they solved it by changing the ovirt storage domain config NFS
version to a lower version instead of whatever it was defaulting to.
The other was blaming the NAS software ZFS underlying the NFS causing some
issues.

CentOS mdraid disks that are xfs formatted and exported NFS to oVirt seems
to work fine in the instances I'm aware of.

On Thu, Feb 11, 2021 at 2:51 AM  wrote:

> Justas Stankūnas 
>
> Wed, Feb 10, 11:29 PM (10 hours ago)
>
> to infra-owner
> Hi,
>
> so i have just installed oVirt on 4 nodes (oVirt node 4.4.4) with a hosted
> engine. For storage I have TrueNAS dedicated machine for NFS.
> hosts are all identical Lenovo thinkcentre m92 with (Intel(R) Core(TM)
> i5-3470T CPU @ 2.90GHz and 16 GB of RAM).
> everything is connected with a physical managed switch over 1Gbps each.
>
> everything is setup without any additional configuration. There is only a
> single vm (hosted engine). but hosts are constant errors and warnings being
> presented and I am lost even from where to start looking.
>
>
>
> Time|   Message
> Feb 10, 2021, 11:07:38 PM| |VM HostedEngine is not responding.
> Feb 10, 2021, 10:46:48 PM| |VM HostedEngine is not responding.
> Feb 10, 2021, 10:46:35 PM| |Failed to connect Host host1.local to Storage
> Pool Home
> Feb 10, 2021, 10:46:35 PM| |Host host1.local cannot access the Storage
> Domain(s) ovirt_manager_nfs attached to the Data Center Home. Setting Host
> state to Non-Operational.
> Feb 10, 2021, 10:46:35 PM| |Host host1.local reports about one of the
> Active Storage Domains as Problematic.
> Feb 10, 2021, 10:46:17 PM| |VDSM host1.local command Get Host Statistics
> failed: Connection timeout for host 'host1.local', last response arrived
> 17522 ms ago.
> Feb 10, 2021, 10:36:27 PM| |VM HostedEngine is not responding.
> Feb 10, 2021, 10:25:54 PM| |VM HostedEngine is not responding.
> Feb 10, 2021, 10:05:03 PM| |VM HostedEngine is not responding.
> Feb 10, 2021, 10:04:54 PM| |Failed to connect Host host1.local to Storage
> Pool Home
> Feb 10, 2021, 10:04:54 PM| |Host host1.local cannot access the Storage
> Domain(s) ovirt_manager_nfs attached to the Data Center Home. Setting Host
> state to Non-Operational.
> Feb 10, 2021, 10:04:54 PM| |Host host1.local reports about one of the
> Active Storage Domains as Problematic.
> Feb 10, 2021, 10:04:33 PM| |Invalid status on Data Center Home. Setting
> Data Center status to Non Responsive (On host host3.local, Error: Network
> error during communication with the Host.).
> Feb 10, 2021, 10:04:33 PM| |VDSM host3.local command SpmStatusVDS failed:
> Connection timeout for host 'host3.local', last response arrived 2184 ms
> ago.
> Feb 10, 2021, 9:54:41 PM| |VM HostedEngine is not responding.
> Feb 10, 2021, 9:33:47 PM| |VM HostedEngine is not responding.
> Feb 10, 2021, 9:25:52 PM| |VDSM host2.local command Get Host Statistics
> failed: Message timeout which can be caused by communication issues
> Feb 10, 2021, 9:23:22 PM| |VM HostedEngine is not responding.
> Feb 10, 2021, 9:12:51 PM| |Failed to connect Host host1.local to Storage
> Pool Home
> Feb 10, 2021, 9:12:51 PM| |Host host1.local cannot access the Storage
> Domain(s) nfs_vms attached to the Data Center Home. Setting Host state to
> Non-Operational.
> Feb 10, 2021, 9:12:51 PM| |Host host1.local reports about one of the
> Active Storage Domains as Problematic.
> Feb 10, 2021, 9:12:44 PM| |Invalid status on Data Center Home. Setting
> Data Center status to Non Responsive (On host host3.local, Error: Network
> error during communication with the Host.).
> Feb 10, 2021, 9:12:44 PM| |VDSM host1.local command Get Host Statistics
> failed: Connection timeout for host 'host1.local', last response arrived
> 16869 ms ago.
> Feb 10, 2021, 9:12:44 PM| |VDSM host3.local command SpmStatusVDS failed:
> Connection timeout for host 'host3.local', last response arrived 16931 ms
> ago.
> Feb 10, 2021, 9:02:51 PM| |VM HostedEngine is not responding.
> Feb 10, 2021, 8:52:25 PM| |VM HostedEngine is not responding.
> Feb 10, 2021, 8:31:34 PM| |VM HostedEngine is not responding.
> Feb 10, 2021, 8:21:06 PM| |VM HostedEngine is not responding.
> Feb 10, 2021, 8:20:36 PM| |Invalid status on Data Center Home. Setting
> Data Center status to Non Responsive (On host host3.local, Error: Network
> error during communication with the Host.).
> Feb 10, 2021, 8:20:36 PM| |VDSM host3.local command Get Host Statistics
> failed: Connection timeout for host 'host3.local', last response arrived
> 23346 ms ago.
> Feb 10, 2021, 8:10:11 PM| |Failed to connect Host host1.local to Storage
> Pool Home
> Feb 10, 2021, 8:10:11 PM| |Host host1.local cannot access the Storage
> Domain(s) ovirt_manager_nfs, nfs_vms, iso attached to the Data Center Home.
> Setting Host state to Non-Operational.
> Feb 10, 2021, 8:10:10 PM| |Host host1.local reports about one of the
> Active Storage Domains as Problematic.
> Feb 10, 2021, 8:10:01 PM| 

[ovirt-users] Re: Single Node Hyperconverged - Failing Gluster Setup

2021-02-09 Thread Edward Berger
If the disk was previously used, you may need to 'wipefs -a /dev/sdb' to
clean out any previous partitioning, etc.

If the installer can't create the gluster PV, it is often because the drive
needs to be added to the multipath blacklist.

lsblk to find the ID and add it to the /etc/multipath.conf blacklist

[root@ovirtnode2 ~]#lsblk /dev/sdb

NAME  MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb8:16 0 200G 0 disk
 -> 3678da6e715b018f01f1abdb887594aae 253:2 0 200G 0 mpath

edit /etc/multipath.conf and append the disk wwid to multipath.conf blacklist

blacklist {

wwid 3678da6e715b018f01f1abdb887594aae }
then restart the multipathd service

service multipathd restart



On Tue, Feb 9, 2021 at 2:19 PM Strahil Nikolov via Users 
wrote:

> What is the output of 'lsblk -t' ?
>
> Best Regards,
> Strahil Nikolov
>
> Ovirt newbie here - using v 4.4.4
>
> Have been trying for days to get this installed on my HP DL380p G6. I have
> 2 disk 170GB Raid 0 for OS and 6 x 330GB disk Raid 5 for Gluster. DNS all
> set up (that took some working out), but I just can't fathom out whats
> (not) happening here. Block size is returned as 512.
>
> I've had some help on Reddit where I've been told that Ovirt is seeing my
> single local disk ass an multipath device, which it is not/??!  I think I
> removed the flag, but it still fails here.
>
> So, Gluster install fails quite early through, though it carries on
> creating all the volumes (with default settings) but then gives me the
> 'Deployment Failed' message :( Here is where it fails
>
> Any help gratefully received!
>
> TASK [fail]
> 
>
> task path: /usr/share/cockpit/ovirt-dashboard/ansible/hc_wizard.yml:62
>
> skipping: [ovirt-gluster.whichelo.com] => (item=[{'cmd': 'blockdev
> --getss /dev/sdb | grep -Po -q "512" && echo true || echo false\n',
> 'stdout': 'true', 'stderr': '', 'rc': 0, 'start': '2021-02-07
> 13:21:10.237701', 'end': '2021-02-07 13:21:10.243111', 'delta':
> '0:00:00.005410', 'changed': True, 'invocation': {'module_args':
> {'_raw_params': 'blockdev --getss /dev/sdb | grep -Po -q "512" && echo true
> || echo false\n', '_uses_shell': True, 'warn': True, 'stdin_add_newline':
> True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable':
> None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines':
> ['true'], 'stderr_lines': [], 'failed': False, 'item': {'vgname':
> 'gluster_vg_sdb', 'pvname': '/dev/sdb'}, 'ansible_loop_var': 'item'},
> {'cmd': 'blockdev --getss /dev/sdb | grep -Po -q "4096" && echo true ||
> echo false\n', 'stdout': 'false', 'stderr': '', 'rc': 0, 'start':
> '2021-02-07 13:21:14.760897', 'end': '2021-02-07 13:21:14.766395', 'delta':
> '0:00:00.005498', 'chang
> ed': True, 'invocation': {'module_args': {'_raw_params': 'blockdev --getss
> /dev/sdb | grep -Po -q "4096" && echo true || echo false\n', '_uses_shell':
> True, 'warn': True, 'stdin_add_newline': True, 'strip_empty_ends': True,
> 'argv': None, 'chdir': None, 'executable': None, 'creates': None,
> 'removes': None, 'stdin': None}}, 'stdout_lines': ['false'],
> 'stderr_lines': [], 'failed': False, 'item': {'vgname': 'gluster_vg_sdb',
> 'pvname': '/dev/sdb'}, 'ansible_loop_var': 'item'}]) =>
> {"ansible_loop_var": "item", "changed": false, "item":
> [{"ansible_loop_var": "item", "changed": true, "cmd": "blockdev --getss
> /dev/sdb | grep -Po -q \"512\" && echo true || echo false\n", "delta":
> "0:00:00.005410", "end": "2021-02-07 13:21:10.243111", "failed": false,
> "invocation": {"module_args": {"_raw_params": "blockdev --getss /dev/sdb |
> grep -Po -q \"512\" && echo true || echo false\n", "_uses_shell": true,
> "argv": null, "chdir": null, "creates": null, "executable": null,
> "removes": null, "stdin": null, "
> stdin_add_newline": true, "strip_empty_ends": true, "warn": true}},
> "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "rc": 0,
> "start": "2021-02-07 13:21:10.237701", "stderr": "", "stderr_lines": [],
> "stdout": "true", "stdout_lines": ["true"]}, {"ansible_loop_var": "item",
> "changed": true, "cm
>
> d": "blockdev --getss /dev/sdb | grep -Po -q \"4096\" && echo true || echo
> false\n", "delta": "0:00:00.005498", "end": "2021-02-07 13:21:14.766395",
> "failed": false, "invocation": {"module_args": {"_raw_params": "blockdev
> --getss /dev/sdb | grep -Po -q \"4096\" && echo true || echo false\n",
> "_uses_shell": true, "argv": null, "chdir": null, "creates": null,
> "executable": null, "removes": null, "stdin": null, "stdin_add_newline":
> true, "strip_empty_ends": true, "warn": true}}, "item": {"pvname":
> "/dev/sdb", "vgname": "gluster_vg_sdb"}, "rc": 0, "start": "2021-02-07
> 13:21:14.760897", "stderr": "", "stderr_lines": [], "stdout": "false",
> "stdout_lines": ["false"]}], "skip_reason": "Conditional result was False"}
>
>
> hc_wizard.yml excerpt:
>
> - name: Check if block device is 4KN
>   shell: >
> blockdev --getss {{ item.pvname }} | grep 

[ovirt-users] Re: HostedEngine VM Paused after power failure

2021-02-09 Thread Edward Berger
If the enginve VM is in a paused state, ssh into host where its paused and
try

virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf
resume HostedEngine


On Tue, Feb 9, 2021 at 2:15 PM Ian Easter  wrote:

> Hello Users,
>
> We have an oVirt (4.4) environment that had 2 hosts in the cluster.  We
> suffered from a power failure that caused the servers to be offline for
> some time.  Once restored, one of the hosts from the cluster lost its OS
> raid and is not accessible.
>
> The other server has the HostedEngine vm on it but in a paused state.  I
> have tried to manually start the vm with the hosted-engine CLI tool but it
> indicates that HostedEngine is running on another host.
>
> Is there any manual intervention I can accomplish here to start the
> HostedEngine on the second, active host server?
>
> *Thank you,*
> *Ian Easter*
> *DevOps Engineer*
> *TelVue Support*
> https://www.telvue.com/support/
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/VFE52Q3ILURK2C6L3XN4TEL76NRTLIWD/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/P7JLB6QZNTMZ5LU57KG4Q6M3FCEZDNT5/


[ovirt-users] Re: Problems Installing host on brand new 4.4 cluster

2021-01-19 Thread Edward Berger
It seems to be failing on adding the ovirtmgmt bridge to the interface
defined on the host as part of the
host addition installation process.   I had this issue during a
hosted-engine install when ovirtmgmt was on a tagged
port which was already configured with a chosen name not supported by the
ovirt installation scripts.
After I reconfigured the network config with the correct style name, I was
able to install hosted engine on CentOS8.
Check if ovirtmgmt exists on the host you're trying to add to your ovirt
installation, note which interface should
have that network bridge added.

In my case, the network port needed to be configured in the form of eno1.##
where ## was the vlan number, replace en01 with correct ethernet interface.
Similar issues could happen if you're using a bond named something other
than what the installation scripts expect (bond.#).

Its a little confusing, but there are actually two different places to
'edit' a host's config from engine.
The obvious one is 'edit host' but the feature to set networks per device
or configure host devices for passthrough
is under the other (almost hidden) area of the engine web UI.

Under the engine UI, try to set the non-op host into 'maintenance' and then
click on the hostname in compute:hosts page, and then networks tab
and then 'setup host networks' and to try to add it by dragging it from the
right hand side of the page to the correct interface on the left
and saving it.  If you're defining any other logical networks you'll need
to get to that page per host  to set them up.



On Tue, Jan 19, 2021 at 5:46 PM David Johnson 
wrote:

> Hi all,
>
> I am standing up a brand new cluster on new hardware.
>
> The ovirt controller is installed and appears to be running fine.
>
> When I attempt to add the new host, I get the flag that says "Non
> Operational", and the exclamation mark with the message "Host has no
> default route".
>
> I have confirmed that I have bidirectional ssh connections between the
> controller and the new host.
>
> Selinux is disabled.
>
> Firewall is disabled.
>
> I can get to the host console via the link in the GUI Compute|Hosts page.
>
> This looks like a common symptom of a host of problems, but there is
> nothing to readily indicate what the actual problem is.
>
> In the ovirt-engine log, I found this entry: "Host 'ovirt-host-03' is set
> to Non-Operational, it is missing the following networks: 'ovirtmgmt'"
>
> This seems self-explanatory, but I see no way to add the missing network
> to the host.
>
> Thank you in advance for your help
>
> Regards,
> David Johnson
> * *
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/CUOZ4YSV5ISVEYHI22Y2SPA5PBOH6LXL/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/W2PNZB5FOAYJGCRB3Q5J3Y6F4OKZEVJR/


[ovirt-users] Re: The he_fqdn proposed for the engine VM resolves on this host - error?

2020-12-28 Thread Edward Berger
The hosted engine fqdn and IP address should be separate from the
hypervisor host's IP address but on the same network so it can communicate
to the host through a bridged interface that the installer creates on the
hypervisor host for the hosted engine VM.

On Mon, Dec 28, 2020 at 3:14 PM lejeczek via Users  wrote:

> hi chaps,
>
> a newcomer here. I use cockpit to deploy hosted engine and I
> get this error/warning message:
>
> "The he_fqdn proposed for the engine VM resolves on this host"
>
> I should mention that if I remove the IP to which FQDN
> resolves off that iface(plain eth no vlans) then I get this:
>
> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false,
> "msg": "The selected network interface is not valid"}
>
> All these errors seem bit too cryptic to me.
> Could you shed bit light on what is oVirt saying exactly and
> why it's not happy that way?
>
> many thanks, L.
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/LTAYI3GYI2ANRKWMME62BJ4DY2XEGFJM/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/OS2UHZ4V56L46M4Q3RFDA3YDA5LXVZVJ/


[ovirt-users] Re: error for gluster-ansible-roles is not installed on Host. To continue deployment, please install gluster-ansible-roles on Host and try again.

2020-11-23 Thread Edward Berger
the hyperconverged gluster RPMs aren't installed by default on Enterprise
Linux with the cockpit RPM but are installed on the oVirt node-ng install.
The quick install neglects this, so look at
https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/#Red_Hat_Enterprise_Linux_hosts_SHE_cockpit_deploy.
You're probably missing this...

yum install cockpit-ovirt-dashboard vdsm-gluster ovirt-host


On Mon, Nov 23, 2020 at 10:12 AM  wrote:

> Hello,
>
> Why have I this message : gluster-ansible-roles is not installed on Host.
> To continue deployment, please install gluster-ansible-roles on Host and
> try again. When I try create glusterfs with Hyperconverged - Configure
> Gluster storage and oVirt hosted engine ?
>
> Could you help me ?
>
> Best regards!
>
> Anne Garcia
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/A5ATHCYUZUFIOXMIJ3EJVDHSRYSI44RF/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/Y6KOULHMT3DU7HXUZ37YTL57UN4N3IUC/


[ovirt-users] Re: [ANN] oVirt 4.4.3 Fifth Release Candidate is now available for testing

2020-10-20 Thread Edward Berger
On the HostedEngineLocal VM

[root@testvirt ~]# yum repolist enabled
repo id
repo name
AppStream
CentOS-8 - AppStream
BaseOS
 CentOS-8 - Base
PowerTools
 CentOS-8 - PowerTools
extras
 CentOS-8 - Extras
ovirt-4.4
Latest oVirt 4.4 Release
ovirt-4.4-advanced-virtualization
Advanced Virtualization packages for x86_64
ovirt-4.4-centos-gluster7
CentOS-8 - Gluster 7
ovirt-4.4-centos-opstools
CentOS-8 - OpsTools - collectd
ovirt-4.4-centos-ovirt44
 CentOS-8 - oVirt 4.4
ovirt-4.4-copr:copr.fedorainfracloud.org:mdbarroso:ovsdbapp
Copr repo for ovsdbapp owned by mdbarroso
ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.22
Copr repo for NetworkManager-1.22 owned by networkmanager
ovirt-4.4-copr:copr.fedorainfracloud.org:nmstate:nmstate-0.2
 Copr repo for nmstate-stable owned by nmstate
ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible
 Copr repo for gluster-ansible owned by sac
ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection
 Copr repo for EL8_collection owned by sbonazzo
ovirt-4.4-epel
 Extra Packages for Enterprise Linux 8 - x86_64
ovirt-4.4-pre
oVirt 4.4 Pre-Release
ovirt-4.4-virtio-win-latest
virtio-win builds roughly matching what will be shipped in upcoming RHEL


and on the Hypervisor

[root@n001 ~]# yum repolist enabled
repo id
repo name
AppStream
CentOS-8 - AppStream
BaseOS
 CentOS-8 - Base
PowerTools
 CentOS-8 - PowerTools
extras
 CentOS-8 - Extras
ovirt-4.4
Latest oVirt 4.4 Release
ovirt-4.4-advanced-virtualization
Advanced Virtualization packages for x86_64
ovirt-4.4-centos-gluster7
CentOS-8 - Gluster 7
ovirt-4.4-centos-opstools
CentOS-8 - OpsTools - collectd
ovirt-4.4-centos-ovirt44
 CentOS-8 - oVirt 4.4
ovirt-4.4-copr:copr.fedorainfracloud.org:mdbarroso:ovsdbapp
Copr repo for ovsdbapp owned by mdbarroso
ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.22
Copr repo for NetworkManager-1.22 owned by networkmanager
ovirt-4.4-copr:copr.fedorainfracloud.org:nmstate:nmstate-0.2
 Copr repo for nmstate-stable owned by nmstate
ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible
 Copr repo for gluster-ansible owned by sac
ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection
 Copr repo for EL8_collection owned by sbonazzo
ovirt-4.4-epel
 Extra Packages for Enterprise Linux 8 - x86_64
ovirt-4.4-pre
oVirt 4.4 Pre-Release
ovirt-4.4-virtio-win-latest
virtio-win builds roughly matching what will be shipped in upcoming RHEL



On Tue, Oct 20, 2020 at 4:54 AM Sandro Bonazzola 
wrote:

>
>
> Il giorno lun 19 ott 2020 alle ore 19:03 Edward Berger <
> edwber...@gmail.com> ha scritto:
>
>> with those packages installed I was able to run the single node
>> hyperconverged wizard,
>> but it fails during deploy "Hosted Engine Deployment" with
>> [ INFO ] TASK [ovirt.ovirt.engine_setup : Update setup packages]
>> [ INFO ] skipping: [localhost]
>> [ INFO ] TASK [ovirt.ovirt.engine_setup : Update all packages]
>> [ ERROR ] fatal: [localhost -> testvirt.bil.psc.edu]: FAILED! =>
>> {"changed": false, "failures": [], "msg": "Depsolve Error occured: \n
>> Problem: cannot install the best update candidate for package
>> ovirt-engine-metrics-1.4.1.1-1.el8.noarch\n - nothing provides
>> rhel-system-roles >= 1.0-19 needed by
>> ovirt-engine-metrics-1.4.2-1.el8.noarch", "rc": 1, "results": []}
>> [ INFO ] TASK [ovirt.ovirt.engine_setup : Clean temporary files]
>> [ INFO ] changed: [localhost -> testvirt.bil.psc.edu]
>>
>> I can 'virsh console HostedEngineLocal' and yum update there says
>> [root@testvirt ~]# yum update
>> Last metadata expiration check: 0:03:58 ago on Mon 19 Oct 2020 12:52:54
>> PM EDT.
>> Error:
>>  Problem: cannot install the best update candidate for package
>> ovirt-engine-metrics-1.4.1.1-1.el8.noarch
>>   - nothing provides rhel-system-roles >= 1.0-19 needed by
>> ovirt-engine-metrics-1.4.2-1.el8.noarch
>> (try to add '--skip-broken' to skip uninstallable packages or '--nobest'
>> to use not only best candidate packages)
>>
>>
>>
> can you please provide output of: "yum repolist enabled" ?
> thanks
>
>
>
>
>
>>
>>
>>
>> On Mon, Oct 19, 2020 at 12:25 PM Edward Berger 
>> wrote:
>>
>>> I'm installing 4.4.3-pre on CentOS8.2 and it seems the glusterfs-server
>>> and gluster-ansible-roles RPMs aren't installed,
>>> with the ovirt-cockpit which pulls other dependencies.
>>>
>>> This caused the cockpit hyperconverged installer to fail. It mentions
>>> the roles rpm but not the glusterfs
>>> with the role installed, failure comes up when it tries to setup the
>>> firewall for non-existing glusterfs-server.
>>>

[ovirt-users] Re: [ANN] oVirt 4.4.3 Fifth Release Candidate is now available for testing

2020-10-19 Thread Edward Berger
with those packages installed I was able to run the single node
hyperconverged wizard,
but it fails during deploy "Hosted Engine Deployment" with
[ INFO ] TASK [ovirt.ovirt.engine_setup : Update setup packages]
[ INFO ] skipping: [localhost]
[ INFO ] TASK [ovirt.ovirt.engine_setup : Update all packages]
[ ERROR ] fatal: [localhost -> testvirt.bil.psc.edu]: FAILED! =>
{"changed": false, "failures": [], "msg": "Depsolve Error occured: \n
Problem: cannot install the best update candidate for package
ovirt-engine-metrics-1.4.1.1-1.el8.noarch\n - nothing provides
rhel-system-roles >= 1.0-19 needed by
ovirt-engine-metrics-1.4.2-1.el8.noarch", "rc": 1, "results": []}
[ INFO ] TASK [ovirt.ovirt.engine_setup : Clean temporary files]
[ INFO ] changed: [localhost -> testvirt.bil.psc.edu]

I can 'virsh console HostedEngineLocal' and yum update there says
[root@testvirt ~]# yum update
Last metadata expiration check: 0:03:58 ago on Mon 19 Oct 2020 12:52:54 PM
EDT.
Error:
 Problem: cannot install the best update candidate for package
ovirt-engine-metrics-1.4.1.1-1.el8.noarch
  - nothing provides rhel-system-roles >= 1.0-19 needed by
ovirt-engine-metrics-1.4.2-1.el8.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to
use not only best candidate packages)





On Mon, Oct 19, 2020 at 12:25 PM Edward Berger  wrote:

> I'm installing 4.4.3-pre on CentOS8.2 and it seems the glusterfs-server
> and gluster-ansible-roles RPMs aren't installed,
> with the ovirt-cockpit which pulls other dependencies.
>
> This caused the cockpit hyperconverged installer to fail. It mentions the
> roles rpm but not the glusterfs
> with the role installed, failure comes up when it tries to setup the
> firewall for non-existing glusterfs-server.
>
> It is similarly missing on 4.4.2-release.
> (the quick installation instructions are missing this or its a bug)
>
>
> On Mon, Oct 19, 2020 at 4:31 AM Lev Veyde  wrote:
>
>> oVirt 4.4.3 Fifth Release Candidate is now available for testing
>>
>> The oVirt Project is pleased to announce the availability of oVirt 4.4.3
>> Fifth Release Candidate for testing, as of October 16th, 2020.
>>
>> This update is the third in a series of stabilization updates to the 4.4
>> series.
>> How to prevent hosts entering emergency mode after upgrade from oVirt
>> 4.4.1
>>
>> Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if
>> already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only
>> required to be done once.
>>
>> Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
>> Host enter emergency mode after upgrading to latest build
>>
>> If you have your root file system on a multipath device on your hosts you
>> should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your
>> host entering emergency mode.
>>
>> In order to prevent this be sure to upgrade oVirt Engine first, then on
>> your hosts:
>>
>>1.
>>
>>Remove the current lvm filter while still on 4.4.1, or in emergency
>>mode (if rebooted).
>>2.
>>
>>Reboot.
>>3.
>>
>>Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3).
>>4.
>>
>>Run vdsm-tool config-lvm-filter to confirm there is a new filter in
>>place.
>>5.
>>
>>Only if not using oVirt Node:
>>- run "dracut --force --add multipath” to rebuild initramfs with the
>>correct filter configuration
>>6.
>>
>>Reboot.
>>
>> Documentation
>>
>>-
>>
>>If you want to try oVirt as quickly as possible, follow the
>>instructions on the Download <https://ovirt.org/download/> page.
>>-
>>
>>For complete installation, administration, and usage instructions,
>>see the oVirt Documentation <https://ovirt.org/documentation/>.
>>-
>>
>>For upgrading from a previous version, see the oVirt Upgrade Guide
>><https://ovirt.org/documentation/upgrade_guide/>.
>>-
>>
>>For a general overview of oVirt, see About oVirt
>><https://ovirt.org/community/about.html>.
>>
>> Important notes before you try it
>>
>> Please note this is a pre-release build.
>>
>> The oVirt Project makes no guarantees as to its suitability or usefulness.
>>
>> This pre-release must not be used in production.
>> Installation instructions
>>
>> For installation instructions and additional information please refer to:
>>
>> 

[ovirt-users] Re: [ANN] oVirt 4.4.3 Fifth Release Candidate is now available for testing

2020-10-19 Thread Edward Berger
 I'm installing 4.4.3-pre on CentOS8.2 and it seems the glusterfs-server
and gluster-ansible-roles RPMs aren't installed,
with the ovirt-cockpit which pulls other dependencies.

This caused the cockpit hyperconverged installer to fail. It mentions the
roles rpm but not the glusterfs
with the role installed, failure comes up when it tries to setup the
firewall for non-existing glusterfs-server.

It is similarly missing on 4.4.2-release.
(the quick installation instructions are missing this or its a bug)


On Mon, Oct 19, 2020 at 4:31 AM Lev Veyde  wrote:

> oVirt 4.4.3 Fifth Release Candidate is now available for testing
>
> The oVirt Project is pleased to announce the availability of oVirt 4.4.3
> Fifth Release Candidate for testing, as of October 16th, 2020.
>
> This update is the third in a series of stabilization updates to the 4.4
> series.
> How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1
>
> Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if
> already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only
> required to be done once.
>
> Due to Bug 1837864  -
> Host enter emergency mode after upgrading to latest build
>
> If you have your root file system on a multipath device on your hosts you
> should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your
> host entering emergency mode.
>
> In order to prevent this be sure to upgrade oVirt Engine first, then on
> your hosts:
>
>1.
>
>Remove the current lvm filter while still on 4.4.1, or in emergency
>mode (if rebooted).
>2.
>
>Reboot.
>3.
>
>Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3).
>4.
>
>Run vdsm-tool config-lvm-filter to confirm there is a new filter in
>place.
>5.
>
>Only if not using oVirt Node:
>- run "dracut --force --add multipath” to rebuild initramfs with the
>correct filter configuration
>6.
>
>Reboot.
>
> Documentation
>
>-
>
>If you want to try oVirt as quickly as possible, follow the
>instructions on the Download  page.
>-
>
>For complete installation, administration, and usage instructions, see
>the oVirt Documentation .
>-
>
>For upgrading from a previous version, see the oVirt Upgrade Guide
>.
>-
>
>For a general overview of oVirt, see About oVirt
>.
>
> Important notes before you try it
>
> Please note this is a pre-release build.
>
> The oVirt Project makes no guarantees as to its suitability or usefulness.
>
> This pre-release must not be used in production.
> Installation instructions
>
> For installation instructions and additional information please refer to:
>
> https://ovirt.org/documentation/
>
> This release is available now on x86_64 architecture for:
>
> * Red Hat Enterprise Linux 8.2 or newer
>
> * CentOS Linux (or similar) 8.2 or newer
>
> This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
> for:
>
> * Red Hat Enterprise Linux 8.2 or newer
>
> * CentOS Linux (or similar) 8.2 or newer
>
> * oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)
>
> See the release notes [1] for installation instructions and a list of new
> features and bugs fixed.
>
> Notes:
>
> - oVirt Appliance is already available for CentOS Linux 8
>
> - oVirt Node NG is already available for CentOS Linux 8
>
> Additional Resources:
>
> * Read more about the oVirt 4.4.3 release highlights:
> http://www.ovirt.org/release/4.4.3/
>
> * Get more oVirt project updates on Twitter: https://twitter.com/ovirt
>
> * Check out the latest project news on the oVirt blog:
> http://www.ovirt.org/blog/
>
>
> [1] http://www.ovirt.org/release/4.4.3/
>
> [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/
>
> --
>
> Lev Veyde
>
> Senior Software Engineer, RHCE | RHCVA | MCITP
>
> Red Hat Israel
>
> 
>
> l...@redhat.com | lve...@redhat.com
> 
> TRIED. TESTED. TRUSTED. 
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/3CRWW4EMTGHRVGGJM6EY4DUEEM6QJKBI/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 

[ovirt-users] Re: 20+ Fresh Installs Failing in 20+ days [newbie & frustrated]

2020-10-12 Thread Edward Berger
for installation time failures of a hosted engine system, look in
/var/log/ovirt-hosted-engine-setup

On Mon, Oct 12, 2020 at 7:50 AM  wrote:

> What logs are required?
>
>
>
> Yours Sincerely,
>
>
>
> *Henni *
>
>
>
> *From:* Edward Berger 
> *Sent:* Monday, 12 October 2020 19:40
> *To:* i...@worldhostess.com
> *Cc:* users 
> *Subject:* [ovirt-users] Re: 20+ Fresh Installs Failing in 20+ days
> [newbie & frustrated]
>
>
>
> As an ovirt user my first reaction reading your message was
>
> "that is a ridiculously small system to be trying ovirt self hosted engine
> on."
>
>
>
> My minimum recommendation is 48GB of RAM dual xeon, since the hosted
> ovirt-engine installation by default
>
> wants 16GB/4vCPU.  I would use a basic KVM/virt-manager install there
> instead.
>
>
>
> You'll have to provide logs to get more help, but I think you're trying to
> do the wrong thing given the hardware spec.
>
>
>
>
>
> On Mon, Oct 12, 2020 at 12:04 AM  wrote:
>
> I have no idea if it is Hardware or Software. It *crashed* every time
> after it starts with the storage setup
>
>
>
> *Error* in ovirt-hosted-engine-setup-ansilble-setup-final_clean [*FAILED*]
> DESTROYED LOCAL STORAGE-POOL
>
>
>
> *HTTPS* --- “certificate invalid”
>
>
>
> The system is very unstable and impossible to do anything remotely ONLY
> accessible on local terminal.
>
>
>
> This is my hardware
>
> SuperMicro X11SSF-M
>
> Intel Xeon E3-1230
>
> 16 GB ECC RAM
>
> 2 x 1 TB Micron 1300 SSD
>
> Key Features
>
> *X11SSM-F specifications*
>
> Single socket H4 (LGA 1151) supports Intel® Xeon® processor E3-1200 v6/v5,
> Intel® 7th/6th Gen. Core™ i3 series,
>
> Intel® Celeron® and Intel® Pentium®
>
> Intel® C236 chipset
>
> Up to 64GB Unbuffered ECC UDIMM DDR4 2400MHz; 4 DIMM slots
>
> Expansion slots:
>
> 1 PCI-E 3.0 x8 (in x16),
>
> 1 PCI-E 3.0 x8,
>
> 2 PCI-E 3.0 x4 (in x8)
>
> Dual GbE LAN with Intel® i210-AT
>
> 8 SATA3 (6Gbps) via C236;
>
> RAID 0, 1, 5, 10
>
> I/O: 1 VGA, 2 COM, 2 SuperDOM, and TPM header
>
> 5 USB 3.0 (2 rear, 2 via header(s), 1 Type A), 6 USB 2.0 (2 rear, 4 via
> header(s))
>
> Integrated IPMI 2.0 and KVM with Dedicated LAN
>
>
>
> Yours Sincerely,
>
>
>
> *Henni *
>
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/J25ZA7AHLUPOGUQORS5IY6FHPHS6SVGI/
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/35R5Y3WVZP5G7T5VTGMQHEBVS3DHWW4U/


[ovirt-users] Re: 20+ Fresh Installs Failing in 20+ days [newbie & frustrated]

2020-10-12 Thread Edward Berger
As an ovirt user my first reaction reading your message was
"that is a ridiculously small system to be trying ovirt self hosted engine
on."

My minimum recommendation is 48GB of RAM dual xeon, since the hosted
ovirt-engine installation by default
wants 16GB/4vCPU.  I would use a basic KVM/virt-manager install there
instead.

You'll have to provide logs to get more help, but I think you're trying to
do the wrong thing given the hardware spec.


On Mon, Oct 12, 2020 at 12:04 AM  wrote:

> I have no idea if it is Hardware or Software. It *crashed* every time
> after it starts with the storage setup
>
>
>
> *Error* in ovirt-hosted-engine-setup-ansilble-setup-final_clean [*FAILED*]
> DESTROYED LOCAL STORAGE-POOL
>
>
>
> *HTTPS* --- “certificate invalid”
>
>
>
> The system is very unstable and impossible to do anything remotely ONLY
> accessible on local terminal.
>
>
>
> This is my hardware
>
> SuperMicro X11SSF-M
>
> Intel Xeon E3-1230
>
> 16 GB ECC RAM
>
> 2 x 1 TB Micron 1300 SSD
>
> Key Features
>
> *X11SSM-F specifications*
>
> Single socket H4 (LGA 1151) supports Intel® Xeon® processor E3-1200 v6/v5,
> Intel® 7th/6th Gen. Core™ i3 series,
>
> Intel® Celeron® and Intel® Pentium®
>
> Intel® C236 chipset
>
> Up to 64GB Unbuffered ECC UDIMM DDR4 2400MHz; 4 DIMM slots
>
> Expansion slots:
>
> 1 PCI-E 3.0 x8 (in x16),
>
> 1 PCI-E 3.0 x8,
>
> 2 PCI-E 3.0 x4 (in x8)
>
> Dual GbE LAN with Intel® i210-AT
>
> 8 SATA3 (6Gbps) via C236;
>
> RAID 0, 1, 5, 10
>
> I/O: 1 VGA, 2 COM, 2 SuperDOM, and TPM header
>
> 5 USB 3.0 (2 rear, 2 via header(s), 1 Type A), 6 USB 2.0 (2 rear, 4 via
> header(s))
>
> Integrated IPMI 2.0 and KVM with Dedicated LAN
>
>
>
> Yours Sincerely,
>
>
>
> *Henni *
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/J25ZA7AHLUPOGUQORS5IY6FHPHS6SVGI/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/4QMSVR2IG3YRGWLXGJHFMLCWK7QBNMNA/


[ovirt-users] Re: Upgrade oVirt Host from 4.4.0 to 4.4.2 fails

2020-10-02 Thread Edward Berger
For oVirt nodes upgrading from 4.4.0 to 4.4.2 you must remove the LVM
filter before the node upgrade produces a proper booting host.
Its in the upgrade release notes as a known issue.
https://www.ovirt.org/release/4.4.2/




On Fri, Oct 2, 2020 at 1:39 PM Erez Zarum  wrote:

> Hey,
> Bunch of hosts installed from oVirt Node Image, i have upgraded the
> self-hosted Engine successfully.
> I have ran Check Upgrade on one of the hosts and it was entitled for an
> upgrade.
> I use the UI to let it Upgrade, after multiple retries it always fails on
> "Prepare NGN host for upgrade."
> so i chose another host as a test.
> I have set the Host into Maintenance and let all the VMs migrate
> successfully.
> made sure i do have the latest 4.4.2 repo (it was 4.4.0) yum install
> https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
> And issued "dnf upgrade"
> Installing:
>  ovirt-openvswitch
>  replacing  openvswitch.x86_64 2.11.1-5.el8
>  ovirt-openvswitch-ovn
>  replacing  ovn.x86_64 2.11.1-5.el8
>  ovirt-openvswitch-ovn-host
>  replacing  ovn-host.x86_64 2.11.1-5.el8
>  ovirt-python-openvswitch
>  replacing  python3-openvswitch.x86_64 2.11.1-5.el8
> Upgrading:
>  ovirt-node-ng-image-update-placeholder
> Installing dependencies:
>  openvswitch2.11
>  ovirt-openvswitch-ovn-common
>  ovn2.11
>  ovn2.11-host
>  python3-openvswitch2.11
> Installing weak dependencies:
>  network-scripts-openvswitch
>  network-scripts-openvswitch2.11
>
> It was very quick, but nothing else happened, I did try to reboot the host
> but I still see the host as oVirt 4.4.0 and as expected it still says that
> an update is available.
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WL67T6DNFNS3QOZ2ZHK75JXTCWHIECFD/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/OWLNJI2Z2YAZK2WA6EWUF7BHUNEFJHOW/


[ovirt-users] Re: Populating ISO storage domain

2020-09-26 Thread Edward Berger
If its in an NFS folder, make sure the ownership is vdsm:kvm (36:36)


On Sat, Sep 26, 2020 at 2:57 PM matthew.st...@fujitsu.com <
matthew.st...@fujitsu.com> wrote:

> I’ve created and ISO storage domain, and placed ISO’s in the export path
> do not show up under Storage > Storage Domains > iso > images; nor as
> available images which creating a new VM.
>
>
>
> Haven’t located method get them noticed.   There is a greyed out ‘scan
> disk’ option.
>
>
>
> What is the proper method to install ISO images.
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/M6QYBMNT43MTWXGKDNHDY3BOPSVMLXTP/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/A766PAM32VYWCVNXSCJ5XVNUXFZSM2MT/


[ovirt-users] Re: VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").

2020-09-19 Thread Edward Berger
I've had situations where the engine UI wouldn't update for
shutdown/startups of VMs which were resolved after ssh-ing into the engine
VM and running systemctl restart ovirt-engine.service.  running
engine-setup was also used on occasion and cleared out old tasks.

On Fri, Sep 18, 2020 at 1:26 AM Gilboa Davara  wrote:

> Hello all (and happy new year),
>
> (Note: Also reported as
> https://bugzilla.redhat.com/show_bug.cgi?id=1880251)
>
> Self hosted engine, single node, NFS.
> Attempted to install CentOS over an existing Fedora VM with one host
> device (USB printer).
> Reboot failed, trying to boot from a non-existent CDROM.
> Tried shutting the VM down, failed.
> Tried powering off the VM, failed.
> Dropped cluster to global maintenance, reboot host + engine (was
> planning to upgrade it anyhow...), VM still stuck.
>
> When trying to power off the VM, the following message can be found
> the in engine.log:
> 2020-09-18 07:58:51,439+03 INFO
> [org.ovirt.engine.core.bll.StopVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-42)
> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Running command: StopVmCommand
> internal: false. Entities affected :  ID:
> b411e573-bcda-4689-b61f-1811c6f03ad5 Type: VMAction group STOP_VM with
> role type USER
> 2020-09-18 07:58:51,441+03 WARN
> [org.ovirt.engine.core.bll.StopVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-42)
> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Strange, according to the
> status 'RebootInProgress' virtual machine
> 'b411e573-bcda-4689-b61f-1811c6f03ad5' should be running in a host but
> it isn't.
> 2020-09-18 07:58:51,594+03 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-42)
> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] EVENT_ID:
> USER_FAILED_STOP_VM(56), Failed to power off VM kids-home-srv (Host:
> , User: gilboa@internal-authz).
>
> My question is simple: Pending a solution to the bug, can I somehow
> drop the state of the VM? It's currently holding a sizable disk image
> and a USB device I need (printer).
>
> As it's my private VM cluster, I have no problem dropping the site
> completely for maintenance.
>
> Thanks,
>
> Gilboa
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/CD536K6HHE5JX7QY2DA6LYNTFABLYR2K/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/QS7WZSPUL26GQUJFLNZXCAGD4PJJSG2B/


[ovirt-users] Re: New oVirt Install - Host Engine Deployment Fails

2020-09-14 Thread Edward Berger
What is the CPU?  I'm asking because you said it was old servers, and at
some point oVirt started filtering out old CPU types which were no longer
supported under windows.   There was also the case where if a certain bios
option wasn't enabled (AES?) a westmere(supported) reported as an older
model(unsupported).


On Mon, Sep 14, 2020 at 12:20 PM  wrote:

> I am attempting a new oVirt install. I have two nodes installed (with
> oVirt Node 4.4). I have NFS shared storage for the hosted engine.
> Both nodes are Dell quad core Xeon CPUs with 32GB of RAM. Both have been
> hypervisors before, XCP-NG and Proxmox. However I'm very interested to
> learn oVirt now.
>
> The hosted engine deployment (through cockpit) fails during the "Finish"
> stage.
> I do see the initial files created on the NFS storage.
>
> [ INFO ] TASK [ovirt.hosted_engine_setup : Convert CPU model name]
> [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes an
> option with an undefined variable. The error was: 'dict object' has no
> attribute ''\n\nThe error appears to be in
> '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml':
> line 105, column 16, but may\nbe elsewhere in the file depending on the
> exact syntax problem.\n\nThe offending line appears to be:\n\n# - debug:
> var=server_cpu_dict\n ^ here\n\nThere appears to be both 'k=v' shorthand
> syntax and YAML in this task. Only one syntax may be used.\n"}
>
> 2020-09-13 17:39:56,507+ ERROR ansible failed {
> "ansible_host": "localhost",
> "ansible_playbook":
> "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml",
> "ansible_result": {
> "_ansible_no_log": false,
> "msg": "The task includes an option with an undefined variable.
> The error was: 'dict object' has no attribute ''
> \n\nThe error appears to be in
> '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_targ
> et_hosted_engine_vm.yml': line 105, column 16, but may\nbe elsewhere in
> the file depending on the exact syntax problem.\
> n\nThe offending line appears to be:\n\n#  - debug: var=server_cpu_dict\n
>  ^ here\n\nThere appears to be bo
> th 'k=v' shorthand syntax and YAML in this task. Only one syntax may be
> used.\n"
> },
> "ansible_task": "Convert CPU model name",
> "ansible_type": "task",
> "status": "FAILED",
> "task_duration": 1
> }
>
> I can see the host engine is created and running locally on the node.
> I can event SSH into the HostedEngineLocal instance.
>
> [root@ovirt-node01]# virsh --readonly list
>  Id   NameState
> ---
>  1HostedEngineLocal   running
>
>
> Looking at the "Convert CPU model name" task:
>
> https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/blob/master/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml
>
> set_fact:
>   cluster_cpu_model: "{{ server_cpu_dict[cluster_cpu.type] }}"
>
> server_cpu_dict is good, I can find that in the logs, cluster_cpu is
> undefined.
> But this is normal correct? The Cluster CPU type is "undefined" until the
> first host is added to the cluster.
> The error makes it seems that server_cpu_dict and not cluster_cpu.type is
> the problem.
> I'm not sure this is really the problem, but that is the only  undefined
> variable I can find.
>
> Any advice or recommendation is appreciated
> -Thanks in advance
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives:


[ovirt-users] Re: Newbie question on network

2020-09-14 Thread Edward Berger
For others having issues with VM network routing...

virbr0 is usually installed by default on centos, etc. to facilitate
containers networking via NAT.
If I'm not planning on running any containers I usually yum remove the
associated packages,
and a reboot to make sure networking is OK.

Sometimes the ipv4 autoconfig stuff also gets in the way of desired routing,
and I add NOZEROCONF=yes to /etc/sysconfig/network to disable it.

When I've seen the !X in traceroutes it has usually been a firewall config
issue on the remote host I'm tracing to.



On Mon, Sep 14, 2020 at 11:50 AM Valerio Luccio 
wrote:

> Thanks to all that gave me hints/suggestions, especially to Edward that
> pointed me to the right setup page.
>
> I was able to set up correctly my internal switch network, but I'm still
> having issues with the virtual network that connects to the university
> backbone. The route on the VM is setup just like on the host and the
> engine. I also tested traceroute and found out something puzzling:
>
>1. traceroute on the host and the engine for any node on the
>university network returns the answer in milliseconds.
>2. traceroute on the VM for a node on my internal switch returns the
>answer in milliseconds with the flag.
>3. traceroute on the VM for the host or the engine returns answer
>after more than 10 seconds with the flag !X
>4. traceroute on the VM for other hosts on the network returns the
>flag !H (host not reachable).
>
> According to the traceroute man pages the !X flag indicates "communication
> administratively prohibited". I temporarily turned off the firewall on the
> host and the engine and that removed the !X flag from 3, but did not speed
> it up and did not solve 4.
>
> Anyone have any clue what I should try next ?
>
> Thanks in advance,
> --
> As a result of Coronavirus-related precautions, NYU and the Center for
> Brain Imaging operations will be managed remotely until further notice.
> All telephone calls and e-mail correspondence are being monitored remotely
> during our normal business hours of 9am-5pm, Monday through Friday.
>
> For MRI scanner-related emergency, please contact: Keith Sanzenbach at
> keith.sanzenb...@nyu.edu and/or Pablo Velasco at pablo.vela...@nyu.edu
> For computer/hardware/software emergency, please contact: Valerio Luccio
> at valerio.luc...@nyu.edu
> For TMS/EEG-related emergency, please contact: Chrysa Papadaniil at
> chr...@nyu.edu
> For CBI-related administrative emergency, please contact: Jennifer Mangan
> at jennifer.man...@nyu.edu
>
> Valerio Luccio (212) 998-8736
> Center for Brain Imaging 4 Washington Place, Room 158
> New York University New York, NY 10003
>
> "In an open world, who needs windows or gates ?"
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives:


[ovirt-users] Re: "Add NFS storage domain", "status": "FAILED",

2020-09-10 Thread Edward Berger
It would seem your host can't resolve the ip address for the server FQDN
listed for the NFS server.
You should fix the DNS problem or try mounting via ip address once you're
sure that it is reachable from the server.


On Thu, Sep 10, 2020 at 12:33 PM  wrote:

> MainProcess|jsonrpc/4::DEBUG::2020-09-10
> 18:14:39,299::commands::211::root::(execCmd) /usr/bin/taskset --cpu-list
> 0-7 /usr/bin/mount -t nfs -o soft,nosharecache,timeo=100,retrans=3,nolock
> storage.world.co.za:/export/nfs/data
> /rhev/data-center/mnt/storage.world.co.za:_export_nfs_data (cwd None)
> MainProcess|jsonrpc/4::DEBUG::2020-09-10
> 18:14:39,310::commands::224::root::(execCmd) FAILED:  = b'mount.nfs:
> Failed to resolve server storage.world.co.za: Name or service not
> known\n';  = 32
> MainProcess|jsonrpc/4::ERROR::2020-09-10
> 18:14:39,310::supervdsm_server::97::SuperVdsm.ServerCallback::(wrapper)
> Error in mount
> Traceback (most recent call last):
>   File "/usr/lib/python3.6/site-packages/vdsm/supervdsm_server.py", line
> 95, in wrapper
> res = func(*args, **kwargs)
>   File "/usr/lib/python3.6/site-packages/vdsm/supervdsm_server.py", line
> 133, in mount
> cgroup=cgroup)
>   File "/usr/lib/python3.6/site-packages/vdsm/storage/mount.py", line 280,
> in _mount
> _runcmd(cmd)
>   File "/usr/lib/python3.6/site-packages/vdsm/storage/mount.py", line 308,
> in _runcmd
> raise MountError(cmd, rc, out, err)
> vdsm.storage.mount.MountError: Command ['/usr/bin/mount', '-t', 'nfs',
> '-o', 'soft,nosharecache,timeo=100,retrans=3,nolock', 
> 'storage.world.co.za:/export/nfs/data',
> '/rhev/data-center/mnt/storage.world.co.za:_export_nfs_data'] failed with
> rc=32 out=b'' err=b'mount.nfs: Failed to resolve server
> storage.world.co.za: Name or service not known\n'
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/4B45SKR2TO26EPXPOVPC4RT6RJXDM7UQ/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives:


[ovirt-users] Re: Newbie question on network

2020-09-10 Thread Edward Berger
The usual process to add another network bridge is to configure a new
cluster logical network in the engine,
then configure specific network interfaces on all hypervisors through the
engine's "configure host networks".







On Thu, Sep 10, 2020 at 11:43 AM Valerio Luccio 
wrote:

> That was my first thought, so I tried to set up manually the default route
> and netmask on the VM to match the engine's, but it didn't solve the
> problem.
>
> Another network question: I have a second network card on the host that is
> connected to an internal switch, how do I add a bridge for that card to be
> used by the VMs ? I created a secondary bridge on the host and then I tried
> to play with the network options on the oVirt portal, but I couldn't figure
> out to associate the new bridge with an new network. Before anyone thinks
> that the two issues are related, I did this after failing to solve the
> first issue.
>
> On 9/10/20 8:00 AM, Edward Berger wrote:
>
> It sounds like you don't have a proper default route on the VM or the
> netmask is set incorrectly,
> which can cause a bad route.
>
> Look at differences between the engine's network config (presuming it can
> reach outside the hypervisor host)
> and the VM's config.   The VM should have the same subnet, netmask and
> default gateway as the engine VM,
> if its connected to ovirtmgmt.
>
> "ip a" "ip r" "traceroute" and "ping" are the usual commands to check
> network connections.
>
>
>
>
> On Thu, Sep 10, 2020 at 6:29 AM  wrote:
>
>> I apologize for asking what is probably a very basic question.
>>
>> I installed and created a self-hosted engine using cockpit on a server. I
>> can reach the self-hosted engine from anywhere within my network.
>>
>> I then created a new VM selecting the default ovirtmgmt for the network.
>> The VM does not seem to connect to the network via the bridge. I the used
>> the console to manually configured the network card and I have connectivity
>> between the VM, the engine and the server, but not beyond. What am I doing
>> wrong ? Can someone point to a good documentation page on the subject ?
>>
>> Thanks in advance,
>> Valerio
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_privacy-2Dpolicy.html=DwMFaQ=slrrB7dE8n7gBJbeO0g-IQ=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY=09a69sjdPT4FnBs3SqcX_DdQWZ4bl9fBgaX-ncTrSLY=FkCDYQbRRKw0YQpvSYfeiiVvAwXj5RhU9WtVkK04TuM=>
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_community_about_community-2Dguidelines_=DwMFaQ=slrrB7dE8n7gBJbeO0g-IQ=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY=09a69sjdPT4FnBs3SqcX_DdQWZ4bl9fBgaX-ncTrSLY=F3bb60_z8-7_2gSPhwfklz-rVUmXJiokypfqBR8CF4M=>
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/IFXOOU4DVR66DWEUCR66CJ2LQFUFCN55/
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ovirt.org_archives_list_users-40ovirt.org_message_IFXOOU4DVR66DWEUCR66CJ2LQFUFCN55_=DwMFaQ=slrrB7dE8n7gBJbeO0g-IQ=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY=09a69sjdPT4FnBs3SqcX_DdQWZ4bl9fBgaX-ncTrSLY=MerUtEwXMg4sXTJtJTMg2r-0bdlzNIOolYwCmfEFF1U=>
>>
>
> --
> As a result of Coronavirus-related precautions, NYU and the Center for
> Brain Imaging operations will be managed remotely until further notice.
> All telephone calls and e-mail correspondence are being monitored remotely
> during our normal business hours of 9am-5pm, Monday through Friday.
>
> For MRI scanner-related emergency, please contact: Keith Sanzenbach at
> keith.sanzenb...@nyu.edu and/or Pablo Velasco at pablo.vela...@nyu.edu
> For computer/hardware/software emergency, please contact: Valerio Luccio
> at valerio.luc...@nyu.edu
> For TMS/EEG-related emergency, please contact: Chrysa Papadaniil at
> chr...@nyu.edu
> For CBI-related administrative emergency, please contact: Jennifer Mangan
> at jennifer.man...@nyu.edu
>
> Valerio Luccio (212) 998-8736
> Center for Brain Imaging 4 Washington Place, Room 158
> New York University New York, NY 10003
>
> "In an open world, who needs windows or gates ?"
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives:


[ovirt-users] Re: Newbie question on network

2020-09-10 Thread Edward Berger
It sounds like you don't have a proper default route on the VM or the
netmask is set incorrectly,
which can cause a bad route.

Look at differences between the engine's network config (presuming it can
reach outside the hypervisor host)
and the VM's config.   The VM should have the same subnet, netmask and
default gateway as the engine VM,
if its connected to ovirtmgmt.

"ip a" "ip r" "traceroute" and "ping" are the usual commands to check
network connections.




On Thu, Sep 10, 2020 at 6:29 AM  wrote:

> I apologize for asking what is probably a very basic question.
>
> I installed and created a self-hosted engine using cockpit on a server. I
> can reach the self-hosted engine from anywhere within my network.
>
> I then created a new VM selecting the default ovirtmgmt for the network.
> The VM does not seem to connect to the network via the bridge. I the used
> the console to manually configured the network card and I have connectivity
> between the VM, the engine and the server, but not beyond. What am I doing
> wrong ? Can someone point to a good documentation page on the subject ?
>
> Thanks in advance,
> Valerio
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/IFXOOU4DVR66DWEUCR66CJ2LQFUFCN55/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/DXQXOBFM7ZRY7D2KLQAKUTEK63DOZUD3/


[ovirt-users] Re: General Design question for oVirt set up between locations

2020-08-04 Thread Edward Berger
If I'm not mistaken manageiq is the suggested solution to manage multiple
ovirt clusters with their own engines.

On Tue, Aug 4, 2020 at 2:45 PM Holger Petrick 
wrote:

> Hello,
>
> I'm looking to deploy oVirt for a company which has locations in different
> countries.
> As I know and also set up in my test environment, the oVirt Engine is the
> central place to manage different Data Center in a central place.
> But how to manage a location when the network connection between a Data
> Center and oVirt Engine is down?
>
> Is it possible to set up on each location a hosted engine and connect also
> the "local" engine / hosts to a "Central" Engine?
> What is the recommendation to deploy oVirt on multiple location?
>
> Thank you.
> Holger
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/BXIN2N64RE6G6MXTNCGN6IPU4SNPDXUC/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NI2ZTN567DM6TXNSRYO34UEDXNS6JVX2/


[ovirt-users] Re: oVirt Hyperconverged question

2020-08-04 Thread Edward Berger
Yes.  You can add compute only nodes to a hyperconverged cluster to use the
same storage.


On Tue, Aug 4, 2020 at 7:02 AM Benedetto Vassallo <
benedetto.vassa...@unipa.it> wrote:

> Hi all,
> I am planning to build a 3 nodes hyperconverged system with oVirt, but I
> have a question.
> After having the system up and running with 3 nodes (compute and storage),
> if I need some extra compute power can I add some other "compute" (with no
> storage) nodes as glusterfs clients to enhance the total compute power of
> the cluster and using the actual storage?
> Thank you and Best Regards.
> --
> Benedetto Vassallo
> Responsabile U.O. Sviluppo e manutenzione dei sistemi
> Sistema Informativo di Ateneo
> Università degli studi di Palermo
>
> Phone: +3909123860056
> Fax: +3909123860880
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/23PVOVF3TP3ESEUROB466VGEKCULGMNI/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2MTS4RBV2HNEUODQT7FLA3NBZBBNZUOX/


[ovirt-users] Re: 4.4rc issue with attaching logical network to ib0

2020-08-04 Thread Edward Berger
I submitted a bug https://bugzilla.redhat.com/show_bug.cgi?id=1865855
Thanks for your help.

On Tue, Aug 4, 2020 at 2:43 AM Ales Musil  wrote:

> To follow up also on the mailing list.
> The infiniband is currently unsupported in nmstate which makes any attempt
> to configure it past 4.4 to fail.
>
> I will try to think about a possible workaround.
> Can you please create a bug
> <https://bugzilla.redhat.com/enter_bug.cgi?product=vdsm>?
>
> Thank you.
> Best regards,
> Ales
>
> On Mon, Aug 3, 2020 at 10:58 AM Ales Musil  wrote:
>
>>
>>
>> On Fri, Jul 31, 2020 at 4:14 PM Edward Berger 
>> wrote:
>>
>>> I'm trying to add a logical network to an omnipath (which appears as an
>>> infinband ib0 under centos kernel driver) and the attempt errors out, under
>>> 4.4RC. This used to work under 4.3 on the same hardware.
>>>
>>> 'Unexpected failure of libnm when running the mainloop: run execution'},
>>> code = -32603
>>>
>>> I want to use ib0 for network file systems and VM migrations.
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/R6XMGK5O47476ARX4HLTNFINZBZZ3AQY/
>>>
>>
>> Hi,
>>
>> can you please provide a supervdsm.log from the corresponding host?
>>
>> Thank you.
>> Best regards,
>> Ales
>>
>> --
>>
>> Ales Musil
>>
>> Software Engineer - RHV Network
>>
>> Red Hat EMEA <https://www.redhat.com>
>>
>> amu...@redhat.comIM: amusil
>> <https://red.ht/sig>
>>
>
>
> --
>
> Ales Musil
>
> Software Engineer - RHV Network
>
> Red Hat EMEA <https://www.redhat.com>
>
> amu...@redhat.comIM: amusil
> <https://red.ht/sig>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XWIMK2QFQAHDUCHTXVLZUNIQBFEOHWV3/


[ovirt-users] Re: oVirt 4.4.1 HCI single server deployment failed nested-kvm

2020-07-30 Thread Edward Berger
the 4.4.1 72310 node-ng iso has a broken installer.  It failed to find my
regular ethernet interfaces and gave the no networks error.
The 4.4.2-rc seems to be working fine hosted-engine installer wise, to an
nfs mount for the engine VM storage.  I didn't try the gluster wizard.

On Thu, Jul 30, 2020 at 10:30 AM wodel youchi 
wrote:

> Hi,
>
> This is not my first time, I have installed ovirt, ovirt-hci, rhv and
> rhv-hci on top of a kvm host many times to test some functionality or to
> test a new version til this latest version of ovirt 4.4.1
>
> On my first test there was a problem with HCI deployment the gluster part.
>
> Now that part works with the new ovirt-node version but not the vm manager
> deployment part.
>
> Regards.
>
> Le jeu. 30 juil. 2020 14:56, Strahil Nikolov via Users 
> a écrit :
>
>> I've run  KVM  VMs  ontop  oVirt Guest.  Are  you sure that the Nested
>> Virtualization is your problem  ?
>> Best Regards,
>> Strahil Nikolov
>>
>> На 29 юли 2020 г. 23:33:48 GMT+03:00, tho...@hoberg.net написа:
>> >I tried using nested virtualization, too, a couple of weeks ago.
>> >
>> >I was using a 3 node HCI CentOS 7.8 cluster and I got pretty far.
>> >Configuring KVM to work with nested page tables isn't all that well
>> >documented but I got there, I even installed some host extensions, that
>> >seem requried.
>> >
>> >Even the actual nesting, that is a VM run inside a VM did work, the
>> >setup came to the point where it ran the hosted engine on temporary
>> >local storage, before it's picked up, fixed up to run on the Gluster
>> >storage and restarted there. But that process failed eventually,
>> >evidently because the overlay network doesn't support nesting. Where
>> >the initial hosted engine is using a local bridge with the (in this
>> >case virtual) host--and that works--afterwards it's using the overlay
>> >network and that evidently doesn't.
>> >
>> >It was only then when I ran across a very obscure message somewhere in
>> >this mailing list, that oVirt on top of oVirt in fact does not work at
>> >all! Up to that point it just wasn't "supported".
>> >
>> >When a hypervisor producer speaks of nested virtualization support, I
>> >would understand it to mean that you can run their product under their
>> >product, ideally also somebody else's product. I've run ESX on VMware
>> >workstation and that was pretty cool.
>> >
>> >In the case of oVirt from what I have gathered (and I'd love to be
>> >wrong), it is supposed to only mean that you can run oVirt on top of
>> >KVM.
>> >
>> >Not the other way around, nor in any other way most likely.
>> >
>> >To me that looks much more like an internal Redhat development
>> >facility, than a product feature.
>> >
>> >Of course I mostly wish they'd find a way to make it work like it does
>> >on VMware.
>> >But next on my wishlist would be an explicit description of what does
>> >and what doesn't work.
>> >
>> >This way it was almost a week of a me against the computer adventure
>> >where I lost.
>> >___
>> >Users mailing list -- users@ovirt.org
>> >To unsubscribe send an email to users-le...@ovirt.org
>> >Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> >oVirt Code of Conduct:
>> >https://www.ovirt.org/community/about/community-guidelines/
>> >List Archives:
>> >
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/7WHRDMXMAWW3DPS24X23X3GCY5S2MCZF/
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/XI4G36UJLPKTLMPNEKXBE3CN6UETXLEB/
>>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/JINUOPVOYLOQMEHLJ72JFMATO44HA7BN/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/4JXYWESSL65E35ATL7S3SA4MDVSEREX4/


[ovirt-users] Re: ovirt 4.4.1.1 hci and problems with ansible 2.9.10 and/or missing python2

2020-07-17 Thread Edward Berger
cockpit hosted-engine deploy fails after defining VM name with static
address with similar python2 error.
[image: engine-deploy-fail.JPG]

On Fri, Jul 17, 2020 at 6:44 AM Gobinda Das  wrote:

> Hi Gianluca,
>  Thanks for opening the bug.
> Adding @Prajith Kesava Prasad  to look into it.
>
>
> On Fri, Jul 17, 2020 at 4:02 PM Gianluca Cecchi 
> wrote:
>
>> On Fri, Jul 17, 2020 at 12:13 PM Martin Perina 
>> wrote:
>>
>>> I've reverified that install new host, check for upgrades, upgrade host
>>> and enroll certificates work fine even with ansible 2.9.10 on standalone
>>> engine installation. So there is some issue inside HCI installer, which
>>> doesn't handle python interpreter correctly.
>>>
>>> Gianluca, could you please create a bug for that?
>>>
>>>
>> Opened here:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1858234
>>
>> I have attached the whole content of /var/log/ovirt-hosted-engine-setup/
>> tree of the host.
>> Let me know if anything else to attach and feel free to change subject
>> and/or component
>>
>> Gianluca
>>
>
>
> --
>
>
> Thanks,
> Gobinda
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZFMOSNKCRE4PRBU6VUQGTSO4SAVGD5IT/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VBROMV6JPXDMGCSHWVWTGDBJYG72NPDL/


[ovirt-users] Re: oVirt Node 4.4.1.1 Cockpit Hyperconverged Gluster deploy fails insufficient free space no matter how small the volume is set

2020-07-16 Thread Edward Berger
Same issue with ovirt-node-ng-installer 4.4.1-2020071311.el8 iso
[image: gluster-fail.PNG]

On Thu, Jul 16, 2020 at 9:33 AM  wrote:

> I also have this message with the deployment of Gluster. I tried the
> modifications and it doesn't seem to work. Did you succeed ?
>
> here error :
>
> TASK [gluster.infra/roles/backend_setup : Change to Install lvm tools for
> RHEL systems.] ***
> task path:
> /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/main.yml:33
> fatal: [ovnode2.telecom.lan]: FAILED! => {"changed": false, "msg": "The
> Python 2 yum module is needed for this module. If you require Python 3
> support use the `dnf` Ansible module instead."}
> fatal: [ovnode1.telecom.lan]: FAILED! => {"changed": false, "msg": "The
> Python 2 yum module is needed for this module. If you require Python 3
> support use the `dnf` Ansible module instead."}
> fatal: [ovnode3.telecom.lan]: FAILED! => {"changed": false, "msg": "The
> Python 2 yum module is needed for this module. If you require Python 3
> support use the `dnf` Ansible module instead."}
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/VZVYGT7QUVWGQZERFYQ54I7VYPOM4ALL/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/GV6MIO2V5F75QDFSWEDUBDTY4G4O74FM/


[ovirt-users] Re: iSCSI array "Storage domain does not exist" error after array reboot

2020-07-07 Thread Edward Berger
I had an issue like this where I was using a centos7 (targetcli iscsi)
server which accidentally had LVM enabled upon reboot
which grabbed the RAID device and stopped targetcli from exporting the RAID
disk as iscsi.
It only showed up after a power outage and it took me a while to figure out
what happened.

I had to stop and disable LVM on the iscsi server, use 'dmsetup ls' to see
what it had touched and 'dmsetup remove' to clear them,
then restart the target service.

Somewhere along the way of troubleshooting targetcli decided to forget the
volume,
but an earlier backup config had it so I copied that into place and got it
running again.

On Tue, Jul 7, 2020 at 9:51 AM Kevin Doyle 
wrote:

> I am running a hosted engine using iscsi. I had to reboot the array, I
> took down all the VM's and put the VM data storage into maintenance mode. I
> also put the hosted engine "hosted-engine --set-maintenance --mode =global"
> and shut down the engine "hosted-engine --vm-shutdown" I also stopped the
> broker and agent systemctl stop ovirt-ha-broker' ; 'systemctl stop
> ovirt-ha-agent' The array was rebooted. I started the broker and agent
> systemctl start ovirt-ha-broker' ; 'systemctl start ovirt-ha-agent' However
> I now see errors in the vdsm log
>
> INFO  (jsonrpc/4) [storage.TaskManager.Task]
> (Task='76547cc5-e4f0-454c-ac46-c341e7f6d54c') aborting: Task is aborted:
> "Storage domain does not exist: (u'5626eba7-ebd8-4578-baf0-ca4f4af5889b',)"
> - code 358 (task:1181)
> 2020-07-07 14:01:25,098+0100 ERROR (jsonrpc/4) [storage.Dispatcher] FINISH
> prepareImage error=Storage domain does not exist:
> (u'5626eba7-ebd8-4578-baf0-ca4f4af5889b',) (dispatcher:83)
> 2020-07-07 14:01:25,098+0100 INFO  (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC
> call Image.prepare failed (error 358) in 0.07 seconds (__init__:312)
>  INFO  (vmrecovery) [vdsm.api] START
> getConnectedStoragePoolsList(options=None) from=internal,
> task_id=93d7e2d6-17ee-4370-b8c4-fb32a3887021 (api:48)
> 2020-07-07 14:01:25,592+0100 INFO  (vmrecovery) [vdsm.api] FINISH
> getConnectedStoragePoolsList return={'poollist': []} from=internal,
> task_id=93d7e2d6-17ee-4370-b8c4-fb32a3887021 (api:54)
> 2020-07-07 14:01:25,592+0100 INFO  (vmrecovery) [vds] recovery: waiting
> for storage pool to go up (clientIF:709)
>
> I have 6 hosts. I have tried rebooting them all, I have tried just running
> 1 host that was originally hosting the engine, but I cannot bring up the
> hosted engine. Has anyone any ideas ? how to reconnect the storage domain
> The hosted engine had its own iscsi disk separate from the VM's
>
> thanks
> Kevin
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/75S43CMY6FVZI56F3AHCEYFJH22N3XXZ/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/SKCE4BRSIWSSSLVF6QHUOVGQ7UW4NQHU/


[ovirt-users] Re: oVirt install questions

2020-06-21 Thread Edward Berger
 While ovirt can do what you would like it to do concerning a single user
interface, but with what you listed,
you're probably better off with just plain KVM/qemu and using virt-manager
for the interface.

Those memory/cpu requirements you listed are really tiny and I wouldn't
recommend even trying ovirt on such challenged systems.
I would specify at least 3 hosts for a gluster hyperconverged system, and a
spare available that can take over if one of the hosts dies.

I think a hosted engine installation VM wants 16GB RAM configured though
I've built older versions with 8GB RAM.
For modern VMs CentOS8 x86_64 recommends at least 2GB for a host. CentOS7
was OK with 1, CentOS6 maybe 512K.
The tendency is always increasing with updated OS versions.

My minimum ovirt systems were mostly 48GB 16core, but most are now 128GB
24core or more.

ovirt node ng is a prepackaged installer for an oVirt hypervisor/gluster
host, with its cockpit interface you can create and install the
hosted-engine VM for the user and admin web interface.  Its very good on
enterprise server hardware with lots of RAM,CPU, and DISKS.

On Sun, Jun 21, 2020 at 4:34 PM David White via Users 
wrote:

> I'm reading through all of the documentation at
> https://ovirt.org/documentation/, and am a bit overwhelmed with all of
> the different options for installing oVirt.
>
> My particular use case is that I'm looking for a way to manage VMs on
> multiple physical servers from 1 interface, and be able to deploy new VMs
> (or delete VMs) as necessary. Ideally, it would be great if I could move a
> VM from 1 host to a different host as well, particularly in the event that
> 1 host becomes degraded (bad HDD, bad processor, etc...)
>
> I'm trying to figure out what the difference is between an oVirt Node and
> the oVirt Engine, and how the engine differs from the Manager.
>
> I get the feeling that `Engine` = `Manager`. Same thing. I further think I
> understand the Engine to be essentially synonymous with a vCenter VM for
> ESXi hosts. Is this correct?
>
> If so, then what's the difference between the `self-hosted` vs the
> `stand-alone` engines?
>
> oVirt Engine requirements look to be a minimum of 4GB RAM and 2CPUs.
> oVirt Nodes, on the other hand, require only 2GB RAM.
> Is this a requirement just for the physical host, or is that how much RAM
> that each oVirt node process requires? In other words, if I have a physical
> host with 12GB of physical RAM, will I only be able to allocate 10GB of
> that to guest VMs? How much of that should I dedicated to the oVirt node
> processes?
>
> Can you install the oVirt Engine as a VM onto an existing oVirt Node? And
> then connect that same node to the Engine, once the Engine is installed?
>
> Reading through the documentation, it also sounds like oVirt Engine and
> oVirt Node require different versions of RHEL or CentOS.
> I read that the Engine for oVirt 4.4.0 requires RHEL (or CentOS) 8.2,
> whereas each Node requires 7.x (although I'll plan to just use the oVirt
> Node ISO).
>
> I'm also wondering about storage.
> I don't really like the idea of using local storage, but a single NFS
> server would also be a single point of failure, and Gluster would be too
> expensive to deploy, so at this point, I'm leaning towards using local
> storage.
>
> Any advice or clarity would be greatly appreciated.
>
> Thanks,
> David
>
>
> Sent with ProtonMail  Secure Email.
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/RGHCN356DXJEDR5FJ7SXSBHBF5FYRWIN/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/FOUZFFDRVNISJNU4MMWBYY3NBPIPLQAM/


[ovirt-users] Re: OVA import fails always

2020-02-28 Thread Edward Berger
I haven't tried many but for one I just untarred the thing to get the disk
image file and created a new VM with that.
Sometimes the ova file is compressed/assembled in some way that might not
be compatible.

On Fri, Feb 28, 2020 at 1:12 AM Jayme  wrote:

> If the problem is with the upload process specifically it’s likely that
> you do not have the ovirt engine certificate installed in your browser.
>
> On Thu, Feb 27, 2020 at 11:34 PM Juan Pablo Lorier 
> wrote:
>
>> Hi,
>>
>> I'm running 4.3.8.2-1.el7 (just updated engine to see if it helps) and I
>> haven't been able to import vms in OVA format, I've tried many appliances
>> downloaded from the web but couldn't get them to work.
>>
>> Any hints?
>>
>> Regards
>>
>> ___
>> 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/KRCE36GYQIOCXYR6K3KWUJA6R4ODWU56/
>>
> ___
> 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/VWU7EM2ZFX6STEJU67WQTIRJZWBBVWZG/
>
___
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/JMSUD7O35H73NOJATIIQS4Z7DZE533C7/


[ovirt-users] Re: oVirt 4.3.7 and Gluster 6.6 multiple issues

2020-02-11 Thread Edward Berger
For number 2, I'd look at the actual gluster file directories, in which I'd
expect to see host3 is missing the files.
I'd rsync the files from one of the other hosts to the same location on
host3 and then run the "gluster heal volume engine".

Since its the engine volume, I wouldn't be surprised if that's the cause of
the other errors.
In the past, I've seen where I had to manually restart glusterd and other
gluster related services to make everything happy.

My latest changes were to update to 4.3.8 and add /etc/host entries for the
gluster hosts on every node, and gluster seems to be stable
in cases where volumes would seem to go offline before.


On Tue, Feb 11, 2020 at 10:31 PM  wrote:

> Hi,
> I am having a couple of issues with fresh ovirt 4.3.7  HCI setup with 3
> nodes
>
>
> 
> 1.-vdsm is showing the following errors for HOST1 and HOST2 (HOST3 seems
> to be ok):
>
> 
>  service vdsmd status
> Redirecting to /bin/systemctl status vdsmd.service
> ● vdsmd.service - Virtual Desktop Server Manager
>Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor
> preset: enabled)
>Active: active (running) since Tue 2020-02-11 18:50:28 PST; 28min ago
>   Process: 25457 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh
> --pre-start (code=exited, status=0/SUCCESS)
>  Main PID: 25549 (vdsmd)
> Tasks: 76
>CGroup: /system.slice/vdsmd.service
>├─25549 /usr/bin/python2 /usr/share/vdsm/vdsmd
>├─25707 /usr/libexec/ioprocess --read-pipe-fd 52
> --write-pipe-fd 51 --max-threads 10 --max-queued-requests 10
>├─26314 /usr/libexec/ioprocess --read-pipe-fd 92
> --write-pipe-fd 86 --max-threads 10 --max-queued-requests 10
>├─26325 /usr/libexec/ioprocess --read-pipe-fd 96
> --write-pipe-fd 93 --max-threads 10 --max-queued-requests 10
>└─26333 /usr/libexec/ioprocess --read-pipe-fd 102
> --write-pipe-fd 101 --max-threads 10 --max-queued-requests 10
>
> Feb 11 18:50:28 tij-059-ovirt1.grupolucerna.local
> vdsmd_init_common.sh[25457]: vdsm: Running test_space
> Feb 11 18:50:28 tij-059-ovirt1.grupolucerna.local
> vdsmd_init_common.sh[25457]: vdsm: Running test_lo
> Feb 11 18:50:28 tij-059-ovirt1.grupolucerna.local systemd[1]: Started
> Virtual Desktop Server Manager.
> Feb 11 18:50:29 tij-059-ovirt1.grupolucerna.local vdsm[25549]: WARN MOM
> not available.
> Feb 11 18:50:29 tij-059-ovirt1.grupolucerna.local vdsm[25549]: WARN MOM
> not available, KSM stats will be missing.
> Feb 11 18:51:25 tij-059-ovirt1.grupolucerna.local vdsm[25549]: ERROR
> failed to retrieve Hosted Engine HA score
>Traceback
> (most recent call last):
>  File
> "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 182, in
> _getHaInfo...
> Feb 11 18:51:34 tij-059-ovirt1.grupolucerna.local vdsm[25549]: ERROR
> failed to retrieve Hosted Engine HA score
>Traceback
> (most recent call last):
>  File
> "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 182, in
> _getHaInfo...
> Feb 11 18:51:35 tij-059-ovirt1.grupolucerna.local vdsm[25549]: ERROR
> failed to retrieve Hosted Engine HA score
>Traceback
> (most recent call last):
>  File
> "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 182, in
> _getHaInfo...
> Feb 11 18:51:43 tij-059-ovirt1.grupolucerna.local vdsm[25549]: ERROR
> failed to retrieve Hosted Engine HA score
>Traceback
> (most recent call last):
>  File
> "/usr/lib/python2.7/site-packages/vdsm/host/api.py", line 182, in
> _getHaInfo...
> Feb 11 18:56:32 tij-059-ovirt1.grupolucerna.local vdsm[25549]: WARN ping
> was deprecated in favor of ping2 and confirmConnectivity
>
>
> 
> 2.-"gluster vol engine heal info" is showing the following and it never
> finishes healing
>
> 
> [root@host2~]# gluster vol heal engine info
> Brick host1:/gluster_bricks/engine/engine
> 

[ovirt-users] Re: VM not getting up

2020-02-07 Thread Edward Berger
Check the actual disk image storage for ownership/permissions issues.

A while back there was a bug that caused VM disk images to be changed from
vdsm:kvm ownership to root.



On Fri, Feb 7, 2020 at 3:26 PM Crazy Ayansh 
wrote:

> There are 6 VM on the server and all were working fine before I rebooted
> the server. Once server rebooted VM didn't get up. Disk is already attached
> with all the VMs and boot is also checked.
>
> On Sat, Feb 8, 2020, 1:48 AM Crazy Ayansh 
> wrote:
>
>> Yes, it is already checked.
>>
>>
>> On Sat, Feb 8, 2020, 12:56 AM Gianluca Cecchi 
>> wrote:
>>
>>>
>>>
>>> Il Ven 7 Feb 2020 20:23 Crazy Ayansh  ha
>>> scritto:
>>>
 [image: image.png]

 disk is already attached, All vm on the same server giving same error.
 Help please.
 ___
 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/YOFES7FT67N4IYKE4B6K6QER5LL2SMA4/
>>>
>>>
>>>
>>> Does the supposed bootable disk have the "bootable" checkbook marked, if
>>> you go and edit the disk?
>>>
>> ___
> 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/7ALWG5LEA5RRYRZFZZV4TPN2GBVHQNXI/
>
___
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/7JXE4U26VF6M5TRY42L7HKBEJOFD5AUK/


[ovirt-users] Re: DHCP Client in Guest VM does not work on ovirtmgmt

2019-11-03 Thread Edward Berger
 I thought that was it.
I remembered some experience I had with a test install that recommended
turning the network filter off.

You probably already did this, but when you turn off filtering or make
other changes
to the logical network like MTU size you must completely shutdown the
attached VMs and restart them
from oVIrt engine to pickup the change for their network interface.

Restarting networking in a VM from within its OS won't pick up the logical
network change
at the necessary KVM/qemu/libvirt levels.

There should a way to verify the various virtual interfaces don't have any
filtering configured or enabled,

On Sun, Nov 3, 2019 at 11:16 AM  wrote:

> Hi Edward,
>
> Yes, it is disabled .
> As screenshot.
>
> https://pasteboard.co/IEZS49Z.png
>
> And I already tested some filter as clean-traffic-gateway, but no success.
>
> Any other idea?
>
> Regards
> Carlos
> ___
> 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/M6OJTXTYTQHQN3TKQUEM7P7TZDCPPQHB/
>
___
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/AG4D7YMF7CEAYWZI2DKEFG7DZOO7BA5Z/


[ovirt-users] Re: DHCP Client in Guest VM does not work on ovirtmgmt

2019-11-01 Thread Edward Berger
Does your network vnic profile have filtering disabled?
There are options to do that in the drop-down menu "Network Filter".

[image: ovirt-network-filter.png]

On Fri, Nov 1, 2019 at 7:35 AM  wrote:

> Hi @hotomoc,
>
> Nothing, it seems there are some filter or like this.
> Maybe some expert could help us.
>
> regards
> Carlos
> ___
> 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/6DVNR44WR7IOW2SHLCMFODPJEK3INULY/
>
___
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/NF6AJPCWOZWUIVM2F2RLZK4LVBZGVFS7/


[ovirt-users] Re: Upgrading from oVirt-Node 4.2.8 to latest

2019-10-09 Thread Edward Berger
log into the ovirt node, and "yum update ovirt-node-ng-image-update" and
reboot.

On Wed, Oct 9, 2019 at 4:51 AM Sven Achtelik  wrote:

> Hi All,
>
>
>
> is there a way to go from 4.2.8 on ovirt node to go directly to the latest
> version, without reinstalling the node from the iso file ? I wasn’t able to
> find anything in documentation on how to get this done.
>
>
>
> Thanks, Sven
> ___
> 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/QEB6VPEPFKLBZZICD7FYB4EM2M4QYOQM/
>
___
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/XBP2QTIGC2F34VMDQONQ5LEF6QGDEQMK/


[ovirt-users] Re: oVirt + Gluster

2019-09-23 Thread Edward Berger
Current oVirt node-ng uses 6

]# yum list installed |grep gluster
gluster-ansible-cluster.noarch1.0.0-1.el7
 installed
gluster-ansible-features.noarch   1.0.5-3.el7
 installed
gluster-ansible-infra.noarch  1.0.4-3.el7
 installed
gluster-ansible-maintenance.noarch1.0.1-1.el7
 installed
gluster-ansible-repositories.noarch   1.0.1-1.el7
 installed
gluster-ansible-roles.noarch  1.0.5-4.el7
 installed
glusterfs.x86_64  6.4-1.el7
 installed
glusterfs-api.x86_64  6.4-1.el7
 installed
glusterfs-cli.x86_64  6.4-1.el7
 installed
glusterfs-client-xlators.x86_64   6.4-1.el7
 installed
glusterfs-events.x86_64   6.4-1.el7
 installed
glusterfs-fuse.x86_64 6.4-1.el7
 installed
glusterfs-geo-replication.x86_64  6.4-1.el7
 installed
glusterfs-libs.x86_64 6.4-1.el7
 installed
glusterfs-rdma.x86_64 6.4-1.el7
 installed
glusterfs-server.x86_64   6.4-1.el7
 installed
libvirt-daemon-driver-storage-gluster.x86_64  4.5.0-10.el7_6.12
 installed
python2-gluster.x86_646.4-1.el7
 installed
vdsm-gluster.x86_64   4.30.24-1.el7
 installed

On Mon, Sep 23, 2019 at 12:22 AM TomK  wrote:

> Hey All,
>
> Seeing GlusterFS up to version 7, do any of the oVirt versions support
> anything higher then 3.X?
>
> Or is Gluster not the preferred distributed file system choice for oVirt?
>
> --
> Thx,
> TK.
> ___
> 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/NNKXLMIGLV3GJJVW3PIF2OXV6V3PS3BV/
>
___
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/ILSB2DR343R42J2KSYNOZW23ZR5ZNGXF/


[ovirt-users] Re: ifcfg-bond0 getting overwritten.

2019-09-22 Thread Edward Berger
vdsm creates persistant network configs that overwrite manual changes at
reboot
in /var/lib/vdsm/persistence/netconf

You can check your other hosts for any differences there.

It is recommended that networks are set up and managed through ovirt engine.

On Sun, Sep 22, 2019 at 6:01 AM TomK  wrote:

> This occurs on only one of the oVirt hosts in my cluster.
> --
> Thx,
> TK.
>
> On 9/22/2019 12:08 AM, TomK wrote:
> > Hey All,
> >
> > My ifcfg-bond0 is getting overwritten on reboot.  Need to add a search
> > string to the configuration.
> >
> > What's overwriting it and should I be trying to add a search string to
> > another location?
> >
> ___
> 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/K5QTMQX4OGCKQZKZBQ4KI4IBXVTHALET/
>
___
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/DXIDOP24DKP7AKUN3JME252QHLSXZMMI/


[ovirt-users] Re: no hosted engine deploy while adding new host (oVirt 4.3.5)

2019-09-18 Thread Edward Berger
You can change that anytime.
On the engine GUI, set the host to maintenance,
The select the "Installation/Reinstall" menu item.
Select the "Hosted Engine" tab, and then pick "DEPLOY"
[image: host-deploy.JPG]

On Wed, Sep 18, 2019 at 6:14 AM  wrote:

> I tryed to add a new host to my oVirt environment. I remember a checkbox
> whether the engine HA wil depoyed or not in oVirt 4.1.
> Now the environmentist oVirt 4.3.5. In the add host dialog windows I cant
> find that option anymore. In edit window after host installation ther ist
> also no hosted engine tab.
>
> hosted-engine --deploy don't ask, if it is an additional host (like it
> used to in 4.1), so it will install a new engine instead of depoying the
> existing engine.
>
> Is there a new way of depoying the engine HA to additional hosts?
> ___
> 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/E46AZHV4THUTBCKE6J5V3WK6CVWDWSUY/
>
___
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/TTMDVV7IVGWRQTXOCNRSSYQHCGNXCBI4/


[ovirt-users] Re: ovirt-engine-extension-aaa-ldap-setup

2019-09-03 Thread Edward Berger
I had a similar issue, my LDAP guy said oVirt engine was asking for
uidObject which our ldap didn't provide and
gave me this config addition to make to the
/etc/ovirt-engine/aaa/MY.DOMAIN.properties file so it would
use inetOrgPerson instead

# override default ldap filter.  defaults found at
# 
https://github.com/oVirt/ovirt-engine-extension-aaa-ldap/blob/master/profiles/openldap.properties
sequence.openldap-init-vars.040.var-set.value =
(objectClass=inetOrgPerson)(${seq:simple_attrsUserName}=*)





On Tue, Sep 3, 2019 at 10:10 AM Rick A  wrote:

>
> Trying to get oVirt to use LDAP for user authentication. It seems to bind,
> but when I test it (Login Flow and Search) before applying the settings, I
> get the message below (I can confirm the credentials ARE valid). I also
> tried to set it up manually and still get the same result.  I'm using the
> same information on Bugzilla and it works fine. I've seen similar threads
> here but without much answers. Anyone have any good links or docs I can
> view to get this set up?
>
> oVirt Node Version: 4.3.3.6-1.el7
>
> API: <--Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS profile='
> mydomain.com' result=CREDENTIALS_INVALID
> ___
> 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/C4ZQYTRO3WVIB6Q6MC2SHGUH7CENKB4K/
>
___
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/ADH6HUHFHTHOERBAE4QWD7DCLZP2H37J/


[ovirt-users] Re: Looking to install additional packages on Ovirt Node

2019-08-14 Thread Edward Berger
on oVirt node ng, repos are usually disabled, so you need to enable the
repo to install other RPMs.
  yum --enablerepo=base install dump xfsdump
  yum --enablerepo=base install pam_krb5

On Wed, Aug 14, 2019 at 8:53 PM  wrote:

> Hello all,
>
> Hope everyone is doing well! I would simply like to ask how it would be
> possible to add additional packages to the Ovirt Centos node. I followed
> the instructions here:
> https://serverfault.com/questions/927652/is-it-ok-to-add-the-epel-repo-to-a-ovirt-node-ng-install/927660
> but I am still receiving an error that the "rear" package cannot be found
> (the package I am trying to install, ofcourse). Please help, I appreciate
> taking the time to read this. Thank you!
> ___
> 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/REN2BBSGUJFDWZQUNBOEU3X242TOWMCD/
>
___
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/7ZFQMSAJHBGXQM3GJSQA5A6UQ4NURU3I/


[ovirt-users] Re: upgrading ovirt 4.2.8 to 4.3.5

2019-08-11 Thread Edward Berger
If you installed your hypervisor hosts from the Node installer iso, updates
are done by
yum update ovirt-node-ng-image-update, and then reboot the host.

 On the hosted-engine VM you run the yum update the "release" and  *setup*
as you were trying on the node.


On Sun, Aug 11, 2019 at 8:41 PM Cole Johnson 
wrote:

> I am trying to upgrade ovirt on a standalone ovirt node host, and when I
> run
>
> # yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm
>
> I get:
>
> # yum install http://resources.ovirt.o  : 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.
> Repository centos-sclo-rh-release is listed more than once in the
> configuration
> Examining /var/tmp/yum-root-sbzUPq/ovirt-release43.rpm:
> ovirt-release43-4.3.5.1-1.el7.noarch
> /var/tmp/yum-root-sbzUPq/ovirt-release43.rpm: does not update
> installed package.
> Loading mirror speeds from cached hostfile
>  * ovirt-4.2-epel: d2lzkl7pfhq30w.cloudfront.net
>  * ovirt-4.3: resources.ovirt.org
>  * ovirt-4.3-epel: d2lzkl7pfhq30w.cloudfront.net
> No package ovirt-release43.txt available.
> Error: Nothing to do
> 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.
> Repository centos-sclo-rh-release is listed more than once in the
> configuration
> Cannot upload enabled repos report, is this client registered?
> rg/pub/yum-repo/ovirt-release43.rpm
>
> and then running
>
> # yum update "ovirt-*-setup*"
>
> I get:
> Loaded plugins: enabled_repos_upload, fastestmirror, imgbased-persist,
>   : 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.
> Repository centos-sclo-rh-release is listed more than once in the
> configuration
> Loading mirror speeds from cached hostfile
>  * ovirt-4.2-epel: d2lzkl7pfhq30w.cloudfront.net
>  * ovirt-4.3: resources.ovirt.org
>  * ovirt-4.3-epel: d2lzkl7pfhq30w.cloudfront.net
> Resolving Dependencies
> --> Running transaction check
> ---> Package ovirt-hosted-engine-setup.noarch 0:2.2.33-1.el7 will be
> updated
> ---> Package ovirt-hosted-engine-setup.noarch 0:2.3.11-1.el7 will be
> an update
> --> Processing Dependency: otopi >= 1.8 for package:
> ovirt-hosted-engine-setup-2.3.11-1.el7.noarch
> --> Processing Dependency: ovirt-ansible-engine-setup >= 1.1.9 for
> package: ovirt-hosted-engine-setup-2.3.11-1.el7.noarc
> h
> --> Processing Dependency: ovirt-ansible-hosted-engine-setup >= 1.0.21
> for package: ovirt-hosted-engine-setup-2.3.11-1.e
> l7.noarch
> --> Processing Dependency: ovirt-ansible-repositories >= 1.1.5 for
> package: ovirt-hosted-engine-setup-2.3.11-1.el7.noarc
> h
> --> Processing Dependency: ovirt-host >= 4.3 for package:
> ovirt-hosted-engine-setup-2.3.11-1.el7.noarch
> --> Processing Dependency: ovirt-host-deploy >= 1.8 for package:
> ovirt-hosted-engine-setup-2.3.11-1.el7.noarch
> --> Processing Dependency: ovirt-hosted-engine-ha >= 2.3.3 for
> package: ovirt-hosted-engine-setup-2.3.11-1.el7.noarch
> --> Processing Dependency: vdsm-python >= 4.30 for package:
> ovirt-hosted-engine-setup-2.3.11-1.el7.noarch
> --> Processing Dependency: vdsm-python >= 4.30 for package:
> ovirt-hosted-engine-setup-2.3.11-1.el7.noarch
> --> Running transaction check
> ---> Package otopi.noarch 0:1.7.8-1.el7 will be obsoleted
> ---> Package ovirt-ansible-engine-setup.noarch 0:1.1.9-1.el7 will be
> installed
> ---> Package ovirt-ansible-hosted-engine-setup.noarch 0:1.0.26-1.el7
> will be installed
> ---> Package ovirt-ansible-repositories.noarch 0:1.1.5-1.el7 will be
> installed
> ---> Package ovirt-host.x86_64 0:4.2.3-1.el7 will be updated
> ---> Package ovirt-host.x86_64 0:4.3.4-1.el7 will be an update
> --> Processing Dependency: ovirt-host-dependencies = 4.3.4-1.el7 for
> package: ovirt-host-4.3.4-1.el7.x86_64
> --> Processing Dependency: aide for package:
> ovirt-host-4.3.4-1.el7.x86_64
> --> Processing Dependency: iperf3 for package:
> ovirt-host-4.3.4-1.el7.x86_64
> --> Processing Dependency: libvirt-admin for package:
> ovirt-host-4.3.4-1.el7.x86_64
> --> Processing Dependency: openscap for package:
> ovirt-host-4.3.4-1.el7.x86_64
> --> Processing Dependency: openscap-utils for package:
> ovirt-host-4.3.4-1.el7.x86_64
> --> Processing Dependency: pam_pkcs11 for package:
> ovirt-host-4.3.4-1.el7.x86_64
> --> Processing Dependency: scap-security-guide for package:
> ovirt-host-4.3.4-1.el7.x86_64
> ---> Package ovirt-host-deploy.noarch 0:1.7.4-1.el7 will be obsoleted
> ---> Package ovirt-hosted-engine-ha.noarch 0:2.2.19-1.el7 will be
> updated
> ---> Package ovirt-hosted-engine-ha.noarch 0:2.3.3-1.el7 

[ovirt-users] Re: Ovirt Hyperconverged Cluster

2019-06-28 Thread Edward Berger
Maybe there is something already on the disk from before?
gluster setup wants it completely blank, no detectable filesystem, no raid,
etc.
see what is there with fdisk.-l  see what PVs exist with pvs.
Manually wipe, reboot and try again?

On Fri, Jun 28, 2019 at 5:37 AM  wrote:

> I have added the lvm global filter and  I have configured the
> multipath.conf but gdploy stay blocked on the PV creation on sda.
> I don't have any log in /var/log/ovirt-hosted-engine-setup
> ___
> 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/SHZOZFQXM6G6U3ZTMQ4EVR4YF3JI6XWK/
>
___
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/CR3DS2MIQWSI7XRKWFUABR44IFCVSOS3/


[ovirt-users] Re: Ovirt Hyperconverged Cluster

2019-06-27 Thread Edward Berger
You might be hitting a multipath config issue.

On a 4.3.4. node-ng cluster I had a similar problem.  spare disk was on
/dev/sda  (boot disk was /dev/sdb)

I found this link
https://stackoverflow.com/questions/45889799/pvcreate-failing-to-create-pv-device-not-found-dev-sdxy-or-ignored-by-filteri

which led me to lsblk /dev/sda and then add the "displayed wwid" to the
multipath.conf blacklist.
after restarting multipathd, I was able to use the cockpit wizard to
install gluster on /dev/sda.


On Thu, Jun 27, 2019 at 10:05 AM  wrote:

> I am installing ovirt 4.2 on three nodes. I am using centos with ovirt
> cockpit. My /sdb is my boot disk and /sda is my local storage,
>
> When I started the setup with cockpit I selected the sda but the ansible
> script stay on sdb. I have fix all changing the playbook manually but in
> the execution the gdeploy tool stay blocked on TASK [Create Physical
> Volume] .
>
> I don't find any logs. How I can fix that?
> ___
> 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/FL5E26QTE4GCLB6JFPNBVYC3XE6AWBWN/
>
___
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/OE2W77N5PI7HAWPA56A6I2MA7EOFS35Q/


[ovirt-users] Re: Replace bad Host from a 9 Node hyperconverged setup 4.3.3

2019-06-06 Thread Edward Berger
I'll presume you didn't fully backup your hosts root file systems on the
host which was fried.

It may be easier to replace with a new hostname/IP.
I would focus on the gluster config first, since it was hyperconverged.

I don't know which way engine UI is using to detect gluster mount on
missing host and decides not to remove the old host.
You probably also have the storage domain "mounted in the data-center" with
backup volume servers pointing at the old host details
The remaining gluster peers also notice the outage, and it could be
detecting that?

I would try to make gluster changes, so maybe the engine UI will allow you
to remove old hyperconverged host entry.
(The Engine UI is really trying to protect your gluster data).
I'd try changing the mount options and there is a way to tell gluster to
only use two hosts and stop trying to connect to the
third, but I don't remember the details.










On Thu, Jun 6, 2019 at 4:32 PM  wrote:

> Definitely is a challenge trying to replace a bad host.
>
> So let me tell you what I see and have done so far:
>
> 1.-I have a host that went bad due to HW issues.
> 2.-This bad host is still showing in the compute --> hosts section.
> 3.-This host was part of a hyperconverged setup with Gluster.
> 4.-The gluster bricks for this server show up with a "?" mark inside the
> volumes under Storage ---> Volumes ---> Myvolume ---> bricks
> 5.-Under Compute ---> Hosts --> mybadhost.mydomain.com the host  is in
> maintenance mode.
> 6.-When I try to remove that host (with "Force REmove" ticked) I keep
> getting:
> Operation Canceled
>  Error while executing action:
> mybadhost.mydomain.com
> - Cannot remove Host. Server having Gluster volume.
> Note: I have also confirmed "host has been rebooted"
>
> Since the bad host was not recoverable (it was fried), I took a brand new
> server with the same specs and installed oVirt 4.3.3 on it and have it
> ready to add it to the cluster with the same hostname and IP but I cant do
> this until I remove the old entries on the WEB UI of the Hosted Engine VM.
>
> If this is not possible would I really need to add this new host with a
> different name and IP?
> What would be the correct and best procedure to fix this?
>
> Note that my setup is a 9 node setup with hyperconverged and replica 3
> bricks and  in a  distributed replicated volume scenario.
>
> Thanks
> ___
> 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/N4HFTCWNFTOJJ34VSBHY5NKK5ZQAEDB7/
>
___
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/BPDZYAPS4LEKVFFNHKEXK4H4LQO5LOL6/


[ovirt-users] Re: Hosted Engine Abruptly Stopped Responding - Unexpected Shutdown

2019-06-06 Thread Edward Berger
When I read your intro, and I hit the memory figure,  I was saying to
myself, what
I'd definitely increase the memory if possible.   As high as you can
affordably fit into the servers.
Engine asks 16GB at installation time, add some for gluster services and
you're at your limits before you add a user VM.

My first non-hyperconverged hosted-engine install used a 32GB and a 24GB
dual xeon machines with only 8GB allocated for the engine VM.
I felt more confident in it when I upgraded the 24GB node to 48GB.  So 48GB
would my minimum, 64 OK, and the more the better..
Later, I was able to find some used 144GB supermicro servers which I
replaced the above nodes with.

Modern 64bit CentOS likes to have around 2GB per core for basic server
functions.
For desktops, I say have at least 8GB because web browsers eat up RAM.



On Thu, Jun 6, 2019 at 5:52 AM  wrote:

> Hello,
>
> I came upon a problem the previous month that I figured it would be good
> to discuss here. I'm sorry I didn't post here earlier but time slipped me.
>
> I have set up a glustered, hyperconverged oVirt environment for
> experimental use as a means to see its  behaviour and get used to its
> management and performance before setting it up as a production environment
> for use in our organization. The environment is up and running since 2018
> October. The three nodes are HP ProLiant DL380 G7 and have the following
> characteristics:
>
> Mem: 22GB
> CPU: 2x Hexa Core - Intel Xeon Hexa Core E56xx
> HDD: 5x 300GB
> Network: BCM5709C with dual-port Gigabit
> OS: Linux RedHat 7.5.1804(Core 3.10.0-862.3.2.el7.x86_64 x86_64) - Ovirt
> Node 4.2.3.1
>
> As I was working on the environment, the engine stopped working.
> Not long before the time the HE stopped, I was in the web interface
> managing my VMs, when the browser froze and the HE was also not responding
> to ICMP requests.
>
> The first thing I did was to connect via ssh to all nodes and run the
> command
> #hosted-engine --vm-status
> which showed that the HE was down in nodes 1 and 2 and up on the 3rd node.
>
> After executing
> #virsh -r list
> the VM list that was shown contained two of the VMs I had previously
> created and were up; the HE was nowhere.
>
> I tried to restart the HE with the
> #hosted-engine --vm-start
> but it didn't work.
>
> I then put all nodes in maintenance mode with the command
> #hosted-engine --set-maintenance --mode=global
> (I guess I should have done that earlier) and re-run
> #hosted-engine --vm-start
> that had the same result as it previously did.
>
> After checking the mails the system sent to the root user, I saw there
> were several mails on the 3rd node (where the HE had been), informing of
> the HE's state. The messages were changing between EngineDown-EngineStart,
> EngineStart-EngineStarting, EngineStarting-EngineMaybeAway,
> EngineMaybeAway-EngineUnexpectedlyDown, EngineUnexpectedlyDown-EngineDown,
> EngineDown-EngineStart and so forth.
>
> I continued by searching the following logs in all nodes :
> /var/log/libvirt/qemu/HostedEngine.log
> /var/log/libvirt/qemu/win10.log
> /var/log/libvirt/qemu/DNStest.log
> /var/log/vdsm/vdsm.log
> /var/log/ovirt-hosted-engine-ha/agent.log
>
> After that I spotted and error that had started appearing almost a month
> ago in node #2:
> ERROR Internal server error Traceback (most recent call last): File
> "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 606, in
> _handle_request res = method(**params) File
> "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 197, in
> _dynamicMethod result = fn(*methodArgs) File
> "/usr/lib/python2.7/site-packages/vdsm/gluster/apiwrapper.py", line 85, in
> logicalVolumeList return self._gluster.logicalVolumeList() File
> "/usr/lib/python2.7/site-packages/vdsm/gluster/api.py", line 90, in wrapper
> rv = func(*args, **kwargs) File
> "/usr/lib/python2.7/site-packages/vdsm/gluster/api.py", line 808, in
> logicalVolumeList status = self.svdsmProxy.glusterLogicalVolumeList() File
> "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 55, in
> __call__ return callMethod() File
> "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 52, in
>  getattr(self._supervdsmProxy._svdsm, self._funcName)(*args,
> AttributeError: 'AutoProxy[instance]' object has no attribute
> 'glusterLogicalVolumeList'
>
>
> The outputs of the following commands were also checked as a way to see if
> there was a mandatory process missing/killed, a memory problem or even disk
> space shortage that led to the sudden death of a process
> #ps -A
> #top
> #free -h
> #df -hT
>
> Finally, after some time delving in the logs, the output of the
> #journalctl --dmesg
> showed the following message
> "Out of memory: Kill process 5422 (qemu-kvm) score 514 or sacrifice child.
> Killed process 5422 (qemu-kvm) total-vm:17526548kB, anon-rss:9310396kB,
> file-rss:2336kB, shmem-rss:12kB"
> which after that the ovirtmgmt started not responding.
>
> I tried to restart the vhostd by 

[ovirt-users] Re: ovirt metrics ansible error

2019-05-28 Thread Edward Berger
> TASK [openshift_control_plane : Wait for control plane pods to appear]
*
> Monday 27 May 2019  13:31:54 + (0:00:00.180)   0:14:33.857

> FAILED - RETRYING: Wait for control plane pods to appear (60 retries
left).
> FAILED - RETRYING: Wait for control plane pods to appear (59 retries
left).
>It eventually counts all the way down to zero and fails.

This looks a lot like the issues I saw when the host firewall (iptables)
was blocking another OKD all-in-one-host install script [1].
Disabling iptables allowed the installation to continue for my proof of
concept "cluster".

[1]https://github.com/gshipley/installcentos

The other error I had with [1] was it was trying to install a couple of
packages (zile and python2-pip) from EPEL with the repo disabled.



On Tue, May 28, 2019 at 10:41 AM Jayme  wrote:

> Shirly,
>
> Oh and I should mention that I did verify that NetworkManager was
> installed on the master0 VM and enabled/started the second go around.  So
> that service is there and running.
>
> # systemctl list-unit-files | grep Network
> dbus-org.freedesktop.NetworkManager.service
> enabled
> NetworkManager-dispatcher.service
> enabled
> NetworkManager-wait-online.service
>  enabled
> NetworkManager.service
>  enabled
>
> On Tue, May 28, 2019 at 11:13 AM Jayme  wrote:
>
>> Shirly,
>>
>> I appreciate the help with this.  Unfortunately I am still running in to
>> the same problem.  So far I've tried to install/enable/start NetworkManager
>> on the existing "master0" server and re-ran the plans from the installer
>> VM.  I ran in to the same problem waiting for control plane pods and same
>> errors in syslog.
>>
>> So I wiped everything out, killed the template along with the installer
>> and master VMs.  On oVirt engine (I am running 4.3.3.7-1 stable) I did have
>> ovirt-engine-metrics-1.3.0x rpm installed, no yum updates available on an
>> update check.  So I installed
>> http://resources.ovirt.org/pub/yum-repo/ovirt-release43-pre.rpm then
>> proceeded to install the latest version of ovirt-engine-metrics which gave
>> me: ovirt-engine-metrics-1.3.1-1.el7.noarch on hosted engine.
>>
>> After that package was installed I proceeded to follow steps from
>> beginning outlined at:
>> https://ovirt.org/documentation/metrics-install-guide/Installing_Metrics_Store.html
>>  --
>> I ran in to the docker check issue again (same as my initial email) so I
>> disabled that and again got as far as starting control plane pods before
>> failure.
>>
>> Not sure where to go from here at this point.  The only thing I can think
>> of that I did differently vs the instructions outlined above is that I have
>> not crated the wildcard DNS record, however I did set configs to create
>> /etc/hosts entries and they /etc/hosts on the machines have the proper IPs
>> assigned for all hostnames (automatically added by the ansible plays).
>>
>> Any ideas how I can get past the plane pods issue?
>>
>> Thanks!
>>
>> On Tue, May 28, 2019 at 4:23 AM Shirly Radco  wrote:
>>
>>> Hi,
>>>
>>> The latest release of 4.3.z should already include a fix for this issue,
>>> ovirt-engine-metrics-1.3.1 rpm.
>>>
>>> The issue is that it requires the NetworkManagar to be installed,
>>> running and enabled for it to work.
>>>
>>> You can install it manually on the master0 vm , start and enable it or
>>> you can also install the updated rpm from the nightly builds if your
>>> environment is oVirt 4.2.z:
>>>
>>> https://resources.ovirt.org/pub/ovirt-4.2-snapshot/rpm/el7/noarch/ovirt-engine-metrics-1.2.3-0.0.master.20190523112218.gitbc6e4fa.el7.noarch.rpm
>>>
>>> Relevant patches are:
>>> https://gerrit.ovirt.org/#/c/99959/
>>> https://gerrit.ovirt.org/#/c/99718/
>>>
>>> Best regards,
>>>
>>> --
>>>
>>> Shirly Radco
>>>
>>> BI Senior Software Engineer
>>>
>>> Red Hat 
>>>
>>> 
>>>
>>>
>>> On Mon, May 27, 2019 at 4:41 PM Jayme  wrote:
>>>
 I managed to get past that but am running in to another problem later
 in the process on the control plane pods to appear task.   I thought
 perhaps a glitch in the process from the failed docker step previously so
 after a few more runs I tried killing everything and restarting the metrics
 process again from the very beginning and end up hitting the same issue
 with control plane pods even though all other steps/tasks seem to be
 working.

 I'm just getting this:

 TASK [openshift_control_plane : Wait for control plane pods to appear]
 *
 Monday 27 May 2019  13:31:54 + (0:00:00.180)   0:14:33.857
 
 FAILED - RETRYING: Wait for control plane pods to appear (60 retries
 left).
 FAILED - RETRYING: Wait for control plane pods to appear (59 retries
 left).
 FAILED - RETRYING: Wait for control plane pods to appear (58 retries
 left).
 FAILED - RETRYING: Wait for control plane pods to appear (57 retries
 left).
 FAILED - RETRYING: 

[ovirt-users] Re: 4.3.3 single node hyperconverged wizard failing because var/log is too small?

2019-05-10 Thread Edward Berger
Thanks! After adding the workaround, I was able to complete the deployment.

On Fri, May 10, 2019 at 1:39 AM Parth Dhanjal  wrote:

> Hey!
>
> oVirt 4.3.3 uses gluster-ansible-roles to deploy the storage.
> There are multiple checks during a deployment.
> This particular check which is failing is a part of the
> gluster-ansible-featues (
> https://github.com/gluster/gluster-ansible-features/tree/master/roles/gluster_hci
> )
>
> A simple workaround can be to skip the test, by editing the finally
> generated inventory file in the last step before deployment and adding 
> gluster_features_force_varlogsizecheck:
> false under the vars section of the file.
>
> Regards
> Parth Dhanjal
>
> On Fri, May 10, 2019 at 5:58 AM Edward Berger  wrote:
>
>> I'm trying to bring up a single node hyperconverged with the current
>> node-ng ISO installation,
>> but it ends with this failure message.
>>
>> TASK [gluster.features/roles/gluster_hci : Check if /var/log has enough
>> disk space] ***
>> fatal: [br014.bridges.psc.edu]: FAILED! => {"changed": true, "cmd": "df
>> -m /var/log | awk '/[0-9]%/ {print $4}'", "delta": "0:00:00.008513", "end":
>> "2019-05-09 20:09:27.914400", "failed_when_result": true, "rc": 0, "start":
>> "2019-05-09 20:09:27.905887", "stderr": "", "stderr_lines": [], "stdout":
>> "7470", "stdout_lines": ["7470"]}
>>
>> I have what the installer created by default for /var/log, so I don't
>> know why its complaining.
>>
>> [root@br014 ~]# df -kh
>> Filesystem  Size
>> Used Avail Use% Mounted on
>> /dev/mapper/onn_br014-ovirt--node--ng--4.3.3.1--0.20190417.0+1  3.5T
>> 2.1G  3.3T   1% /
>> devtmpfs 63G
>> 0   63G   0% /dev
>> tmpfs63G
>> 4.0K   63G   1% /dev/shm
>> tmpfs63G
>> 18M   63G   1% /run
>> tmpfs63G
>> 0   63G   0% /sys/fs/cgroup
>> /dev/mapper/onn_br014-home  976M
>> 2.6M  907M   1% /home
>> /dev/mapper/onn_br014-tmp   976M
>> 2.8M  906M   1% /tmp
>> /dev/mapper/onn_br014-var15G
>> 42M   14G   1% /var
>> /dev/sda2   976M
>> 173M  737M  19% /boot
>> /dev/mapper/onn_br014-var_log   7.8G
>> 41M  7.3G   1% /var/log
>> /dev/mapper/onn_br014-var_log_audit 2.0G
>> 7.6M  1.8G   1% /var/log/audit
>> /dev/mapper/onn_br014-var_crash 9.8G
>> 37M  9.2G   1% /var/crash
>> /dev/sda1   200M
>> 12M  189M   6% /boot/efi
>> tmpfs13G
>> 0   13G   0% /run/user/1000
>> tmpfs13G
>> 0   13G   0% /run/user/0
>> /dev/mapper/gluster_vg_sdb-gluster_lv_engine3.7T
>> 33M  3.7T   1% /gluster_bricks/engine
>> /dev/mapper/gluster_vg_sdc-gluster_lv_data  3.7T
>> 34M  3.7T   1% /gluster_bricks/data
>> /dev/mapper/gluster_vg_sdd-gluster_lv_vmstore   3.7T
>> 34M  3.7T   1% /gluster_bricks/vmstore
>>
>> The machine had 4 4TB disks, so sda is the installation for oVirt
>> node-ng, the other 3 disks for the gluster volumes.
>>
>> root@br014 ~]# pvs
>>   PV VG Fmt  Attr PSize  PFree
>>   /dev/sda3  onn_br014  lvm2 a--  <3.64t 100.00g
>>   /dev/sdb   gluster_vg_sdb lvm2 a--  <3.64t <26.02g
>>   /dev/sdc   gluster_vg_sdc lvm2 a--  <3.64t  0
>>   /dev/sdd   gluster_vg_sdd lvm2 a--  <3.64t  0
>>
>> [root@br014 ~]# vgs
>>   VG #PV #LV #SN Attr   VSize  VFree
>>   gluster_vg_sdb   1   1   0 wz--n- <3.64t <26.02g
>>   gluster_vg_sdc   1   2   0 wz--n- <3.64t  0
>>   gluster_vg_sdd   1   2   0 wz--n- <3.64t  0
>>   onn_br0141  11   0 wz--n- <3.64t 100.00g
>>
>> [root@br014 ~]# lvs
>>   LV   VG Attr   LSize
>> PoolOrigin D

[ovirt-users] 4.3.3 single node hyperconverged wizard failing because var/log is too small?

2019-05-09 Thread Edward Berger
I'm trying to bring up a single node hyperconverged with the current
node-ng ISO installation,
but it ends with this failure message.

TASK [gluster.features/roles/gluster_hci : Check if /var/log has enough
disk space] ***
fatal: [br014.bridges.psc.edu]: FAILED! => {"changed": true, "cmd": "df -m
/var/log | awk '/[0-9]%/ {print $4}'", "delta": "0:00:00.008513", "end":
"2019-05-09 20:09:27.914400", "failed_when_result": true, "rc": 0, "start":
"2019-05-09 20:09:27.905887", "stderr": "", "stderr_lines": [], "stdout":
"7470", "stdout_lines": ["7470"]}

I have what the installer created by default for /var/log, so I don't know
why its complaining.

[root@br014 ~]# df -kh
Filesystem  Size  Used
Avail Use% Mounted on
/dev/mapper/onn_br014-ovirt--node--ng--4.3.3.1--0.20190417.0+1  3.5T  2.1G
3.3T   1% /
devtmpfs 63G
0   63G   0% /dev
tmpfs63G
4.0K   63G   1% /dev/shm
tmpfs63G
18M   63G   1% /run
tmpfs63G
0   63G   0% /sys/fs/cgroup
/dev/mapper/onn_br014-home  976M  2.6M
907M   1% /home
/dev/mapper/onn_br014-tmp   976M  2.8M
906M   1% /tmp
/dev/mapper/onn_br014-var15G
42M   14G   1% /var
/dev/sda2   976M  173M
737M  19% /boot
/dev/mapper/onn_br014-var_log   7.8G   41M
7.3G   1% /var/log
/dev/mapper/onn_br014-var_log_audit 2.0G  7.6M
1.8G   1% /var/log/audit
/dev/mapper/onn_br014-var_crash 9.8G   37M
9.2G   1% /var/crash
/dev/sda1   200M   12M
189M   6% /boot/efi
tmpfs13G
0   13G   0% /run/user/1000
tmpfs13G
0   13G   0% /run/user/0
/dev/mapper/gluster_vg_sdb-gluster_lv_engine3.7T   33M
3.7T   1% /gluster_bricks/engine
/dev/mapper/gluster_vg_sdc-gluster_lv_data  3.7T   34M
3.7T   1% /gluster_bricks/data
/dev/mapper/gluster_vg_sdd-gluster_lv_vmstore   3.7T   34M
3.7T   1% /gluster_bricks/vmstore

The machine had 4 4TB disks, so sda is the installation for oVirt node-ng,
the other 3 disks for the gluster volumes.

root@br014 ~]# pvs
  PV VG Fmt  Attr PSize  PFree
  /dev/sda3  onn_br014  lvm2 a--  <3.64t 100.00g
  /dev/sdb   gluster_vg_sdb lvm2 a--  <3.64t <26.02g
  /dev/sdc   gluster_vg_sdc lvm2 a--  <3.64t  0
  /dev/sdd   gluster_vg_sdd lvm2 a--  <3.64t  0

[root@br014 ~]# vgs
  VG #PV #LV #SN Attr   VSize  VFree
  gluster_vg_sdb   1   1   0 wz--n- <3.64t <26.02g
  gluster_vg_sdc   1   2   0 wz--n- <3.64t  0
  gluster_vg_sdd   1   2   0 wz--n- <3.64t  0
  onn_br0141  11   0 wz--n- <3.64t 100.00g

[root@br014 ~]# lvs
  LV   VG Attr   LSize
PoolOrigin Data%
Meta%  Move Log Cpy%Sync Convert
  gluster_lv_enginegluster_vg_sdb -wi-ao
3.61t

  gluster_lv_data  gluster_vg_sdc Vwi-aot---  3.61t
gluster_thinpool_gluster_vg_sdc
0.05
  gluster_thinpool_gluster_vg_sdc  gluster_vg_sdc twi-aot---
<3.61t
0.05   0.13
  gluster_lv_vmstore   gluster_vg_sdd Vwi-aot---  3.61t
gluster_thinpool_gluster_vg_sdd
0.05
  gluster_thinpool_gluster_vg_sdd  gluster_vg_sdd twi-aot---
<3.61t
0.05   0.13
  home onn_br014  Vwi-aotz--  1.00g
pool00
4.79
  ovirt-node-ng-4.3.3.1-0.20190417.0   onn_br014  Vwi---tz-k <3.51t
pool00
root
  ovirt-node-ng-4.3.3.1-0.20190417.0+1 onn_br014  Vwi-aotz-- <3.51t
pool00  ovirt-node-ng-4.3.3.1-0.20190417.0
0.13
  pool00   onn_br014  twi-aotz--
3.53t
0.19   1.86
  root onn_br014  Vri---tz-k <3.51t
pool00

  swap onn_br014  -wi-ao
4.00g

  tmp  onn_br014  Vwi-aotz--  1.00g
pool00
4.84
  var  onn_br014  Vwi-aotz-- 15.00g
pool00
3.67
  var_crashonn_br014  Vwi-aotz-- 10.00g
pool00
2.86
  var_log  onn_br014  Vwi-aotz--  8.00g
pool00
3.25
  var_log_auditonn_br014  Vwi-aotz--  2.00g
pool00
4.86



Here's the full deploy log from the UI.  Let me know if you need specific
logs.


PLAY [Setup backend]
***

TASK [Gathering Facts]

[ovirt-users] Re: unable to upload disk images after upgrade to 4.3.3 -- ticket failures

2019-04-25 Thread Edward Berger
Today, I updated engine to the latest Version 4.3.3.6-1.el7.
Trying to upload an install iso to the hosted storage domain gives same
disk paused by system issue.

Apr 25, 2019, 5:26:18 PMTransfer was stopped by system. Reason: failed to
add image ticket to ovirt-imageio-proxy.


on the node which was running ovirt-image

/var/log/ovirt-imageio-daemon contains:
2019-04-25 17:08:51,757 INFO(Thread-2) [http] OPEN client=local
2019-04-25 17:08:51,758 INFO(Thread-2) [tickets] [local] ADD
ticket={u'uuid': u'6971e886-5339-4df1-88df-445e51fba1c8', u'ops':
[u'write'], u'url': u'fi
le:///rhev/data-center/mnt/glusterSD/10.200.0.131:
_engine/0ec355b1-e665-4fdf-87c4-87e1d636c76d/images/4121f1fb-c508-47bc-9acb-a10da9461358/04658323-b267-4f
66-96f1-6c5848c3d2be', u'sparse': True, u'timeout': 300,
u'transfer_id': u'e85ce170-03e6-480d-bbc5-8551c266cc97', u'size':
1045426176}
2019-04-25 17:08:51,759 INFO(Thread-2) [http] CLOSE client=local
[connection=0.001420/1, dispatch=0.000634/1]

going to that directory above shows
# ls -l
total 1025
-rw-rw. 1 vdsm kvm 1045426176 Apr 25 17:08
04658323-b267-4f66-96f1-6c5848c3d2be
-rw-rw. 1 vdsm kvm1048576 Apr 25 17:08
04658323-b267-4f66-96f1-6c5848c3d2be.lease
-rw-r--r--. 1 vdsm kvm345 Apr 25 17:08
04658323-b267-4f66-96f1-6c5848c3d2be.meta

image is showing same size as the iso file.

On engine
# systemctl status -l ovirt-imageio-proxy.service
● ovirt-imageio-proxy.service - oVirt ImageIO Proxy
   Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-proxy.service;
enabled; vendor preset: disabled)
   Active: active (running) since Thu 2019-04-25 16:36:24 EDT; 51min ago
 Main PID: 56989 (ovirt-imageio-p)
   CGroup: /system.slice/ovirt-imageio-proxy.service
   └─56989 /usr/bin/python2 /usr/bin/ovirt-imageio-proxy

Apr 25 16:36:24 dispatch.yard.psc.edu systemd[1]: Starting oVirt ImageIO
Proxy...
Apr 25 16:36:24 dispatch.yard.psc.edu systemd[1]: Started oVirt ImageIO
Proxy.
Apr 25 17:08:30 dispatch.yard.psc.edu ovirt-imageio-proxy[56989]:
128.182.168.116 - - [25/Apr/2019 17:08:30] "GET /info/ HTTP/1.1" 200 20
Apr 25 17:25:46 dispatch.yard.psc.edu ovirt-imageio-proxy[56989]:
128.182.168.116 - - [25/Apr/2019 17:25:46] "GET /info/ HTTP/1.1" 200 20

# cat image-proxy.log
(MainThread) INFO 2019-04-25 16:25:55,755 image_proxy:43:root:(main) Server
shut down, exiting
(MainThread) INFO 2019-04-25 16:36:24,874 server:45:server:(start) Starting
(pid=56989, version=1.5.1)
(MainThread) INFO 2019-04-25 16:36:24,879 image_proxy:34:root:(main) Server
started, successfully notified systemd


On Tue, Apr 23, 2019 at 4:51 PM Edward Berger  wrote:

> Previously I had issues with the upgrades to 4.3.3 failing because of
> "stale" image transfer data, so I removed it from the database using the
> info given here on the mailing list and was able to complete the oVirt node
> and engine upgrades.
>
> Now I have a new problem.  I can't upload a disk image anymore, which used
> to work.
> "test connection" returns success.
>
> In the dashboard Storage/Disks view, it starts and then stops with "paused
> by system"
>
> I tried pointing it at another node, same problem. I tried restarting
> services ovirt-imageio-proxy on engine and ovirt-imageio-daemon on the
> node, same failure.
>
> in the dashboard events when trying to upload disk I get this error
>   Transfer was stopped by system. Reason: failed to add image ticket
> to ovirt-imageio-proxy.
>
> or when trying to resume transfer "paused by system" giving it the local
> path again.
>Transfer was stopped by system. Reason: failure in transfer image
> ticket renewal.
>
> I'm not sure what logs I should be looking deeper into..
>
> Here's what the database says
> engine=# select * from image_transfers;
> -[ RECORD 1 ]-+-
> command_id| 59dce2b1-f8ba-44dd-9df9-c6e39773a3f9
> command_type  | 1024
> phase | 4
> last_updated  | 2019-04-23 12:22:25.098-04
> message   | Uploading from byte 0
> vds_id|
> disk_id   | 6693d5ac-d3eb-43d7-9abe-97c5197efc23
> imaged_ticket_id  |
> proxy_uri |
> signed_ticket |
> bytes_sent| 0
> bytes_total   | 1996488704
> type  | 2
> active| f
> daemon_uri|
> client_inactivity_timeout | 60
> -[ RECORD 2 ]-+-
> command_id| 16898219-be5b-4826-8f20-3355fa47272a
> command_type  | 1024
> phase | 4
> last_updated  | 2019-04-23 16:15:34.591-04
> message   | Uploading from byte 0
&g

[ovirt-users] unable to upload disk images after upgrade to 4.3.3 -- ticket failures

2019-04-23 Thread Edward Berger
Previously I had issues with the upgrades to 4.3.3 failing because of
"stale" image transfer data, so I removed it from the database using the
info given here on the mailing list and was able to complete the oVirt node
and engine upgrades.

Now I have a new problem.  I can't upload a disk image anymore, which used
to work.
"test connection" returns success.

In the dashboard Storage/Disks view, it starts and then stops with "paused
by system"

I tried pointing it at another node, same problem. I tried restarting
services ovirt-imageio-proxy on engine and ovirt-imageio-daemon on the
node, same failure.

in the dashboard events when trying to upload disk I get this error
  Transfer was stopped by system. Reason: failed to add image ticket to
ovirt-imageio-proxy.

or when trying to resume transfer "paused by system" giving it the local
path again.
   Transfer was stopped by system. Reason: failure in transfer image
ticket renewal.

I'm not sure what logs I should be looking deeper into..

Here's what the database says
engine=# select * from image_transfers;
-[ RECORD 1 ]-+-
command_id| 59dce2b1-f8ba-44dd-9df9-c6e39773a3f9
command_type  | 1024
phase | 4
last_updated  | 2019-04-23 12:22:25.098-04
message   | Uploading from byte 0
vds_id|
disk_id   | 6693d5ac-d3eb-43d7-9abe-97c5197efc23
imaged_ticket_id  |
proxy_uri |
signed_ticket |
bytes_sent| 0
bytes_total   | 1996488704
type  | 2
active| f
daemon_uri|
client_inactivity_timeout | 60
-[ RECORD 2 ]-+-
command_id| 16898219-be5b-4826-8f20-3355fa47272a
command_type  | 1024
phase | 4
last_updated  | 2019-04-23 16:15:34.591-04
message   | Uploading from byte 0
vds_id|
disk_id   | 3b8e3053-bfe4-49d3-abd2-5452b1674400
imaged_ticket_id  |
proxy_uri |
signed_ticket |
bytes_sent| 0
bytes_total   | 1998585856
type  | 2
active| f
daemon_uri|
client_inactivity_timeout | 60

I really need the image uploading to work. Any suggestions on what to do
next?
___
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/U4B34UZ4VRF43JFWCMZOMERY6QWEZ6ET/


[ovirt-users] Re: engine-setup failing on 4.3.2 -> 4.3.3 fails during Engine schema refresh fail

2019-04-17 Thread Edward Berger
Thanks! That fixed the problem.  engine-setup was able to complete.

On Wed, Apr 17, 2019 at 3:48 AM Yedidyah Bar David  wrote:

> On Wed, Apr 17, 2019 at 10:30 AM Lucie Leistnerova 
> wrote:
> >
> > Hi Edward,
> >
> > On 4/16/19 9:23 PM, Edward Berger wrote:
> >
> > I was trying to upgrade a hyperconverged oVirt hosted engine and failed
> in the engine-setup command with these error and warnings.
> >
> > ...
> > [ INFO  ] Creating/refreshing Engine database schema
> > [ ERROR ] schema.sh: FATAL: Cannot execute sql command:
> --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_03_0830_add_foreign_key_to_image_transfers.sql
> >
> > The error is
> >
> > ERROR:  insert or update on table "image_transfers" violates foreign key
> constraint "fk_image_transfers_command_enitites"
> > DETAIL:  Key (command_id)=(fedc82f7-9bf7-4988-b9d9-23853e04e44e) is not
> present in table "command_entities".
> >
> > So there is some image transfer left without appropriate command entity.
> > If you are sure that no such transfer is active. You can remove it from
> the table.
> >
> >
> > $ scl enable rh-postgresql10 bash
> > $ psql engine
> >
> > engine=# delete from image_transfers where
> command_id='fedc82f7-9bf7-4988-b9d9-23853e04e44e';
>
> Or, more generally, copying from
> 04_03_0270_add_foreign_key_to_image_transfers.sql:
>
> DELETE FROM image_transfers
> WHERE command_id NOT IN
> (SELECTcommand_entities.command_id
>  FROM  command_entities);
>
> and then try again.
>
> Adding Also Bhushan, who reported this in private as well.
>
> Adding Daniel, author of the patch causing this:
>
> https://gerrit.ovirt.org/#/q/I65906d09ba201c93da65e9a2b67cef5f9f177747,n,z
>
> Daniel:
>
> This already happened in the past, and we fixed it by adding
> 04_03_0265_remove_foreign_key_in_image_transfers.sql . Not sure why we
> needed to add 04_03_0830_add_foreign_key_to_image_transfers.sql again,
> but perhaps add now another copy of
> 04_03_0265_remove_foreign_key_in_image_transfers.sql before it as
> well.
>
> Also: Perhaps push a patch to OST to verify this flow.
>
> Thanks and best regards,
>
> >
> >
> > [ ERROR ] Failed to execute stage 'Misc configuration': Engine schema
> refresh failed
> > ...
> > [ INFO  ] Yum Verify: 16/16: ovirt-engine-tools.noarch 0:4.3.3.5-1.el7 -
> e
> > [WARNING] Rollback of DWH database postponed to Stage "Clean up"
> > [ INFO  ] Rolling back database schema
> > ...
> > [ INFO  ] Stage: Pre-termination
> > [ INFO  ] Stage: Termination
> > [ ERROR ] Execution of setup failed
> >
> > Attaching engine-setup logfile.
> >
> > ___
> > 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/45EDYLIQE4QUJYZUG6KJJRJAKCJ5OI3P/
> >
> > Best regards,
> >
> > --
> > Lucie Leistnerova
> > Quality Engineer, QE Cloud, RHVM
> > Red Hat EMEA
> >
> > IRC: lleistne @ #rhev-qe
> >
> > ___
> > 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/2UT7ANKVQKB5NSE3DQAFH6EFDEYDEWVB/
>
>
>
> --
> Didi
>
___
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/2JYEJFL6C2LD4ZXDU5UTLG55M33X3ZMJ/


[ovirt-users] unable to put node 4.3.0 host into maintenance for upgrade, Image transfer in progress

2019-03-21 Thread Edward Berger
When trying to put a node 4.3.0 into maintenance, I get the following error:
--
Error while executing action: Cannot switch Host winterfell.psc.edu to
Maintenance mode. Image transfer is in progress for the following (2) disks:

8d130846-bd84-46b0-9a45-b6a2ecf66865,
35fd6f8f-65f5-49e7-ae5a-9b10c5c0a38f

Please wait for the operations to complete and try again.
--

Attached is an image of the disks UI for those, showing their status.
>From the engine UI there seems to be no way to clean out "completed" or
"failed" uploads/downloads.

I tried running the taskcleaner.sh and unlock-entity disk UUIDs but I still
get the error.
Not sure what to try next...
___
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/DCKMKLTRVC3RMSG2XVRKFVJFW4HO7UHD/


[ovirt-users] Re: oVirt 4.3 - create windows2012 failed due to ovirt-imageio-proxy

2019-03-18 Thread Edward Berger
That is completely normal if you didn't download and install the CA
certificate from your ovirt engine GUI.
There's a download link for it on the page before you login?

On Mon, Mar 18, 2019 at 5:01 PM  wrote:

> Hi,
>
> I tried to create windows2012 vm on nfs data domain, but the disk was
> locked.
> Found the error message as following:
>
> Connection to ovirt-imageio-proxy service has failed. Make sure the
> service is installed, configured, and ovirt-engine certificate is
> registered as a valid CA in the browser.
>
> Is this known issue?
>
> Thanks,
> Jingjie
> ___
> 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/QBZQG553L7WYVHQFDRWUAYKYZ2HLSJKW/
>
___
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/3NYKJQ34KV4Q26735GUCDSN6GGLNZEZZ/


[ovirt-users] Re: oVirt Node install failed

2019-02-26 Thread Edward Berger
OK, if the icon is there that is a good thing.  There would be no icon if
you didn't select deploy.
Its not terribly obvious when first installing a second host that it needs
the deploy part set.

There's something else causing the engine migration to fail.   You can dig
through the logs on the engine and hosts.

I would look next at the underlying storage for the ovirt-engine image to
see if it got bit by the bug that leaves it owned by root and not vdsm:kvm.
That prevented me from migrating engine to properly deployed nodes when
upgrading to 4.3

On one of the hosts, follow the path /rhev/data-center/mnt/*  to  "ls -l"
the images directory for your hosted-storage and check the ownership.
If its owned by root and not vdsm:kvm then chown it to that (aka 36:36) and
try migrating again.



On Mon, Feb 25, 2019 at 10:50 PM  wrote:

> The crown icon on the left of the second host is gray. When I try to
> migrate the engine, I get the error:
>
>  Migration of VM 'HostedEngine' to host 'ovirt2' failed: VM destroyed
> during the startup
> EVENT_ID: VM_MIGRATION_NO_VDS_TO_MIGRATE_TO(166), No available host was
> found to migrate VM HostedEngine to.
> ___
> 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/NHG7MBNCPYMSXC7PGYWIZ6WEDT2Y6LYU/
>
___
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/RTSYZ7CKQDASLYSLG4YTBICTFZH3E7UA/


[ovirt-users] Re: oVirt Node install failed

2019-02-25 Thread Edward Berger
If you haven't "installed" or "reinstalled" the second host without
purposely selecting "DEPLOY" under hosted-engine actions,
it will not be able to run the hosted-engine VM.
A quick way to tell if you did is to look at the hosts view and look for
the "crowns" on the left like this attached pic example.

On Sun, Feb 24, 2019 at 11:27 PM  wrote:

> Thanks for the answer.
>
> Now I have two hosts 4.2.6 and 4.2.8, and the engine 4.2.6. VMs migrate
> between these hosts without problems. But the VM with the engine to migrate
> to host 4.2.8 refuses - he say:
>
> No available Host to migrate to.
>
> Since it cannot migrate, there is no way to put the host in maintenance
> mode. And there is no possibility of upgrade.How to find out why? Install
> Host 4.2.6?
> ___
> 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/ECVQUALTXCX2VE63T5K4AMYO2UID2HMM/
>
___
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/SWQBUYOUB3PRJYZNY6RQQBYBSFPUCQVM/


[ovirt-users] please help with console issues on vGPU enabled VMs.

2019-02-14 Thread Edward Berger
We are attempting to get vGPU-enabled guests working with our oVirt 4.3.0
configuration, but have run into problems.

We are running:
   NVidia License Server version 2018.09
   NVidia License Client Manager 2018.10.0.25098346
and that license info is correctly retrieved by the clients.

With a Centos 7.6 guest, we can ssh into the guest and see that the X
server is running and a gdm process is also running, but when we open a
remote console viewer, all we get is a black screen.  The X server reports
the correct vGPU profile.  The only error we see in the Xorg.0.log file is:
[ 5.176] (EE) NVIDIA(GPU-0): Failed to update the GLS device with FRL
configuration
but that is not fatal.

With a Windows 10 guest, we do get a login screen to appear, but the mouse
and keyboard do not seem to be functional.

Host configuration:
 host is running oVirt-node 4.3.0
 NVidia driver NVIDIA-vGPU-rhel-7.6-410.91.x86_64.rpm installed
CentOS 7.6 guest configuration:
 NVidia driver NVIDIA-Linux-x86_64-410.92-grid.run installed
 added an explicit BusID in the guest's xorg.conf file
 disabled SELinux
Windows 10 guest configuration:
NVidia driver 412.16_grid_win10_server2016_64bit_international.exe
installed
Remote viewer:
 remote-viewer 5.0-11.el7 running on CentOS 7.3

Both host and guest NVidia drivers come from the
NVIDIA-GRID-RHEL-7.6-410.92-410.91-412.16.zip package.  We have tried with
both V100 and P4 GPUs (with ECC disabled), and encounter similar problems.
Any ideas on what to try, or how to better diagnose the cause of these
problems?
Thanks.
___
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/RS2DHOWGM45K7AM5KKEJQIR3LDIT7BO5/


[ovirt-users] Re: update to 4.2.8 fails

2019-02-13 Thread Edward Berger
If its a node-ng install, you should just update the whole image with
yum update ovirt-node-ng-image-update

On Wed, Feb 13, 2019 at 8:12 PM Vincent Royer  wrote:

> Sorry, this is a node install w/ he.
>
> On Wed, Feb 13, 2019, 4:44 PM Vincent Royer 
>> trying to update from 4.2.6 to 4.2.8
>>
>> yum update fails with:
>>
>> --> Finished Dependency Resolution
>>
>>
>>
>>
>> Error: Package: vdsm-4.20.46-1.el7.x86_64 (ovirt-4.2)
>>
>>
>>
>>
>>Requires: libvirt-daemon-kvm >= 4.5.0-10.el7_6.3
>>
>>
>>
>>
>>Installed: libvirt-daemon-kvm-3.9.0-14.el7_5.8.x86_64
>> (installed)
>>
>>
>>
>>libvirt-daemon-kvm = 3.9.0-14.el7_5.8
>>
>>
>>
>>
>> Error: Package: 10:qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64
>> (ovirt-4.2-centos-qemu-ev)
>>
>>
>>
>>Requires: libepoxy.so.0()(64bit)
>>
>>
>>
>>
>> Error: Package: 10:qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64
>> (ovirt-4.2-centos-qemu-ev)
>>
>>
>>
>>Requires: libibumad.so.3()(64bit)
>>
>>
>>
>>
>> Error: Package: 10:qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64
>> (ovirt-4.2-centos-qemu-ev)
>>
>>
>>
>>Requires: libgbm.so.1()(64bit)
>>
>>
>>
>>
>>  You could try using --skip-broken to work around the problem
>>
>>
>>
>>
>>  You could try running: rpm -Va --nofiles --nodigest
>>
>>
>>
>>
>> Uploading Enabled Repositories Report
>>
>>
>>
>>
>> 2019-02-13 16:42:14,190 [INFO] yum:17779:Dummy-18 @connection.py:868 -
>> Connection built: host=subscription.rhsm.redhat.com port=443
>> handler=/subscription auth=identity_cert ca_dir=/etc/rhsm/ca/
>> insecure=False
>>
>> Loaded plugins: fastestmirror, product-id, subscription-manager
>>
>>
>>
>>
>> 2019-02-13 16:42:14,199 [WARNING] yum:17779:Dummy-18 @logutil.py:141 -
>> logging already initialized
>>
>>
>>
>> 2019-02-13 16:42:14,200 [ERROR] yum:17779:Dummy-18 @identity.py:145 -
>> Reload of consumer identity cert /etc/pki/consumer/cert.pem raised an
>> exception with msg: [Errno 2] No such file or directory:
>> '/etc/pki/consumer/key.pem'
>>
>> 2019-02-13 16:42:14,200 [INFO] yum:17779:Dummy-18 @connection.py:868 -
>> Connection built: host=subscription.rhsm.redhat.com port=443
>> handler=/subscription auth=identity_cert ca_dir=/etc/rhsm/ca/
>> insecure=False
>>
>> 2019-02-13 16:42:14,201 [INFO] yum:17779:Dummy-18 @repolib.py:471 - repos
>> updated: Repo updates
>>
>>
>>
>>
>>
>>
>>
>>
>> Total repo updates: 0
>>
>>
>>
>>
>> Updated
>>
>>
>>
>>
>> 
>>
>>
>>
>>
>> Added (new)
>>
>>
>>
>>
>> 
>>
>>
>>
>>
>> Deleted
>>
>>
>>
>>
>> 
>>
>>
>>
>>
>> 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@brian yum.repos.d]# yum repolist
>>
>>
>>
>>
>> Loaded plugins: enabled_repos_upload, fastestmirror, imgbased-persist,
>> package_upload, product-id, search-disabled-repos, subscription-manager,
>> vdsmupgrade
>>
>>
>> 2019-02-13 16:42:36,489 [ERROR] yum:17809:MainThread @identity.py:145 -
>> Reload of consumer identity cert /etc/pki/consumer/cert.pem raised an
>> exception with msg: [Errno 2] No such file or directory:
>> '/etc/pki/consumer/key.pem'
>>
>> 2019-02-13 16:42:36,490 [INFO] yum:17809:MainThread @connection.py:868 -
>> Connection built: host=subscription.rhsm.redhat.com port=443
>> handler=/subscription auth=identity_cert ca_dir=/etc/rhsm/ca/
>> insecure=False
>>
>> 2019-02-13 16:42:36,491 [INFO] yum:17809:MainThread @repolib.py:471 -
>> repos updated: Repo updates
>>
>>
>>
>>
>>
>>
>>
>>
>> Total repo updates: 0
>>
>>
>>
>>
>> Updated
>>
>>
>>
>>
>> 
>>
>>
>>
>>
>> Added (new)
>>
>>
>>
>>
>> 
>>
>>
>>
>>
>> Deleted
>>
>>
>>
>>
>> 
>>
>>
>>
>>
>> This system is not registered with an entitlement server. You can use
>> subscription-manager to register.
>>
>>
>>
>> Loading mirror speeds from cached hostfile
>>
>>
>>
>>
>>  * ovirt-4.2: mirrors.rit.edu
>>
>>
>>
>>
>>  * ovirt-4.2-epel: mirror.sjc02.svwh.net
>>
>>
>>
>>
>> repo id
>>
>>   repo name
>>
>> status
>> centos-sclo-rh-release/x86_64
>>
>>   CentOS-7 - SCLo rh
>>
>> 8,113
>> ovirt-4.2/7
>>
>>   Latest oVirt 4.2 Release
>>
>> 2,558
>> ovirt-4.2-centos-gluster312/x86_64
>>
>>  CentOS-7 - Gluster 3.12
>>
>>  262
>> ovirt-4.2-centos-opstools/x86_64
>>
>>  CentOS-7 - OpsTools - release
>>
>>  853
>> ovirt-4.2-centos-ovirt42/x86_64
>>
>>   CentOS-7 - oVirt 4.2
>>
>>   631
>> ovirt-4.2-centos-qemu-ev/x86_64
>>
>>   CentOS-7 - QEMU EV
>>
>>71
>> ovirt-4.2-epel/x86_64
>>
>>   Extra Packages for Enterprise Linux 7 - x86_64
>>
>>
>> *Help!*
>>
>>
>>
>> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to 

[ovirt-users] Re: Problem installing hyperconverged setup

2019-02-13 Thread Edward Berger
I don't believe the wizard followed your wishes if it comes up with 1005gb
for the thinpool.
500gb data + 500gb vmstore +5gb metadata = 1005gb

The wizard tries to do the same setup on all three gluster hosts.
So if you change anything, you have to "check and edit" the config file it
generates in all three locations
before deploy..

With only 450gb min-size-disk, I'd start over again, delete the data and
vmstore domains during the wizard setup
and bump up engine size to fill up the available space on the smallest disk
(400gb or so).

The other domains aren't necessary and you might want to give them their
own larger disks later.

On Wed, Feb 13, 2019 at 8:41 AM  wrote:

> Hi,
>
> I am currently setting up an Ovirt cluster in a test environment and
> cannot get the hyperconverged setup to run properly.  I have installed 3
> nodes on version 4.2.8.
>
> I keep getting the following error -
>
> TASK [Create LVs with specified size for the VGs]
> **
> failed: [node01.ovirt.local] (item={u'lv': u'gluster_thinpool_sdb',
> u'size': u'1005GB', u'extent': u'100%FREE', u'vg': u'gluster_vg_sdb'}) =>
> {"changed": false, "item": {"extent": "100%FREE", "lv":
> "gluster_thinpool_sdb", "size": "1005GB", "vg": "gluster_vg_sdb"}, "msg":
> "  WARNING: Pool zeroing and 3.00 MiB large chunk size slows down thin
> provisioning.\n  WARNING: Consider disabling zeroing (-Zn) or using smaller
> chunk size (<512.00 KiB).\n  Volume group \"gluster_vg_sdb\" has
> insufficient free space (157261 extents): 343040 required.\n", "rc": 5}
> to retry, use: --limit @/tmp/tmpbXqHhw/lvcreate.retry
>
> All 3 nodes have an /sdb installed which are different sizes but all in
> excess of 450Gb.  I have specified JBOD in the setup.
>
> I have tried reducing the size of the engine, data and vmstore bricks to
> 50Gb each instead of the default but the installation still fails.
>
> I think it has something to do with the thin provisioning but not sure
> what.
>
> Any help would be much appreciated.
>
> Thanks
> Paul.
> ___
> 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/BXNOIJCQHCOZCHEH4MLVB4F4AURGHBIZ/
>
___
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/4LQUWXCPNVTJWGH4UMO7WOVZRCGTBOPO/


[ovirt-users] Re: Error starting hosted engine

2019-02-12 Thread Edward Berger
ls -l /rhev/data-center/mnt/glusterSD/*/*/images/*
# any under "engine volume" that are owned by root chown and chmod as
vdsm:kvm 660

# then engine should be able to start.


On Tue, Feb 12, 2019 at 4:43 PM Endre Karlson 
wrote:

> I Also tried to run
> service vdsmd stop
> vdsm-tool configure --force
> service vdsmd start
>
> and then restart the ha agent on all nodes but it doesnt help, the
> upgraded to 4.3 node is still not able to start hte engine.
>
> / E
>
> Den tir. 12. feb. 2019 kl. 22:01 skrev Endre Karlson <
> endre.karl...@gmail.com>:
>
>> Yes that seems correct, but is there no way to work around it ?
>>
>> Den tir. 12. feb. 2019 kl. 06:24 skrev Sahina Bose :
>>
>>>
>>>
>>> On Tue, Feb 12, 2019 at 10:51 AM Endre Karlson 
>>> wrote:
>>>
 It's a upgrade from 4.2.x < latest version of 4.2 series. I upgraded by
 adding the 4.3 repo and doing the steps on the upgrade guide page
 https://www.ovirt.org/release/4.3.0/#centos--rhel

>>>
>>> Seems like you're running into
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1666795
>>>
>>>

 Den man. 11. feb. 2019 kl. 23:35 skrev Greg Sheremeta <
 gsher...@redhat.com>:

> Hi,
>
> Is this an upgrade or a fresh installation? What version? What
> installation or upgrade commands / methods did you use?
>
> Best wishes,
> Greg
>
>
>
> On Mon, Feb 11, 2019 at 5:11 PM Endre Karlson 
> wrote:
>
>> https://paste.ubuntu.com/p/BrmPYRKmzT/
>> https://paste.fedoraproject.org/paste/MjfioF9-Pzk02541abKyOw
>>
>> Seems like it's a error with vdsmd and glusterfs ?
>>
>> // Endre
>> ___
>> 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/OWKVL6PWBCPYPKD6QWQJERZDDRYRIUKU/
>>
>
>
> --
>
> GREG SHEREMETA
>
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>
> Red Hat NA
>
> 
>
> gsher...@redhat.comIRC: gshereme
> 
>
 ___
 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/LYXZVYVJAJFEBITTNQBNNF6WVTPNZJMJ/

>>> ___
> 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/P4Z7IQROW7RHX6TMWEQ6FCQ3KHN7X7NP/
>
___
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/DVX2Q67HLIULUFXRKSH6EK7FYB4FL6N4/


[ovirt-users] vGPU remote console problems

2019-02-12 Thread Edward Berger
A coworker and I are trying to bring up some nvidia vGPU VMs on ovirt 4.3,
but are experiencing issues with the remote consoles for both Windows and
Linux.

A windows10 VM for example works OK with a windows remote desktop client
after enabling the service inside the VM, but using the oVirt VM portal
spice/vnc seems to cause the mouse pointer to disappear and clicks seem to
go nowhere.

We're more likely to want linux VMs though.
CentOS not booting all the way to gnome desktop after installing the nvidia
driver.

What works well for you?
Are there known tweaks I should try to make?
Any helpful hints?

Thanks!
___
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/RVIAFYRBL6CUSKKBTXXK5E6GKO54XVHQ/


[ovirt-users] Re: unable to migrate hosted-engine to oVirt 4.3 updated nodes

2019-02-10 Thread Edward Berger
This has been fixed by finding the gluster volume(s) which were owned by
root instead of vdsm:kvm and chown-ing them to vdsm:kvm.  Afterwards the
engine was able to be migrated and the gluster volume heal engine
operations were able to succeed.


On Thu, Feb 7, 2019 at 12:03 AM Sahina Bose  wrote:

> On Thu, Feb 7, 2019 at 8:57 AM Edward Berger  wrote:
> >
> > I'm seeing migration failures for the hosted-engine VM from a 4.28 node
> to a 4.30 node so I can complete the node upgrades.
>
> You may be running into
> https://bugzilla.redhat.com/show_bug.cgi?id=1641798. Can you check the
> version of libvirt used on the nodes?
> >
> > In one case I tried to force an update on the last node and now have a
> cluster where the hosted-engine VM fails to start properly.   Sometimes
> something thinks the VM is running, but clicking for details it seems to
> have no disk.  I was so close to putting that one into production with
> working LDAP user logins and custom SSL cert and then Oops! with the
> upgrade.
> >
> > In both cases the hosted VM storage is on gluster.  One hyperconverged
> oVirt nodes, the other two nodes with an external gluster 5 server cluster
> >
> > I will note that I had set the engines previously (while at 4.2.8) to
> use the gluster direct method enabling (libgfapi disk access level 4.2)
> instead of the default fuse client for improved performance.
> >
> > Other details  Engine was updated first.
> > Nodes were updated with
> >
> > yum install
> https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/noarch/ovirt-node-ng-image-update-4.3.0-1.el7.noarch.rpm
> >
> > I forgot to mention another symptom.
> > On the hyperconverged cluster, the "gluster volume heal engine" command
> errors out on 4.3, but other gluster volumes accepted it.
>
> +Ravishankar Narayanankutty to check the heal failures
>
> >
> > rolling back to 4.28 allows the heal command to succeed (nothing to do
> actually) on engine, but I'm still unable to start a working engine VM with
> hosted-engine --vm-start
> >
> >
> > ___
> > 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/HFHLP473CFIMINFBUO4NH6WO3GPIQSVU/
>
___
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/6J3KALX3P46RHCF6APYGH62FBIMROFL5/


[ovirt-users] Re: HE doesn't install under nested virtualization

2019-02-08 Thread Edward Berger
But, I'm not sure the oVirt/qemu/libvirt/kvm software stack knows that, and
probably errs on the side of failure for unknown CPUs.

On Fri, Feb 8, 2019 at 2:55 PM Hetz Ben Hamo  wrote:

> Ryzen, Threadripper, EPYC - all have the same virtualization down to the
> last bit (the last option that you mentioned).
>
>
>
> On Fri, Feb 8, 2019 at 9:26 PM Edward Berger  wrote:
>
>> I'm wondering what cluster cpu compatibility version the Ryzen 2700 would
>> go under?
>> It used to default to Opteron G3 when I tried it before, which is now
>> "unsupported" as of ovirt 4.3.
>> CentOS 7 complains about "untested" CPU with Ryzen 2700 in my experience.
>> Maybe Fedora is better there.
>>
>> Here are what shows up in the available cluster options... I'm not sure
>> where and how its defined for specific CPUs.
>>
>>
>>- AMD Opteron G4
>>- AMD Opteron G5
>>- AMD EPYC
>>- AMD EPYC IBPB SSBD
>>
>>
>>
>> On Fri, Feb 8, 2019 at 2:07 PM Hetz Ben Hamo  wrote:
>>
>>> Yup, and nested is enabled.
>>>
>>> The HE is booting and starting to run, I get the status messages about
>>> starting etc, so it's not related to CPU functionality IMHO.
>>>
>>>
>>> On Fri, Feb 8, 2019 at 9:02 PM Greg Sheremeta 
>>> wrote:
>>>
>>>> Does amd require a nested flag set like Intel does?
>>>>
>>>> On Fri, Feb 8, 2019, 12:03 PM Hetz Ben Hamo  wrote:
>>>>
>>>>> Yes, that's the first thing I did and I checked in the VM that the kvm
>>>>> and kvm_amd module loaded.
>>>>>
>>>>>
>>>>> On Fri, Feb 8, 2019 at 6:42 PM femi adegoke 
>>>>> wrote:
>>>>>
>>>>>> Do you have your CPU type set for "host-passthrough"?
>>>>>>
>>>>>> On Feb 8 2019, at 8:25 am, Hetz Ben Hamo  wrote:
>>>>>>
>>>>>> I'm to setup an oVirt enviroment using virt-manager on Fedora 29 to
>>>>>> record some videos. For that - I'm using nested virtualization.
>>>>>>
>>>>>> The problem - after it's setting the HE - it goes up and down like
>>>>>> crazy (I defined the email setting to get all the messages) until it 
>>>>>> gives
>>>>>> up.
>>>>>>
>>>>>> enclosed - a gzipped vdsm.log.
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> 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/L45YCPOPV7DEC4KG7NEHTYRPJKN5EDOK/
>>>>>>
>>>>>> ___
>>>>> 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/XSNLP34EKMTB4NASFKMZXMXRZU4HFVXB/
>>>>>
>>>> ___
>>> 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/7H5VAMLDQRAJXSCLGBLTJKOZ62Y5NXVZ/
>>>
>>
___
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/JTM2MVQIL3QPQKYTKN2F52FSHNQBSM3Y/


[ovirt-users] Re: HE doesn't install under nested virtualization

2019-02-08 Thread Edward Berger
I'm wondering what cluster cpu compatibility version the Ryzen 2700 would
go under?
It used to default to Opteron G3 when I tried it before, which is now
"unsupported" as of ovirt 4.3.
CentOS 7 complains about "untested" CPU with Ryzen 2700 in my experience.
Maybe Fedora is better there.

Here are what shows up in the available cluster options... I'm not sure
where and how its defined for specific CPUs.

- AMD Opteron G4
- AMD Opteron G5
- AMD EPYC
- AMD EPYC IBPB SSBD


On Fri, Feb 8, 2019 at 2:07 PM Hetz Ben Hamo  wrote:

> Yup, and nested is enabled.
>
> The HE is booting and starting to run, I get the status messages about
> starting etc, so it's not related to CPU functionality IMHO.
>
>
> On Fri, Feb 8, 2019 at 9:02 PM Greg Sheremeta  wrote:
>
>> Does amd require a nested flag set like Intel does?
>>
>> On Fri, Feb 8, 2019, 12:03 PM Hetz Ben Hamo  wrote:
>>
>>> Yes, that's the first thing I did and I checked in the VM that the kvm
>>> and kvm_amd module loaded.
>>>
>>>
>>> On Fri, Feb 8, 2019 at 6:42 PM femi adegoke 
>>> wrote:
>>>
 Do you have your CPU type set for "host-passthrough"?

 On Feb 8 2019, at 8:25 am, Hetz Ben Hamo  wrote:

 I'm to setup an oVirt enviroment using virt-manager on Fedora 29 to
 record some videos. For that - I'm using nested virtualization.

 The problem - after it's setting the HE - it goes up and down like
 crazy (I defined the email setting to get all the messages) until it gives
 up.

 enclosed - a gzipped vdsm.log.


 ___
 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/L45YCPOPV7DEC4KG7NEHTYRPJKN5EDOK/

 ___
>>> 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/XSNLP34EKMTB4NASFKMZXMXRZU4HFVXB/
>>>
>> ___
> 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/7H5VAMLDQRAJXSCLGBLTJKOZ62Y5NXVZ/
>
___
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/2KXURZ5TJ3JBQELRPJ7BQNSNMBEDXLKS/


[ovirt-users] Re: unable to migrate hosted-engine to oVirt 4.3 updated nodes

2019-02-07 Thread Edward Berger
Ok, I'll check.
4.2.8 nodes
   libvirt.x86_644.5.0-10.el7_6.3
installed
4.3.0 upgraded nodes
  libvirt.x86_644.5.0-10.el7_6.4
installed


On Thu, Feb 7, 2019 at 12:03 AM Sahina Bose  wrote:

> On Thu, Feb 7, 2019 at 8:57 AM Edward Berger  wrote:
> >
> > I'm seeing migration failures for the hosted-engine VM from a 4.28 node
> to a 4.30 node so I can complete the node upgrades.
>
> You may be running into
> https://bugzilla.redhat.com/show_bug.cgi?id=1641798. Can you check the
> version of libvirt used on the nodes?
> >
> > In one case I tried to force an update on the last node and now have a
> cluster where the hosted-engine VM fails to start properly.   Sometimes
> something thinks the VM is running, but clicking for details it seems to
> have no disk.  I was so close to putting that one into production with
> working LDAP user logins and custom SSL cert and then Oops! with the
> upgrade.
> >
> > In both cases the hosted VM storage is on gluster.  One hyperconverged
> oVirt nodes, the other two nodes with an external gluster 5 server cluster
> >
> > I will note that I had set the engines previously (while at 4.2.8) to
> use the gluster direct method enabling (libgfapi disk access level 4.2)
> instead of the default fuse client for improved performance.
> >
> > Other details  Engine was updated first.
> > Nodes were updated with
> >
> > yum install
> https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/noarch/ovirt-node-ng-image-update-4.3.0-1.el7.noarch.rpm
> >
> > I forgot to mention another symptom.
> > On the hyperconverged cluster, the "gluster volume heal engine" command
> errors out on 4.3, but other gluster volumes accepted it.
>
> +Ravishankar Narayanankutty to check the heal failures
>
> >
> > rolling back to 4.28 allows the heal command to succeed (nothing to do
> actually) on engine, but I'm still unable to start a working engine VM with
> hosted-engine --vm-start
> >
> >
> > ___
> > 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/HFHLP473CFIMINFBUO4NH6WO3GPIQSVU/
>
___
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/UZWZGGO3LDBCIT4RRZHL2SKOVOA66Y5G/


[ovirt-users] unable to migrate hosted-engine to oVirt 4.3 updated nodes

2019-02-06 Thread Edward Berger
I'm seeing migration failures for the hosted-engine VM from a 4.28 node to
a 4.30 node so I can complete the node upgrades.

In one case I tried to force an update on the last node and now have a
cluster where the hosted-engine VM fails to start properly.   Sometimes
something thinks the VM is running, but clicking for details it seems to
have no disk.  I was so close to putting that one into production with
working LDAP user logins and custom SSL cert and then Oops! with the
upgrade.

In both cases the hosted VM storage is on gluster.  One hyperconverged
oVirt nodes, the other two nodes with an external gluster 5 server cluster

I will note that I had set the engines previously (while at 4.2.8) to use
the gluster direct method enabling (libgfapi disk access level 4.2) instead
of the default fuse client for improved performance.

Other details  Engine was updated first.
Nodes were updated with

yum install
https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/noarch/ovirt-node-ng-image-update-4.3.0-1.el7.noarch.rpm

I forgot to mention another symptom.
On the hyperconverged cluster, the "gluster volume heal engine" command
errors out on 4.3, but other gluster volumes accepted it.

rolling back to 4.28 allows the heal command to succeed (nothing to do
actually) on engine, but I'm still unable to start a working engine VM with
hosted-engine --vm-start
___
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/HFHLP473CFIMINFBUO4NH6WO3GPIQSVU/


[ovirt-users] glusterevents daemon fails after upgrade from 4.2.8 to 4.3

2019-02-06 Thread Edward Berger
 I upgraded some nodes from 4.28 to 4.3 and now when I look at the cockpit
"services"
tab I see a red failure for Gluster Events Notifier and clicking through I
get these messages below.

14:00
glustereventsd.service failed.
systemd
14:00
Unit glustereventsd.service entered failed state.
systemd
14:00
glustereventsd.service: main process exited, code=exited, status=1/FAILURE
systemd
14:00
ValueError: Attempted relative import in non-package
glustereventsd
14:00
from .eventsapiconf import (LOG_FILE,
glustereventsd
14:00
File "/usr/libexec/glusterfs/events/utils.py", line 29, in 
glustereventsd
14:00
import utils
glustereventsd
14:00
File "/usr/libexec/glusterfs/events/handlers.py", line 12, in 
glustereventsd
14:00
import handlers
glustereventsd
14:00
File "/usr/sbin/glustereventsd", line 24, in 
glustereventsd
___
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/K6N5EWVRPYRAXBUON2XNJVT5OH42PDEN/


[ovirt-users] oVirt 4.3 node-ng host kernel options for nvidia vGPU

2019-02-05 Thread Edward Berger
Hi,
One of our projects wants to try offering VMs with nvidia vGPU.

My co-worker had some problems before, so I thought I'd try the latest 4.3
ovirt-node-ng.

In the "Edit Host" -> kernel dialog I see two promising checkbox options
Hostdev Passthrough & SR-IOV (which adds to kernel line intel_iommu=on)
  and
Blacklist Nouveau (which adds to kernel line rdblacklist=nouveau)

but they seem to be acting as mutually exclusive options, when both are
selected
the kernel command line box is outlined in red and I can't continue on.
Am I wrong to want both options?
___
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/EMZRVQ536NQUTRAUPNK36YT5FCJTE6AL/


[ovirt-users] Re: ovirt-node 4.2 iso - hyperconverged wizard doesn't write gdeployConfig settings

2019-02-04 Thread Edward Berger
On each host you should check if systemctl status glusterd shows "enabled"
and whatever is the gluster events daemon. (I'm not logged in to look right
now)

I'm not sure which part of gluster-wizard or hosted-engine engine
installation is supposed to do the enabling, but I've seen where incomplete
installs left it disabled.

If the gluster servers haven't come up properly then there's no working
image for engine.
I had a situation where it was in a "paused" state and I had to run
"hosted-engine --vm-status" on possible nodes to find which one has VM in
paused state
then log into that node and run this command..

virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf
resume HostedEngine


On Mon, Feb 4, 2019 at 3:23 PM feral  wrote:

> On that note, have you also had issues with gluster not restarting on
> reboot, as well as all of the HA stuff failing on reboot after power loss?
> Thus far, the only way I've got the cluster to come back to life, is to
> manually restart glusterd on all nodes, then put the cluster back into "not
> mainentance" mode, and then manually starting the hosted-engine vm. This
> also fails after 2 or 3 power losses, even though the entire cluster is
> happy through the first 2.
>
> On Mon, Feb 4, 2019 at 12:21 PM feral  wrote:
>
>> Yea, I've been able to build a config manually myself, but sure would be
>> nice if the gdeploy worked (at all), as it takes an hour to deploy every
>> test, and manually creating the conf, I have to be super conservative about
>> my sizes, as I'm still not entirely sure what the deploy script actually
>> does. IE: I've got 3 nodes with 1.2TB for the gluster each, but if I try to
>> build a deployment to make use of more than 900GB, it fails as it's
>> creating the thinpool with whatever size it wants.
>>
>> Just wanted to make sure I wasn't the only one having this issue. Given
>> we know at least two people have noticed, who's the best to contact? I
>> haven't been able to get any response from devs on any of (the myriad)  of
>> issues with the 4.2.8 image.
>> Also having a ton of strange issues with the hosted-engine vm deployment.
>>
>> On Mon, Feb 4, 2019 at 11:59 AM Edward Berger 
>> wrote:
>>
>>> Yes, I had that issue with an 4.2.8 installation.
>>> I had to manually edit the "web-UI-generated" config to be anywhere
>>> close to what I wanted.
>>>
>>> I'll attach an edited config as an example.
>>>
>>> On Mon, Feb 4, 2019 at 2:51 PM feral  wrote:
>>>
>>>> New install of ovirt-node 4.2 (from iso). Setup each node with
>>>> networking and ssh keys, and use the hyperconverged gluster deployment
>>>> wizard. None of the user specified settings are ever reflected in the
>>>> gdeployConfig.conf.
>>>> Anyone running into this?
>>>>
>>>> --
>>>> _
>>>> Fact:
>>>> 1. Ninjas are mammals.
>>>> 2. Ninjas fight ALL the time.
>>>> 3. The purpose of the ninja is to flip out and kill people.
>>>> ___
>>>> 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/TF56FSFRNGCWEM4VJFOGKKAELJ3ID7NR/
>>>>
>>>
>>
>> --
>> _
>> Fact:
>> 1. Ninjas are mammals.
>> 2. Ninjas fight ALL the time.
>> 3. The purpose of the ninja is to flip out and kill people.
>>
>
>
> --
> _
> Fact:
> 1. Ninjas are mammals.
> 2. Ninjas fight ALL the time.
> 3. The purpose of the ninja is to flip out and kill people.
>
___
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/5WONWLWDFCWGL7HCEKZXEQVY76QTPOLS/


[ovirt-users] Re: ovirt-node 4.2 iso - hyperconverged wizard doesn't write gdeployConfig settings

2019-02-04 Thread Edward Berger
Yes, I had that issue with an 4.2.8 installation.
I had to manually edit the "web-UI-generated" config to be anywhere close
to what I wanted.

I'll attach an edited config as an example.

On Mon, Feb 4, 2019 at 2:51 PM feral  wrote:

> New install of ovirt-node 4.2 (from iso). Setup each node with networking
> and ssh keys, and use the hyperconverged gluster deployment wizard. None of
> the user specified settings are ever reflected in the gdeployConfig.conf.
> Anyone running into this?
>
> --
> _
> Fact:
> 1. Ninjas are mammals.
> 2. Ninjas fight ALL the time.
> 3. The purpose of the ninja is to flip out and kill people.
> ___
> 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/TF56FSFRNGCWEM4VJFOGKKAELJ3ID7NR/
>
#gdeploy configuration generated by cockpit-gluster plugin
# edited by Ed B. 1-24-2019

[hosts]
10.200.0.131
10.200.0.134
10.200.0.135

[script1:10.200.0.131]
action=execute
ignore_script_errors=no
file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d md1 -h 10.200.0.131, 
10.200.0.134, 10.200.0.135

[script1:10.200.0.134]
action=execute
ignore_script_errors=no
file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d md1 -h 10.200.0.131, 
10.200.0.134, 10.200.0.135

[script1:10.200.0.135]
action=execute
ignore_script_errors=no
file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d md1 -h 10.200.0.131, 
10.200.0.134, 10.200.0.135

[disktype]
raid10

[diskcount]
8

[stripesize]
256

[service1]
action=enable
service=chronyd

[service2]
action=restart
service=chronyd

[shell2]
action=execute
command=vdsm-tool configure --force

[script3]
action=execute
file=/usr/share/gdeploy/scripts/blacklist_all_disks.sh
ignore_script_errors=no

[pv1:10.200.0.131]
action=create
devices=md1
ignore_pv_errors=no

[pv1:10.200.0.134]
action=create
devices=md1
ignore_pv_errors=no

[pv1:10.200.0.135]
action=create
devices=md1
ignore_pv_errors=no

[vg1:10.200.0.131]
action=create
vgname=gluster_vg_md1
pvname=md1
ignore_vg_errors=no

[vg1:10.200.0.134]
action=create
vgname=gluster_vg_md1
pvname=md1
ignore_vg_errors=no

[vg1:10.200.0.135]
action=create
vgname=gluster_vg_md1
pvname=md1
ignore_vg_errors=no

[lv1:10.200.0.131]
action=create
poolname=gluster_thinpool_md1
ignore_lv_errors=no
vgname=gluster_vg_md1
lvtype=thinpool
size=12000GB
poolmetadatasize=16GB

[lv2:10.200.0.134]
action=create
poolname=gluster_thinpool_md1
ignore_lv_errors=no
vgname=gluster_vg_md1
lvtype=thinpool
size=12000GB
poolmetadatasize=16GB

[lv3:10.200.0.135]
action=create
poolname=gluster_thinpool_md1
ignore_lv_errors=no
vgname=gluster_vg_md1
lvtype=thinpool
size=12000GB
poolmetadatasize=16GB

[lv4:10.200.0.131]
action=create
lvname=gluster_lv_engine
ignore_lv_errors=no
vgname=gluster_vg_md1
mount=/gluster_bricks/engine
size=2048GB
lvtype=thick

[lv5:10.200.0.131]
action=create
lvname=gluster_lv_data
ignore_lv_errors=no
vgname=gluster_vg_md1
mount=/gluster_bricks/data
lvtype=thinlv
poolname=gluster_thinpool_md1
virtualsize=9800GB

[lv6:10.200.0.131]
action=create
lvname=gluster_lv_vmstore
ignore_lv_errors=no
vgname=gluster_vg_md1
mount=/gluster_bricks/vmstore
lvtype=thinlv
poolname=gluster_thinpool_md1
virtualsize=2048GB

[lv7:10.200.0.134]
action=create
lvname=gluster_lv_engine
ignore_lv_errors=no
vgname=gluster_vg_md1
mount=/gluster_bricks/engine
size=2048GB
lvtype=thick

[lv8:10.200.0.134]
action=create
lvname=gluster_lv_data
ignore_lv_errors=no
vgname=gluster_vg_md1
mount=/gluster_bricks/data
lvtype=thinlv
poolname=gluster_thinpool_md1
virtualsize=9800GB

[lv9:10.200.0.134]
action=create
lvname=gluster_lv_vmstore
ignore_lv_errors=no
vgname=gluster_vg_md1
mount=/gluster_bricks/vmstore
lvtype=thinlv
poolname=gluster_thinpool_md1
virtualsize=2048GB

[lv10:10.200.0.135]
action=create
lvname=gluster_lv_engine
ignore_lv_errors=no
vgname=gluster_vg_md1
mount=/gluster_bricks/engine
size=2048GB
lvtype=thick

[lv11:10.200.0.135]
action=create
lvname=gluster_lv_data
ignore_lv_errors=no
vgname=gluster_vg_md1
mount=/gluster_bricks/data
lvtype=thinlv
poolname=gluster_thinpool_md1
virtualsize=9800GB

[lv12:10.200.0.135]
action=create
lvname=gluster_lv_vmstore
ignore_lv_errors=no
vgname=gluster_vg_md1
mount=/gluster_bricks/vmstore
lvtype=thinlv
poolname=gluster_thinpool_md1
virtualsize=2048GB

[selinux]
yes

[service3]
action=restart
service=glusterd
slice_setup=yes

[firewalld]
action=add
ports=111/tcp,2049/tcp,54321/tcp,5900/tcp,5900-6923/tcp,5666/tcp,16514/tcp,54322/tcp
services=glusterfs

[script2]
action=execute
file=/usr/share/gdeploy/scripts/disable-gluster-hooks.sh

[shell3]
action=execute
command=usermod -a -G gluster qemu

[volume1]
action=create
volname=engine
transport=tcp
replica=yes
replica_count=3

[ovirt-users] Re: host NonResponsive after trying to update network MTUs

2019-01-31 Thread Edward Berger
 I've ended up resetting engine's MTU and reverting the MTU on ovirtmgmt to
1500 and resyncing all the host nodes.
The underlying NIC MTU was still 9000 for other VLANs.
Afterwards, the host is available again and was able to install with engine
deploy enabled.

Maybe the network switch|router is misconfigured?
I don't have the direct access to examine it.
The symptom was that ssh host to engine, or the other way, would connect
but hang before completing negotiations.
This caused the "unresponsive" host problems.

On Wed, Jan 30, 2019 at 5:02 AM Sahina Bose  wrote:

> On Tue, Jan 29, 2019 at 10:05 PM Edward Berger 
> wrote:
> >
> > Done. It still won't let me remove the host.
> > clicked maintenance, checked ignore gluster... box.
> > clicked remove.  got popup " track00.yard.psc.edu:
> >
> > Cannot remove Host. Server having Gluster volume."
>
> If the server has bricks, the only option to remove the host is to
> replace/remove the bricks.
> Can you try reinstall of host instead?
>
> >
> >
> > On Tue, Jan 29, 2019 at 4:24 AM Sahina Bose  wrote:
> >>
> >> On Mon, Jan 28, 2019 at 7:31 AM Edward Berger 
> wrote:
> >> >
> >> > I have a problem host which also is the one I deployed a
> hyperconverged oVirt node-ng cluster from with the cockpit's hyperconverged
> installation wizard.
> >> >
> >> > When I realized after deploying that I hadn't set the MTUs correctly
> for the engine-mgmt, associated vlan and eno.2 device and also for my
> infiniband interface ib0, I went in and tried to set them to new values
> 9000 and 65520 it got into some kind of hung state.
> >> >
> >> > The engine task window shows a task in "executing" and a never ending
> spinning widget
> >> > "Handing non responsive Host track00..."
> >> >
> >> > I can tried updating the hosts /etc/sysconfig/network-scripts by hand.
> >> > I've tried every combination of the engines set host in maintenance
> mode , "sync networks" "refresh host capabilities" activating and
> rebooting, but I'm still stuck with an unresponsive host.
> >> >
> >> > I had another host that also failed but it allowed me to put it into
> maintenance mode and then remove it from the cluster and "add new" it back
> and it was happy.
> >> >
> >> > This one won't let me remove it because its serving the gluster
> volume mount point, even though I did give the mount options for the 2nd
> and 3rd backup volume servers.
> >> >
> >> > I'd appreciate any help restoring it to proper working order.
> >>
> >> Can you try removing the host after checking the "Ignore quorum loss
> ..." box?
> >>
> >> >
> >> > I'm attaching the gzip'd engine log.
> >> > ___
> >> > 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/HT2G345VWDWSIQDAYLFI55S6VE6HGGCA/
>
___
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/OCHCMI74EJFPGZ4NNHQIMI5TLCDBOA7B/


[ovirt-users] Re: host NonResponsive after trying to update network MTUs

2019-01-29 Thread Edward Berger
Done. It still won't let me remove the host.
clicked maintenance, checked ignore gluster... box.
clicked remove.  got popup " track00.yard.psc.edu:

   - Cannot remove Host. Server having Gluster volume."


On Tue, Jan 29, 2019 at 4:24 AM Sahina Bose  wrote:

> On Mon, Jan 28, 2019 at 7:31 AM Edward Berger  wrote:
> >
> > I have a problem host which also is the one I deployed a hyperconverged
> oVirt node-ng cluster from with the cockpit's hyperconverged installation
> wizard.
> >
> > When I realized after deploying that I hadn't set the MTUs correctly for
> the engine-mgmt, associated vlan and eno.2 device and also for my
> infiniband interface ib0, I went in and tried to set them to new values
> 9000 and 65520 it got into some kind of hung state.
> >
> > The engine task window shows a task in "executing" and a never ending
> spinning widget
> > "Handing non responsive Host track00..."
> >
> > I can tried updating the hosts /etc/sysconfig/network-scripts by hand.
> > I've tried every combination of the engines set host in maintenance mode
> , "sync networks" "refresh host capabilities" activating and rebooting, but
> I'm still stuck with an unresponsive host.
> >
> > I had another host that also failed but it allowed me to put it into
> maintenance mode and then remove it from the cluster and "add new" it back
> and it was happy.
> >
> > This one won't let me remove it because its serving the gluster volume
> mount point, even though I did give the mount options for the 2nd and 3rd
> backup volume servers.
> >
> > I'd appreciate any help restoring it to proper working order.
>
> Can you try removing the host after checking the "Ignore quorum loss ..."
> box?
>
> >
> > I'm attaching the gzip'd engine log.
> > ___
> > 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/HT2G345VWDWSIQDAYLFI55S6VE6HGGCA/
>
___
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/5J4AVNG3UC7RJWHSW7X5GMHXGJBNZGXP/


[ovirt-users] Re: host NonResponsive after trying to update network MTUs

2019-01-28 Thread Edward Berger
After changing the engine's MTU and ifdown eth0 && ifup eth0, the host is
now able to get capabilities and resync the hosts' networks, and allows the
host to be activated.

However I have a new problem.  During the course of fighting the above, I
"undeployed" hosted-engine, and now it looks it seems to freeze when I try
to reinstall with engine deploy... It eventually times out with a failure.


On Sun, Jan 27, 2019 at 8:59 PM Edward Berger  wrote:

> I have a problem host which also is the one I deployed a hyperconverged
> oVirt node-ng cluster from with the cockpit's hyperconverged installation
> wizard.
>
> When I realized after deploying that I hadn't set the MTUs correctly for
> the engine-mgmt, associated vlan and eno.2 device and also for my
> infiniband interface ib0, I went in and tried to set them to new values
> 9000 and 65520 it got into some kind of hung state.
>
> The engine task window shows a task in "executing" and a never ending
> spinning widget
> "Handing non responsive Host track00..."
>
> I can tried updating the hosts /etc/sysconfig/network-scripts by hand.
> I've tried every combination of the engines set host in maintenance mode ,
> "sync networks" "refresh host capabilities" activating and rebooting, but
> I'm still stuck with an unresponsive host.
>
> I had another host that also failed but it allowed me to put it into
> maintenance mode and then remove it from the cluster and "add new" it back
> and it was happy.
>
> This one won't let me remove it because its serving the gluster volume
> mount point, even though I did give the mount options for the 2nd and 3rd
> backup volume servers.
>
> I'd appreciate any help restoring it to proper working order.
>
> I'm attaching the gzip'd engine log.
>
___
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/UX2HLMQW6SIDCUS7ESSXV22NYZYGIHKU/


[ovirt-users] aquantia 107 (10Gbase-T NIC) driver for oVirt node-ng?

2018-10-18 Thread Edward Berger
I'm not sure where to send a request for including the current Aquantia 107
(10GbaseT nic) driver to be included in the ovirt-node-ng image.  I don't
see a centos RPM for kmod-redhat-atlantic, apparently there's a scientific
linux rpm available for download.
___
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/5JONAJMDG2C6DMW2EY5URSUZIDD5TQQU/


[ovirt-users] Re: Windows vm and cpu type

2018-08-31 Thread Edward Berger
For my cluster, I changed the bios settings to enable the AES instruction
on each node,
one at a time, after migrating VMs to other nodes and back when done,
then I was able to upgrade the cluster CPU type to the appropriate westmere
when they were all updated.

I'm not sure if something else might need enabled for libvirt and newer
CPUs.

As a side note, I did have problems installing Server2016 on a real nehalem
CPU VM,
where it would become unresponsive, so the test for newer Nehalem is there
for good reason.
The lack of AES instruction test is what's used to give nehalem for the cpu
type.

On Fri, Aug 31, 2018 at 10:52 AM carl langlois 
wrote:

> most of my cpu are
> Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz
>
> so yes it is newer..Not sure how to resolve this.
>
> On Tue, Aug 28, 2018 at 2:29 PM Edward Berger  wrote:
>
>> Is your CPU really nehalem or is it something newer?
>> cat /proc/cpuinfo and google the model if you're not sure.
>>
>> For my E5650 servers I found I had to go into the BIOS and enable some
>> AES instruction
>> before the oVirt node (actually libvirt) detected the CPU type as newer
>> than Nehalem.
>>
>>
>> On Tue, Aug 28, 2018 at 10:04 AM carl langlois 
>> wrote:
>>
>>> Hi all,
>>>
>>> I am trying to create a windows VM on my cluster that is set with cpu
>>> type to Nehalem. The probleme is that ovirt tell me that the guest os does
>>> not support this cpu..
>>>
>>> What is the best ways to fix it without impacting my 41 running vms?.
>>>
>>> Thanks
>>>
>>> Regards
>>>
>>>
>>> ___
>>> 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/IUWS6CERIOTXMVLGA4WIEGHDDPF6YMSI/
>>>
>>
___
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/B2ROGIMMH7ESUNDD7UNJ7ZDKYYSCOTXG/


[ovirt-users] Re: Windows vm and cpu type

2018-08-28 Thread Edward Berger
Is your CPU really nehalem or is it something newer?
cat /proc/cpuinfo and google the model if you're not sure.

For my E5650 servers I found I had to go into the BIOS and enable some AES
instruction
before the oVirt node (actually libvirt) detected the CPU type as newer
than Nehalem.


On Tue, Aug 28, 2018 at 10:04 AM carl langlois 
wrote:

> Hi all,
>
> I am trying to create a windows VM on my cluster that is set with cpu type
> to Nehalem. The probleme is that ovirt tell me that the guest os does not
> support this cpu..
>
> What is the best ways to fix it without impacting my 41 running vms?.
>
> Thanks
>
> Regards
>
>
> ___
> 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/IUWS6CERIOTXMVLGA4WIEGHDDPF6YMSI/
>
___
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/SYON7NBRC25NZAHZP5THSBQJCYCEELA3/


[ovirt-users] Re: [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable to resolve address\n"}

2018-08-10 Thread Edward Berger
I saw something like this also.

The new ansible based installation tries to verify hostnames using the
getent command
with something like...
   getent ahostsv4 hostname.domain | grep hostname.domain

In my case that failed to pickup a cname I wanted to use, even though
nslookup hostname.domain
returns a valid IP address for it.


On Thu, Aug 9, 2018 at 10:57 PM, Ariez Ahito 
wrote:

> failed hosted-engine deployment
>
> i tried using command line but encountered this error
>
> i also tried downloading ovirt-node iso and using WEBUI but encountered
> same problem
>
> i deployed this hosted-engine 3.5 without any problems.
>
> any thoughts?
> ___
> 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/WW2NFYHW2RGIWQU4HJVOOKHBJ7RIDLOL/
>
___
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/6D2AUPWZDCOVZ2D2EL3CX2RZW77MIZNH/