- Users - oVirt List Archives

[Users] Last removed host from DC cannot be installed again
by MEP 10 Jun '13

10 Jun '13

3 6

Re: [Users] SD Again
by Alessandro Bianchi 10 Jun '13

10 Jun '13

3 6

Re: [Users] Fwd: Nagios monitoring plugin check_rhev3 1.2 released
by Itamar Heim 10 Jun '13

10 Jun '13

> -------- Original Message -------- > Subject: [Users] Nagios monitoring plugin check_rhev3 1.2 released > Date: Thu, 16 May 2013 16:31:24 +0200 > From: René Koch <r.koch(a)ovido.at> > To: users <Users(a)ovirt.org> > > I'm happy to announce version 1.2 of check_rhev3. > > check_rhev3 is a monitoring plugin for Icinga/Nagios and it's forks, > which is > used to monitor datacenters, clusters, hosts, vms, vm pools and storage > domains > of Red Hat Enterprise Virtualization (RHEV) and oVirt virtualization > environments. > > The download locations are > * https://labs.ovido.at/download/check_rhev3/check_rhev3-1.2.tar.gz > * > https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.i… > > * > https://labs.ovido.at/download/check_rhev3/nagios-plugins-rhev3-1.2-1.el6.x… > > > For further information on how to install this plugin visit: > https://github.com/ovido/check_rhev3/wiki/Installation-Documentation > > A detailed usage documentation can be found here: > https://github.com/ovido/check_rhev3/wiki/Usage-Documentation > > > Changelog: > > - General: > - Moved project to github: https://github.com/ovido/check_rhev3 > > - New features: > - Verify RHEV-M certificate > - Allow authentication sessions for authentication in RHEV >= 3.1 and > oVirt >= 3.1 > - Use option -n <nic> to check a specific nic > > - Bugs fixed: > - Performance data issue with check_multi > > > If you have any questions or ideas, please drop me an email: > r.koch(a)ovido.at. > > Thank you for using check_rhev3. > > > Hi Rene, we deployed the plugin and noticed its flooding the event log with login events for the user its using via the REST API. can you please add persistent session to the REST API calls so login will happen only once and won't flood the log? http://www.ovirt.org/Features/RESTSessionManagement Thanks, Itamar Thanks, Itamar

4 16

[Users] any way to change VM timezone during import?
by Yuriy Demchenko 10 Jun '13

10 Jun '13

