Hi Jim,
I don't have any targeted suggestions, because there isn't much to latch on to.
I can say Gluster replica three (no arbiters) on dedicated servers serving a
couple Ovirt VM clusters here have not had these sorts of issues.
I suspect your long heal times (and the resultant long
> On May 3, 2018, at 12:42 AM, Yaniv Kaul wrote:
> Patches are welcome to improve the way oVirt uses Postgresql, supports
> various versions, etc.
> Can you give examples for some of the things you'd do differently?
A little pre-ramble - I was trying not to be offensive in
I've been down this road. Postgres won't lie about its version for you. If you
want to do this, you have to patch the Ovirt installer[1]. I stopped trying to
use my PG cluster at some point - the relationship between the installer and
the product combined with the overly restrictive
> On Mar 28, 2018, at 10:59 PM, Artem Tambovskiy
> wrote:
>
> Hi,
>
> How many hosts you have? Check hosted-engine.conf on all hosts including the
> one you have problem with and look if all host_id values are unique. It might
> happen that you have several hosts
I still can't resolve this issue.
I have a host that is stuck in a cycle; it will be marked non responsive, then
come back up, ending with an "finished activation" message in the GUI. Then it
repeats.
The root cause seems to be sanlock. I'm just unclear on why it started or how
to resolve
Hello,
Have an issue that feels sanlock related, but I can't get sorted with our
installation. This is 4.2.1, hosted engine. One of our hosts is stuck in a
loop. It:
- gets a VDSM GetStatsVDS timeout, is marked as down,
- throws a warning about not being fenced (because that's not enabled
> On Mar 20, 2018, at 5:00 AM, Alexander Wels <aw...@redhat.com> wrote:
>
> On Monday, March 19, 2018 7:47:00 PM EDT Jamie Lawrence wrote:
>> So, uploading from one of the hosts to an ISO domain claims success, and
>> manually checking shows the ISO uploaded jus
Hello,
I'm trying to iron out the last few oddities of this setup, and one of them is
the iso upload process. This worked in the last rebuild, but... well.
So, uploading from one of the hosts to an ISO domain claims success, and
manually checking shows the ISO uploaded just fine, perms set
I missed this when you sent it; apologies for the delay.
> On Feb 13, 2018, at 12:11 AM, Ondra Machacek <omach...@redhat.com> wrote:
>
> Hello,
>
> On 02/09/2018 08:17 PM, Jamie Lawrence wrote:
>> Hello,
>> I'm bringing up a new 4.2 cluster and would like to us
Hello,
I have a sanlock problem. I don't fully understand the logs, but from what I
can gather, messages like this means it ain't working.
2018-02-16 14:51:46 22123 [15036]: s1 renewal error -107 delta_length 0
last_success 22046
2018-02-16 14:51:47 22124 [15036]: 53977885 aio collect RD
> On Feb 14, 2018, at 1:27 AM, Simone Tiraboschi <stira...@redhat.com> wrote:
> On Wed, Feb 14, 2018 at 2:11 AM, Jamie Lawrence <jlawre...@squaretrade.com>
> wrote:
> Hello,
>
> I'm seeing the hosted engine install fail on an Ansible playbook step. Log
> b
Hello,
I'm seeing the hosted engine install fail on an Ansible playbook step. Log
below. I tried looking at the file specified for retry, below
(/usr/share/ovirt-hosted-engine-setup/ansible/bootstrap_local_vm.retry); it
contains the word, 'localhost'.
The log below didn't contain anything I
Hello,
I'm bringing up a new 4.2 cluster and would like to use LDAP auth. Our LDAP
servers are fine and function normally for a number of other services, but I
can't get this working.
Our LDAP setup requires startTLS and a login. That last bit seems to be where
the trouble is. After
> On Feb 1, 2018, at 1:21 AM, Yaniv Kaul wrote:
> The engine-backup utility is your friend and will properly back up for you
> everything you need.
Thanks, but that is an answer to a different question I didn't ask.
It does, implicitly, seem to indicate that there probably
Hello,
I currently have an Ovirt 4.1.8 installation with a hosted engine using Gluster
for storage, with the DBs hosted on a dedicated PG cluster.
For reasons[1], it seems possibly simpler for me to upgrade our installation by
reinstalling rather than upgrading. In this case, I can happily
I'm a bit out of date on the topic, but unless they have changed, avoid the
NUCs. I bought a couple but gave up on them because of a firmware bug (?
limitation, at least) that Intel said it won't fix. It causes a lockup on boot
if a monitor is not connected. I've been told that different
> On May 24, 2017, at 6:25 AM, supp...@jac-properties.com wrote:
>
> Which makes sense seeing as that's what Red Hat officially supports. It just
> made sense for our infrastructure to put it on our postgres cluster that is
> running 9.5.x. Unfortunately things like this happen sometimes when
> On May 14, 2017, at 3:35 AM, Yedidyah Bar David wrote:
> In addition to Yaniv's explanation below, can you explain why it was
> bad? That is, what software/process was broken by it? Please note that
> this is the CN of the CA's cert, not of the individual certs its signs
>
The key generated by the engine install ended up with a bad CN; it has a
five-digit number appended to the host name, and no SAN.
I've lived with this through setup, but now I'm getting close to prod use, and
need to clean up so that it is usable for general consumption. And the SPICE
HTML
Does anyone know the answer to the specific question below? I'm not asking for
workarounds to try; that approach has repeatedly gone nowhere and time is
becoming an issue for me. If I'm on the wrong track, I'd be happy to hear that,
too. (Well, not happy, but that would at least be progress.)
>
> On May 2, 2017, at 12:04 AM, Simone Tiraboschi <stira...@redhat.com> wrote:
>
>
>
> On Sat, Apr 29, 2017 at 1:11 AM, Jamie Lawrence <jlawre...@squaretrade.com>
> wrote:
> I’m wondering if I can do this a different way. Since it is already imported,
&g
I’m wondering if I can do this a different way. Since it is already imported, I
can create VMs, and the only other warning I’m getting in the logs is
unrelated, I’m thinking that the problem here is that something didn’t get
properly set in the DB, and I should be able to fix that manually.
In
> On Apr 27, 2017, at 12:12 AM, Simone Tiraboschi <stira...@redhat.com> wrote:
>
>
>
> On Tue, Apr 25, 2017 at 7:53 PM, Jamie Lawrence <jlawre...@squaretrade.com>
> wrote:
> Hi all,
>
> In my hopefully-near-complete quest to automate Ovirt configuratio
> On Apr 26, 2017, at 1:49 AM, Yaniv Kaul wrote:
> In my hopefully-near-complete quest to automate Ovirt configuration in our
> environment, I’m very close. One outstanding issue that remains is that, even
> though the hosted engine storage domain actually was imported and
> On Apr 21, 2017, at 6:38 AM, knarra <kna...@redhat.com> wrote:
>
> On 04/21/2017 06:34 PM, Jamie Lawrence wrote:
>>> On Apr 20, 2017, at 10:36 PM, knarra <kna...@redhat.com> wrote:
>>>> The installer claimed it did, but I believe it didn’t. Below the e
> On Apr 20, 2017, at 10:36 PM, knarra wrote:
>> The installer claimed it did, but I believe it didn’t. Below the error from
>> my original email, there’s the below (apologies for not including it
>> earlier; I missed it). Note: 04ff4cf1-135a-4918-9a1f-8023322f89a3 is the
> On Apr 20, 2017, at 9:18 AM, Simone Tiraboschi wrote:
> Could you please share the output of
> sudo -u vdsm sudo service sanlock status
That command line prompts for vdsm’s password, which it doesn’t have. But
output returned as root is below. Is that ‘operation not
> On Apr 19, 2017, at 11:35 PM, knarra <kna...@redhat.com> wrote:
>
> On 04/20/2017 03:15 AM, Jamie Lawrence wrote:
>> I trialed installing the hosted engine, following the instructions at
>> http://www.ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_E
So, tracing this further, I’m pretty sure this is something about sanlock.
As best I can tell this[1] seems to be the failure that is blocking importing
the pool, creating storage domains, importing the HE, etc. Contrary to the log,
sanlock is running; I verified it starts on system-boot and
I trialed installing the hosted engine, following the instructions at
http://www.ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_Engine/
. This is using Gluster as the backend storage subsystem.
Answer file at the end.
Per the docs,
"When the hosted-engine deployment script
I forget where I found it, likely somewhere in the code. But:
u: vdsm@ovirt
p: shibboleth
-j
> On Apr 14, 2017, at 3:58 PM, Konstantin Raskoshnyi wrote:
>
> Hi guys
>
> I'm trying to run virsh list (or any other virsh commands)
>
> virsh list
> Please enter your
> On Apr 12, 2017, at 1:31 AM, Evgenia Tokar wrote:
>
> Hi Jamie,
>
> Are you trying to setup hosted engine using the "hosted-engine --deploy"
> command, or are you trying to migrate existing he vm?
>
> For hosted engine setup you need to provide a clean storage domain,
Or at least, refusing to mount a dirty pool.
I have 4.1 set up, configured and functional, currently wired up with two VM
hosts and three Gluster hosts. It is configured with a (temporary) NFS data
storage domain, with the end-goal being two data domains on Gluster; one for
the hosted engine,
Or at least, refusing to mount a dirty pool. I’m having trouble getting the
hosted engine installed.
I have 4.1 set up, configured and functional, currently wired up with two VM
hosts and three Gluster hosts. It is configured with a (temporary) NFS data
storage domain, with the end-goal being
> On Mar 27, 2017, at 10:42 PM, Yedidyah Bar David wrote:
>> I know what I was doing is unsupported. I was wondering down the wrong
>> troubleshooting path for a bit there, but I think ultimately what I need is
>> also unsupported.
>>
>> It was because I was trying to push
> On Mar 25, 2017, at 10:57 PM, Yedidyah Bar David <d...@redhat.com> wrote:
>
> On Fri, Mar 24, 2017 at 3:08 AM, Jamie Lawrence
> <jlawre...@squaretrade.com> wrote:
[…]
>> Anyone know what I am missing?
>
> Probably OVESETUP_PROV
Hello,
I’m working on an answerfile for an unattended Ovirt install. The engine and
the data warehouse DBs live remotely. I think I have most of the relevant keys
defined, but appear to be missing one, because the installer is attempting to
manage a local Postgres. Log and error below. Keys
> On Jun 6, 2016, at 1:59 AM, Fabrice Bacchella
> wrote:
> I'm surprised, because in my mind, the default value are the least usefull
> version of each options. Why don't set them to good, useful values and let
> the user changed them to the opposite if there is
> On Apr 11, 2016, at 11:41 AM, Frank Thommen
> wrote:
>
> Thanks to all who answered. Brett brings it to the point: All sent links so
> far are indeed helpful - thanks a lot - but not the reference I expected.
>
I had the same issue a while back. Never figured it out, and don't have
much else useful to add, other than to say it isn't just you two.
-j
On Tue, Apr 5, 2016 at 3:22 AM, Alan Griffiths
wrote:
> Hi,
>
>
>
> I’m seeing the same PXE boot issue with 3.6.4 on Centos
> On Feb 18, 2016, at 11:45 PM, René Koch wrote:
>
> Hi Jamie,
>
> That reason for this is, that the iso will be mounted as long as you're in
> run once mode.
>
> You can fix this by powering off your vm after the installation and run it
> again in "normal" mode. As you
Hello all,
I’m running overt 3.6.0 on Centos 7.[1]
I’ve been working on getting Ovirt to slot in to our environment, and almost
have a setup that works. I can now build isos on demand for automated installs
(I’m working around some local networking choices without modifying them for
now,
Hello all,
I’d like to get the LDAP plugin working. We have a lovely LDAP setup deployed
(OpenLDAP), and nobody here has a clue how to map what we have to the options
the installer presents.
Well, a clue, yes.
We include the core, cosine, nis, inetorgperson and misc schemas in the config.
> On Dec 4, 2015, at 12:50 AM, Juan Hernández <jhern...@redhat.com> wrote:
>
> On 12/03/2015 10:59 PM, Jamie Lawrence wrote:
>>vm.set_os(params.OperatingSystem(cmdline=kernel_cmd))
>
> This line ^ is overwriting the complete OS configuration that you
Hello,
I’m currently playing with scripted VM creation and have an issue getting the
newly created VM to PXE boot. My objective is to port some creation scripts
from the environment this will eventually replace and worry about making this
more “Ovirt-ey” later.
Skipping the details,
[Snippage]
> On Nov 10, 2015, at 12:26 AM, Yedidyah Bar David wrote:
>>> IIUC engine-setup never fails on missing DNS resolution, only warns.
>
> Sorry, that was wrong. Let me sketch the flow:
[Nice writeup of the DNS test flow omitted]
>> I may well be missing something
Hi Alex,
On 6 Nov 2015, at 20:05, alexmcwhir...@triadic.us wrote:
Im using an older version of ovirt, so it may not apply. But i have
all of my systems setup with /etc/hosts and no DNS at all. The
installer complained, but it still installed and ran just fine.
Downing the interface you want
Hi all,
I’m having trouble finding current references to this problem. (I’m
seeing workarounds from 2013, but, not surprisingly, things have changed
since then.)
I’m attempting to run engine-setup, and get to the DNS reverse lookup
of the FQDN. The machine has two (bonded) interfaces, one
On Tue, Oct 20, 2015 at 1:51 AM, Dan Kenigsberg wrote:
> Until then, can you share your own use case for runnig LXC?
>
One use case that recently came up in discussion is in a build farm.
Lightweight containers with the possibility to use AUFS and RAM disks make
for fast,
49 matches
Mail list logo