[ovirt-users] [Attention needed] GlusterFS repository down - affects CI / Installations

[Nadav Goldin]

Hi,
The GlusterFS repository became unavailable this morning, as a result all
Jenkins jobs that use the repository will fail, the common error would be:

>
> http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-7/noarch/repodata/repomd.xml:
> [Errno 14] HTTP Error 403 - Forbidden
>

Also, installations of oVirt will fail.

We are working on a solution and will update asap.

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

Re: [ovirt-users] [Attention needed] GlusterFS repository down - affects CI / Installations

[Ravishankar N]

@gluster infra  - FYI.

On 04/27/2016 02:20 PM, Nadav Goldin wrote:

Hi,
The GlusterFS repository became unavailable this morning, as a result 
all Jenkins jobs that use the repository will fail, the common error 
would be:



http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-7/noarch/repodata/repomd.xml:
[Errno 14] HTTP Error 403 - Forbidden


Also, installations of oVirt will fail.

We are working on a solution and will update asap.

Nadav.



___
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] [Gluster-infra] [Attention needed] GlusterFS repository down - affects CI / Installations

[Niels de Vos]

On Wed, Apr 27, 2016 at 02:30:57PM +0530, Ravishankar N wrote:
> @gluster infra  - FYI.
> 
> On 04/27/2016 02:20 PM, Nadav Goldin wrote:
> >Hi,
> >The GlusterFS repository became unavailable this morning, as a result all
> >Jenkins jobs that use the repository will fail, the common error would be:
> >
> >
> > http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-7/noarch/repodata/repomd.xml:
> >[Errno 14] HTTP Error 403 - Forbidden
> >
> >
> >Also, installations of oVirt will fail.

I thought oVirt moved to using the packages from the CentOS Storage SIG?
In any case, automated tests should probably use those instead of the
packages on download.gluster.org. We're trying to minimize the work
packagers need to do, and get the glusterfs and other components in the
repositories that are provided by different distributions.

For more details, see the quickstart for the Storage SIG here:
  https://wiki.centos.org/SpecialInterestGroup/Storage/gluster-Quickstart

HTH,
Niels


signature.asc
Description: PGP signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Keyboard mapping VNC

[Jonas Israelsson]

No one ?

I've tested now also with a hosted engine setup. Can't see there either 
that the keyboard layout information set in the web-ui ever reaches the VM.

Think we have a bug here.

Rgds,
Jonas

On 11/04/16 17:43, Jonas Israelsson wrote:

Greetings.

We are under the impression the the keyboard layout for the VNC-server 
is missing from a vm's xml definition, hence the same default layout 
is always used.


We therefore (just to test) created a small host hook adding a static 
keyboard layout, and with the hook, it seem to work as expected as the 
-k switch to kvm is now populated.


vm started with our hook

  passwd='***' passwdValidTo='2016-04-11T09:21:09'>
network='vdsm-ovirtmgmt' fromConfig='0'/>

  


and one without

  passwdValidTo='1970-01-01T00:00:01'>
network='vdsm-ovirtmgmt' fromConfig='0'/>

  


oVirt Engine Version: 3.6.3.4-1.el7.centos
Node: oVirt Node Hypervisor release 3.6 (0.999.201512141021.el7.centos)

Is this a known issue ?

Brgds,
Jonas
___
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] [Attention needed] GlusterFS repository down - affects CI / Installations

[Nadav Goldin]

The issue should be resolved now.

Nadav.

On Wed, Apr 27, 2016 at 11:50 AM, Nadav Goldin  wrote:

> Hi,
> The GlusterFS repository became unavailable this morning, as a result all
> Jenkins jobs that use the repository will fail, the common error would be:
>
>>
>> http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-7/noarch/repodata/repomd.xml:
>> [Errno 14] HTTP Error 403 - Forbidden
>>
>
> Also, installations of oVirt will fail.
>
> We are working on a solution and will update asap.
>
> Nadav.
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Error deleting template

[Giulio Casella]

Hi all,
I have a problem deleting a template from admin portal.
In file /var/log/vdsm/vdsm.log (on SPM hypervisor) I got:

jsonrpc.Executor/4::ERROR::2016-04-27 
10:19:57,122::hsm::1518::Storage.HSM::(deleteImage) Empty or not found 
image  in SD  [...]


