vdsm changing disk scheduler when starting, configurable?
by Darrell Budic
It seems vdsmd under 4.1.x (or something under it’s control) changes the disk schedulers when it starts or a host node is activated, and I’d like to avoid this. Is it preventable? Or configurable anywhere? This was probably happening under earlier version, but I just noticed it while upgrading some converged boxes today.
It likes to set deadline, which I understand is the RHEL default for centos 7 on non SATA disks. But I’d rather have NOOP on my SSDs because SSDs, and NOOP on my SATA spinning platters because ZFS does it’s own scheduling, and running anything other than NOOP can cause increased CPU utilization for no gain. It’s also fighting ZFS, which tires to set NOOP on whole disks it controls, and my kernel command line setting.
Thanks,
-Darrell
7 years, 4 months
vdsm (4.1) restarts glusterd when activating a node, even if it's already running
by Darrell Budic
Upgrading some nodes today, and noticed that vdsmd restarts glusterd on a node when it activates it. This is causing a short break in healing when the shd gets disconnected, forcing some extra healing when the healing process reports “Transport Endpoint Disconnected” (N/A in the ovirt gui).
This is on a converged cluster (3 nodes, gluster replica volume across all 3, ovirt-engine running elsewhere). Centos 7 install, just upgraded to Ovirt 4.1.2, running cluster 3.10 from the Centos SIG.
The process I’m observing:
Place a node into maintenance via GUI
Update node from command line
Reboot node (kernel update)
Watch gluster heal itself after reboot
Activate node in GUI
gluster is completely stopped on this node
gluster is started on this node
healing begins again, but isn’t working
“gluster vol heal XXXX info” reports this node’s information not available because “Transport endpoint not connected”.
This clears up in 5-10 minutes, then volume heals normally
Someone with a similar setup want to check this and see if it’s something specific to my nodes, or just a general problem with the way it’s restarting gluster? Looking for a little confirmation before I file a bug report on it.
Or a dev want to comment on why it stops and starts gluster, instead of a restart which would presumably leave the brick processes and shd running and not causing this effect?
Thanks,
-Darrell
7 years, 4 months
Storage, extend or new lun ?
by Enrico Becchetti Gmail
Dear All,
I've oVirt 3.5.3-1-1.el6 with two kind of storage , NFS and Fibre
Channel. Each Hypervisor
has HBA controller and Data CLutser has four Storage named: DATA_FC,
DATA_NFS, EXPORT
and ISO-DOMAIN.
Anybody know how can I extend a DATA_FC ? Which is the best practies ?
Extend LUN from HP MSA controller or adding a new lun ?
if I extend lun inside HP MSA oVirt see the new size ?
Enrico
Thanks a lot.
Best Regards
7 years, 4 months
Cannot find master domain
by Iman Darabi
hi.
i moved my host to maintenance mode and upgrade it. then restarted server.
after restarting, i activated server but the data domain is inactive and i
get the following error:
"Cannot find master domain: u'spUUID=9a1584cf-81bb-4ce8-975f-659e643a14b5,
msdUUID=193072f2-9c4a-405c-86a8-c4b036413171'", 'code': 304
The output of "multipath -v2" is as follows:
Jul 01 12:38:34 | sdb: emc prio: path not correctly configured for failover
Jul 01 12:38:34 | sdc: emc prio: path not correctly configured for failover
Jul 01 12:38:34 | 3600508b1001cbeb7dc20cfc250a2e506: ignoring map
Jul 01 12:38:34 | sdb: emc prio: path not correctly configured for failover
Jul 01 12:38:34 | sdc: emc prio: path not correctly configured for failover
Jul 01 12:38:34 | DM message failed [fail_if_no_path]
reject: 3600601604d003a00036edddd268de611 undef DGC ,VNX5400WDVR
size=2.0T features='0' hwhandler='1 emc' wp=undef
|-+- policy='service-time 0' prio=0 status=undef
| |- 12:0:0:16384 sdb 8:16 undef faulty running
| `- 12:0:1:16384 sdc 8:32 undef faulty running
|-+- policy='service-time 0' prio=50 status=undef
| `- 11:0:1:0 sde 8:64 undef ready running
`-+- policy='service-time 0' prio=10 status=undef
`- 11:0:0:0 sdd 8:48 undef ready running
thanks.
--
R&D expert at Ferdowsi University of Mashhadhttps://ir.linkedin.com/in/
imandarabi
<https://www.linkedin.com/profile/public-profile-settings?trk=prof-edit-ed...>
7 years, 4 months
Recovering hosted-engine
by Andrew Dent
--------=_MB617458AF-4FCC-4AB6-8A34-3338D99C6BB8
Content-Type: text/plain; format=flowed; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Hi
A couple of questions about hosted-engine recovery.
Part way through this URL, in the section "Workflow for Restoring the=20
Self-Hosted Engine Environment"
http://www.ovirt.org/documentation/self-hosted/chap-Backing_up_and_Restorin=
g_an_EL-Based_Self-Hosted_Environment/
it looks like once the hosted-engine is recovered on Host 1, the VMs on=20
Host 2 and 3 will be running, but not accessible to the recovered Hosted=20
Engine.
Is that correct?
If so, how to you remove host 2 and host 3 from the environment, then=20
add back in again while keeping the VMs running?
Host 2 and Host 3 are not recoverable in their current state. These=20
hosts need to be removed from the environment, and then added again to=20
the environment using the hosted-engine deployment script. For more=20
information on these actions, see the Removing Non-Operational Hosts=20
from a Restored Self-Hosted Engine Environment section below and Chapter=20
7: Installing Additional Hosts to a Self-Hosted Environment=20
<http://www.ovirt.org/documentation/self-hosted/chap-Backing_up_and_Restori=
ng_an_EL-Based_Self-Hosted_Environment/chap-Installing_Additional_Hosts_to_=
a_Self-Hosted_Environment>.
BTW: The link referring to chapter 7 is broken.
Kind regards
Andrew
--------=_MB617458AF-4FCC-4AB6-8A34-3338D99C6BB8
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<?xml version=3D"1.0" encoding=3D"utf-16"?><html><head>
<style id=3D"signatureStyle"><!--#x75154ce80e9e4bf, #x75154ce80e9e4bf, #x75=
154ce80e9e4bf, #x75154ce80e9e4bf #xb71224f920234978acc74f4d23143069, #x7515=
4ce80e9e4bf
{font-family: Tahoma; font-size: 12pt;}
#x75154ce80e9e4bf, #x75154ce80e9e4bf
{font-family: 'Segoe UI'; font-size: 12pt;}
#x75154ce80e9e4bf #xb71224f920234978acc74f4d23143069 p.MsoNormal, #x75154ce=
80e9e4bf p.MsoNormal
{margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-seri=
f;}
#x75154ce80e9e4bf #xb71224f920234978acc74f4d23143069 div.WordSection1, #x75=
154ce80e9e4bf div.WordSection1
{page: WordSection1;}
#x75154ce80e9e4bf a:link
{color: rgb(5, 99, 193); text-decoration: underline;}
--></style>
<style><!--body
{font-family: 'Segoe UI'; font-size: 12pt;}
--></style>
</head>
<body><div>Hi</div><div><br /></div><div>A couple of questions about hosted=
-engine recovery.</div><div>Part way through this URL, in the section "Work=
flow for Restoring the Self-Hosted Engine Environment"=C2=A0</div><div><a h=
ref=3D"http://www.ovirt.org/documentation/self-hosted/chap-Backing_up_and_R=
estoring_an_EL-Based_Self-Hosted_Environment/">http://www.ovirt.org/documen=
tation/self-hosted/chap-Backing_up_and_Restoring_an_EL-Based_Self-Hosted_En=
vironment/</a></div><div>it looks like once the hosted-engine is recovered=
on Host 1, the VMs on Host 2 and 3 will be running, but not accessible to t=
he recovered Hosted Engine.=C2=A0</div><div>Is that correct?</div><div>If s=
o, how to you remove host 2 and host 3 from the environment, then add back=
in again while keeping the VMs running?</div><div><br /></div><div><div>
<code style=3D"box-sizing: border-box; font-family: Menlo, Monaco, Consolas=
, 'Courier New', monospace; font-size: 14.4px; padding: 2px 4px; color: rgb=
(199, 37, 78); border-radius: 4px; font-variant-ligatures: normal; orphans: =
2; widows: 2; background-color: rgb(249, 242, 244);">Host 2</code><span st=
yle=3D"color: rgb(51, 51, 51); font-family: 'Source Sans Pro', 'Open Sans', =
'Helvetica Neue', Helvetica, Arial, sans-serif; font-variant-ligatures: no=
rmal; orphans: 2; widows: 2; background-color: rgb(255, 255, 255);">=C2=A0a=
nd=C2=A0</span><code style=3D"box-sizing: border-box; font-family: Menlo, M=
onaco, Consolas, 'Courier New', monospace; font-size: 14.4px; padding: 2px=
4px; color: rgb(199, 37, 78); border-radius: 4px; font-variant-ligatures: n=
ormal; orphans: 2; widows: 2; background-color: rgb(249, 242, 244);">Host 3=
</code><span style=3D"color: rgb(51, 51, 51); font-family: 'Source Sans Pro=
', 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; font-varian=
t-ligatures: normal; orphans: 2; widows: 2; background-color: rgb(255, 255, =
255);">=C2=A0are not recoverable in their current state. These hosts need=
to be removed from the environment, and then added again to the environment =
using the hosted-engine deployment script. For more information on these a=
ctions, see the Removing Non-Operational Hosts from a Restored Self-Hosted=
Engine Environment section below and=C2=A0</span><a href=3D"http://www.ovir=
t.org/documentation/self-hosted/chap-Backing_up_and_Restoring_an_EL-Based_S=
elf-Hosted_Environment/chap-Installing_Additional_Hosts_to_a_Self-Hosted_En=
vironment" style=3D"box-sizing: border-box; color: rgb(97, 182, 14); text-d=
ecoration: none; font-family: 'Source Sans Pro', 'Open Sans', 'Helvetica Ne=
ue', Helvetica, Arial, sans-serif; font-variant-ligatures: normal; orphans: =
2; widows: 2; background-color: rgb(255, 255, 255);">Chapter 7: Installing =
Additional Hosts to a Self-Hosted Environment</a><span style=3D"color: rgb=
(51, 51, 51); font-family: 'Source Sans Pro', 'Open Sans', 'Helvetica Neue'=
, Helvetica, Arial, sans-serif; font-variant-ligatures: normal; orphans: 2; =
widows: 2; background-color: rgb(255, 255, 255);">.</span></div></div><div=
><br /></div><div>BTW: The link referring to chapter 7 is broken.=C2=A0</di=
v><div><br /></div><div id=3D"signature_old"><div id=3D"x75154ce80e9e4bf">
<div class=3D"WordSection1">
<div id=3D"xb71224f920234978acc74f4d23143069"><div class=3D"WordSection1"><=
p class=3D"MsoNormal"><font face=3D"Tahoma"><font size=3D"3" style=3D"font-=
size: 12pt;">Kind r</font><span style=3D"font-size: 12pt;">egards</span></f=
ont></p><p class=3D"MsoNormal"><font size=3D"3" style=3D"font-size: 12pt;"=
face=3D"Tahoma"><br /></font></p><p class=3D"MsoNormal"><font size=3D"3" st=
yle=3D"font-size: 12pt;" face=3D"Tahoma">Andrew=C2=A0</font></p></div></div=
>
</div>
</div></div><div><br /></div>
</body></html>
--------=_MB617458AF-4FCC-4AB6-8A34-3338D99C6BB8--
7 years, 4 months
oVirt Node update not updating kernel, glibc, etc
by Mike DePaulo
Hi,
I installed 3 ovirt 4.1.1 nodes in early May. Today used oVirt's
webgui to update ("Upgrade") 2 of them. They are both reporting oVirt
Node 4.1.2 & vdsm-4.19.15-1.el7.centos now.
However, it appears that the kernel was not updated:
[root@death-star peers]# uname -a
Linux death-star 3.10.0-514.16.1.el7.x86_64 #1 SMP Wed Apr 12 15:04:24
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
And neither was glibc The installed version is still 2.17-157.el7_3.1
rather than 2.17-157.el7_3.4 .
The following lines were appended to /var/log/yum.log:
Jul 01 18:47:49 Installed: ovirt-node-ng-image-4.1.2-1.el7.centos.noarch
Jul 01 18:50:27 Installed: ovirt-node-ng-image-update-4.1.2-1.el7.centos.noarch
Jul 01 18:50:27 Erased:
ovirt-node-ng-image-update-placeholder-4.1.1.1-1.el7.centos.noarch
Thanks in advance,
-Mike
7 years, 4 months
Re: [ovirt-users] [ovirt-devel] problem about vm in ovirt node can ping node, but cannot ping gateway or the third host in LAN
by Edward Haas
If I understood correctly, you are using a nested solution where the node
is itself a VM.
If this is the case, you may have a security feature active on the physical
host/node.
In oVirt we have the default filter which allows only a single source mac
to exit the vNIC, but you disabled it.
I guess you should have something similar on the upper node.
Please note that such topics fit the user list, not devel.
Thanks,
Edy.
On Fri, Jun 30, 2017 at 1:46 PM, pengyixiang <yxpengi386(a)163.com> wrote:
> hi, everyone
>
> I am a new bird in ovirt, and I transplate ovirt node to debian
> jessie(customed) system, it's work well now, then we create vm, use default
> nic1, like this:
>
> in vm, we ping node, it's ok; and in node, we ping vm, it's ok too;
> then in node, we ping gatway or other computer in the lan, it's ok too;
>
> but when in vm, we ping gatway or other computer in the lan, it's not ok,
> why is this?
>
>
> >>> next is some test infomation:
>
> 1) after vm up, vnet0 is created, and use :
>
> # brctl show ovirtmgmt
>
> we get this:
>
> bridge name bridge id STP enabled interfaces
> ovirtmgmt 8000.000c29e3037e no eth0
>
> vnet0
>
>
> 2) then we test network in three host in the same time
>
> in vm
>
> # tcpdump -i eth0 arp
>
> vm send request
>
> vm not recv reply
>
> # ping hostA
>
>
> in node(vm in)
>
> # tcpdump -i vnet0 arp
>
> vnet0 send request
>
> vnet0 not recv reply
>
>
> in third host in the lan(hostA)
>
> # tcpdump -i eth0 arp
>
> eth0 recv request
>
> eth0 send reply
>
>
> problem like this:
>
>
> why is this, do I lost some configurations ?
>
>
> ovirtmgmt configuration:
>
>
> vnet info:(node installed in ESXI)
>
>
>
>
> Look forward to your reply
>
>
> Have a nice day
>
> --
>
>
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
7 years, 4 months
