- Users - oVirt List Archives

java.io.IOException: Command returned failure code 1 during SSH session
by Gregor Binder 13 Jun '16

13 Jun '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, during inspecting the engine.log I found this entry: - ------------ [org.ovirt.engine.core.uutils.ssh.SSHDialog] (DefaultQuartzScheduler_Worker-81) [] Exception: java.io.IOException: Command returned failure code 1 during SSH session 'root@<hostmachine name remove>' - ------------ Message: Failed to check for available updates on host host01 with message 'Command returned failure code 1 during SSH session 'root@<hostmachine name remove>' - ------------ Looks like a serious problem because the engine can't check for updates. cheers gregor - -- GPG-Key: 67F1534F URL: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x137FB29D67F1534 F -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXXCaMAAoJEBN/sp1n8VNP1B4QAL1EZRBMe+TFYENj2WH0saTm GBOZxKljwkno0xdGpql64ZsmPogQ9Ybtus6eEWBuzGScc0uHvsbzVKWrVNf2afAP XbvWYvdTWECfhSTbQQ0MS/itwkuOfeEONywdo9jcCv+261oEJwQyltjDKK6NDgYl K4L5Qyvhac0EZsjRpDtKDyHj+QT321hLI5gRps/eMPIAHWl8zaq+LJVFDI4EV3gE 9Ndcljyxjd6IyqIG4LzQobNowA8Jp+QAIrA316ekkb9BLF7o/W9VaITmS+5xS5Dl y2lL7Ga/LYdpEkMh8ZQmLwjoTWZvKoL08xFQgnUQ4Ry/UI8ENukmIXecuQebhEHH Bs4WnaZCDxditHymI809lwf2jpeGVjLkOPuLfev38AIfKS00acm0Yb3TIWNbzs6F ZJ+rz9X6gtPBET2XOSDPWa/JsCcIbg/XjqEM4qzOANmKzWA4mJpVh7uM6M8mgFd+ 4kZA8hVz4sckat1jbXFXgIJuMvNDwjgKUsDVBoZ1wKJvfj/btfgFaVI/osDnNQ8l rtnuGCDNhZvJCctxIbLOpC7+raImWLOy89Od1W3KMYg6ECgAM7t5A7VRtTdzSqyt pji7NaXsZxNqCh2QCXa8srjUQgWttpkRsH/iR3xq/s7QdS+Moail5AoF8XeCzFvB GX+DLN8RPMcIilUXuaUs =OnF7 -----END PGP SIGNATURE-----

4 3

Disk from FC storage not removed
by Krzysztof Dajka 13 Jun '16

13 Jun '16

Hi, Recently I tried to delete 1TB disk created on top ~3TB LUN from ovirtengine. Disk is preallocated and I backuped data to other disk so I could recreate it once again as thin volume. I couldn't remove this disk when it was attached to a VM. But once I detached it I could remove it permanently. The thing is it only disappeared from ovirtengine GUI. I've got 4 hosts with FC HBA attached to storage array and all of them are saying that this 1TB disk which should be gone is opened by all hosts simultaneously. [root@wrops1 BLUE ~]# lvdisplay -m /dev/e69d1c16-36d1-4375-aaee-69f5a5ce1616/ee53af81-820d-4916-b766-5236ca99daf8 --- Logical volume --- LV Path /dev/e69d1c16-36d1-4375-aaee-69f5a5ce1616/ee53af81-820d-4916-b766-5236ca99daf8 LV Name ee53af81-820d-4916-b766-5236ca99daf8 VG Name e69d1c16-36d1-4375-aaee-69f5a5ce1616 LV UUID sBdBRk-tNyZ-Rval-F4lw-ka6X-wOe8-AQenTb LV Write Access read/write LV Creation host, time wrops1.blue, 2015-07-31 10:40:57 +0200 LV Status available # open 1 LV Size 1.00 TiB Current LE 8192 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 8192 Block device 253:29 --- Segments --- Logical extents 0 to 8191: Type linear Physical volume /dev/mapper/3600000e00d0000000024057200000000 Physical extents 8145 to 16336 Deactivating LV doesn't work: [root@wrops1 BLUE ~]# lvchange -an /dev/e69d1c16-36d1-4375-aaee-69f5a5ce1616/ee53af81-820d-4916-b766-5236ca99daf8 Logical volume e69d1c16-36d1-4375-aaee-69f5a5ce1616/ee53af81-820d-4916-b766-5236ca99daf8 is used by another device. Removing from hypervisor doesn't work either. [root@wrops1 BLUE ~]# lvremove --force /dev/e69d1c16-36d1-4375-aaee-69f5a5ce1616/ee53af81-820d-4916-b766-5236ca99daf8 Logical volume e69d1c16-36d1-4375-aaee-69f5a5ce1616/ee53af81-820d-4916-b766-5236ca99daf8 is used by another device. I tried and rebooted one host and as soon as it booted the volume became opened once again. Lsof on all hosts doesn't give anything meaningful regarding this LV. As opposed to other LV which are used by qemu-kvm. Has anyone encountered similar problem? How can I remove this LV?