Looking in the (data) storage domain the disk with that UUID doesn't exists.
It seems I reached an inconsistent state between engine database and 
images on disk.


Is there a (safe) way to rebuild a consistent situation? Maybe deleting 
entries from database?


My setup is based:
manager RHEV 3.5.8-0.1.el6ev
hypervisors: RHEV Hypervisor - 7.2 - 20160328.0.el7ev


Thanx in advance,
Giulio

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

[ovirt-users] [ANN] oVirt 3.6.6 First Release Candidate is now available for testing

[Sandro Bonazzola]

The oVirt Project is pleased to announce the availability of the First
Release Candidate of oVirt 3.6.6 for testing, as of April 27th, 2016

This release is available now for:
* Fedora 22
* Red Hat Enterprise Linux 6.7
* CentOS Linux 6.7 (or similar)
* Red Hat Enterprise Linux 7.2 or later
* CentOS Linux (or similar) 7.2 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.2 or later
* CentOS Linux (or similar) 7.2 or later
* Fedora 22

This release candidate includes the following updated packages:
* ovirt-engine
* ovirt-engine-extension-aaa-jdbc
* ovirt-engine-extension-aaa-ldap
* ovirt-engine-dwh-3.6.6 (git hash 33f6636)
* ovirt-hosted-engine-setup-1.3.6.0
* ovirt-vmconsole v1.0.2
* vdsm v4.17.27

See the release notes [1] for installation / upgrade instructions and a
list of new features and bugs fixed.

Notes:
* A new oVirt Live ISO is already available [2].
* A new oVirt Node Next Install ISO is already available[3]
* Mirrors[4] might need up to one day to synchronize.

Additional Resources:
* Read more about the oVirt 3.6.6 release highlights:
http://www.ovirt.org/release/3.6.6/
* 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/3.6.6/
[2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ovirt-live/
[3]
http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ovirt-node-ng-installer/
[4] http://www.ovirt.org/Repository_mirrors#Current_mirrors

-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt Node Next Beta

[Fabian Deutsch]

Hey,

the just released oVirt 3.6.6rc1 release marks the first official oVirt release
which is accompanied by oVirt Node Next (Beta).

Since it's pre-alpha release a few weeks ago, Node has seen a lot of testing
and fixes, which brought it to the beta level.

If you have not yet started to test oVirt Node Next, this is the time to do so.
Take a look at the quick-start guide to see the next steps [0].

What is oVirt Node?
oVirt Node is a ready-to-use OS image, containing all the OS and oVirt packages
needed to act as host for oVirt Engine.
The image can be installed in minutes, can be administered using Cockpit [1],
and provides a safe upgrade and rollback mechanism.

Where can I learn more about oVirt Node?
A quick-start guide, and links to additional documentation can be found on the
oVirt Node Project page .

On behalf of the Node team
- fabian

--
[0] http://www.ovirt.org/node/
[1] http://cockpit-project.org/
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] New oVirt-Live (3.6.6 rc1) is available for download

[Lev Veyde]

Hi,

The new oVirt-Live 3.6.6 rc1 is available for download.

You can download it from:
http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ovirt-live/ovirt-live-el7-3.6.6_rc1.iso

Thanks in advance,
Lev Veyde.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [Gluster-infra] [Attention needed] GlusterFS repository down - affects CI / Installations

[Sandro Bonazzola]

On Wed, Apr 27, 2016 at 11:09 AM, Niels de Vos  wrote:

> On Wed, Apr 27, 2016 at 02:30:57PM +0530, Ravishankar N wrote:
> > @gluster infra  - FYI.
> >
> > On 04/27/2016 02:20 PM, Nadav Goldin wrote:
> > >Hi,
> > >The GlusterFS repository became unavailable this morning, as a result
> all
> > >Jenkins jobs that use the repository will fail, the common error would
> be:
> > >
> > >
> http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-7/noarch/repodata/repomd.xml
> :
> > >[Errno 14] HTTP Error 403 - Forbidden
> > >
> > >
> > >Also, installations of oVirt will fail.
>
> I thought oVirt moved to using the packages from the CentOS Storage SIG?
>

