[ovirt-users] [QE][ACTION NEEDED] oVirt 3.4.4 RC status

2014-08-20 Thread Sandro Bonazzola
Hi,
We're going to start composing oVirt 3.4.4 RC on *2014-09-09 08:00 UTC* from 
3.4 branch.
Maintainers:
- Please be sure that 3.4 snapshot allow to create VMs before *2014-09-08 15:00 
UTC*
- Please be sure that no pending patches are going to block the release before 
*2014-09-08 15:00 UTC*
- If any patch must block the RC release please raise the issue as soon as 
possible.


A bug tracker [1] has been opened and shows no open blockers.


There are still 7 bugs [2] targeted to 3.4.4.
Excluding node and documentation bugs we still have 3 bugs [3] targeted to 
3.4.4.

Whiteboard  Bug ID  Status  Summary
network 1001186 NEW With AIO installer and NetworkManager 
enabled, the ovirtmgmt bridge is not properly configured
network 1048880 NEW [vdsm][openstacknet] Migration fails 
for vNIC using OVS + security groups
node988341  NEW Should not create bond when report an 
error in configuration process
node995321  NEW remove existing efi entries oVirt Node 
Hypervisor in UEFI menu failed
node1023481 ASSIGNEDSane and working default libvirt config
node1097735 NEW Reboot button failed to work in 
progress_page with serial console to install ovirt-node iso.
sla 1059309 NEW [events] 'Available memory of host 
$host (...) under defined threshold...' is logged only once



Maintainers / Assignee:
- Please add the bugs to the tracker if you think that 3.4.4 should not be 
released without them fixed.
- Please update the target to 3.5.1 or later for bugs that won't be in 3.4.4:
  it will ease gathering the blocking bugs for next releases.
- Please fill release notes, the page has been created here [4]

Community:
- If you're testing oVirt 3.4 nightly snapshot, please add yourself to the test 
page [5]


[1] http://bugzilla.redhat.com/1118689
[2] http://red.ht/1qwhPXB
[3] http://red.ht/1r8jnap
[4] http://www.ovirt.org/OVirt_3.4.4_Release_Notes
[5] http://www.ovirt.org/Testing/oVirt_3.4.4_Testing


-- 
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] AIO setup problem with master failes due to nfs

2014-08-20 Thread Gianluca Cecchi
Hello,
using this on CentOS 6.5 to configure AIO with ita branch for translation,
updated at 1608

[root@ovirtita ~]# rpm -qa|egrep engine|vdsm|ovirt
vdsm-xmlrpc-4.16.0-206.gitdd70c9e.el6.noarch
ovirt-engine-websocket-proxy-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
vdsm-yajsonrpc-4.16.0-206.gitdd70c9e.el6.noarch
ovirt-engine-jboss-as-7.1.1-1.el6.x86_64
ovirt-engine-restapi-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
vdsm-jsonrpc-4.16.0-206.gitdd70c9e.el6.noarch
ovirt-release-master-001-0.0.master.noarch
ovirt-engine-lib-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-extensions-api-impl-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-host-deploy-1.3.0-0.0.master.2014085624.git89155f8.el6.noarch
ovirt-image-uploader-3.6.0-0.0.master.20140808125503.git066ed25.el6.noarch
ovirt-engine-setup-base-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
vdsm-jsonrpc-java-1.0.1-0.0.master.20140812113145.git7d15fda.el6.noarch
ovirt-host-deploy-java-1.3.0-0.0.master.2014085624.git89155f8.el6.noarch
ovirt-engine-userportal-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-backend-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-host-deploy-offline-1.3.0-0.0.master.2014085624.git89155f8.el6.x86_64
ovirt-iso-uploader-3.6.0-0.0.master.20140812133505.gita6b721e.el6.noarch
vdsm-python-4.16.0-206.gitdd70c9e.el6.noarch
ovirt-engine-setup-plugin-websocket-proxy-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-cli-3.6.0.0-1.20140718.gite0c7d55.el6.noarch
ovirt-engine-dbscripts-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-tools-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-setup-plugin-allinone-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-sdk-python-3.6.0.0-1.20140811.git56f9da6.el6.noarch
vdsm-python-zombiereaper-4.16.0-206.gitdd70c9e.el6.noarch
ovirt-engine-webadmin-portal-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-extensions-api-impl-javadoc-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
vdsm-cli-4.16.0-206.gitdd70c9e.el6.noarch
ovirt-engine-setup-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
vdsm-4.16.0-206.gitdd70c9e.el6.x86_64


SELinux is set to permissive, iptables and ip6tables are stopped and set to
off.
In setup I say not to configure firewall.
It aborts at nfs share stage with

[ INFO  ] Restarting nfs services
[ ERROR ] Failed to execute stage 'Closing up': [Errno 111] Connection
refused
[ INFO  ] Stage: Clean up
  Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140820084635-z4gm0h.log
