Re: [ovirt-users] ReinitiaalizeFSM-EngineDown -- what does this mean?

2017-01-07 Thread Yedidyah Bar David 
On Sun, Jan 8, 2017 at 1:05 AM, Jim Kusznir  wrote:
> Hello:
>
> I've been getting a bunch of e-mails from my ovirt system stating that a
> "state transition" has occurred, first: StartState-ReinitalizeFSM, then a
> 2nd e-mail ReinitailzeFSM-EngineDown.
>
> These are all for my host2 system, my hosted engine is running on host1.
> Host2 appears to be working just fine, and has the majority of my VMs on it
> at the moment.
>
> Timing is also a bit wierd:  Got my first one at 12:05AM this morning, then
> 2:40, 2:55am, 4:20, 4:25, and 4:40am, then 7:11, 7:40, 9:51am and 12:26PM.
>
> I'd appreciate any insight!

Please check on each hosted-engine host:
/var/log/ovirt-hosted-engine-ha/agent.log .
You should be able to understand why the agent sent you these emails.
If you still
have questions, please attach the relevant parts of this log file.

Best,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to import KVM VM from oVirt web-ui

2017-01-07 Thread Tomáš Golembiovský 
On Sun, 8 Jan 2017 00:25:12 +0200
Nir Soffer  wrote:

> On Sat, Jan 7, 2017 at 5:11 PM, George Chlipala  wrote:
> > I am trying to import a VM from libvirt/KVM from the oVirt web UI
> > using the Virtual Machines > Import.   Here are the steps that I take.
> >
> > - I select "KVM (via Libvirt)" as source
> > - I set the URI as "qemu+ssh://root@/system".  I have
> > previously generated an SSH key for vdsm on the VM node and copied the
> > key to the libvirt host.
> > - I unlick "Require authentication" (using SSH keys)
> > - I select the proxy host as the VM host I setup vdsm with the ssh keys.
> > - Click "Load" to retrieve a list of VMs on the libvirt/KVM system
> > - Select the VMs to migrate and click the right arrow to move to the
> > right side of the wizard (Virtual Machines to Import)
> > - Click "Next"
> > - Select the proper storage domain, i.e. master storage domain.   (I
> > have tried both Preallocated and Thin-provisioned options for storage
> > and both fail to import.  I have also tried selecting "Clone" for the
> > VMs without success.)
> > - Click "OK"
> >
> > oVirt seems to start the import, but then gives a message that it
> > failed to import.  I have gone through the vdsm.log and this seems to
> > be the relevant lines...
> >
> > Thread-1123476::ERROR::2017-01-06 17:39:58,316::v2v::674::root::(_run)
> > Job u'60fc807f-e557-4526-aff7-c34e773a684c' failed
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 669, in _run
> > self._import()
> >   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 686, in _import
> > with self._command.execute() as self._proc:
> >   File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
> > return self.gen.next()
> >   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 591, in execute
> > with self._volumes(), self._password_file():
> >   File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
> > return self.gen.next()
> >   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 453, in
> > _password_file
> > os.write(fd, self._password.value)
> > TypeError: must be string or buffer, not None  
> 
> I think we solved this bug recently.

Yes, this is fixed in vdsm 4.18.21.

https://bugzilla.redhat.com/show_bug.cgi?id=1400527

As a workaround, uncheck the "Require authentication" checkbox, but also
fill the user name and password fields with some strings. You don't have
to enter any real values. Using "abcd" or "12345" is OK, the values will
not be used during the import.


> > Thread-1123476::ERROR::2017-01-06 17:39:58,316::v2v::681::root::(_run)
> > Job u'60fc807f-e557-4526-aff7-c34e773a684c', error trying to abort:
> > AttributeError("'NoneType' object has no attribute 'returncode'",)
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 678, in _run
> > self._abort()
> >   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 738, in _abort
> > if self._proc.returncode is None:
> > AttributeError: 'NoneType' object has no attribute 'returncode'  
> 
> Another bug.
> 
> Can you file a bug?
> https://bugzilla.redhat.com/enter_bug.cgi?product=vdsm
> 