We did that for CentOS Virt SIG builds.
On oVirt upstream we're still on Gluster upstream.
We'll move to Storage SIG there as well.



> In any case, automated tests should probably use those instead of the
> packages on download.gluster.org. We're trying to minimize the work
> packagers need to do, and get the glusterfs and other components in the
> repositories that are provided by different distributions.
>
> For more details, see the quickstart for the Storage SIG here:
>   https://wiki.centos.org/SpecialInterestGroup/Storage/gluster-Quickstart
>
> HTH,
> Niels
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [Gluster-infra] [Attention needed] GlusterFS repository down - affects CI / Installations

[Michael Scherer]

Le mercredi 27 avril 2016 à 14:30 +0530, Ravishankar N a écrit :
> @gluster infra  - FYI.

So that's fixed. There was a issue on rackspace, I will post a detailed
timeline as soon as I have time to write it.

In short, the volume hosting the content went down, a reboot fixed the
issue.

> On 04/27/2016 02:20 PM, Nadav Goldin wrote:
> > Hi,
> > The GlusterFS repository became unavailable this morning, as a result 
> > all Jenkins jobs that use the repository will fail, the common error 
> > would be:
> >
> > 
> > http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-7/noarch/repodata/repomd.xml:
> > [Errno 14] HTTP Error 403 - Forbidden
> >
> >
> > Also, installations of oVirt will fail.
> >
> > We are working on a solution and will update asap.
> >
> > Nadav.
> >
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> 
> 
> ___
> Gluster-infra mailing list
> gluster-in...@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-infra

-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS




signature.asc
Description: This is a digitally signed message part
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Unsupported CPU for Windows 10 64-bit Guest

[Jared Bloomer]

I have a new install of ovirt up and running. It is a pretty beefy machine so I 
would really like to figure this out so I can start actually using it. 

The Host machine is equipped with 2 Intel Xeon E5-2603 v3 CPUs. 

Ovirt shows the following for the hardware

CPU Model:
Intel(R) Xeon(R) CPU E5-2603 v3 @ 1.60GHz


CPU Type:
Intel Nehalem Family



However when trying to deploy a VM with the Operating System set as Windows 10 
x64 I get the error message

The guest OS doesn't support the following CPUs: opteron_g1, conroe, nehalem, 
penryn. Its possible to change the cluster cpu or set a different one per VM

How can I go about deploying a Windows 10 Guest on this Host?


Thanks,
Jared Bloomer





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

Re: [ovirt-users] Unsupported CPU for Windows 10 64-bit Guest

[Alexander Wels]

On Wednesday, April 27, 2016 09:57:17 AM Jared Bloomer wrote:
> I have a new install of ovirt up and running. It is a pretty beefy machine
> so I would really like to figure this out so I can start actually using it.
> 
> The Host machine is equipped with 2 Intel Xeon E5-2603 v3 CPUs.
> 
> Ovirt shows the following for the hardware
> 
> CPU Model:
> Intel(R) Xeon(R) CPU E5-2603 v3 @ 1.60GHz
> 
> 
> CPU Type:
> Intel Nehalem Family
> 
> 

IIRC this simply reports what cpu type the cluster is set to that the host is 
in. Looked up the Xeons you mention, and as far as I can tell that is a 
haswell no-TSX cpu. Simply select the cluster this host is in and switch the 
cpu type to haswell no-TSX. You should be able to deploy your VM then.

> 
> However when trying to deploy a VM with the Operating System set as Windows
> 10 x64 I get the error message
> 
> The guest OS doesn't support the following CPUs: opteron_g1, conroe,
> nehalem, penryn. Its possible to change the cluster cpu or set a different
> one per VM
> 
> How can I go about deploying a Windows 10 Guest on this Host?
> 
> 
> Thanks,
> Jared Bloomer

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

Re: [ovirt-users] Unsupported CPU for Windows 10 64-bit Guest

[Jared Bloomer]

I tried setting it to thank, and haswell, and sandy bridge. Everytime I try to 
deploy a VM it says the host does not have the cpu required by the cluster and 
reports the host as non-operational

Thanks,
Jared Bloomer





On Apr 27, 2016, at 2:22 PM, Alexander Wels  wrote:

> On Wednesday, April 27, 2016 09:57:17 AM Jared Bloomer wrote:
>> I have a new install of ovirt up and running. It is a pretty beefy machine
>> so I would really like to figure this out so I can start actually using it.
>> 
>> The Host machine is equipped with 2 Intel Xeon E5-2603 v3 CPUs.
>> 
>> Ovirt shows the following for the hardware
>> 
>> CPU Model:
>> Intel(R) Xeon(R) CPU E5-2603 v3 @ 1.60GHz
>> 
>> 
>> CPU Type:
>> Intel Nehalem Family
>> 
>> 
> 
> IIRC this simply reports what cpu type the cluster is set to that the host is 
> in. Looked up the Xeons you mention, and as far as I can tell that is a 
> haswell no-TSX cpu. Simply select the cluster this host is in and switch the 
> cpu type to haswell no-TSX. You should be able to deploy your VM then.
> 
>> 
>> However when trying to deploy a VM with the Operating System set as Windows
>> 10 x64 I get the error message
>> 
>> The guest OS doesn't support the following CPUs: opteron_g1, conroe,
>> nehalem, penryn. Its possible to change the cluster cpu or set a different
>> one per VM
>> 
>> How can I go about deploying a Windows 10 Guest on this Host?
>> 
>> 
>> Thanks,
>> Jared Bloomer

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

Re: [ovirt-users] Unsupported CPU for Windows 10 64-bit Guest

[Alexander Wels]

On Wednesday, April 27, 2016 02:25:32 PM Jared Bloomer wrote:
> I tried setting it to thank, and haswell, and sandy bridge. Everytime I try
> to deploy a VM it says the host does not have the cpu required by the
> cluster and reports the host as non-operational
> 
> Thanks,
> Jared Bloomer
> 

Strange, can you post the output of the following two commands on the HOST?

vdsClient -s 0 getVdsCaps | grep -i flags

virsh -r capabilities

That should tells us what libvirt thinks the capabilities of the machine are.

> On Apr 27, 2016, at 2:22 PM, Alexander Wels  wrote:
> > On Wednesday, April 27, 2016 09:57:17 AM Jared Bloomer wrote:
> >> I have a new install of ovirt up and running. It is a pretty beefy
> >> machine
> >> so I would really like to figure this out so I can start actually using
> >> it.
> >> 
> >> The Host machine is equipped with 2 Intel Xeon E5-2603 v3 CPUs.
> >> 
> >> Ovirt shows the following for the hardware
> >> 
> >> CPU Model:
> >> Intel(R) Xeon(R) CPU E5-2603 v3 @ 1.60GHz
> >> 
> >> 
> >> CPU Type:
> >> Intel Nehalem Family
> > 
> > IIRC this simply reports what cpu type the cluster is set to that the host
> > is in. Looked up the Xeons you mention, and as far as I can tell that is
> > a haswell no-TSX cpu. Simply select the cluster this host is in and
> > switch the cpu type to haswell no-TSX. You should be able to deploy your
> > VM then.> 
> >> However when trying to deploy a VM with the Operating System set as
> >> Windows
> >> 10 x64 I get the error message
> >> 
> >> The guest OS doesn't support the following CPUs: opteron_g1, conroe,
> >> nehalem, penryn. Its possible to change the cluster cpu or set a
> >> different
> >> one per VM
> >> 
> >> How can I go about deploying a Windows 10 Guest on this Host?
> >> 
> >> 
> >> Thanks,
> >> Jared Bloomer

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

Re: [ovirt-users] Keyboard mapping VNC

[Michal Skrivanek]

> On 27 Apr 2016, at 11:24, Jonas Israelsson  
> wrote:
> 
> No one ?

Hi,
sorry for late response

> 
> I've tested now also with a hosted engine setup. Can't see there either that 
> the keyboard layout information set in the web-ui ever reaches the VM.

That should work. HE is a bit different, and noVNC client doesn't support 
keymaps properly, but you should see it in xml

Does spice work? Any special reason you can't use it?

> Think we have a bug here.

Looks like that is a regression indeed. Feel free to open bug yourself, it 
shouldn't be difficult to fix