[ INFO  ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20140820084948-setup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed

NOTE: I set to enabled=0 the rows
in /etc/yum.repos.d/ovirt-master-snapshot.repo so that I'm not forced to
update engine-setup itself or other packages.

Whole output:
[root@ovirtita ~]# engine-setup
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
  Configuration files:
['/etc/ovirt-engine-setup.conf.d/10-packaging-aio.conf',
'/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
'/etc/ovirt-engine-setup.conf.d/10-packaging.conf']
  Log file:
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140820084635-z4gm0h.log
  Version: otopi-1.3.0_master
(otopi-1.3.0-0.0.master.20140728.git336a22e.el6)
[ INFO  ] Hardware supports virtualization
[ INFO  ] Stage: Environment packages setup
[ INFO  ] Stage: Programs detection
[ INFO  ] Stage: Environment setup
[ INFO  ] Stage: Environment customization

  --== PRODUCT OPTIONS ==--

  Configure Engine on this host (Yes, No) [Yes]:
  Configure WebSocket Proxy on this host (Yes, No) [Yes]:

  --== PACKAGES ==--

[ INFO  ] Checking for product updates...
[ INFO  ] No product updates found

  --== ALL IN ONE CONFIGURATION ==--

  Configure VDSM on this host? (Yes, No) [No]: Yes
  Local storage domain path [/var/lib/images]:
  Local storage domain name [local_storage]:

  --== NETWORK CONFIGURATION ==--

  Setup can automatically configure the firewall on this system.
  Note: automatic configuration of the firewall may overwrite
current settings.
  Do you want Setup to configure the firewall? (Yes, No) [Yes]: No
  Host fully qualified DNS name of this server
[ovirtita.localdomain.local]:
[WARNING] Failed to resolve ovirtita.localdomain.local using DNS, it can be
resolved only locally

  --== DATABASE CONFIGURATION ==--

  Where is the Engine database 

[ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2 status

2014-08-20 Thread Sandro Bonazzola
Hi,
early this week we postponed oVirt 3.5.0 RC2 to Thu *2014-08-21 08:00 UTC*,
we'll discuss current status in today oVirt sync meeting and eventually 
postpone RC2 by another week.

Maintainers (supposing we keep Thu *2014-08-21 08:00 UTC*):
- Please be sure that 3.5 snapshot allow to create VMs before *2014-08-20 15:00 
UTC*
- Please be sure that no pending patches are going to block the release before 
*2014-08-20 15:00 UTC*
- If any patch must block the RC release please raise the issue as soon as 
possible.

The bug tracker [1] shows the following proposed blockers to be reviewed:

Whiteboard  Bug ID  Status  Summary
infra   1127877 POSTvdsm-tool configure --force does not configure 
qemu.conf properly in the first run on a fresh install
sla 1129261 NEW prepareImage api call fails with [Errno 2] No 
such file or directory
sla 1130038 NEW prepareImage api call fails with [Errno 2] No 
such file or directory
storage 1128776 POSTCan't change a vm disk's storage domain from a 
file domain to a block domain when creating a template from a vm
storage 1127294 POSTLive Merge: Resolve unknown merge status in 
vdsm after host crash
storage 1109920 POSTLive Merge: Extend internal block volumes 
during merge


And the following dependencies still open:
Bug 1041569 - [NFR] libvirt: Returning the watermark for all the images opened 
for writing
Bug 1102881 - virDomainBlockCommit fails with live snapshots on oVirt block 
storage


Some of above blockers may be dropped on today oVirt sync meeting if still open.
Some of the bugs blocking the release prevents automated testing to verify the 
release.
Please fix them as soon as possible.


Feature freeze is now effective, and branch has been created.
All new patches must be backported to 3.5 branch too.
Features completed are marked in green on Features Status Table [2]

There are still 425 bugs [3] targeted to 3.5.0.
Excluding node and documentation bugs we still have 381 bugs [4] targeted to 
3.5.0.

More in detail [5]:

Whiteboard  NEW ASSIGNEDPOSTTotal
unassigned7   .   .   7
gluster 9   5   2   16
i18n.   .   1   1
infra   28  2   7   37
integration 25  .   6   31
network 18  1   15  34
node24  6   6   36
ppc 2   .   4   6
sla 38  .   18  56
storage 86  10  9   105
ux  22  2   .   24
virt59  4   9   72
Total   318 30  77  425


Maintainers / Assignee:
- Please ensure that completed features are marked in green on Features Status 
Table [2]
- Please remember to rebuild your packages before *2014-08-20 15:00* (supposing 
we keep Thu *2014-08-21 08:00 UTC*) if needed, otherwise nightly
snapshot will be taken.
- If you find a blocker bug please remember to add it to the tracker [1]
- Please fill release notes, the page has been created here [6]
- Please review and add test cases to oVirt 3.5 Third Test Day [7]
- Please update the target to 3.5.1 or later for bugs that won't be in 3.5.0:
  it will ease gathering the blocking bugs for next releases.


Community:
- Due to the RC2 delay, the 3rd test day has been postponed to Aug 28th.
- You're welcome to join us testing next beta release and getting involved in 
oVirt Quality Assurance[8]


[1] http://bugzilla.redhat.com/1073943
[2] http://bit.ly/17qBn6F
[3] http://red.ht/1pVEk7H
[4] http://red.ht/1zT2mSq
[5] http://red.ht/1q7SqNL
[6] http://www.ovirt.org/OVirt_3.5_Release_Notes
[7] http://www.ovirt.org/OVirt_3.5_TestDay
[8] http://www.ovirt.org/OVirt_Quality_Assurance

Thanks,

-- 
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] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2 status

2014-08-20 Thread Oved Ourfali


- Original Message -
 From: Sandro Bonazzola sbona...@redhat.com
 To: Users@ovirt.org, de...@ovirt.org
 Sent: Wednesday, August 20, 2014 10:10:03 AM
 Subject: [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2 status
 
 Hi,
 early this week we postponed oVirt 3.5.0 RC2 to Thu *2014-08-21 08:00 UTC*,
 we'll discuss current status in today oVirt sync meeting and eventually
 postpone RC2 by another week.
 
 Maintainers (supposing we keep Thu *2014-08-21 08:00 UTC*):
 - Please be sure that 3.5 snapshot allow to create VMs before *2014-08-20
 15:00 UTC*
 - Please be sure that no pending patches are going to block the release
 before *2014-08-20 15:00 UTC*
 - If any patch must block the RC release please raise the issue as soon as
 possible.
 
 The bug tracker [1] shows the following proposed blockers to be reviewed:
 
 WhiteboardBug ID  Status  Summary
 infra 1127877 POSTvdsm-tool configure --force does not configure 
 qemu.conf
 properly in the first run on a fresh install

This isn't a blocker. Still working on that, but it shouldn't block anything.

 sla   1129261 NEW prepareImage api call fails with [Errno 2] No 
 such file or
 directory
 sla   1130038 NEW prepareImage api call fails with [Errno 2] No 
 such file or
 directory
 storage   1128776 POSTCan't change a vm disk's storage domain 
 from a file
 domain to a block domain when creating a template from a vm
 storage   1127294 POSTLive Merge: Resolve unknown merge 
 status in vdsm after
 host crash
 storage   1109920 POSTLive Merge: Extend internal block 
 volumes during merge
 
 
 And the following dependencies still open:
 Bug 1041569 - [NFR] libvirt: Returning the watermark for all the images
 opened for writing
 Bug 1102881 - virDomainBlockCommit fails with live snapshots on oVirt block
 storage
 
 
 Some of above blockers may be dropped on today oVirt sync meeting if still
 open.
 Some of the bugs blocking the release prevents automated testing to verify
 the release.
 Please fix them as soon as possible.
 
 
 Feature freeze is now effective, and branch has been created.
 All new patches must be backported to 3.5 branch too.
 Features completed are marked in green on Features Status Table [2]
 
 There are still 425 bugs [3] targeted to 3.5.0.
 Excluding node and documentation bugs we still have 381 bugs [4] targeted to
 3.5.0.
 
 More in detail [5]:
 
 WhiteboardNEW ASSIGNEDPOSTTotal
 unassigned  7   .   .   7
 gluster   9   5   2   16
 i18n  .   .   1   1
 infra 28  2   7   37
 integration   25  .   6   31
 network   18  1   15  34
 node  24  6   6   36
 ppc   2   .   4   6
 sla   38  .   18  56
 storage   86  10  9   105
 ux22  2   .   24
 virt  59  4   9   72
 Total 318 30  77  425
 
 
 Maintainers / Assignee:
 - Please ensure that completed features are marked in green on Features
 Status Table [2]
 - Please remember to rebuild your packages before *2014-08-20 15:00*
 (supposing we keep Thu *2014-08-21 08:00 UTC*) if needed, otherwise nightly
 snapshot will be taken.
 - If you find a blocker bug please remember to add it to the tracker [1]
 - Please fill release notes, the page has been created here [6]
 - Please review and add test cases to oVirt 3.5 Third Test Day [7]
 - Please update the target to 3.5.1 or later for bugs that won't be in 3.5.0:
   it will ease gathering the blocking bugs for next releases.
 
 
 Community:
 - Due to the RC2 delay, the 3rd test day has been postponed to Aug 28th.
 - You're welcome to join us testing next beta release and getting involved in
 oVirt Quality Assurance[8]
 
 
 [1] http://bugzilla.redhat.com/1073943
 [2] http://bit.ly/17qBn6F
 [3] http://red.ht/1pVEk7H
 [4] http://red.ht/1zT2mSq
 [5] http://red.ht/1q7SqNL
 [6] http://www.ovirt.org/OVirt_3.5_Release_Notes
 [7] http://www.ovirt.org/OVirt_3.5_TestDay
 [8] http://www.ovirt.org/OVirt_Quality_Assurance
 
 Thanks,
 
 --
 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
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] AIO setup problem with master failes due to nfs

2014-08-20 Thread Gianluca Cecchi
On Wed, Aug 20, 2014 at 9:06 AM, Gianluca Cecchi gianluca.cec...@gmail.com
wrote:


 result = vdscli.connect().getVdsCapabilities()
   File /usr/lib64/python2.6/xmlrpclib.py, line 1199, in __call__
 return self.__send(self.__name, args)
   File /usr/lib64/python2.6/xmlrpclib.py, line 1489, in __request
 verbose=self.__verbose
   File /usr/lib64/python2.6/xmlrpclib.py, line 1235, in request
 self.send_content(h, request_body)
   File /usr/lib64/python2.6/xmlrpclib.py, line 1349, in send_content
 connection.endheaders()
   File /usr/lib64/python2.6/httplib.py, line 908, in endheaders
 self._send_output()
   File /usr/lib64/python2.6/httplib.py, line 780, in _send_output
 self.send(msg)
   File /usr/lib64/python2.6/httplib.py, line 739, in send
 self.connect()
   File /usr/lib64/python2.6/site-packages/vdsm/sslutils.py, line 181, in
 connect
 sock = socket.create_connection((self.host, self.port), self.timeout)
   File /usr/lib64/python2.6/socket.py, line 567, in create_connection
 raise error, msg
 error: [Errno 111] Connection refused
 2014-08-20 08:49:48 ERROR otopi.context context._executeMethod:161 Failed
 to execute stage 'Closing up': [Errno 111] Connection refused



Sorry, rereading better, it seems not an nfs problem but with getting host
capabilities...
Probably it should be better to put an echo in setup to confirm nfs part
has finished and that we are in another part of setup...

The server is a kvm guest on Fedora 20 system
Indeed when running manually I get
 [root@ovirtita host-deploy]# vdsClient -s 0 getVdsCaps
Connection to 0.0.0.0:54321 refused

what to check?

[root@ovirtita host-deploy]# lsmod|grep kvm
kvm_intel  54317  0
kvm   333734  1 kvm_intel

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


Re: [ovirt-users] Power Management with UPS Network UPS Tools (NUT)

2014-08-20 Thread Eli Mesika
Hi

oVirt 3.5 install hypervisors with the fence-agents package which has a certain 
list of supported power management (PM) cards 
in oVirt 3.5 if you want to add custom PM card in addition to the supported PM 
cards you should follow http://www.ovirt.org/Custom_Fencing

Basically once you write your own script and install it on each host where 
fence-agents package is installed and modify oVirt configuration as described 
in the wiki, you should be able to see your custom agent in the list and use it.

Please let me know if you need any further assist with that 

CCing also Marec G who is in charge of the fence-agents package 

Thanks
Eli

- Original Message -
 From: OvirtAndKvm ov...@goproject.info
 To: users@ovirt.org
 Sent: Wednesday, August 20, 2014 3:04:22 AM
 Subject: [ovirt-users] Power Management with UPS Network UPS Tools (NUT)
 
 I would like to implement Power Management using an Eton E5 UPS, if this is
 not possible then I would like to know what UPS systems can be easily used
 with oVirt.
 
 Can someone point me to information on how to configure the UPS, CentOS 6.5
 (preferably), and oVirt to use the UPS system, so that I could purchase,
 install and implement the UPS.
 
 If anyone has information regarding UPS, please reply to this email with
 links to the information.
 
 Can oVirt use Network UPS Tools (NUT) for Power Management ? If so, is
 there any documentation on this subject that you could provide links to,
 please.
 
 http://www.ovirt.org/Features/HostPowerManagementPolicy
 
 http://www.howtoforge.com/network-ups-tools-nut-for-usb-upss-on-centos-5.5
 http://www.networkupstools.org/docs/user-manual.chunked/ar01s05.html
 http://www.networkupstools.org/features.html
 http://www.ovirt.org/Automatic_Fencing
 
 So far the most common statement I have found is Ignore the warning about
 power management, but this is not what I want to do.
 http://www.r11networks.com/2013/04/ovirt-installation-guide/
 
 http://www.ovirt.org/DraftAdministrationGuide
 
 
 
 http://www.ovirt.org/DraftAdministrationGuide#Host_Power_Management_settings_explained
 
 Choose one of the following:
 
 * apc - APC MasterSwitch network power switch. Not for use with APC 5.x
 power switch devices.
 * apc_snmp - Use with APC 5.x power switch devices.
 * bladecenter - IBM Bladecentre Remote Supervisor Adapter.
 * cisco_ucs - Cisco Unified Computing System.
 * drac5 - Dell Remote Access Controller for Dell computers.
 * drac7 - Dell Remote Access Controller for Dell computers.
 * eps - ePowerSwitch 8M+ network power switch.
 * hpblade - HP BladeSystem.
 * ilo , ilo2 , ilo3 , ilo4 - HP Integrated Lights-Out.
 * ipmilan - Intelligent Platform Management Interface and Sun Integrated
 Lights Out Management devices.
 * rsa - IBM Remote Supervisor Adaptor.
 * rsb - Fujitsu-Siemens RSB management interface.
 * wti - WTI Network PowerSwitch.
 
 Configuring Host Power Management Settings
 
 
 Summary
 
 Configure your host power management device settings to perform host
 life-cycle operations (stop, start, restart) from the Administration Portal.
 
 It is necessary to configure host power management in order to utilize host
 high availability and virtual machine high availability.
 
 
 
 
 ___
 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] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2 status