There's probably no need to open the bug. The error is harmless and we
already have a patch pending for that.

https://gerrit.ovirt.org/#/c/67083/


> > Thread-1123477::ERROR::2017-01-06 17:39:58,351::v2v::674::root::(_run)
> > Job u'dc9a86ca-8ece-4c8a-b492-9bc2c8fc3409' failed
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 669, in _run
> > self._import()
> >
> > Here is some information about my installation.
> >
> > oVirt Engine Version: 4.0.5.5-1.el7.centos (hosted)
> >
> > Key packages on VM host/node.
> >
> > ovirt-engine-appliance-4.0-20161115.1.el7.centos.noarch
> > ovirt-hosted-engine-ha-2.0.4-1.el7.centos.noarch
> > ovirt-setup-lib-1.0.2-1.el7.centos.noarch
> > ovirt-imageio-common-0.4.0-1.el7.noarch
> > ovirt-host-deploy-1.5.3-1.el7.centos.noarch
> > ovirt-iso-uploader-4.0.2-1.el7.centos.noarch
> > ovirt-hosted-engine-setup-2.0.3-1.el7.centos.noarch
> > centos-release-ovirt40-1.0-1.el7.centos.noarch
> > ovirt-imageio-daemon-0.4.0-1.el7.noarch
> > python-ovirt-engine-sdk4-4.0.2-1.el7.centos.x86_64
> > ovirt-guest-tools-iso-4.0-1.fc23.noarch
> > ovirt-vmconsole-host-1.0.4-1.el7.centos.noarch
> > ovirt-engine-sdk-python-3.6.9.1-1.el7.centos.noarch
> > ovirt-release40-4.0.5-2.noarch
> > libgovirt-0.3.3-4.el7.x86_64
> > ovirt-vmconsole-1.0.4-1.el7.centos.noarch-4.18.15.3-1.el7.centos.x86_64
> >
> > Any help would be greatly appreciated.
> >
> > - George Chlipala
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users  
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] ReinitiaalizeFSM-EngineDown -- what does this mean?

2017-01-07 Thread Jim Kusznir 
Hello:

I've been getting a bunch of e-mails from my ovirt system stating that a
"state transition" has occurred, first: StartState-ReinitalizeFSM, then a
2nd e-mail ReinitailzeFSM-EngineDown.

These are all for my host2 system, my hosted engine is running on host1.
Host2 appears to be working just fine, and has the majority of my VMs on it
at the moment.

Timing is also a bit wierd:  Got my first one at 12:05AM this morning, then
2:40, 2:55am, 4:20, 4:25, and 4:40am, then 7:11, 7:40, 9:51am and 12:26PM.

I'd appreciate any insight!

--Jim
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] unable to start VMs after upgrade

2017-01-07 Thread Jim Kusznir 
Hello:

I'm still fairly new to ovirt.  I'm running a 3-node cluster largely built
by Jason Brooks' howto for ovirt+gluster on the contributed docs section of
the ovirt webpage.

I had everything mostly working, and this morning when I logged in, I saw a
new symbol attached to all three of my hosts indicating an upgrade is
available.  So I clicked on egine3 and told it to upgrade.  It migrated my
VMs off, did its upgrade, and everything looked good.  I was able to
migrate a vm or two back, and they continued to function just fine.

Then I tried to upgrade eingine1, which was running my hosted engine.  In
theory, all three engines/hosts were set up to be able to run the engine,
per Jason's instructions.  However, it failed to migrate the engine off
host1, and I realized that I still have the same issue I had on an earlier
incarnation of this cluster: inability to migrate the engine around.  Ok,
I'll deal with that later (with help from this list, hopefully).

I went on about the work I came in to do, and tried to start up a VM.  It
appeared to start, but it never booted.  It did  raise the CPU usage for
that VM, but console was all black, no resize or anything.  Tried several
settings.  This was on a VM I had just powered down.  I noticed it was
starting the VM on engine3, so I did a runonce specifying the vm start on
engine2.  Booted up just fine.  After booting, I could migrate to engine3,
and all was good.