Thanks,
michal
> 
> Rgds,
> Jonas
> 
>> On 11/04/16 17:43, Jonas Israelsson wrote:
>> Greetings.
>> 
>> We are under the impression the the keyboard layout for the VNC-server is 
>> missing from a vm's xml definition, hence the same default layout is always 
>> used.
>> 
>> We therefore (just to test) created a small host hook adding a static 
>> keyboard layout, and with the hook, it seem to work as expected as the -k 
>> switch to kvm is now populated.
>> 
>> vm started with our hook
>> 
>>  > passwd='***' passwdValidTo='2016-04-11T09:21:09'>
>>> network='vdsm-ovirtmgmt' fromConfig='0'/>
>>  
>> 
>> 
>> and one without
>> 
>>  > passwdValidTo='1970-01-01T00:00:01'>
>>> network='vdsm-ovirtmgmt' fromConfig='0'/>
>>  
>> 
>> 
>> oVirt Engine Version: 3.6.3.4-1.el7.centos
>> Node: oVirt Node Hypervisor release 3.6 (0.999.201512141021.el7.centos)
>> 
>> Is this a known issue ?
>> 
>> Brgds,
>> Jonas
>> ___
>> 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] Cannot add Interface. Not enough MAC addresses left in MAC Address Pool.

[Bill James]

oh, never mind. I found it. Its now in the gui under "Configure".



On 04/27/2016 04:08 PM, Bill James wrote:

How do you increase and display the settings of
I saw some references to changing via /MaxMacsCountInPool & 
//MacPoolRanges but those don't seem to exist in ovirt3.6./


http://lists.ovirt.org/pipermail/users/2015-November/035694.html
https://www.ovirt.org/develop/developer-guide/engine/engine-config-options/


[root@ovirt dev engine.conf.d]# engine-config -g MaxMacsCountInPool
null
[root@ovirt dev engine.conf.d]# engine-config -s 
"MacPoolRanges=00:1a:4a:ab:64:00-00:1a:4a:ab:64:ff,00:1A:4A:97:5F:00-00:1A:4A:97:5F:FF"


Error setting MacPoolRanges's value. No such entry.



2016-04-27 15:06:06,807 INFO 
[org.ovirt.engine.core.bll.AddVmFromTemplateComm
and] (default task-32) [31879003] Lock freed to object 
'EngineLock:{exclusiveL
ocks='[sr140vm1.dev.j2noc.com=ACTION_TYPE_FAILED_OBJECT_LOCKED>]', s
haredLocks='[----=ACTION_TYPE_FAILE

D_TEMPLATE_IS_USED_FOR_CREATE_VM$VmName sr140vm1.dev.j2noc.com>]'}'
2016-04-27 15:06:08,289 WARN 
[org.ovirt.engine.core.bll.network.vm.AddVmInter
faceCommand] (default task-48) [4e78dc27] CanDoAction of action 
'AddVmInterfac
e' failed for user bill.ja...@j2global.com@j2global.com. Reasons: 
VAR__TYPE__I

NTERFACE,VAR__ACTION__ADD,MAC_POOL_NOT_ENOUGH_MAC_ADDRESSES



Strange thing is I only have 143 VMs.

ovirt-engine-3.6.4.1-1.el7.centos.noarch



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

Re: [ovirt-users] Cannot add Interface. Not enough MAC addresses left in MAC Address Pool.

[Nir Soffer]

On Thu, Apr 28, 2016 at 2:16 AM, Bill James  wrote:
> oh, never mind. I found it. Its now in the gui under "Configure".
>
>
>
>
> On 04/27/2016 04:08 PM, Bill James wrote:
>
> How do you increase and display the settings of
> I saw some references to changing via MaxMacsCountInPool & MacPoolRanges but
> those don't seem to exist in ovirt3.6.

You can create your own pool in the the dc, and select any range you like.

Select Data Center tab, select your data center, edit, create new pool...