Hi, I need to import a bunch of VM's (about 50) from kvm to ovirt, will be using virt-v2v and rest api for bulk import. However, after import new VM's gets GMT-12 timezone and no way to change it - and that's bothering me, as fsck inside VMs keeps complaining at timestamps in future each time vm gets shutdown/startup, selinux relabelling occurs, etc. I've read about bug with default timezone (https://bugzilla.redhat.com/show_bug.cgi?id=873795) but I don't have time to wait for 3.3.0 to release... Is there any api calls or any other way to set timezone for VM during import? -- Yuriy Demchenko

3 3

[Users] Console.vv not found
by lof yer 09 Jun '13

09 Jun '13

I compiled from latest master and installed it. I used chrome as the client and got an error after clicking that monitor.

3 4

[Users] How do I run virsh on a F18 ovirt node?
by Dax Kelson 07 Jun '13

07 Jun '13

It asks for username/password? TIA, Dax Kelson

2 2

[Users] Outage window :: resources.ovirt.org / Mailman / etc. :: 2013-06-07 03:00 - 11:00 UTC
by Karsten 'quaid' Wade 07 Jun '13

07 Jun '13

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2MDCOHTKMPKPWXGFTKLJU Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable There is going to be an outage of resources.ovirt.org for up to 2 hours sometime during an 8 hour service window. The outage will occur 2013-06-07 between 03:00 and 11:00 UTC. To view in your local time: date -d '2013-06-07 03:00 UTC' date -d '2013-06-07 11:00 UTC' =3D=3D Details =3D=3D =46rom the Linode service bulletin/reminder: "This is just a friendly reminder that your maintenance window starts at 8PM PDT tonight and lasts until 4AM PDT. Downtime from this maintenance is expected to be less than 120 minutes, however please note that the entire maintenance window may be used if required. Your Linode will be gracefully powered down and rebooted during the maintenance. Services not configured to start on a reboot will need to be manually started. Additional information regarding this maintenance event can be found here: <https://blog.linode.com/2013/05/17/fremont-upgrades/> " =3D=3D Affected services =3D=3D * resources.ovirt.org * Mailman (lists.ovirt.org) * some backup services =3D=3D=3D Not-affected services =3D=3D * www.ovirt.org / wiki.ovirt.org * gerrit.ovirt.org * jenkins.ovirt.org * Anything at AlterWay and RackSpace facilities ** Foreman ** Puppet ** Jenkins slaves ** ... =3D=3D Future plans =3D=3D We'll be migrating all services from this host and decommissioning it ASA= P. ------enig2MDCOHTKMPKPWXGFTKLJU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iD8DBQFRsUHi2ZIOBq0ODEERAnYGAKCDzrI0KY/hzRt9ivfjq/ObA5Sb9ACfRvE9 Su00mscZQ27MWQ0KXHHMOHo= =NNQP -----END PGP SIGNATURE----- ------enig2MDCOHTKMPKPWXGFTKLJU--

1 0

[Users] iSCSI bug in vdsm/ovirt?
by Dax Kelson 06 Jun '13

06 Jun '13

On my fully updated Fedora 18 ovirt test environment, one of my nodes refused to attach to the iSCSI domain where it was working before. My vdsm.log had these errors: storageRefresh::WARNING::2013-06-06 14:57:50,887::fileUtils::185::fileUtils::(createdir) Dir /rhev/data-center/hsm-tasks already exists Thread-18::DEBUG::2013-06-06 14:57:50,904::misc::84::Storage.Misc.excCmd::(<lambda>) FAILED: <err> = 'iscsiadm: Could not stat /var/lib/iscsi/nodes//,3260,-1/default to delete node: No such file or directory\n\niscsiadm: Error while adding record: encountered iSCSI database failure\n'; <rc> = 6 Thread-18::DEBUG::2013-06-06 14:57:50,905::misc::84::Storage.Misc.excCmd::(<lambda>) '/usr/bin/sudo -n /sbin/iscsiadm -m iface' (cwd None) Thread-18::DEBUG::2013-06-06 14:57:50,933::misc::84::Storage.Misc.excCmd::(<lambda>) SUCCESS: <err> = ''; <rc> = 0 Thread-18::ERROR::2013-06-06 14:57:50,933::hsm::2215::Storage.HSM::(connectStorageServer) Could not connect to storageServer Traceback (most recent call last): File "/usr/share/vdsm/storage/hsm.py", line 2211, in connectStorageServer conObj.connect() File "/usr/share/vdsm/storage/storageServer.py", line 341, in connect iscsi.addIscsiNode(self._iface, self._target, self._cred) File "/usr/share/vdsm/storage/iscsi.py", line 132, in addIscsiNode iscsiadm.node_new(iface.name, portalStr, targetName) File "/usr/share/vdsm/storage/iscsiadm.py", line 237, in node_new raise IscsiNodeError(rc, out, err) IscsiNodeError: (6, [], ['iscsiadm: Could not stat /var/lib/iscsi/nodes//,3260,-1/default to delete node: No such file or directory', '', 'iscsiadm: Error while adding record: encountered iSCSI database failure']) Rebooting didn't fix it. The problem was the config file in the iSCSI was empty: # find /var/lib/iscsi/ /var/lib/iscsi/ /var/lib/iscsi/nodes /var/lib/iscsi/nodes/iqn.1999-07.com.gurulabs:ovirt /var/lib/iscsi/nodes/iqn.1999-07.com.gurulabs:ovirt/10.100.0.14,3260 <-- empty /var/lib/iscsi/ifaces /var/lib/iscsi/slp /var/lib/iscsi/static /var/lib/iscsi/isns /var/lib/iscsi/send_targets This command fixed the problem rm -rf /var/lib/iscsi/nodes/* && reboot

1 0

Re: [Users] SD Again
by Alessandro Bianchi 06 Jun '13

06 Jun '13

3 3

[Users] SD again ...
by Alessandro Bianchi 06 Jun '13

06 Jun '13

1 0