What happened?  I get no error messages, starting any vm on engine3, start
paused, attaching display, then running it, I always get the same thing:
blank console, about 50% cpu usage reported by the web interface, no
response on any network, and by all signs available to me, no actual
booting (reminds me of a PC that doesn't POST).  Simply changing the engine
it starts on to one that has not been upgraded fixes the problem.

I'd greatly appreciate your help:

1) how to fix it so the upgraded engine can start VMs again
2) How to fix the cluster so the HostedEngine can migrate between hosts
(and I'm able to put host1 in maintence mode).

Ovirt 4 series, latest in repos as of last weekend (Jan1).

--Jim
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Disk move failures

2017-01-07 Thread Nir Soffer 
On Sat, Jan 7, 2017 at 11:36 AM, Pavel Gashev  wrote:
> The same is here. Upgrade vdsm to 4.17.35.
>
> -Original Message-
> From:  on behalf of Michael Watters 
> 
> Date: Saturday 7 January 2017 at 00:04
> To: "Users@ovirt.org" 
> Subject: [ovirt-users] Disk move failures
>
> I am receiving several LVM errors when attempting to move a disk from
> one storage domain to another.
>
>> VDSM ovirt-node-production2 command failed: Logical Volume extend
> failed
>
> vdsm.log shows a failure message as follows.
>
>> d6d4529e-db0d-49ac-a0c3-ee9d2e8cc9bb::ERROR::2017-01-06
> 15:05:54,926::image::405::Storage.Image::(_createTargetImage)
> Unexpected error
> Traceback (most recent call last):
>   File "/usr/share/vdsm/storage/image.py", line 394, in
> _createTargetImage
> dstVol.extend((volParams['apparentsize'] + 511) / 512)
>   File "/usr/share/vdsm/storage/blockVolume.py", line 310, in extend
> lvm.extendLV(self.sdUUID, self.volUUID, sizemb)
>   File "/usr/share/vdsm/storage/lvm.py", line 1179, in extendLV
> _resizeLV("lvextend", vgName, lvName, size)
>   File "/usr/share/vdsm/storage/lvm.py", line 1175, in _resizeLV
> raise se.LogicalVolumeExtendError(vgName, lvName, "%sM" % (size, ))
> LogicalVolumeExtendError: Logical Volume extend failed:
> 'vgname=32f7c737-c1ee-4d2e-82a7-1b5e6efe0cf8 lvname=7ec88b4b-e893-47dc-
> 895f-5f8e584ed2cf newsize=1024M'
>
> Does anybody know what would cause this?  I am able to create volumes
> and extend them from the command line without any issues.

Sounds like lvm changing exit code in backward incompatible way, revealing
incorrect error handling in vdsm:
https://github.com/oVirt/vdsm/commit/6fbdbe9e797733e4615cf33cd222ef9b0aae3158

Fixed in 4.17.35.

Nir

> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to import KVM VM from oVirt web-ui

2017-01-07 Thread Nir Soffer 
On Sat, Jan 7, 2017 at 5:11 PM, George Chlipala  wrote:
> I am trying to import a VM from libvirt/KVM from the oVirt web UI
> using the Virtual Machines > Import.   Here are the steps that I take.
>
> - I select "KVM (via Libvirt)" as source
> - I set the URI as "qemu+ssh://root@/system".  I have
> previously generated an SSH key for vdsm on the VM node and copied the
> key to the libvirt host.
> - I unlick "Require authentication" (using SSH keys)
> - I select the proxy host as the VM host I setup vdsm with the ssh keys.
> - Click "Load" to retrieve a list of VMs on the libvirt/KVM system
> - Select the VMs to migrate and click the right arrow to move to the
> right side of the wizard (Virtual Machines to Import)
> - Click "Next"
> - Select the proper storage domain, i.e. master storage domain.   (I
> have tried both Preallocated and Thin-provisioned options for storage
> and both fail to import.  I have also tried selecting "Clone" for the
> VMs without success.)
> - Click "OK"
>
> oVirt seems to start the import, but then gives a message that it
> failed to import.  I have gone through the vdsm.log and this seems to
> be the relevant lines...
>
> Thread-1123476::ERROR::2017-01-06 17:39:58,316::v2v::674::root::(_run)
> Job u'60fc807f-e557-4526-aff7-c34e773a684c' failed
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 669, in _run
> self._import()
>   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 686, in _import
> with self._command.execute() as self._proc:
>   File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
> return self.gen.next()
>   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 591, in execute
> with self._volumes(), self._password_file():
>   File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
> return self.gen.next()
>   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 453, in
> _password_file
> os.write(fd, self._password.value)
> TypeError: must be string or buffer, not None

I think we solved this bug recently.

> Thread-1123476::ERROR::2017-01-06 17:39:58,316::v2v::681::root::(_run)
> Job u'60fc807f-e557-4526-aff7-c34e773a684c', error trying to abort:
> AttributeError("'NoneType' object has no attribute 'returncode'",)
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 678, in _run
> self._abort()
>   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 738, in _abort
> if self._proc.returncode is None:
> AttributeError: 'NoneType' object has no attribute 'returncode'

Another bug.

Can you file a bug?
https://bugzilla.redhat.com/enter_bug.cgi?product=vdsm

> Thread-1123477::ERROR::2017-01-06 17:39:58,351::v2v::674::root::(_run)
> Job u'dc9a86ca-8ece-4c8a-b492-9bc2c8fc3409' failed
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 669, in _run
> self._import()
>
> Here is some information about my installation.
>
> oVirt Engine Version: 4.0.5.5-1.el7.centos (hosted)
>
> Key packages on VM host/node.
>
> ovirt-engine-appliance-4.0-20161115.1.el7.centos.noarch
> ovirt-hosted-engine-ha-2.0.4-1.el7.centos.noarch
> ovirt-setup-lib-1.0.2-1.el7.centos.noarch
> ovirt-imageio-common-0.4.0-1.el7.noarch
> ovirt-host-deploy-1.5.3-1.el7.centos.noarch
> ovirt-iso-uploader-4.0.2-1.el7.centos.noarch
> ovirt-hosted-engine-setup-2.0.3-1.el7.centos.noarch
> centos-release-ovirt40-1.0-1.el7.centos.noarch
> ovirt-imageio-daemon-0.4.0-1.el7.noarch
> python-ovirt-engine-sdk4-4.0.2-1.el7.centos.x86_64
> ovirt-guest-tools-iso-4.0-1.fc23.noarch
> ovirt-vmconsole-host-1.0.4-1.el7.centos.noarch
> ovirt-engine-sdk-python-3.6.9.1-1.el7.centos.noarch
> ovirt-release40-4.0.5-2.noarch
> libgovirt-0.3.3-4.el7.x86_64
> ovirt-vmconsole-1.0.4-1.el7.centos.noarch-4.18.15.3-1.el7.centos.x86_64
>
> Any help would be greatly appreciated.
>
> - George Chlipala
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Hosted Engine Update problems [SOLVED]

2017-01-07 Thread Gary Pedretty 
I tried the suggestion of deleting the postmaster.pid file after verifying that 
it was not locked by any process.  

Then I restarted postgres which succeeded and then restarted the engine VM.

The vm came up normally and passed the liveliness test.


Gary



Gary Pedrettyg...@ravnalaska.net 

Systems Manager  www.flyravn.com 

Ravn Alaska   /\907-450-7251
5245 Airport Industrial Road /  \/\ 907-450-7238 fax
Fairbanks, Alaska  99709/\  /\ \ Second greatest commandment
Serving All of Alaska  /  \/  /\  \ \/\   “Love your neighbor as
Really loving the record green up date! Summmer!!   yourself” Matt 22:39













> On Jan 7, 2017, at 12:01 PM, Gary Pedretty  wrote:
> 
> After more testing, I can get the engine vm to run manually with ha-agent 
> stopped.  It still fails the liveliness check.  Here is the repeating error 
> in the engine.log from the engine vm
> 
> ERROR [org.ovirt.engine.core.bll.Backend] (ServerService Thread Pool — 46) [] 
> Error in getting DB connection, database is inaccessible: Error retrieving 
> database metadata; nested exception is 
> org.springframework.jdbc.support.MetaDataAccessException: Could not get 
> Connection for extracting meta data; nested exception is 
> org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC 
> Connection; nested exception is java.sql.SQLException: 
> javax.resource.ResourceException: IJ000453: Unable to get managed connection 
> for java:/ENGINEDataSource
> 
> 
> Found a suggestion about trying a test connection to the database and get the 
> following.
> 
> [root@fai-kvm-engine ~]# psql --host localhost --port 5432 --user engine 
> --password engine
> Password for user engine:
> psql: could not connect to server: Connection refused
> Is the server running on host "localhost" (::1) and accepting
> TCP/IP connections on port 5432?
> could not connect to server: Connection refused
> Is the server running on host "localhost" (127.0.0.1) and accepting
> TCP/IP connections on port 5432?
> [root@fai-kvm-engine ~]#
> 
> and checking that postgresql is running shows 
> 
> [root@fai-kvm-engine ~]# systemctl status postgresql
> â— postgresql.service - PostgreSQL database server
>Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled; 
> vendor preset: disabled)
>Active: failed (Result: exit-code) since Sat 2017-01-07 20:58:04 UTC; 2s 
> ago
>   Process: 23867 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p 
> ${PGPORT} -w -t 300 (code=exited, status=1/FAILURE)
>   Process: 23860 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA} 
> (code=exited, status=0/SUCCESS)
> 
> Jan 07 20:58:03 fai-kvm-engine.ravnalaska.net 
>  systemd[1]: Starting PostgreSQL 
> database server...
> Jan 07 20:58:03 fai-kvm-engine.ravnalaska.net 
>  pg_ctl[23867]: pg_ctl: another server 
> might be running; trying to start server anyway
> Jan 07 20:58:03 fai-kvm-engine.ravnalaska.net 
>  pg_ctl[23867]: FATAL:  pre-existing 
> shared memory block (key 5432001, ID 0) is still in use
> Jan 07 20:58:03 fai-kvm-engine.ravnalaska.net 
>  pg_ctl[23867]: HINT:  If you're sure 
> there are no old server processes still running, remove the shared memory 
> block or just delete the file "postmaster.pid".
> Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net 
>  pg_ctl[23867]: pg_ctl: could not 
> start server
> Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net 
>  pg_ctl[23867]: Examine the log output.
> Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net 
>  systemd[1]: postgresql.service: 
> control process exited, code=exited status=1
> Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net 
>  systemd[1]: Failed to start 
> PostgreSQL database server.
> Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net 
>  systemd[1]: Unit postgresql.service 
> entered failed state.
> Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net 
>  systemd[1]: postgresql.service failed.
> 
> 
> 
> Gary Pedrettyg...@ravnalaska.net 
> 
> Systems Manager  www.flyravn.com 
> 
> Ravn Alaska