2 4

Problem accessing to hosted-engine after wrong network config
by Alexis HAUSER 13 Jun '16

13 Jun '16

hi, I made a terrible and stupid mistake : I changed the VLAN of the wrong ovirt network interface : ovirtmgmt... I now don't have anymore access to my hosted engine. I can still access to the host hypervisor anyway. Any idea how I can change the ovirtmgmt VLAN (disabling the option enable VLAN tagging at all) without accessing the hosted-engine ? If there is no way, how can I access the hosted engine console ? I tried with remote-viewer and ssh forwarding with no success... Is there other ways using hosted-engine --console and ssh X forwarding ?

3 9

Disable iptables management by ovirt
by Mark Gagnon 13 Jun '16

13 Jun '16

Is it possible to disable the automated management of iptables rules once your hosts/engine are running? @CUSTOM_RULES@ won't cut it because we wanted to filter by source. Thank you

2 1

java.io.IOException: Command returned failure code 1 during SSH session
by gregor 12 Jun '16

12 Jun '16

Hi, during inspecting the engine.log I found this entry: - ------------ [org.ovirt.engine.core.uutils.ssh.SSHDialog] (DefaultQuartzScheduler_Worker-81) [] Exception: java.io.IOException: Command returned failure code 1 during SSH session 'root@<hostmachine name remove>' - ------------ Message: Failed to check for available updates on host host01 with message 'Command returned failure code 1 during SSH session 'root@<hostmachine name remove>' - ------------ Looks like a serious problem because the engine can't check for updates. cheers gregor

2 2

Re: [ovirt-users] Can't start VM after shutdown
by gregor 12 Jun '16

12 Jun '16

Thanks for sharing the information's, I check the file structure and database entries. I had problems with too long names during coding a oVirt backup tool [1]. Here is a limitations list [2]. There was the problem that a Windows VM name can only be 15 characters long, others can named with 64 characters. Which OS you used on the problematic VM? cheers gregor [1] https://github.com/wefixit-AT/oVirtBackup [2] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualiza… On 12/06/16 02:16, Colin Coe wrote: > We had the same problem. Turned out that qemu-img was complaining that > the image file was too long. We use RHEV and Red Hat support did the > hard work to correct the image chain. Its quite a process... > > CC > > On Sat, Jun 11, 2016 at 10:39 PM, gregor <gregor_forum(a)catrix.at > <mailto:gregor_forum@catrix.at>> wrote: > > Hi, > > a VM has snapshots which are unable to remove during when the VM is up. > Therefore I power down the Windows Server 2012 VM. The snapshots are > still unable to remove and the VM can't boot anymore !!! > > This is the message from engine.log > > ------------------ > Message: VM srv03 is down with error. Exit message: Bad volume > specification > ------------------ > > Clone is not possible I get: > ------------------ > Message: VDSM command failed: Image is not a legal chain > ------------------ > > All others VM's can be powered down and start without any problem. > What can I do? > This is very important because now no one can work :-( !!! > > cheers > gregor > _______________________________________________ > Users mailing list > Users(a)ovirt.org <mailto:Users@ovirt.org> > http://lists.ovirt.org/mailman/listinfo/users > >

1 0

Re: [ovirt-users] Can't start VM after shutdown
by gregor 12 Jun '16

12 Jun '16