>
> http://lists.ovirt.org/pipermail/users/2015-November/035694.html
> https://www.ovirt.org/develop/developer-guide/engine/engine-config-options/
>
>
> [root@ovirt dev engine.conf.d]# engine-config -g MaxMacsCountInPool
> null
> [root@ovirt dev engine.conf.d]# engine-config -s
> "MacPoolRanges=00:1a:4a:ab:64:00-00:1a:4a:ab:64:ff,00:1A:4A:97:5F:00-00:1A:4A:97:5F:FF"
>
> Error setting MacPoolRanges's value. No such entry.
>
>
>
> 2016-04-27 15:06:06,807 INFO
> [org.ovirt.engine.core.bll.AddVmFromTemplateComm
> and] (default task-32) [31879003] Lock freed to object
> 'EngineLock:{exclusiveL
> ocks='[sr140vm1.dev.j2noc.com=]',
> s
> haredLocks='[----= ACTION_TYPE_FAILE
> D_TEMPLATE_IS_USED_FOR_CREATE_VM$VmName sr140vm1.dev.j2noc.com>]'}'
> 2016-04-27 15:06:08,289 WARN
> [org.ovirt.engine.core.bll.network.vm.AddVmInter
> faceCommand] (default task-48) [4e78dc27] CanDoAction of action
> 'AddVmInterfac
> e' failed for user bill.ja...@j2global.com@j2global.com. Reasons:
> VAR__TYPE__I
> NTERFACE,VAR__ACTION__ADD,MAC_POOL_NOT_ENOUGH_MAC_ADDRESSES
>
>
>
> Strange thing is I only have 143 VMs.
>
> ovirt-engine-3.6.4.1-1.el7.centos.noarch
>
>
>
> ___
> 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] Hosts temporarily in "Non Operational" state after upgrade

[Will Dennis]

Hi all,

Had run updates tonight on my three oVirt hosts (3.6 hyperconverged) on on two 
of them, they went into “non Operational” state for a few minutes each before 
springing back to life… The synopsis was this:

- Ran updates throughout the web Admin UI
...then I got the following series of messages via the “Events” tab in the UI:
- Updates successfully ran
- VDSM “command failed: Heartbeat exceeded” message
- host is not responding message
- "Failed to connect to hosted_storage" message
- “The error message for connection localhost:/engine returned by VDSM was: 
Problem while trying to mount target”
- "Host  reports about one of the Active Storage Domains as Problematic”
- “Host  cannot access the Storage Domain(s) hosted_storage attached to 
the data center Default. Setting host state to Non-Operational.”
- "Detected change in status of brick {…} of volume {…} from DOWN to UP.” (once 
for every brick on the host for every Gluster volume.)
- "Host  was autorecovered.”
- "Status of host  was set to Up."

(BTW, it would be awesome if the UI’s Events log could be copied and pasted… 
Doesn’t work for me at least…)

Duration of outage was ~3 mins per each affected host. Didn’t happen on the 
first host I upgraded, but did on the last two.

I know I’m a little over the bleeding edge running hyperconverged on 3.6 :) 
but, should this behavior be expected?

Also, if I go onto the hosts directly and run a ‘yum update’ after this upgrade 
process (not that I went thru with it, just wanted to see what was available to 
be upgraded) I see a bunch of ovirt-* packages that can be upgraded, which 
didn’t get updated thru the web UI’s upgrade process —
ovirt-engine-sdk-pythonnoarch   3.6.5.0-1.el7.centos 
ovirt-3.6  480 k
ovirt-hosted-engine-ha noarch   1.3.5.3-1.1.el7  
centos-ovirt36 295 k
ovirt-hosted-engine-setup  noarch   1.3.5.0-1.1.el7  
centos-ovirt36 270 k
ovirt-release36noarch   007-1
ovirt-3.6  9.5 k

Are these packages not related to the “Upgrade” process available thru the web 
UI?