Re: [ovirt-users] Hosted Engine Update problems

2017-01-07 Thread Gary Pedretty 
After more testing, I can get the engine vm to run manually with ha-agent 
stopped.  It still fails the liveliness check.  Here is the repeating error in 
the engine.log from the engine vm

ERROR [org.ovirt.engine.core.bll.Backend] (ServerService Thread Pool — 46) [] 
Error in getting DB connection, database is inaccessible: Error retrieving 
database metadata; nested exception is 
org.springframework.jdbc.support.MetaDataAccessException: Could not get 
Connection for extracting meta data; nested exception is 
org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC 
Connection; nested exception is java.sql.SQLException: 
javax.resource.ResourceException: IJ000453: Unable to get managed connection 
for java:/ENGINEDataSource


Found a suggestion about trying a test connection to the database and get the 
following.

[root@fai-kvm-engine ~]# psql --host localhost --port 5432 --user engine 
--password engine
Password for user engine:
psql: could not connect to server: Connection refused
Is the server running on host "localhost" (::1) and accepting
TCP/IP connections on port 5432?
could not connect to server: Connection refused
Is the server running on host "localhost" (127.0.0.1) and accepting
TCP/IP connections on port 5432?
[root@fai-kvm-engine ~]#

and checking that postgresql is running shows 