Sound's bad. Recreating the VM is no way because this is a productive VM. During testing I need to recreate it more than once. oVirt works perfect which Linux VM's but when it comes to Windows VM's we get lots of problems. Which OS you used on the problematic VM? cheers gregor On 11/06/16 19:22, Anantha Raghava wrote: > Hi, > > Even I observed this behaviour. > > When we take the snapshot, the main VM using which the snapshot was > taken is shutdown and a new VM with external-<VMName> comes to life. We > cannot get the original VM back to life, but a clone starts functioning. > > We cannot remove the snapshot whether or not the VM is running. I had to > remove the entire VM that came to life with snapshot and recreate the > entire VM from scratch. Luckily the VM was still not in production, > hence could afford it. > > First I could not understand, why, when a snapshot is created, the VM > with snapshot comes to life and starts running and not the original VM. > > Is it necessary that we shutdown the VM before taking snapshots? > Snapshot is supposed to be a backup of original VM, that unless we > restore by cloning should not come to life as I understand. > > -- > > Thanks & Regards, > > Anantha Raghava > > > On Saturday 11 June 2016 08:09 PM, gregor wrote: >> Hi, >> >> a VM has snapshots which are unable to remove during when the VM is up. >> Therefore I power down the Windows Server 2012 VM. The snapshots are >> still unable to remove and the VM can't boot anymore !!! >> >> This is the message from engine.log >> >> ------------------ >> Message: VM srv03 is down with error. Exit message: Bad volume specification >> ------------------ >> >> Clone is not possible I get: >> ------------------ >> Message: VDSM command failed: Image is not a legal chain >> ------------------ >> >> All others VM's can be powered down and start without any problem. >> What can I do? >> This is very important because now no one can work :-( !!! >> >> cheers >> gregor >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >

1 0

Can't start VM after shutdown
by gregor 11 Jun '16

11 Jun '16

Hi, a VM has snapshots which are unable to remove during when the VM is up. Therefore I power down the Windows Server 2012 VM. The snapshots are still unable to remove and the VM can't boot anymore !!! This is the message from engine.log ------------------ Message: VM srv03 is down with error. Exit message: Bad volume specification ------------------ Clone is not possible I get: ------------------ Message: VDSM command failed: Image is not a legal chain ------------------ All others VM's can be powered down and start without any problem. What can I do? This is very important because now no one can work :-( !!! cheers gregor

1 0

oVirt 4.0.0 Second Release candidate is now available for testing
by Rafael Martins 10 Jun '16

10 Jun '16

The oVirt Project is pleased to announce the availability of the Second Release Candidate of oVirt 4.0.0 for testing, as of June 10th, 2016 This is pre-release software. Please take a look at our community page[1] to know how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This pre-release should not to be used in production. This release is available now for: * Fedora 23 * 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 23 * oVirt Next Generation Node 4.0 See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO will be available soon. * A new oVirt Next Generation Node is already available. [4] * A new oVirt Engine Appliance is already available. * A new oVirt Guest Tools ISO will be available soon. * Mirrors[5] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 4.0.0 release candidate highlights: http://www.ovirt.org/release/4.0.0/ * 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] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.0.0/ [4] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/ [5] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Rafael Martins

1 0

ovirt engine upgrade
by Rafael Almeida 10 Jun '16

10 Jun '16

This is a multi-part message in MIME format. --------------D4C59C416DD0E06A51171A1A Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello, friends, I have one simple question, what is the best and safe way to upgrade ovirt engine 3.6 my environment in production is: - ovirt engine 3.6 over centos 7.2 x64 in a independent host - 4 Hipervisor's host over centos 7.2 x64 - 16 VM's - 2 storage's FC with the host's updrades, i don't have problems greetings -- Rafael Almeida Orellana --------------D4C59C416DD0E06A51171A1A Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hello, friends, I have one simple question, what is the best and safe way to upgrade ovirt engine 3.6 my environment in production is: - ovirt engine 3.6 over centos 7.2 x64 in a independent host - 4 Hipervisor's host over centos 7.2 x64 - 16 VM's - 2 storage's FC with the host's updrades, i don't have problems greetings <div class="moz-signature">-- Rafael Almeida Orellana </div> </body> </html> --------------D4C59C416DD0E06A51171A1A--

3 2