FYI, here’s what did get updated thru the web UI “Upgrade” process —
Apr 27 21:36:28 Updated: libvirt-client-1.2.17-13.el7_2.4.x86_64
Apr 27 21:36:28 Updated: libvirt-daemon-1.2.17-13.el7_2.4.x86_64
Apr 27 21:36:28 Updated: libvirt-daemon-driver-network-1.2.17-13.el7_2.4.x86_64
Apr 27 21:36:28 Updated: libvirt-daemon-driver-qemu-1.2.17-13.el7_2.4.x86_64
Apr 27 21:36:28 Updated: libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.4.x86_64
Apr 27 21:36:28 Updated: vdsm-infra-4.17.26-1.el7.noarch
Apr 27 21:36:28 Updated: vdsm-python-4.17.26-1.el7.noarch
Apr 27 21:36:28 Updated: vdsm-xmlrpc-4.17.26-1.el7.noarch
Apr 27 21:36:28 Updated: libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.4.x86_64
Apr 27 21:36:29 Updated: mom-0.5.3-1.1.el7.noarch
Apr 27 21:36:29 Updated: libvirt-lock-sanlock-1.2.17-13.el7_2.4.x86_64
Apr 27 21:36:29 Updated: libvirt-daemon-driver-secret-1.2.17-13.el7_2.4.x86_64
Apr 27 21:36:29 Updated: libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.4.x86_64
Apr 27 21:36:29 Updated: 
libvirt-daemon-driver-interface-1.2.17-13.el7_2.4.x86_64
Apr 27 21:36:29 Updated: libvirt-daemon-driver-storage-1.2.17-13.el7_2.4.x86_64
Apr 27 21:36:29 Updated: libvirt-daemon-kvm-1.2.17-13.el7_2.4.x86_64
Apr 27 21:36:29 Updated: 1:libguestfs-1.28.1-1.55.el7.centos.2.x86_64
Apr 27 21:36:29 Updated: 1:libguestfs-tools-c-1.28.1-1.55.el7.centos.2.x86_64
Apr 27 21:36:29 Installed: libguestfs-winsupport-7.2-1.el7.x86_64
Apr 27 21:36:29 Updated: vdsm-yajsonrpc-4.17.26-1.el7.noarch
Apr 27 21:36:29 Updated: vdsm-jsonrpc-4.17.26-1.el7.noarch
Apr 27 21:36:29 Installed: unzip-6.0-15.el7.x86_64
Apr 27 21:36:30 Installed: gtk2-2.24.28-8.el7.x86_64
Apr 27 21:36:31 Installed: 1:virt-v2v-1.28.1-1.55.el7.centos.2.x86_64
Apr 27 21:36:31 Updated: safelease-1.0-7.el7.x86_64
Apr 27 21:36:31 Updated: vdsm-hook-vmfex-dev-4.17.26-1.el7.noarch
Apr 27 21:36:32 Updated: vdsm-4.17.26-1.el7.noarch
Apr 27 21:36:32 Updated: vdsm-gluster-4.17.26-1.el7.noarch
Apr 27 21:36:32 Updated: vdsm-cli-4.17.26-1.el7.noarch

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

Re: [ovirt-users] Fwd: Having issues with Hosted Engine

[Sahina Bose]

This seems like issue reported in 
https://bugzilla.redhat.com/show_bug.cgi?id=1327121


Nir, Simone?

On 04/28/2016 05:35 AM, Luiz Claudio Prazeres Goncalves wrote:


Hi everyone,

Until today my environment was fully updated (3.6.5+centos7.2) with 3 
nodes (kvm1,kvm2 and kvm3 hosts) . I also have 3 external gluster 
nodes (gluster-root1,gluster1 and gluster2 hosts ) , replica 3, which 
the engine storage domain is sitting on top (3.7.11 fully 
updated+centos7.2)


For some weird reason i've been receiving emails from oVirt with 
EngineUnexpectedDown (attached picture) on a daily basis more or less, 
but the engine seems to be working fine and my vm's are up and running 
normally. I've never had any issue to access the User Interface to 
manage the vm's


Today I run "yum update" on the nodes and realised that vdsm was 
outdated, so I updated the kvm hosts and they are now , again, fully 
updated.



Reviewing the logs It seems to be an intermittent connectivity issue 
when trying to access the gluster engine storage domain as you can see 
below. I don't have any network issue in place and I'm 100% sure about 
it. I have another oVirt Cluster using the same network and using a 
engine storage domain on top of an iSCSI Storage Array with no issues.


*Here seems to be the issue:*

Thread-::INFO::2016-04-27 
23:01:27,864::fileSD::357::Storage.StorageDomain::(validate) 
sdUUID=03926733-1872-4f85-bb21-18dc320560db


Thread-::DEBUG::2016-04-27 
23:01:27,865::persistentDict::234::Storage.PersistentDict::(refresh) 
read lines (FileMetadataRW)=[]