[root@fai-kvm-engine ~]# systemctl status postgresql
â— postgresql.service - PostgreSQL database server
   Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled; vendor 
preset: disabled)
   Active: failed (Result: exit-code) since Sat 2017-01-07 20:58:04 UTC; 2s ago
  Process: 23867 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p 
${PGPORT} -w -t 300 (code=exited, status=1/FAILURE)
  Process: 23860 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA} 
(code=exited, status=0/SUCCESS)

Jan 07 20:58:03 fai-kvm-engine.ravnalaska.net systemd[1]: Starting PostgreSQL 
database server...
Jan 07 20:58:03 fai-kvm-engine.ravnalaska.net pg_ctl[23867]: pg_ctl: another 
server might be running; trying to start server anyway
Jan 07 20:58:03 fai-kvm-engine.ravnalaska.net pg_ctl[23867]: FATAL:  
pre-existing shared memory block (key 5432001, ID 0) is still in use
Jan 07 20:58:03 fai-kvm-engine.ravnalaska.net pg_ctl[23867]: HINT:  If you're 
sure there are no old server processes still running, remove the shared memory 
block or just delete the file "postmaster.pid".
Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net pg_ctl[23867]: pg_ctl: could not 
start server
Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net pg_ctl[23867]: Examine the log 
output.
Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net systemd[1]: postgresql.service: 
control process exited, code=exited status=1
Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net systemd[1]: Failed to start 
PostgreSQL database server.
Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net systemd[1]: Unit 
postgresql.service entered failed state.
Jan 07 20:58:04 fai-kvm-engine.ravnalaska.net systemd[1]: postgresql.service 
failed.