2014-08-20 Thread Sandro Bonazzola
Il 20/08/2014 09:12, Oved Ourfali ha scritto:
 
 
 - Original Message -
 From: Sandro Bonazzola sbona...@redhat.com
 To: Users@ovirt.org, de...@ovirt.org
 Sent: Wednesday, August 20, 2014 10:10:03 AM
 Subject: [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2 status

 Hi,
 early this week we postponed oVirt 3.5.0 RC2 to Thu *2014-08-21 08:00 UTC*,
 we'll discuss current status in today oVirt sync meeting and eventually
 postpone RC2 by another week.

 Maintainers (supposing we keep Thu *2014-08-21 08:00 UTC*):
 - Please be sure that 3.5 snapshot allow to create VMs before *2014-08-20
 15:00 UTC*
 - Please be sure that no pending patches are going to block the release
 before *2014-08-20 15:00 UTC*
 - If any patch must block the RC release please raise the issue as soon as
 possible.

 The bug tracker [1] shows the following proposed blockers to be reviewed:

 Whiteboard   Bug ID  Status  Summary
 infra1127877 POSTvdsm-tool configure --force does not 
 configure qemu.conf
 properly in the first run on a fresh install
 
 This isn't a blocker. Still working on that, but it shouldn't block anything.

According to nsoffer and me in 
http://lists.ovirt.org/pipermail/users/2014-August/026776.html
looks like it will cause Hosted Engine deployment failure on a clean system and 
also a failure adding a clean system to the Engine.
This is violating release criteria:
MUST: Ovirt/host installation should work flawlessly (w/o SSL)
See http://www.ovirt.org/OVirt_3.5_release-management#MUST

So this is a blocker.



 
 sla  1129261 NEW prepareImage api call fails with [Errno 2] No 
 such file or
 directory
 sla  1130038 NEW prepareImage api call fails with [Errno 2] No 
 such file or
 directory
 storage  1128776 POSTCan't change a vm disk's storage domain 
 from a file
 domain to a block domain when creating a template from a vm
 storage  1127294 POSTLive Merge: Resolve unknown merge 
 status in vdsm after
 host crash
 storage  1109920 POSTLive Merge: Extend internal block 
 volumes during merge


 And the following dependencies still open:
 Bug 1041569 - [NFR] libvirt: Returning the watermark for all the images
 opened for writing
 Bug 1102881 - virDomainBlockCommit fails with live snapshots on oVirt block
 storage


 Some of above blockers may be dropped on today oVirt sync meeting if still
 open.
 Some of the bugs blocking the release prevents automated testing to verify
 the release.
 Please fix them as soon as possible.


 Feature freeze is now effective, and branch has been created.
 All new patches must be backported to 3.5 branch too.
 Features completed are marked in green on Features Status Table [2]

 There are still 425 bugs [3] targeted to 3.5.0.
 Excluding node and documentation bugs we still have 381 bugs [4] targeted to
 3.5.0.

 More in detail [5]:

 Whiteboard   NEW ASSIGNEDPOSTTotal
 unassigned 7   .   .   7
 gluster  9   5   2   16
 i18n .   .   1   1
 infra28  2   7   37
 integration  25  .   6   31
 network  18  1   15  34
 node 24  6   6   36
 ppc  2   .   4   6
 sla  38  .   18  56
 storage  86  10  9   105
 ux   22  2   .   24
 virt 59  4   9   72
 Total318 30  77  425


 Maintainers / Assignee:
 - Please ensure that completed features are marked in green on Features
 Status Table [2]
 - Please remember to rebuild your packages before *2014-08-20 15:00*
 (supposing we keep Thu *2014-08-21 08:00 UTC*) if needed, otherwise nightly
 snapshot will be taken.
 - If you find a blocker bug please remember to add it to the tracker [1]
 - Please fill release notes, the page has been created here [6]
 - Please review and add test cases to oVirt 3.5 Third Test Day [7]
 - Please update the target to 3.5.1 or later for bugs that won't be in 3.5.0:
   it will ease gathering the blocking bugs for next releases.


 Community:
 - Due to the RC2 delay, the 3rd test day has been postponed to Aug 28th.
 - You're welcome to join us testing next beta release and getting involved in
 oVirt Quality Assurance[8]


 [1] http://bugzilla.redhat.com/1073943
 [2] http://bit.ly/17qBn6F
 [3] http://red.ht/1pVEk7H
 [4] http://red.ht/1zT2mSq
 [5] http://red.ht/1q7SqNL
 [6] http://www.ovirt.org/OVirt_3.5_Release_Notes
 [7] http://www.ovirt.org/OVirt_3.5_TestDay
 [8] http://www.ovirt.org/OVirt_Quality_Assurance

 Thanks,

 --
 Sandro Bonazzola
 Better technology. Faster innovation. Powered by community collaboration.
 See how it works at redhat.com
 ___
 Users mailing list
 Users@ovirt.org
 

Re: [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2 status

2014-08-20 Thread Oved Ourfali


- Original Message -
 From: Sandro Bonazzola sbona...@redhat.com
 To: Oved Ourfali ov...@redhat.com
 Cc: Users@ovirt.org, de...@ovirt.org
 Sent: Wednesday, August 20, 2014 11:08:52 AM
 Subject: Re: [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2 status
 
 Il 20/08/2014 09:12, Oved Ourfali ha scritto:
  
  
  - Original Message -
  From: Sandro Bonazzola sbona...@redhat.com
  To: Users@ovirt.org, de...@ovirt.org
  Sent: Wednesday, August 20, 2014 10:10:03 AM
  Subject: [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2 status
 
  Hi,
  early this week we postponed oVirt 3.5.0 RC2 to Thu *2014-08-21 08:00
  UTC*,
  we'll discuss current status in today oVirt sync meeting and eventually
  postpone RC2 by another week.
 
  Maintainers (supposing we keep Thu *2014-08-21 08:00 UTC*):
  - Please be sure that 3.5 snapshot allow to create VMs before *2014-08-20
  15:00 UTC*
  - Please be sure that no pending patches are going to block the release
  before *2014-08-20 15:00 UTC*
  - If any patch must block the RC release please raise the issue as soon as
  possible.
 
  The bug tracker [1] shows the following proposed blockers to be reviewed:
 
  Whiteboard Bug ID  Status  Summary
  infra  1127877 POSTvdsm-tool configure --force does not 
  configure
  qemu.conf
  properly in the first run on a fresh install
  
  This isn't a blocker. Still working on that, but it shouldn't block
  anything.
 
 According to nsoffer and me in
 http://lists.ovirt.org/pipermail/users/2014-August/026776.html
 looks like it will cause Hosted Engine deployment failure on a clean system
 and also a failure adding a clean system to the Engine.
 This is violating release criteria:
 MUST: Ovirt/host installation should work flawlessly (w/o SSL)
 See http://www.ovirt.org/OVirt_3.5_release-management#MUST
 
 So this is a blocker.
 
 

Okay.
I'll check the status and return with an ETA.

Oved

 
  
  sla1129261 NEW prepareImage api call fails with [Errno 
  2] No such file
  or
  directory
  sla1130038 NEW prepareImage api call fails with [Errno 
  2] No such file
  or
  directory
  storage1128776 POSTCan't change a vm disk's storage domain 
  from a file
  domain to a block domain when creating a template from a vm
  storage1127294 POSTLive Merge: Resolve unknown merge 
  status in vdsm
  after
  host crash
  storage1109920 POSTLive Merge: Extend internal block 
  volumes during
  merge
 
 
  And the following dependencies still open:
  Bug 1041569 - [NFR] libvirt: Returning the watermark for all the images
  opened for writing
  Bug 1102881 - virDomainBlockCommit fails with live snapshots on oVirt
  block
  storage
 
 
  Some of above blockers may be dropped on today oVirt sync meeting if still
  open.
  Some of the bugs blocking the release prevents automated testing to verify
  the release.
  Please fix them as soon as possible.
 
 
  Feature freeze is now effective, and branch has been created.
  All new patches must be backported to 3.5 branch too.
  Features completed are marked in green on Features Status Table [2]
 
  There are still 425 bugs [3] targeted to 3.5.0.
  Excluding node and documentation bugs we still have 381 bugs [4] targeted
  to
  3.5.0.
 
  More in detail [5]:
 
  Whiteboard NEW ASSIGNEDPOSTTotal
  unassigned   7   .   .   7
  gluster9   5   2   16
  i18n   .   .   1   1
  infra  28  2   7   37
  integration25  .   6   31
  network18  1   15  34
  node   24  6   6   36
  ppc2   .   4   6
  sla38  .   18  56
  storage86  10  9   105
  ux 22  2   .   24
  virt   59  4   9   72
  Total  318 30  77  425
 
 
  Maintainers / Assignee:
  - Please ensure that completed features are marked in green on Features
  Status Table [2]
  - Please remember to rebuild your packages before *2014-08-20 15:00*
  (supposing we keep Thu *2014-08-21 08:00 UTC*) if needed, otherwise
  nightly
  snapshot will be taken.
  - If you find a blocker bug please remember to add it to the tracker [1]
  - Please fill release notes, the page has been created here [6]
  - Please review and add test cases to oVirt 3.5 Third Test Day [7]
  - Please update the target to 3.5.1 or later for bugs that won't be in
  3.5.0:
it will ease gathering the blocking bugs for next releases.
 
 
  Community:
  - Due to the RC2 delay, the 3rd test day has been postponed to Aug 28th.
  - You're welcome to join us testing next beta release and getting involved
  in
  oVirt Quality Assurance[8]
 
 
  [1] 

Re: [ovirt-users] vm install via iso - optical drive eject behaviour?

2014-08-20 Thread Omer Frenkel


- Original Message -
 From: Paul Jansen vla...@yahoo.com.au
 To: users users@ovirt.org
 Sent: Tuesday, August 19, 2014 2:25:41 PM
 Subject: [ovirt-users] vm install via iso - optical drive eject behaviour?
 
 Hello.
 I currently have oVirt 3.4.x set up.
 A colleague mentioned that he was having an issue where booting a VM with an
 attached iso and installing via cd/dvd does not allow the contents of the
 'drive' to eject after the install. Sure enough, I have tested this myself
 and observed the same behaviour.
 Installing an EL/fedora iso image with a kickstart that has a 'reboot
 --eject' line in will eject the 'drive' after the installing when doing the
 exact same thing on VMware ESXi (and 'real' hardware).
 A suggestion was made that VMware emulates a laptop style optical drive that
 once the disk ejects the system cannot close the drive bay upon reboot -
 this is a manual operation.
 Does oVirt emulate a destop style drive where even if the disk is ejected,
 when a reboot occurs the drive will close?
 
 The long an short of this that even though the 'reboot --eject' option is in
 the kickstart, the iso image seems be be reattached when the VM reboots and
 the installs process starts again. An infinite loop effectively.
 
 I'm told this isn't an issue with an KVM/Qemu VM under virt-manager.
 
 Any suggestions as to how to solve this?
 I should point out that I cannot simply extract files and boot via PXE as
 this process is supposed to be testing an install process via generated
 media.
 
 Thanks.

there is an open RFE for detecting the reboot and eject the cd in run once.

until that, what i do is: (assuming the HD doesn't have anything bootable on it)
edit the vm, 
select in 'boot options':
 first device- hard disk,
 second device-CD and select the CD file you want to use.

start the vm regularly (not run once)

 
 
 ___
 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] vm install via iso - optical drive eject behaviour?

2014-08-20 Thread Jorick Astrego


On 08/20/2014 11:21 AM, Omer Frenkel wrote:


- Original Message -

From: Paul Jansen vla...@yahoo.com.au
To: users users@ovirt.org
Sent: Tuesday, August 19, 2014 2:25:41 PM
Subject: [ovirt-users] vm install via iso - optical drive eject behaviour?

Hello.
I currently have oVirt 3.4.x set up.
A colleague mentioned that he was having an issue where booting a VM with an
attached iso and installing via cd/dvd does not allow the contents of the
'drive' to eject after the install. Sure enough, I have tested this myself
and observed the same behaviour.
Installing an EL/fedora iso image with a kickstart that has a 'reboot
--eject' line in will eject the 'drive' after the installing when doing the
exact same thing on VMware ESXi (and 'real' hardware).
A suggestion was made that VMware emulates a laptop style optical drive that
once the disk ejects the system cannot close the drive bay upon reboot -
this is a manual operation.
Does oVirt emulate a destop style drive where even if the disk is ejected,
when a reboot occurs the drive will close?

The long an short of this that even though the 'reboot --eject' option is in
the kickstart, the iso image seems be be reattached when the VM reboots and
the installs process starts again. An infinite loop effectively.

I'm told this isn't an issue with an KVM/Qemu VM under virt-manager.

Any suggestions as to how to solve this?
I should point out that I cannot simply extract files and boot via PXE as
this process is supposed to be testing an install process via generated
media.

Thanks.

there is an open RFE for detecting the reboot and eject the cd in run once.

until that, what i do is: (assuming the HD doesn't have anything bootable on it)
edit the vm,
select in 'boot options':
  first device- hard disk,
  second device-CD and select the CD file you want to use.

start the vm regularly (not run once)

Does this work for you?

In 3.5rc1, I have the following issue:

https://bugzilla.redhat.com/show_bug.cgi?id=1131018

   Description of problem:
   Installing a VM with the Second Boot device CDROM. After installation, I 
choose reboot in the VM and the installer of the CDROM appears again even 
though I have the HDD as first boot device.

   When I power down the VM, don't change anything, and power it up again. It 
does start from the local HDD

Kind regards,

Jorick Astrego
Netbulae

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


[ovirt-users] Ovirt api function

2014-08-20 Thread Shanil S
Hi,


I would like to create the following functions using the ovirt api

1. Rebuild VM
2. Restore the screenthots of one vm to another vm
3. Display cpu,network etc usages

I couldn't find out any direct api method to do the above, Is it possible
to do these operations using api ? If anyone knows it please help me to
sort out it.



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


Re: [ovirt-users] vm install via iso - optical drive eject behaviour?

2014-08-20 Thread Omer Frenkel


- Original Message -
 From: Jorick Astrego j.astr...@netbulae.eu
 To: users@ovirt.org
 Sent: Wednesday, August 20, 2014 12:53:56 PM
 Subject: Re: [ovirt-users] vm install via iso - optical drive eject   
 behaviour?
 
 
 On 08/20/2014 11:21 AM, Omer Frenkel wrote:
 
 
 
 - Original Message -
 
 
 
 From: Paul Jansen vla...@yahoo.com.au To: users users@ovirt.org Sent:
 Tuesday, August 19, 2014 2:25:41 PM
 Subject: [ovirt-users] vm install via iso - optical drive eject behaviour?
 
 Hello.
 I currently have oVirt 3.4.x set up.
 A colleague mentioned that he was having an issue where booting a VM with an
 attached iso and installing via cd/dvd does not allow the contents of the
 'drive' to eject after the install. Sure enough, I have tested this myself
 and observed the same behaviour.
 Installing an EL/fedora iso image with a kickstart that has a 'reboot
 --eject' line in will eject the 'drive' after the installing when doing the
 exact same thing on VMware ESXi (and 'real' hardware).
 A suggestion was made that VMware emulates a laptop style optical drive that
 once the disk ejects the system cannot close the drive bay upon reboot -
 this is a manual operation.
 Does oVirt emulate a destop style drive where even if the disk is ejected,
 when a reboot occurs the drive will close?
 
 The long an short of this that even though the 'reboot --eject' option is in
 the kickstart, the iso image seems be be reattached when the VM reboots and
 the installs process starts again. An infinite loop effectively.
 
 I'm told this isn't an issue with an KVM/Qemu VM under virt-manager.
 
 Any suggestions as to how to solve this?
 I should point out that I cannot simply extract files and boot via PXE as
 this process is supposed to be testing an install process via generated
 media.
 
 Thanks.
 there is an open RFE for detecting the reboot and eject the cd in run once.
 
 until that, what i do is: (assuming the HD doesn't have anything bootable on
 it)
 edit the vm,
 select in 'boot options':
  first device- hard disk,
  second device-CD and select the CD file you want to use.
 
 start the vm regularly (not run once)
 Does this work for you?
 

interesting, i just installed one vm and it worked for me yesterday,
and i tried again now couple of times (to be sure) and i see the same issue.

trying to investigate now what is the difference

 In 3.5rc1, I have the following issue:
 
 https://bugzilla.redhat.com/show_bug.cgi?id=1131018
 
 
 
 
 Description of problem:
 Installing a VM with the Second Boot device CDROM. After installation, I
 choose reboot in the VM and the installer of the CDROM appears again even
 though I have the HDD as first boot device.
 
 When I power down the VM, don't change anything, and power it up again. It
 does start from the local HDD
 Kind regards,
 
 Jorick Astrego
 Netbulae
 
 
 ___
 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] can you re-create self hosted storage pool?

2014-08-20 Thread Joop
On 19-8-2014 17:08, Darrell Budic wrote:
 Through a series of creative experiments, I've managed to corrupt the lock 
 files for my self-hosted engine's storage pool. Is there any way to destroy 
 and recreate the pool without reinstalling the self-hosted engine on all 
 systems (after destroying it entirely)?


Don't know if my situation reflects yours but I had a problem with
hosted-engine too. I had a way newer version of kvm/libvirt on host01
and decided to yum remove it. Sofar no problem but it also removed
hosted-engine and then i had a problem. In the end I solved it by just
reinstalling hosted-engine and running engine-deploy on host01 and
answering the question if this was a reinstall and pointing to the
anwser file on host02. Once it was done all came up nicely.
So it seems possible to maybe do this in a roundrobin way and
update/reinstall your hosts.

Joop

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


[ovirt-users] VM's remain listed after cleanup and reinstall

2014-08-20 Thread Jorick Astrego

Hi,

Running ovirt 3.5rc1 All In One, there is something strange going on, 
where does ovirt store it's VM definitions?


I did an engine-cleanup and removed everything from /var/lib/images, but 
after a reinstall there are still test VM's listed in ovirt


   history

 669  engine-cleanup
 672  rm -rf /var/lib/images-*
 673  rm -rf /var/lib/images/*
 674  rm -rf /var/lib/exports/iso/*
 676  engine-setup --jboss-home=/usr/share/ovirt-engine-jboss-as

   I go to the engine:

Engine-cleanup drops the database, is there somewhere else they get 
stored?  They are listed as external but there is nothing external 
hooked up to the ovirt (all in one)


Kind regards,

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


Re: [ovirt-users] VM's remain listed after cleanup and reinstall

2014-08-20 Thread Omer Frenkel


- Original Message -
 From: Jorick Astrego j.astr...@netbulae.eu
 To: users@ovirt.org
 Sent: Wednesday, August 20, 2014 4:16:54 PM
 Subject: [ovirt-users] VM's remain listed after cleanup and reinstall
 
 Hi,
 
 Running ovirt 3.5rc1 All In One, there is something strange going on, where
 does ovirt store it's VM definitions?
 
 I did an engine-cleanup and removed everything from /var/lib/images, but
 after a reinstall there are still test VM's listed in ovirt
 
 
 history
 
 669 engine-cleanup
 672 rm -rf /var/lib/images-*
 673 rm -rf /var/lib/images/*
 674 rm -rf /var/lib/exports/iso/*
 676 engine-setup --jboss-home=/usr/share/ovirt-engine-jboss-as
 
 I go to the engine:
 
 Engine-cleanup drops the database, is there somewhere else they get stored?
 They are listed as external but there is nothing external hooked up to the
 ovirt (all in one)
 

external means the engine discovered these vms are actually running on your 
host, but its not in the db,
so the engine import the information from vdsm.

you can just stop the vms and remove them.

but for next time
before you do cleanup, stop the vms :)

 Kind regards,
 
 Jorick Astrego
 Netbulae
 
 ___
 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] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2 status

2014-08-20 Thread Vinzenz Feenstra

On 08/20/2014 09:10 AM, Sandro Bonazzola wrote:

Hi,
early this week we postponed oVirt 3.5.0 RC2 to Thu *2014-08-21 08:00 UTC*,
we'll discuss current status in today oVirt sync meeting and eventually 
postpone RC2 by another week.

Maintainers (supposing we keep Thu *2014-08-21 08:00 UTC*):
- Please be sure that 3.5 snapshot allow to create VMs before *2014-08-20 15:00 
UTC*
- Please be sure that no pending patches are going to block the release before 
*2014-08-20 15:00 UTC*
- If any patch must block the RC release please raise the issue as soon as 
possible.

The bug tracker [1] shows the following proposed blockers to be reviewed:

Whiteboard  Bug ID  Status  Summary
infra   1127877 POSTvdsm-tool configure --force does not configure 
qemu.conf properly in the first run on a fresh install
sla 1129261 NEW prepareImage api call fails with [Errno 2] No 
such file or directory
sla 1130038 NEW prepareImage api call fails with [Errno 2] No 
such file or directory
storage 1128776 POSTCan't change a vm disk's storage domain from a 
file domain to a block domain when creating a template from a vm
storage 1127294 POSTLive Merge: Resolve unknown merge status in 
vdsm after host crash
storage 1109920 POSTLive Merge: Extend internal block volumes 
during merge
I actually think that 
https://bugzilla.redhat.com/show_bug.cgi?id=1131548 should be considered 
a blocker, however this seems to be related to live merge currently it 
is assigned to virt.
The point is that there's an exception thrown during recovery which will 
cause the state of the VM to be in a very unusable state.

Known indications so far:
- It's shown as 'Paused' in the UI while the VM effectively is 'UP'
- The guest agent communication channels are not initialized due to the 
earlier bail out caused by the exception

   - Consequence visible in UI:
   - You can't soft shutdown the vm
   - Causes most likely exceptions when trying to access methods from 
the guest agent during shutdown of the VM, live migration might fail

   - and other issues




And the following dependencies still open:
Bug 1041569 - [NFR] libvirt: Returning the watermark for all the images opened 
for writing
Bug 1102881 - virDomainBlockCommit fails with live snapshots on oVirt block 
storage


Some of above blockers may be dropped on today oVirt sync meeting if still open.
Some of the bugs blocking the release prevents automated testing to verify the 
release.
Please fix them as soon as possible.


Feature freeze is now effective, and branch has been created.
All new patches must be backported to 3.5 branch too.
Features completed are marked in green on Features Status Table [2]

There are still 425 bugs [3] targeted to 3.5.0.
Excluding node and documentation bugs we still have 381 bugs [4] targeted to 
3.5.0.

More in detail [5]:

Whiteboard  NEW ASSIGNEDPOSTTotal
unassigned  7   .   .   7
gluster 9   5   2   16
i18n.   .   1   1
infra   28  2   7   37
integration 25  .   6   31
network 18  1   15  34
node24  6   6   36
ppc 2   .   4   6
sla 38  .   18  56
storage 86  10  9   105
ux  22  2   .   24
virt59  4   9   72
Total   318 30  77  425


Maintainers / Assignee:
- Please ensure that completed features are marked in green on Features Status 
Table [2]
- Please remember to rebuild your packages before *2014-08-20 15:00* (supposing 
we keep Thu *2014-08-21 08:00 UTC*) if needed, otherwise nightly
snapshot will be taken.
- If you find a blocker bug please remember to add it to the tracker [1]
- Please fill release notes, the page has been created here [6]
- Please review and add test cases to oVirt 3.5 Third Test Day [7]
- Please update the target to 3.5.1 or later for bugs that won't be in 3.5.0:
   it will ease gathering the blocking bugs for next releases.


Community:
- Due to the RC2 delay, the 3rd test day has been postponed to Aug 28th.
- You're welcome to join us testing next beta release and getting involved in 
oVirt Quality Assurance[8]


[1] http://bugzilla.redhat.com/1073943
[2] http://bit.ly/17qBn6F
[3] http://red.ht/1pVEk7H
[4] http://red.ht/1zT2mSq
[5] http://red.ht/1q7SqNL
[6] http://www.ovirt.org/OVirt_3.5_Release_Notes
[7] http://www.ovirt.org/OVirt_3.5_TestDay
[8] http://www.ovirt.org/OVirt_Quality_Assurance

Thanks,




--
Regards,

Vinzenz Feenstra | Senior Software Engineer
RedHat Engineering Virtualization R  D
Phone: +420 532 294 625
IRC: vfeenstr or evilissimo

Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com


Re: [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2 status

2014-08-20 Thread Vinzenz Feenstra

On 08/20/2014 03:40 PM, Vinzenz Feenstra wrote:

On 08/20/2014 09:10 AM, Sandro Bonazzola wrote:

Hi,
early this week we postponed oVirt 3.5.0 RC2 to Thu *2014-08-21 08:00 
UTC*,
we'll discuss current status in today oVirt sync meeting and 
eventually postpone RC2 by another week.


Maintainers (supposing we keep Thu *2014-08-21 08:00 UTC*):
- Please be sure that 3.5 snapshot allow to create VMs before 
*2014-08-20 15:00 UTC*
- Please be sure that no pending patches are going to block the 
release before *2014-08-20 15:00 UTC*
- If any patch must block the RC release please raise the issue as 
soon as possible.


The bug tracker [1] shows the following proposed blockers to be 
reviewed:


WhiteboardBug IDStatusSummary
infra1127877POSTvdsm-tool configure --force does not 
configure qemu.conf properly in the first run on a fresh install
sla1129261NEWprepareImage api call fails with [Errno 
2] No such file or directory
sla1130038NEWprepareImage api call fails with [Errno 
2] No such file or directory
storage1128776POSTCan't change a vm disk's storage 
domain from a file domain to a block domain when creating a template 
from a vm
storage1127294POSTLive Merge: Resolve unknown merge 
status in vdsm after host crash
storage1109920POSTLive Merge: Extend internal block 
volumes during merge
I actually think that 
https://bugzilla.redhat.com/show_bug.cgi?id=1131548 should be 
considered a blocker, however this seems to be related to live merge 
currently it is assigned to virt.
The point is that there's an exception thrown during recovery which 
will cause the state of the VM to be in a very unusable state.

Known indications so far:
- It's shown as 'Paused' in the UI while the VM effectively is 'UP'
- The guest agent communication channels are not initialized due to 
the earlier bail out caused by the exception

   - Consequence visible in UI:
   - You can't soft shutdown the vm
   - Causes most likely exceptions when trying to access methods from 
the guest agent during shutdown of the VM, live migration might fail

   - and other issues
So the fix for this issue I described above is already merged to 
ovirt-3.5 the bug had two issues and the first one is solved already by 
the merged patch. The second portion on the other hand is supposedly 
less severe so it might not be a blocker anymore.





And the following dependencies still open:
Bug 1041569 - [NFR] libvirt: Returning the watermark for all the 
images opened for writing
Bug 1102881 - virDomainBlockCommit fails with live snapshots on oVirt 
block storage



Some of above blockers may be dropped on today oVirt sync meeting if 
still open.
Some of the bugs blocking the release prevents automated testing to 
verify the release.

Please fix them as soon as possible.


Feature freeze is now effective, and branch has been created.
All new patches must be backported to 3.5 branch too.
Features completed are marked in green on Features Status Table [2]

There are still 425 bugs [3] targeted to 3.5.0.
Excluding node and documentation bugs we still have 381 bugs [4] 
targeted to 3.5.0.


More in detail [5]:

WhiteboardNEWASSIGNEDPOSTTotal
unassigned 7..7
gluster95216
i18n..11
infra282737
integration25.631
network1811534
node246636
ppc2.46
sla38.1856
storage86109105
ux222.24
virt594972
Total3183077425


Maintainers / Assignee:
- Please ensure that completed features are marked in green on 
Features Status Table [2]
- Please remember to rebuild your packages before *2014-08-20 15:00* 
(supposing we keep Thu *2014-08-21 08:00 UTC*) if needed, otherwise 
nightly

snapshot will be taken.
- If you find a blocker bug please remember to add it to the tracker [1]
- Please fill release notes, the page has been created here [6]
- Please review and add test cases to oVirt 3.5 Third Test Day [7]
- Please update the target to 3.5.1 or later for bugs that won't be 
in 3.5.0:

   it will ease gathering the blocking bugs for next releases.


Community:
- Due to the RC2 delay, the 3rd test day has been postponed to Aug 28th.
- You're welcome to join us testing next beta release and getting 
involved in oVirt Quality Assurance[8]



[1] http://bugzilla.redhat.com/1073943
[2] http://bit.ly/17qBn6F
[3] http://red.ht/1pVEk7H
[4] http://red.ht/1zT2mSq
[5] http://red.ht/1q7SqNL
[6] http://www.ovirt.org/OVirt_3.5_Release_Notes
[7] http://www.ovirt.org/OVirt_3.5_TestDay
[8] http://www.ovirt.org/OVirt_Quality_Assurance

Thanks,







--
Regards,

Vinzenz Feenstra | Senior Software Engineer
RedHat Engineering Virtualization R  D
Phone: +420 532 294 625
IRC: vfeenstr or 

Re: [ovirt-users] vm install via iso - optical drive eject behaviour?

2014-08-20 Thread Omer Frenkel


- Original Message -
 From: Omer Frenkel ofren...@redhat.com
 To: Jorick Astrego j.astr...@netbulae.eu
 Cc: users@ovirt.org
 Sent: Wednesday, August 20, 2014 2:16:25 PM
 Subject: Re: [ovirt-users] vm install via iso - optical drive eject   
 behaviour?
 
 
 
 - Original Message -
  From: Jorick Astrego j.astr...@netbulae.eu
  To: users@ovirt.org
  Sent: Wednesday, August 20, 2014 12:53:56 PM
  Subject: Re: [ovirt-users] vm install via iso - optical drive eject
  behaviour?
  
  
  On 08/20/2014 11:21 AM, Omer Frenkel wrote:
  
  
  
  - Original Message -
  
  
  
  From: Paul Jansen vla...@yahoo.com.au To: users users@ovirt.org
  Sent:
  Tuesday, August 19, 2014 2:25:41 PM
  Subject: [ovirt-users] vm install via iso - optical drive eject behaviour?
  
  Hello.
  I currently have oVirt 3.4.x set up.
  A colleague mentioned that he was having an issue where booting a VM with
  an
  attached iso and installing via cd/dvd does not allow the contents of the
  'drive' to eject after the install. Sure enough, I have tested this myself
  and observed the same behaviour.
  Installing an EL/fedora iso image with a kickstart that has a 'reboot
  --eject' line in will eject the 'drive' after the installing when doing the
  exact same thing on VMware ESXi (and 'real' hardware).
  A suggestion was made that VMware emulates a laptop style optical drive
  that
  once the disk ejects the system cannot close the drive bay upon reboot -
  this is a manual operation.
  Does oVirt emulate a destop style drive where even if the disk is ejected,
  when a reboot occurs the drive will close?
  
  The long an short of this that even though the 'reboot --eject' option is
  in
  the kickstart, the iso image seems be be reattached when the VM reboots and
  the installs process starts again. An infinite loop effectively.
  
  I'm told this isn't an issue with an KVM/Qemu VM under virt-manager.
  
  Any suggestions as to how to solve this?
  I should point out that I cannot simply extract files and boot via PXE as
  this process is supposed to be testing an install process via generated
  media.
  
  Thanks.
  there is an open RFE for detecting the reboot and eject the cd in run once.
  
  until that, what i do is: (assuming the HD doesn't have anything bootable
  on
  it)
  edit the vm,
  select in 'boot options':
   first device- hard disk,
   second device-CD and select the CD file you want to use.
  
  start the vm regularly (not run once)
  Does this work for you?
  
 
 interesting, i just installed one vm and it worked for me yesterday,
 and i tried again now couple of times (to be sure) and i see the same issue.
 
 trying to investigate now what is the difference
 

ok found the issue, there is a bug in add disk that cause the boot order to be 
wrong (order is calculated before the disk is added).
looks like this affects vms created from blank (or other diskless) template and 
the disk is added afterwards
while this is fixed, a workaround is to first create the vm and the disk,
and only after that, edit the vm and choose the wanted boot options, this will 
cause the boot order to be re-calculated, taking into account also the disk.

if your vm already created, you can edit the boot order to something and then 
return it to what you like.

  In 3.5rc1, I have the following issue:
  
  https://bugzilla.redhat.com/show_bug.cgi?id=1131018
  
  
  
  
  Description of problem:
  Installing a VM with the Second Boot device CDROM. After installation, I
  choose reboot in the VM and the installer of the CDROM appears again even
  though I have the HDD as first boot device.
  
  When I power down the VM, don't change anything, and power it up again. It
  does start from the local HDD
  Kind regards,
  
  Jorick Astrego
  Netbulae
  
  
  ___
  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


[ovirt-users] oVirt 3.5.0 release schedule updated

2014-08-20 Thread Sandro Bonazzola
Here is the updated schedule for oVirt 3.5.0 after today oVirt sync meeting 
discussion.
These are tentative planning dates and may change:

General availability: 2014-09-17 (Wed)
oVirt 3.5 Third Test Day: 2014-09-11 (Thu)
RC2 Build:2014-09-03 (Wed)
Build refresh:2014-08-21 (Thu)

Release management page has been updated accordingly:
http://www.ovirt.org/OVirt_3.5_release-management

oVirt Google Calendar has been updated accordingly:
ICAL: 
https://www.google.com/calendar/ical/ppqtk46u9cglj7l987ruo2l0f8%40group.calendar.google.com/public/basic.ics
XML: 
https://www.google.com/calendar/feeds/ppqtk46u9cglj7l987ruo2l0f8%40group.calendar.google.com/public/basic
HTML: 
https://www.google.com/calendar/embed?src=ppqtk46u9cglj7l987ruo2l0f8%40group.calendar.google.comctz=UTC


Thanks,

-- 
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] vm install via iso - optical drive eject behaviour?

2014-08-20 Thread Sven Kieske
Also this bug regarding boot order with cloud init
might be relevant:

https://bugzilla.redhat.com/show_bug.cgi?id=1064927

Am 20.08.2014 16:20, schrieb Omer Frenkel:
 
 
 - Original Message -
 From: Omer Frenkel ofren...@redhat.com
 To: Jorick Astrego j.astr...@netbulae.eu
 Cc: users@ovirt.org
 Sent: Wednesday, August 20, 2014 2:16:25 PM
 Subject: Re: [ovirt-users] vm install via iso - optical driveeject   
 behaviour?



 - Original Message -
 From: Jorick Astrego j.astr...@netbulae.eu
 To: users@ovirt.org
 Sent: Wednesday, August 20, 2014 12:53:56 PM
 Subject: Re: [ovirt-users] vm install via iso - optical drive eject
 behaviour?


 On 08/20/2014 11:21 AM, Omer Frenkel wrote:



 - Original Message -



 From: Paul Jansen vla...@yahoo.com.au To: users users@ovirt.org
 Sent:
 Tuesday, August 19, 2014 2:25:41 PM
 Subject: [ovirt-users] vm install via iso - optical drive eject behaviour?

 Hello.
 I currently have oVirt 3.4.x set up.
 A colleague mentioned that he was having an issue where booting a VM with
 an
 attached iso and installing via cd/dvd does not allow the contents of the
 'drive' to eject after the install. Sure enough, I have tested this myself
 and observed the same behaviour.
 Installing an EL/fedora iso image with a kickstart that has a 'reboot
 --eject' line in will eject the 'drive' after the installing when doing the
 exact same thing on VMware ESXi (and 'real' hardware).
 A suggestion was made that VMware emulates a laptop style optical drive
 that
 once the disk ejects the system cannot close the drive bay upon reboot -
 this is a manual operation.
 Does oVirt emulate a destop style drive where even if the disk is ejected,
 when a reboot occurs the drive will close?

 The long an short of this that even though the 'reboot --eject' option is
 in
 the kickstart, the iso image seems be be reattached when the VM reboots and
 the installs process starts again. An infinite loop effectively.

 I'm told this isn't an issue with an KVM/Qemu VM under virt-manager.

 Any suggestions as to how to solve this?
 I should point out that I cannot simply extract files and boot via PXE as
 this process is supposed to be testing an install process via generated
 media.

 Thanks.
 there is an open RFE for detecting the reboot and eject the cd in run once.

 until that, what i do is: (assuming the HD doesn't have anything bootable
 on
 it)
 edit the vm,
 select in 'boot options':
  first device- hard disk,
  second device-CD and select the CD file you want to use.

 start the vm regularly (not run once)
 Does this work for you?


 interesting, i just installed one vm and it worked for me yesterday,
 and i tried again now couple of times (to be sure) and i see the same issue.

 trying to investigate now what is the difference

 
 ok found the issue, there is a bug in add disk that cause the boot order to 
 be wrong (order is calculated before the disk is added).
 looks like this affects vms created from blank (or other diskless) template 
 and the disk is added afterwards
 while this is fixed, a workaround is to first create the vm and the disk,
 and only after that, edit the vm and choose the wanted boot options, this 
 will cause the boot order to be re-calculated, taking into account also the 
 disk.
 
 if your vm already created, you can edit the boot order to something and then 
 return it to what you like.
 
 In 3.5rc1, I have the following issue:

 https://bugzilla.redhat.com/show_bug.cgi?id=1131018




 Description of problem:
 Installing a VM with the Second Boot device CDROM. After installation, I
 choose reboot in the VM and the installer of the CDROM appears again even
 though I have the HDD as first boot device.

 When I power down the VM, don't change anything, and power it up again. It
 does start from the local HDD
 Kind regards,

 Jorick Astrego
 Netbulae


 ___
 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
 
 
 

-- 
Mit freundlichen Grüßen / Regards

Sven Kieske

Systemadministrator
Mittwald CM Service GmbH  Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] oVirt Weekly Sync Minutes: Aug. 20, 2014

2014-08-20 Thread Brian Proffitt
=
#ovirt: oVirt Weekly Sync
=


Meeting started by bkp at 14:03:25 UTC. The full logs are available at
http://ovirt.org/meetings/ovirt/2014/ovirt.2014-08-20-14.03.log.html .



Meeting summary
---
* Agenda and Roll Call  (bkp, 14:03:56)
  * infra update  (bkp, 14:04:32)
  * 3.4.z updates  (bkp, 14:04:33)
  * 3.5 status  (bkp, 14:04:33)
  * conferences and workshops  (bkp, 14:04:33)
  * other topics  (bkp, 14:04:33)

* infra update  (bkp, 14:05:16)
  * infra PHX setup has a working foreman-proxy running, starting to
spawn vms and autoinstall directly from foreman.ovirt.org  (bkp,
14:09:30)
  * infra jenkins and gerrit to be upgraded soon (hopefully this week)
(bkp, 14:09:30)
  * infra New task created of migrating master-related vdsm jobs to
f20/f21  (bkp, 14:09:30)

* 3.4.z updates  (bkp, 14:11:11)
  * 3.4.z updates 7 bugs still open, no blockers.  (bkp, 14:23:03)
  * 3.4.z updates RC targeted to 2014-09-09  (bkp, 14:23:03)
  * 3.4.z updates A nasty bug that prevents exporting (and probably a
bunch of other operations) on vDisks that were imported to block
storage from file storage -
https://bugzilla.redhat.com/show_bug.cgi?id=1130761  (bkp, 14:23:03)
  * 3.4.z updates Documentation will be added to 3.4.4 release notes, as
well as 3.4.2 and 3.4.3, retroactively  (bkp, 14:23:03)

* 3.5 status  (bkp, 14:23:26)
  * 3.4.z updates An async build will be made for vdsm for 3.4.z  (bkp,
14:24:26)
  * 3.5 status integration oVirt 3.5.0 RC2 not ready for 08-21-14
release  (bkp, 14:37:09)
  * 3.5 status integration Six blockers outstanding, and two dependency
bugs still open, so cannot qualify for RC  (bkp, 14:37:09)
  * 3.5 status infra BZ 1127877 Awaiting review from danken, with
ybronhei at LinuxCon.  (bkp, 14:52:58)
  * 3.5 status infra BZ 1127877 Assistance to review
http://gerrit.ovirt.org/#/c/31400/2 and the rest of

http://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:configurators_reorg,n,z
requested; These were +1d or had no comments  (bkp, 14:52:58)
  * 3.5 status sla BZ 1129261 waiting for the logs, going to append it
there  (bkp, 15:00:27)
  * 3.5 status sla BZ 1130038 waiting for the logs, going to append it
there  (bkp, 15:00:27)
  * 3.5 status storage Blockers covered earlier in meeting  (bkp,
15:00:27)

* Conferences and Workshops  (bkp, 15:03:44)
  * Conferences and Workshops LinuxCon NA in progress. Three oVirt talks
scheduled, lots of booth time for me. (Including now)  (bkp,
15:03:44)

* Other Topics  (bkp, 15:04:00)

Meeting ended at 15:06:48 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* bkp (88)
* sbonazzo (38)
* danken (36)
* amureini (17)
* oved (16)
* alitke (13)
* msivak (6)
* dcaro (3)
* eedri (3)
* jmoskovc (2)
* moolit (2)
* ovirtbot (2)
* lvernia (1)
* awels (1)
* fromani (1)
* nsoffer (1)
* Rydekull (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

-- 
Brian Proffitt

oVirt Community Manager
Project Atomic Community Lead
Open Source and Standards, Red Hat - http://community.redhat.com
Phone: +1 574 383 9BKP
IRC: bkp @ OFTC
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt 3.5.0 release schedule updated

2014-08-20 Thread Eli Mesika


- Original Message -
 From: Sandro Bonazzola sbona...@redhat.com
 To: Users@ovirt.org, de...@ovirt.org
 Sent: Wednesday, August 20, 2014 5:49:53 PM
 Subject: [ovirt-users] oVirt 3.5.0 release schedule updated
 
 Here is the updated schedule for oVirt 3.5.0 after today oVirt sync meeting
 discussion.
 These are tentative planning dates and may change:
 
 General availability: 2014-09-17 (Wed)
 oVirt 3.5 Third Test Day: 2014-09-11 (Thu)

Sandro, please note that the TLV office have a summer event in this date from 
14:00 local time
(We have to drive about an hour to the event location, what makes our day work 
end around 13:00)


 RC2 Build:2014-09-03 (Wed)
 Build refresh:2014-08-21 (Thu)
 
 Release management page has been updated accordingly:
 http://www.ovirt.org/OVirt_3.5_release-management
 
 oVirt Google Calendar has been updated accordingly:
 ICAL:
 https://www.google.com/calendar/ical/ppqtk46u9cglj7l987ruo2l0f8%40group.calendar.google.com/public/basic.ics
 XML:
 https://www.google.com/calendar/feeds/ppqtk46u9cglj7l987ruo2l0f8%40group.calendar.google.com/public/basic
 HTML:
 https://www.google.com/calendar/embed?src=ppqtk46u9cglj7l987ruo2l0f8%40group.calendar.google.comctz=UTC
 
 
 Thanks,
 
 --
 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
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users