Thread-::DEBUG::2016-04-27 
23:01:27,865::persistentDict::252::Storage.PersistentDict::(refresh) 
Empty metadata


Thread-::ERROR::2016-04-27 
23:01:27,865::task::866::Storage.TaskManager.Task::(_setError) 
Task=`d2acf575-1a60-4fa0-a5bb-cd4363636b94`::Unexpected error


Traceback (most recent call last):

  File "/usr/share/vdsm/storage/task.py", line 873, in _run

return fn(*args, **kargs)

  File "/usr/share/vdsm/logUtils.py", line 49, in wrapper

res = f(*args, **kwargs)

  File "/usr/share/vdsm/storage/hsm.py", line 2835, in 
getStorageDomainInfo


dom = self.validateSdUUID(sdUUID)

  File "/usr/share/vdsm/storage/hsm.py", line 278, in validateSdUUID

sdDom.validate()

  File "/usr/share/vdsm/storage/fileSD.py", line 360, in validate

raise se.StorageDomainAccessError(self.sdUUID)

StorageDomainAccessError: Domain is either partially accessible or 
entirely inaccessible: (u'03926733-1872-4f85-bb21-18dc320560db',)


Thread-::DEBUG::2016-04-27 
23:01:27,865::task::885::Storage.TaskManager.Task::(_run) 
Task=`d2acf575-1a60-4fa0-a5bb-cd4363636b94`::Task._run: 
d2acf575-1a60-4fa0-a5bb-cd4363636b94 
('03926733-1872-4f85-bb21-18dc320560db',) {} failed - stopping task


Thread-::DEBUG::2016-04-27 
23:01:27,865::task::1246::Storage.TaskManager.Task::(stop) 
Task=`d2acf575-1a60-4fa0-a5bb-cd4363636b94`::stopping in state 
preparing (force False)


Thread-::DEBUG::2016-04-27 
23:01:27,865::task::993::Storage.TaskManager.Task::(_decref) 
Task=`d2acf575-1a60-4fa0-a5bb-cd4363636b94`::ref 1 aborting True


Thread-::INFO::2016-04-27 
23:01:27,865::task::1171::Storage.TaskManager.Task::(prepare) 
Task=`d2acf575-1a60-4fa0-a5bb-cd4363636b94`::aborting: Task is 
aborted: 'Domain is either partially accessible or entirely 
inaccessible' - code 379


Thread-::DEBUG::2016-04-27 
23:01:27,866::task::1176::Storage.TaskManager.Task::(prepare) 
Task=`d2acf575-1a60-4fa0-a5bb-cd4363636b94`::Prepare: aborted: Domain 
is either partially accessible or entirely inaccessible



*Question: Anyone know what might be happening? I have several gluster 
config's, as you can see below. All the storage domain are using the 
same config's*



*More information:*

I have the "engine" storage domain, "vmos1" storage domain and 
"master" storage domain, so everything looks good.


[root@kvm1 vdsm]# vdsClient -s 0 getStorageDomainsList

03926733-1872-4f85-bb21-18dc320560db

35021ff4-fb95-43d7-92a3-f538273a3c2e

e306e54e-ca98-468d-bb04-3e8900f8840c


*Gluster config:*

[root@gluster-root1 ~]# gluster volume info

Volume Name: engine

Type: Replicate

Volume ID: 64b413d2-c42e-40fd-b356-3e6975e941b0

Status: Started

Number of Bricks: 1 x 3 = 3

Transport-type: tcp

Bricks:

Brick1: gluster1.xyz.com:/gluster/engine/brick1

Brick2: gluster2.xyz.com:/gluster/engine/brick1

Brick3: gluster-root1.xyz.com:/gluster/engine/brick1

Options Reconfigured:

performance.cache-size: 1GB

performance.write-behind-window-size: 4MB

performance.write-behind: off

performance.quick-read: off

performance.read-ahead: off

performance.io-cache: off

performance.stat-prefetch: off

cluster.eager-lock: enable

cluster.quorum-type: auto

network.remote-dio: enable

cluster.server-quorum-type: server

cluster.data-self-heal-algorithm: full

performance.low-prio-threads: 32

features.shard-block-size: 512MB

features.shard: on

storage.owner-gid: 36

storage.owner-uid: 36

performa