Gary Pedrettyg...@ravnalaska.net 

Systems Manager  www.flyravn.com 

Ravn Alaska   /\907-450-7251
5245 Airport Industrial Road /  \/\ 907-450-7238 fax
Fairbanks, Alaska  99709/\  /\ \ Second greatest commandment
Serving All of Alaska  /  \/  /\  \ \/\   “Love your neighbor as
Really loving the record green up date! Summmer!!   yourself” Matt 22:39













> On Jan 6, 2017, at 10:05 PM, Gary Pedretty  wrote:
> 
> I just tried running the most recent update that came out for Ovirt Hosted 
> Engine setup.  This is a glusterized setup with 4 hosts setup as per the 
> Documentation.   Each host had the icon showing upgrades available so I 
> started clicking upgrade for each host doing them one at time. 3 of them went 
> into maintenance fine, migrated their VMs and then activated when done.  The 
> last one to do was the one actually running the hosted-engine VM.  This host 
> also had one other VM.  It migrated the other VM just fine, but stalled 
> trying to migrate the hosted-engine.  Eventually the web interface became 
> non-responsive and I moved to command line.  I have tried everything to get 
> the engine to start up.  I have tried putting all the hosts in maintenance so 
> that I could selectively tell it to start the hosted-engine VM on one host 
> specifically, but each fails with the “Failed Liveliness error.  I have tried 
> restarting the ha agents, re-initializing the lockspace all with no success.  
> All my VMs are still running fine, I just cannot get the hosted-engine to 
> run.   I can if necessary shutdown

[ovirt-users] Unable to import KVM VM from oVirt web-ui

2017-01-07 Thread George Chlipala 
I am trying to import a VM from libvirt/KVM from the oVirt web UI
using the Virtual Machines > Import.   Here are the steps that I take.

