[Users] 3.2 beta: how to add iscsi domain to a f18 host
by Gianluca Cecchi
Hello,
having a fedora 18 system configured as a node and working with a
local_storage DC/CLuster, I then created an iSCSI dc and cluster and
moved there the host
Then I configured a CentOS server as an iSCSI sw target.
But in admin portal the
host
section remains greyed out and I can't proceed.
I suspect I have to manually install/configure some prerequisites to
have the host work as iSCSI initiator....
Is it true?
What I have to do on host part (or engine part) if I have not a node
iso but a standard fedora 18 system as hypervisor?
Here what I see in new domain box:
https://docs.google.com/file/d/0BwoPbcrMv8mvX281aWlMYUlzWXc/edit?usp=sharing
Thanks,
Gianluca
11 years, 2 months
[Users] Storage FC on ovirt 3.2 : /dev/dm* bad chown
by Kevin Maziere Aubry
Hi
My environnement is Fedora18 / Ovirt 3.2 and VDSM vdsm-4.10.3-6.fc18.x86_64.
I use a storage on fiber channel. When creating a VM the disk is created by
ovirt.
When starting the VM the disk has not the permission to be accessed by vdsm.
In fact the device for the disk has root:disks as owner/group.
Changing that by 36.36 permit the VM to start and work fine.
But snapshots do not work, and a reboot cause udev to remap the disk to
another /dev/dm-* device.
My fedora18 has selinux disabled.
On irc :
<apuimedo> vdsm/storage/blockSD.py: cmd = [constants.EXT_CHOWN,
"%s:%s" %
<apuimedo> vdsm/storage/blockSD.py: self.log.error("failed to
chown %s", masterDir)
<apuimedo> vdsm/storage/fileUtils.py:def chown(path, user=-1, group=-1):
<apuimedo> vdsm/storage/fileUtils.py: os.chown(path, uid, gid)
<apuimedo> vdsm/storage/lvm.py: cmd = [constants.EXT_CHOWN,
USER_GROUP, lv_path]
Kevin Mazière
Responsable Infrastructure
Alter Way – Hosting
1 rue Royal - 227 Bureaux de la Colline
92213 Saint-Cloud Cedex
Tél : +33 (0)1 41 16 38 41
Mob : +33 (0)7 62 55 57 05
http://www.alterway.fr
11 years, 2 months
[Users] Fwd: Re: 3.2 beta and f18 host on dell R815 problem
by Gianluca Cecchi
Find attach
Putty.log=output of cpuid command
Engine.log after patching and retry.
No file under host-deploy, it gives syntax error
>> > ---------- Forwarded message ----------
>> > From: Alon Bar-Lev <alonbl(a)redhat.com>
>> > Date: Thu, Jan 31, 2013 at 1:48 PM
>> > Subject: Re: [Users] 3.2 beta and f18 host on dell R815 problem
>> > To: Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
>> >
>> >
>> > Sorry, had error.
>> >
>> > ----- Original Message -----
>> >> From: "Alon Bar-Lev" <alonbl(a)redhat.com>
>> >> To: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com>
>> >> Sent: Thursday, January 31, 2013 2:40:55 PM
>> >> Subject: Re: [Users] 3.2 beta and f18 host on dell R815 problem
>> >>
>> >> Hi!
>> >>
>> >> Can you please try to replace the attach file at:
>> >>
/usr/share/ovirt-host-deploy/plugins/ovirt-host-deploy/vdsm/hardware.py
>> >>
>> >> Retry and send me the log?
>> >>
>> >> I added some more debug to see what went wrong.
>> >>
>> >> Thanks!
>> >> Alon
>> >>
>> >>
>> >> ----- Original Message -----
>> >> > From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com>
>> >> > To: "users" <users(a)ovirt.org>
>> >> > Sent: Thursday, January 31, 2013 1:57:38 PM
>> >> > Subject: Re: [Users] 3.2 beta and f18 host on dell R815 problem
>> >> >
>> >> > Output of command
>> >> > # virsh capabilities
>> >> > on this host
>> >> >
>> >> > https://docs.google.com/file/d/0BwoPbcrMv8mveG5OaVBZN1VENlU/edit
>> >> > _______________________________________________
>> >> > Users mailing list
>> >> > Users(a)ovirt.org
>> >> > http://lists.ovirt.org/mailman/listinfo/users
>> >> >
>> >>
>
>
11 years, 2 months
[Users] latest vdsm cannot read ib device speeds causing storage attach fail
by Dead Horse
Any ideas on this one? (from VDSM log):
Thread-25::DEBUG::2013-01-22
15:35:29,065::BindingXMLRPC::914::vds::(wrapper) client [3.57.111.30]::call
getCapabilities with () {}
Thread-25::ERROR::2013-01-22 15:35:29,113::netinfo::159::root::(speed)
cannot read ib0 speed
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/vdsm/netinfo.py", line 155, in
speed
s = int(file('/sys/class/net/%s/speed' % dev).read())
IOError: [Errno 22] Invalid argument
Causes VDSM to fail to attach storage
Engine side sees:
ERROR [org.ovirt.engine.core.bll.storage.NFSStorageHelper]
(QuartzScheduler_Worker-96) [553ef26e] The connection with details
192.168.0.1:/ovirt/ds failed because of error code 100 and error message
is: general exception
2013-01-22 15:35:30,160 INFO
[org.ovirt.engine.core.bll.SetNonOperationalVdsCommand]
(QuartzScheduler_Worker-96) [1ab78378] Running command:
SetNonOperationalVdsCommand internal: true. Entities affected : ID:
8970b3fe-1faf-11e2-bc1f-00151712f280 Type: VDS
2013-01-22 15:35:30,200 INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(QuartzScheduler_Worker-96) [1ab78378] START,
SetVdsStatusVDSCommand(HostName = kezan, HostId =
8970b3fe-1faf-11e2-bc1f-00151712f280, status=NonOperational,
nonOperationalReason=STORAGE_DOMAIN_UNREACHABLE), log id: 4af5c4cd
2013-01-22 15:35:30,211 INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(QuartzScheduler_Worker-96) [1ab78378] FINISH, SetVdsStatusVDSCommand, log
id: 4af5c4cd
2013-01-22 15:35:30,242 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(QuartzScheduler_Worker-96) [1ab78378] Try to add duplicate audit log
values with the same name. Type: VDS_SET_NONOPERATIONAL_DOMAIN. Value:
storagepoolname
Engine = latest master
VDSM = latest master
node = el6
11 years, 2 months