- I select "KVM (via Libvirt)" as source
- I set the URI as "qemu+ssh://root@/system".  I have
previously generated an SSH key for vdsm on the VM node and copied the
key to the libvirt host.
- I unlick "Require authentication" (using SSH keys)
- I select the proxy host as the VM host I setup vdsm with the ssh keys.
- Click "Load" to retrieve a list of VMs on the libvirt/KVM system
- Select the VMs to migrate and click the right arrow to move to the
right side of the wizard (Virtual Machines to Import)
- Click "Next"
- Select the proper storage domain, i.e. master storage domain.   (I
have tried both Preallocated and Thin-provisioned options for storage
and both fail to import.  I have also tried selecting "Clone" for the
VMs without success.)
- Click "OK"

oVirt seems to start the import, but then gives a message that it
failed to import.  I have gone through the vdsm.log and this seems to
be the relevant lines...

Thread-1123476::ERROR::2017-01-06 17:39:58,316::v2v::674::root::(_run)
Job u'60fc807f-e557-4526-aff7-c34e773a684c' failed
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 669, in _run
self._import()
  File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 686, in _import
with self._command.execute() as self._proc:
  File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
return self.gen.next()
  File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 591, in execute
with self._volumes(), self._password_file():
  File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
return self.gen.next()
  File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 453, in
_password_file
os.write(fd, self._password.value)
TypeError: must be string or buffer, not None
Thread-1123476::ERROR::2017-01-06 17:39:58,316::v2v::681::root::(_run)
Job u'60fc807f-e557-4526-aff7-c34e773a684c', error trying to abort:
AttributeError("'NoneType' object has no attribute 'returncode'",)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 678, in _run
self._abort()
  File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 738, in _abort
if self._proc.returncode is None:
AttributeError: 'NoneType' object has no attribute 'returncode'
Thread-1123477::ERROR::2017-01-06 17:39:58,351::v2v::674::root::(_run)
Job u'dc9a86ca-8ece-4c8a-b492-9bc2c8fc3409' failed
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 669, in _run
self._import()

Here is some information about my installation.

oVirt Engine Version: 4.0.5.5-1.el7.centos (hosted)

Key packages on VM host/node.

ovirt-engine-appliance-4.0-20161115.1.el7.centos.noarch
ovirt-hosted-engine-ha-2.0.4-1.el7.centos.noarch
ovirt-setup-lib-1.0.2-1.el7.centos.noarch
ovirt-imageio-common-0.4.0-1.el7.noarch
ovirt-host-deploy-1.5.3-1.el7.centos.noarch
ovirt-iso-uploader-4.0.2-1.el7.centos.noarch
ovirt-hosted-engine-setup-2.0.3-1.el7.centos.noarch
centos-release-ovirt40-1.0-1.el7.centos.noarch
ovirt-imageio-daemon-0.4.0-1.el7.noarch
python-ovirt-engine-sdk4-4.0.2-1.el7.centos.x86_64
ovirt-guest-tools-iso-4.0-1.fc23.noarch
ovirt-vmconsole-host-1.0.4-1.el7.centos.noarch
ovirt-engine-sdk-python-3.6.9.1-1.el7.centos.noarch
ovirt-release40-4.0.5-2.noarch
libgovirt-0.3.3-4.el7.x86_64
ovirt-vmconsole-1.0.4-1.el7.centos.noarch-4.18.15.3-1.el7.centos.x86_64

Any help would be greatly appreciated.

- George Chlipala
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Disk move failures

2017-01-07 Thread Pavel Gashev 
The same is here. Upgrade vdsm to 4.17.35.

-Original Message-
From:  on behalf of Michael Watters 

Date: Saturday 7 January 2017 at 00:04
To: "Users@ovirt.org" 
Subject: [ovirt-users] Disk move failures

I am receiving several LVM errors when attempting to move a disk from
one storage domain to another. 

> VDSM ovirt-node-production2 command failed: Logical Volume extend
failed

vdsm.log shows a failure message as follows.

> d6d4529e-db0d-49ac-a0c3-ee9d2e8cc9bb::ERROR::2017-01-06
15:05:54,926::image::405::Storage.Image::(_createTargetImage)
Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/image.py", line 394, in
_createTargetImage
dstVol.extend((volParams['apparentsize'] + 511) / 512)
  File "/usr/share/vdsm/storage/blockVolume.py", line 310, in extend
lvm.extendLV(self.sdUUID, self.volUUID, sizemb)
  File "/usr/share/vdsm/storage/lvm.py", line 1179, in extendLV
_resizeLV("lvextend", vgName, lvName, size)
  File "/usr/share/vdsm/storage/lvm.py", line 1175, in _resizeLV
raise se.LogicalVolumeExtendError(vgName, lvName, "%sM" % (size, ))
LogicalVolumeExtendError: Logical Volume extend failed:
'vgname=32f7c737-c1ee-4d2e-82a7-1b5e6efe0cf8 lvname=7ec88b4b-e893-47dc-
895f-5f8e584ed2cf newsize=1024M'

Does anybody know what would cause this?  I am able to create volumes
and extend them from the command line without any issues.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] OVF disk errors

2017-01-07 Thread Pavel Gashev 
Michael,

oVirt 3.6 doesn't work well on CentOS 7.3. Upgrade vdsm to 4.17.35.

-Original Message-
From:  on behalf of Michael Watters 

Date: Thursday 5 January 2017 at 23:12
To: "users@ovirt.org" 
Subject: [ovirt-users] OVF disk errors

Hello,

I have two hosts in a cluster running ovirt 3.6 and I keep seeing
errors in the event log as follows.

Jan 5, 2017 2:34:01 PM

Host ovirt-node-production2 power management was verified successfully.

Jan 5, 2017 2:34:01 PM

Status of host ovirt-node-production2 was set to Up.

Jan 5, 2017 2:33:58 PM

Executing power management status on Host ovirt-node-production2 using Proxy 
Host ovirt-node-production1 and Fence Agent ipmilan:1.2.3.4

Jan 5, 2017 2:33:48 PM

Failed to update OVF disks c7c567a3-ebd5-4e3a-bf1e-66080e8a09b4, OVF data isn't 
updated on those OVF stores (Data Center Default, Storage Domain 
2-Production-Faster).

Jan 5, 2017 2:33:47 PM

Host ovirt-node-production2 is not responding. It will stay in Connecting 
state for a grace period of 104 seconds and after that an attempt to fence the 
host will be issued.

Jan 5, 2017 2:33:47 PM

Failed to update OVF disks 389bd0fe-804c-428d-9de1-640d83fe9a29, OVF data isn't 
updated on those OVF stores (Data Center Default, Storage Domain 
1-Production-Slower).

Jan 5, 2017 2:33:42 PM

VDSM ovirt-node-production2 command failed: Logical Volume extend failed


What concerns me the most is the last two errors.  I've verified that all disks 
are online and all volume groups are working as expected.  Is there a way to 
manually update an OVF disk?  Here is what the engine database shows for these 
disk IDs.


engine=# select * from storage_domains_ovf_info where ovf_disk_id = 
'c7c567a3-ebd5-4e3a-bf1e-66080e8a09b4' ;
  storage_domain_id   | status | ovf_disk_id
  | stored_ovfs_ids |last_updated
--++--+-+
 32f7c737-c1ee-4d2e-82a7-1b5e6efe0cf8 |  1 | 
c7c567a3-ebd5-4e3a-bf1e-66080e8a09b4 | | 2016-11-21 
13:48:55.756-05
(1 row)


engine=# select * from storage_domains_ovf_info where ovf_disk_id = 
'389bd0fe-804c-428d-9de1-640d83fe9a29' ;
  storage_domain_id   | status | ovf_disk_id
  | stored_ovfs_ids |last_updated
--++--+-+
 52e48bb6-e477-41fe-aa25-69fc04b47c98 |  1 | 
389bd0fe-804c-428d-9de1-640d83fe9a29 | | 2016-12-31 
00:13:58.924-05
(1 row)




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users