[Engine-devel] oVirt 3.4.0 beta is now available
The oVirt team is pleased to announce that the 3.4.0 Release is now available in beta for testing. Release notes and information on the changes for this update are still being worked on and will be available soon on the wiki[1]. Please ensure to follow install instruction from release notes if you're going to test it. A new repository ovirt-3.4.0-prerelease has been added for delivering this beta and future refreshes until release candidate. A new oVirt Node build will be available soon as well. You're welcome to join us testing this beta release in tomorrow test day [2]! [1] http://www.ovirt.org/OVirt_3.4.0_release_notes [2] http://www.ovirt.org/OVirt_3.4_Test_Day -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] oVirt 3.3.3 Release Candidate is now available
The oVirt team is pleased to announce that the 3.3.3 Release Candidate is now available in ovirt-updates-testing [1]. Feel free to join us testing it[2] and verifying the bugzilla entries actually under verification [3]. Release notes for this update are available on the wiki [4]. A new oVirt Node build will be available soon as well. [1] http://resources.ovirt.org/releases/updates-testing [2] http://www.ovirt.org/Testing/Ovirt_3.3.3_testing [3] http://red.ht/KEesdK [4] http://www.ovirt.org/OVirt_3.3.3_release_notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Application URI - saved anywhere?
- Original Message -
From: Ori Liel ol...@redhat.com
To: engine-devel engine-devel@ovirt.org
Sent: Wednesday, January 22, 2014 2:32:29 PM
Subject: [Engine-devel] Application URI - saved anywhere?
Hi,
RSDL lists the possible links that the user can activate in Rest-API. The URI
of A link looks something like this:
/ovirt-engine/api/vms/{vm:id}/start
My question is about the prefix: /ovirt-engine/api/. Until now RSDL was
generated at run-time, under a running application server, and this prefix
was received by querying for the base-uri of the current user's request. I'm
in the process of enabling RSDL generation at build time, and thus won't
have a request to get this URI from. I'm thinking to add this constant:
/ovirt-engine/api somewhere in pom.xml files, and use it. Does that sound
reasonable? (if not, why, and what do you think I should do instead?)
This entry already exists today in the ovirt-engine repo, in ear/pom.xml as the
contextRoot of the API webapp.
Would that be enough?
Thanks,
Ori.
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Application URI - saved anywhere?
- Original Message -
From: Oved Ourfalli ov...@redhat.com
To: Ori Liel ol...@redhat.com
Cc: engine-devel engine-devel@ovirt.org
Sent: Wednesday, January 22, 2014 2:44:34 PM
Subject: Re: [Engine-devel] Application URI - saved anywhere?
- Original Message -
From: Ori Liel ol...@redhat.com
To: engine-devel engine-devel@ovirt.org
Sent: Wednesday, January 22, 2014 2:32:29 PM
Subject: [Engine-devel] Application URI - saved anywhere?
Hi,
RSDL lists the possible links that the user can activate in Rest-API. The URI
of A link looks something like this:
/ovirt-engine/api/vms/{vm:id}/start
My question is about the prefix: /ovirt-engine/api/. Until now RSDL was
generated at run-time, under a running application server, and this prefix
was received by querying for the base-uri of the current user's request. I'm
in the process of enabling RSDL generation at build time, and thus won't
have a request to get this URI from. I'm thinking to add this constant:
/ovirt-engine/api somewhere in pom.xml files, and use it. Does that sound
reasonable? (if not, why, and what do you think I should do instead?)
This entry already exists today in the ovirt-engine repo, in ear/pom.xml as
the contextRoot of the API webapp.
Would that be enough?
Thanks for pointing that out, I'll move if from there to the base pom.xml,
since this value should be available for both the GUI and the API.
Thanks,
Ori.
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] [ANN] oVirt 3.4.0 Test Day - Tomorrow Jan 23th
Hi all, tomorrow Jan 23th we'll have oVirt 3.4.0 test day. On this day all relevant engineers will be online ready to support any issues you find during install / operating this new release. Just make sure you have 1 hosts or more to test drive the new release. If you're curious to see how it works, this is your chance. Thanks again for everyone who will join us tomorrow! Location #ovirt irc channel Please communicate here to allow others to see any issues What In this test day you have a license to kill ;) Follow the documentation to setup your environment, and test drive the new features. Please remember we expect to see some issues, and anything you come up with will save a you when you'll install final release Remember to try daily tasks you'd usually do in the engine, to see there are no regressions. Write down the configuration you used (HW, console, etc) in the report etherpad[1]. Documentation Release notes: http://www.ovirt.org/OVirt_3.4.0_release_notes Features pages links: http://bit.ly/17qBn6F If you find errors in the wiki please annotate it as well in report etherpad [1] Prerequisites / recommendations Use CentOS or RHEL 6.5 only. 6.4 is unsupported due to various issues (sanlock, libvirt, etc). Use Fedora 19 only. Fedora 20 is unsupported due to various issues (sos, jboss). Latest RPMs repository to be enabled for testing the release are listed in the release notes page [2]. NEW issues / reports For any new issue, please update the reports etherpad [1] Feature owners, please make sure: your feature is updated and referenced on release page [2]. you have testing instruction for your feature either on test day page [3] or in your feature page. your team regression testing section is organized and up to date on test day page [3]. [1] http://etherpad.ovirt.org/p/3.4-testday-1 [2] http://www.ovirt.org/OVirt_3.4.0_release_notes [3] http://www.ovirt.org/OVirt_3.4_Test_Day Thanks. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] Change in Engine user session timeout options
Hi guys, this is just a small update, patch [1] was merged recently into master branch and also made its way into ovirt-engine-3.4 branch. This patch removes UserSessionTimeOutInvalidationInterval config option, so there's only UserSessionTimeOutInterval option now. You can use it to customize Engine user session expiration, which is 30 mins by default. [1] http://gerrit.ovirt.org/#/c/23113/ Regards, Vojtech ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] oVirt 3.4.0 beta is now available
Il 22/01/2014 15:49, Martin Perina ha scritto: Hi, I tried to install on F19, but openstack* packages = 3.0.2 are missing: thanks, updated release page, it needs updates-testing Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available: openstack-java-quantum-client-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-client = 3.0.2 Available: openstack-java-keystone-client-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-client = 3.0.1-1.fc19 I didn't found any info about additional repositories in release notes ... Thanks Martin Perina - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: annou...@ovirt.org, arch a...@ovirt.org, us...@ovirt.org, engine-devel engine-devel@ovirt.org Sent: Wednesday, January 22, 2014 11:56:19 AM Subject: [Engine-devel] oVirt 3.4.0 beta is now available The oVirt team is pleased to announce that the 3.4.0 Release is now available in beta for testing. Release notes and information on the changes for this update are still being worked on and will be available soon on the wiki[1]. Please ensure to follow install instruction from release notes if you're going to test it. A new repository ovirt-3.4.0-prerelease has been added for delivering this beta and future refreshes until release candidate. A new oVirt Node build will be available soon as well. You're welcome to join us testing this beta release in tomorrow test day [2]! [1] http://www.ovirt.org/OVirt_3.4.0_release_notes [2] http://www.ovirt.org/OVirt_3.4_Test_Day -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] find-bugs errors
- Original Message - From: Vojtech Szocs vsz...@redhat.com Sent: Wednesday, January 22, 2014 8:47:21 AM - Original Message - From: Einav Cohen eco...@redhat.com To: Moti Asayag masa...@redhat.com, Vojtech Szocs vsz...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Tuesday, January 21, 2014 10:41:24 PM Subject: find-bugs errors (1) @Moti: see [1] and [2]. it seems that they were caused by http://gerrit.ovirt.org/#/c/23507/ (2) @Vojtech[/UI Maintainers/others]: see [3] - it seems that the UI's AppErrors.java file became too large for find-bugs to handle. Any ideas on how to handle this (add to ignore list/ divide to several files/...)? As far as I can tell, FindBugs has hard-coded limit of class size (1M) method count (1K). Any class exceeding these limits will be skipped with SKIPPED_CLASS_TOO_BIG warning. See [a] for details. In WebAdmin we already exclude ApplicationConstants from SKIPPED_CLASS_TOO_BIG warning [b]. I suggest to do the same for AppErrors. Dividing AppErrors into smaller files doesn't make sense as this is GWT i18n interface that only contains i18n constant keys with default values, no logic whatsoever. Thanks, Vojtech - it looks like AppErrors was added to the relevant exclude-filters.xml file [http://gerrit.ovirt.org/#/c/23547/] earlier today - thanks Arik/Tomas/Omer for the prompt handling! find-bugs is now green again. [a] http://sourceforge.net/p/findbugs/feature-requests/260/ [b] frontend/webadmin/modules/webadmin/exclude-filters.xml Vojtech [1] http://jenkins.ovirt.org/job/ovirt_engine_master_find_bugs/6308/findbugsResult/module.-1158699741/source.27/#386 [2] http://jenkins.ovirt.org/job/ovirt_engine_master_find_bugs/6308/findbugsResult/module.-1158699741/source.28/#387 [3] http://jenkins.ovirt.org/job/ovirt_engine_master_find_bugs/6308/findbugsResult/module.-1188557915/ - Forwarded Message - From: Jenkins ci oVirt Server jenk...@ovirt.org To: engine-patc...@ovirt.org, fsimo...@redhat.com Sent: Tuesday, January 21, 2014 4:11:24 PM Subject: [Engine-patches] [oVirt Jenkins] ovirt_engine_master_find_bugs - Build # 6308 - Still Unstable! Project: http://jenkins.ovirt.org/job/ovirt_engine_master_find_bugs/ Build: http://jenkins.ovirt.org/job/ovirt_engine_master_find_bugs/6308/ Build Number: 6308 Build Status: Still Unstable Triggered By: Started by an SCM change - Changes Since Last Success: - Changes for Build #6301 [Moti Asayag] engine: Extract AddNetworksByLabelParametersBuilder [Moti Asayag] engine: Support attaching two labeled networks to a cluster [Moti Asayag] engine: Extract RemoveNetworksByLabelParametersBuilder [Moti Asayag] engine: Support detaching two labeled networks from a cluster [Lior Vernia] webadmin: Replaced Profiles by vNIC Profiles Changes for Build #6302 [Sergey Gotliv] engine, dao: Introduce ISCSI Bond entity, tables and dao [Sergey Gotliv] engine: Introduce commands to manage iscsi bonds entities [Sergey Gotliv] engine: Setup multiple iscsi sessions with the iscsi target Changes for Build #6303 [Sergey Gotliv] webadmin: Allow to configure ISCSI multipathing in the dc context [Martin Perina] tools: Adds more validations to MAIL_PORT in notifier [Moti Asayag] engine: Fix findbugs warnings about Map values iteration [Lior Vernia] webadmin: Hide content widget of boot protocol label Changes for Build #6304 [Lior Vernia] webadmin: Integrate VM icon into Add/Edit Network dialog Changes for Build #6305 [Alexander Wels] webadmin: Double click collapse system tree Changes for Build #6306 [Daniel Erez] restapi: del storage conn if domain creation fails Changes for Build #6307 [Moti Asayag] restapi: Preserve labels when setup networks is sent Changes for Build #6308 [Federico Simoncelli] core: set local storage domain format - Failed Tests: - No tests ran. ___ Engine-patches mailing list engine-patc...@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-patches ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Inconsistent model-entity mapping in VmSnapshotListModel
- Original Message - From: Martin Betak mbe...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Wednesday, January 22, 2014 2:14:40 PM Subject: [Engine-devel] Inconsistent model-entity mapping in VmSnapshotListModel Hi all, during some of my frontend patches I noticed that the properties - singleQxlPci - allowConsoleReconnect - runAndPause are not mapped from UnitVmModel to VM business entity in VmSnapshotListModel#onCloneVm method while being mapped in all other fronted VM-related *ListModels (UserPortalListModel, VmListModel, TemplateListModel) and also that the 'comment' property is not being mapped in UserPortalListModel#postVmNameUniqueCheck method. Since I know that copy pasting the appropriate setter to 6 different places when adding new VM property can be tedious and very error prone I would like to ask the frontend maintainers if the above is desired behavior or just bug caused by omission. I guess onCloneVm/postVmNameUniqueCheck were simply missed while adding these properties. So yeah, if these properties can indeed be modified from the relevant dialog, then it seems like a bug. @Tomas - did I miss something? is there any reason not to map them? Best regards, Martin ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] oVirt 3.4.0 beta is now available
- Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Martin Perina mper...@redhat.com Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org Sent: Wednesday, January 22, 2014 5:01:55 PM Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available Il 22/01/2014 15:49, Martin Perina ha scritto: Hi, I tried to install on F19, but openstack* packages = 3.0.2 are missing: thanks, updated release page, it needs updates-testing I had enabled ovirt-updates-testing and still got this : -- Finished Dependency Resolution Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available: openstack-java-quantum-client-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-client = 3.0.2 Available: openstack-java-keystone-client-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-client = 3.0.1-1.fc19 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available: openstack-java-quantum-client-3.0.1-1.fc19.noarch (updates)
Re: [Engine-devel] oVirt 3.4.0 beta is now available
Hi Eli, On 01/22/2014 01:10 PM, Eli Mesika wrote: - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Martin Perina mper...@redhat.com Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org Sent: Wednesday, January 22, 2014 5:01:55 PM Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available Il 22/01/2014 15:49, Martin Perina ha scritto: Hi, I tried to install on F19, but openstack* packages = 3.0.2 are missing: thanks, updated release page, it needs updates-testing I had enabled ovirt-updates-testing and still got this : Here it worked, without looking your 'yum repolist' output I do guess you need to enable the repo from: /etc/yum.repos.d/fedora-updates-testing.repo # yum install ovirt-engine snip Installing: ovirt-enginenoarch 3.4.0-0.5.beta1.fc19 ovirt-3.4.0-prerelease 1.3 /snip snip Installing for dependencies: openstack-java-glance-clientnoarch 3.0.2-1.fc19updates-testing 21 k openstack-java-glance-model noarch 3.0.2-1.fc19updates-testing 18 k openstack-java-keystone-client noarch 3.0.2-1.fc19updates-testing 33 k openstack-java-keystone-model noarch 3.0.2-1.fc19updates-testing 30 k openstack-java-quantum-client noarch 3.0.2-1.fc19updates-testing 20 k openstack-java-quantum-modelnoarch 3.0.2-1.fc19updates-testing 24 k /snip -- Finished Dependency Resolution Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available: openstack-java-quantum-client-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-client = 3.0.2 Available: openstack-java-keystone-client-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-client = 3.0.1-1.fc19 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch
Re: [Engine-devel] oVirt 3.4.0 beta is now available
- Original Message - From: Douglas Schilling Landgraf dougsl...@redhat.com To: Eli Mesika emes...@redhat.com, Sandro Bonazzola sbona...@redhat.com Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org Sent: Wednesday, January 22, 2014 9:31:59 PM Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available Hi Eli, On 01/22/2014 01:10 PM, Eli Mesika wrote: - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Martin Perina mper...@redhat.com Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org Sent: Wednesday, January 22, 2014 5:01:55 PM Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available Il 22/01/2014 15:49, Martin Perina ha scritto: Hi, I tried to install on F19, but openstack* packages = 3.0.2 are missing: thanks, updated release page, it needs updates-testing I had enabled ovirt-updates-testing and still got this : Here it worked, without looking your 'yum repolist' output I do guess you need to enable the repo from: /etc/yum.repos.d/fedora-updates-testing.repo Thanks, I enabled ovirt-updates-testing in ovirt repo . :-( # yum install ovirt-engine snip Installing: ovirt-enginenoarch 3.4.0-0.5.beta1.fc19 ovirt-3.4.0-prerelease 1.3 /snip snip Installing for dependencies: openstack-java-glance-clientnoarch 3.0.2-1.fc19updates-testing 21 k openstack-java-glance-model noarch 3.0.2-1.fc19updates-testing 18 k openstack-java-keystone-client noarch 3.0.2-1.fc19updates-testing 33 k openstack-java-keystone-model noarch 3.0.2-1.fc19updates-testing 30 k openstack-java-quantum-client noarch 3.0.2-1.fc19updates-testing 20 k openstack-java-quantum-modelnoarch 3.0.2-1.fc19updates-testing 24 k /snip -- Finished Dependency Resolution Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available: openstack-java-quantum-client-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-client = 3.0.2 Available: openstack-java-keystone-client-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-client = 3.0.1-1.fc19 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
Re: [Engine-devel] [Users] oVirt 3.4.0 beta is now available
- Original Message - From: Eli Mesika emes...@redhat.com To: dougsl...@redhat.com Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org Sent: Wednesday, January 22, 2014 9:48:54 PM Subject: Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available - Original Message - From: Douglas Schilling Landgraf dougsl...@redhat.com To: Eli Mesika emes...@redhat.com, Sandro Bonazzola sbona...@redhat.com Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org Sent: Wednesday, January 22, 2014 9:31:59 PM Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available Hi Eli, On 01/22/2014 01:10 PM, Eli Mesika wrote: - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Martin Perina mper...@redhat.com Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org Sent: Wednesday, January 22, 2014 5:01:55 PM Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available Il 22/01/2014 15:49, Martin Perina ha scritto: Hi, I tried to install on F19, but openstack* packages = 3.0.2 are missing: thanks, updated release page, it needs updates-testing I had enabled ovirt-updates-testing and still got this : Here it worked, without looking your 'yum repolist' output I do guess you need to enable the repo from: /etc/yum.repos.d/fedora-updates-testing.repo Thanks, I enabled ovirt-updates-testing in ovirt repo . :-( engine-setup fails with the following error Failed to execute stage 'Misc configuration': Command '/bin/systemctl' failed to execute any ideas ? # yum install ovirt-engine snip Installing: ovirt-enginenoarch 3.4.0-0.5.beta1.fc19 ovirt-3.4.0-prerelease 1.3 /snip snip Installing for dependencies: openstack-java-glance-clientnoarch 3.0.2-1.fc19updates-testing 21 k openstack-java-glance-model noarch 3.0.2-1.fc19updates-testing 18 k openstack-java-keystone-client noarch 3.0.2-1.fc19updates-testing 33 k openstack-java-keystone-model noarch 3.0.2-1.fc19updates-testing 30 k openstack-java-quantum-client noarch 3.0.2-1.fc19updates-testing 20 k openstack-java-quantum-modelnoarch 3.0.2-1.fc19updates-testing 24 k /snip -- Finished Dependency Resolution Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available:
Re: [Engine-devel] [Users] oVirt 3.4.0 beta is now available
On 01/22/2014 03:00 PM, Eli Mesika wrote:
- Original Message -
From: Eli Mesika emes...@redhat.com
To: dougsl...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org
Sent: Wednesday, January 22, 2014 9:48:54 PM
Subject: Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available
- Original Message -
From: Douglas Schilling Landgraf dougsl...@redhat.com
To: Eli Mesika emes...@redhat.com, Sandro Bonazzola
sbona...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org
Sent: Wednesday, January 22, 2014 9:31:59 PM
Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available
Hi Eli,
On 01/22/2014 01:10 PM, Eli Mesika wrote:
- Original Message -
From: Sandro Bonazzola sbona...@redhat.com
To: Martin Perina mper...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org
Sent: Wednesday, January 22, 2014 5:01:55 PM
Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available
Il 22/01/2014 15:49, Martin Perina ha scritto:
Hi,
I tried to install on F19, but openstack* packages = 3.0.2 are
missing:
thanks, updated release page, it needs updates-testing
I had enabled ovirt-updates-testing and still got this :
Here it worked, without looking your 'yum repolist' output I do guess
you need to enable the repo from:
/etc/yum.repos.d/fedora-updates-testing.repo
Thanks, I enabled ovirt-updates-testing in ovirt repo . :-(
engine-setup fails with the following error
Failed to execute stage 'Misc configuration': Command '/bin/systemctl' failed
to execute
any ideas ?
Hi Eli,
Would be nice too see your engine-setup log file to determine which
error happened. Should be available here: /var/log/ovirt-engine/setup/
Anyway, I could reproduce a similar output during a setup (below the
log) and in my case was postgresql with error: FATAL: could not create
shared memory segment: Invalid argument
Resolved with wiki:
http://www.ovirt.org/Troubleshooting#Installation
In session:
I am having trouble connecting to the database. In the system log, I
get the following message from Postgres
@Sandro, should or maybe installer detect this kind of situation?
=
2014-01-22 17:37:52 DEBUG otopi.plugins.otopi.services.systemd
plugin.execute:446 execute-output: ('/bin/systemctl', 'start',
'postgresql.service') stderr:
Job for postgresql.service failed. See 'systemctl status
postgresql.service' and 'journalctl -xn' for details.
2014-01-22 17:37:52 DEBUG otopi.context context._executeMethod:152
method exception
Traceback (most recent call last):
File /usr/lib/python2.7/site-packages/otopi/context.py, line 142,
in _executeMethod
method['method']()
File
/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/provisioning/postgres.py,
line 182, in _misc
self._provisioning.provision()
File /usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py,
line 552, in provision
self._restart()
File /usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py,
line 407, in _restart
state=state,
File /usr/share/otopi/plugins/otopi/services/systemd.py, line 138,
in state
'start' if state else 'stop'
File /usr/share/otopi/plugins/otopi/services/systemd.py, line 77,
in _executeServiceCommand
raiseOnError=raiseOnError
File /usr/lib/python2.7/site-packages/otopi/plugin.py, line 451, in
execute
command=args[0],
RuntimeError: Command '/bin/systemctl' failed to execute
2014-01-22 17:37:52 ERROR otopi.context context._executeMethod:161
Failed to execute stage 'Misc configuration': Command '/bin/systemctl'
failed to execute
2014-01-22 17:37:52 DEBUG otopi.transaction transaction.abort:131
aborting 'Yum Transaction'
2014-01-22 17:37:52 INFO otopi.plugins.otopi.packagers.yumpackager
yumpackager.info:92 Yum Performing yum transaction rollback
Loaded plugins: versionlock
--
Cheers
Douglas
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] [Users] oVirt 3.4.0 beta is now available
Il 23/01/2014 03:19, Douglas Schilling Landgraf ha scritto:
On 01/22/2014 03:00 PM, Eli Mesika wrote:
- Original Message -
From: Eli Mesika emes...@redhat.com
To: dougsl...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org
Sent: Wednesday, January 22, 2014 9:48:54 PM
Subject: Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available
- Original Message -
From: Douglas Schilling Landgraf dougsl...@redhat.com
To: Eli Mesika emes...@redhat.com, Sandro Bonazzola
sbona...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org
Sent: Wednesday, January 22, 2014 9:31:59 PM
Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available
Hi Eli,
On 01/22/2014 01:10 PM, Eli Mesika wrote:
- Original Message -
From: Sandro Bonazzola sbona...@redhat.com
To: Martin Perina mper...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org
Sent: Wednesday, January 22, 2014 5:01:55 PM
Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available
Il 22/01/2014 15:49, Martin Perina ha scritto:
Hi,
I tried to install on F19, but openstack* packages = 3.0.2 are
missing:
thanks, updated release page, it needs updates-testing
I had enabled ovirt-updates-testing and still got this :
Here it worked, without looking your 'yum repolist' output I do guess
you need to enable the repo from:
/etc/yum.repos.d/fedora-updates-testing.repo
Thanks, I enabled ovirt-updates-testing in ovirt repo . :-(
engine-setup fails with the following error
Failed to execute stage 'Misc configuration': Command '/bin/systemctl'
failed to execute
any ideas ?
Hi Eli,
Would be nice too see your engine-setup log file to determine which error
happened. Should be available here: /var/log/ovirt-engine/setup/
Anyway, I could reproduce a similar output during a setup (below the log) and
in my case was postgresql with error: FATAL: could not create shared
memory segment: Invalid argument
Resolved with wiki:
http://www.ovirt.org/Troubleshooting#Installation
In session:
I am having trouble connecting to the database. In the system log, I get the
following message from Postgres
@Sandro, should or maybe installer detect this kind of situation?
Seems like http://www.ovirt.org/OVirt_3.4.0_release_notes#Known_issues
On Fedora 19 with recent versions of PostgreSQL it may be necessary to manually
change kernel.shmmax settings (BZ 1039616)
Please try:
# engine-setup --otopi-environment=OVESETUP_SYSTEM/shmmax=int:68719476736
=
2014-01-22 17:37:52 DEBUG otopi.plugins.otopi.services.systemd
plugin.execute:446 execute-output: ('/bin/systemctl', 'start',
'postgresql.service')
stderr:
Job for postgresql.service failed. See 'systemctl status postgresql.service'
and 'journalctl -xn' for details.
2014-01-22 17:37:52 DEBUG otopi.context context._executeMethod:152 method
exception
Traceback (most recent call last):
File /usr/lib/python2.7/site-packages/otopi/context.py, line 142, in
_executeMethod
method['method']()
File
/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/provisioning/postgres.py,
line 182, in _misc
self._provisioning.provision()
File /usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py, line
552, in provision
self._restart()
File /usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py, line
407, in _restart
state=state,
File /usr/share/otopi/plugins/otopi/services/systemd.py, line 138, in
state
'start' if state else 'stop'
File /usr/share/otopi/plugins/otopi/services/systemd.py, line 77, in
_executeServiceCommand
raiseOnError=raiseOnError
File /usr/lib/python2.7/site-packages/otopi/plugin.py, line 451, in
execute
command=args[0],
RuntimeError: Command '/bin/systemctl' failed to execute
2014-01-22 17:37:52 ERROR otopi.context context._executeMethod:161 Failed to
execute stage 'Misc configuration': Command '/bin/systemctl' failed to
execute
2014-01-22 17:37:52 DEBUG otopi.transaction transaction.abort:131 aborting
'Yum Transaction'
2014-01-22 17:37:52 INFO otopi.plugins.otopi.packagers.yumpackager
yumpackager.info:92 Yum Performing yum transaction rollback
Loaded plugins: versionlock
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] [ANN] oVirt 3.4.0 Test Day - Tomorrow Jan 23th
Hi, After adding the node to engine, it goes to non operational state with the error Host 10.70.43.160 is compatible with versions (3.0,3.1,3.2,3.3) and cannot join Cluster Default which is set to version 3.4.. I have enabled the repo http://resources.ovirt.org/releases/3.4.0_pre/rpm/Fedora/$releasever/ in host. Following is the vdsm version installed in F19 node: [root@localhost ~]# rpm -qa | grep vdsm vdsm-cli-4.14.1-2.fc19.noarch vdsm-4.14.1-2.fc19.x86_64 vdsm-python-4.14.1-2.fc19.x86_64 vdsm-python-zombiereaper-4.14.1-2.fc19.noarch vdsm-xmlrpc-4.14.1-2.fc19.noarch vdsm-gluster-4.14.1-2.fc19.noarch [root@localhost ~]# vdsClient -s 0 getVdsCaps clusterLevels = ['3.0', '3.1', '3.2', '3.3'] Anything I am missing here? Regards, Ramesh - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: arch a...@ovirt.org, engine-devel engine-devel@ovirt.org, us...@ovirt.org Sent: Wednesday, January 22, 2014 6:37:23 PM Subject: [ANN] oVirt 3.4.0 Test Day - Tomorrow Jan 23th Hi all, tomorrow Jan 23th we'll have oVirt 3.4.0 test day. On this day all relevant engineers will be online ready to support any issues you find during install / operating this new release. Just make sure you have 1 hosts or more to test drive the new release. If you're curious to see how it works, this is your chance. Thanks again for everyone who will join us tomorrow! Location #ovirt irc channel Please communicate here to allow others to see any issues What In this test day you have a license to kill ;) Follow the documentation to setup your environment, and test drive the new features. Please remember we expect to see some issues, and anything you come up with will save a you when you'll install final release Remember to try daily tasks you'd usually do in the engine, to see there are no regressions. Write down the configuration you used (HW, console, etc) in the report etherpad[1]. Documentation Release notes: http://www.ovirt.org/OVirt_3.4.0_release_notes Features pages links: http://bit.ly/17qBn6F If you find errors in the wiki please annotate it as well in report etherpad [1] Prerequisites / recommendations Use CentOS or RHEL 6.5 only. 6.4 is unsupported due to various issues (sanlock, libvirt, etc). Use Fedora 19 only. Fedora 20 is unsupported due to various issues (sos, jboss). Latest RPMs repository to be enabled for testing the release are listed in the release notes page [2]. NEW issues / reports For any new issue, please update the reports etherpad [1] Feature owners, please make sure: your feature is updated and referenced on release page [2]. you have testing instruction for your feature either on test day page [3] or in your feature page. your team regression testing section is organized and up to date on test day page [3]. [1] http://etherpad.ovirt.org/p/3.4-testday-1 [2] http://www.ovirt.org/OVirt_3.4.0_release_notes [3] http://www.ovirt.org/OVirt_3.4_Test_Day Thanks. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Arch mailing list a...@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] oVirt 3.4.0 beta is now available
Il 22/01/2014 19:10, Eli Mesika ha scritto: - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Martin Perina mper...@redhat.com Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org Sent: Wednesday, January 22, 2014 5:01:55 PM Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available Il 22/01/2014 15:49, Martin Perina ha scritto: Hi, I tried to install on F19, but openstack* packages = 3.0.2 are missing: thanks, updated release page, it needs updates-testing I had enabled ovirt-updates-testing and still got this : I mean Fedora updates-testing... However today openstak packages should be available also in Fedora updates repository -- Finished Dependency Resolution Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available: openstack-java-quantum-client-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-client = 3.0.2 Available: openstack-java-keystone-client-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-client = 3.0.1-1.fc19 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch
Re: [Engine-devel] Inconsistent model-entity mapping in VmSnapshotListModel
- Original Message - From: Daniel Erez de...@redhat.com To: Martin Betak mbe...@redhat.com Cc: engine-devel engine-devel@ovirt.org, Tomas Jelinek tjeli...@redhat.com Sent: Wednesday, January 22, 2014 7:04:11 PM Subject: Re: [Engine-devel] Inconsistent model-entity mapping in VmSnapshotListModel - Original Message - From: Martin Betak mbe...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Wednesday, January 22, 2014 2:14:40 PM Subject: [Engine-devel] Inconsistent model-entity mapping in VmSnapshotListModel Hi all, during some of my frontend patches I noticed that the properties - singleQxlPci - allowConsoleReconnect - runAndPause are not mapped from UnitVmModel to VM business entity in VmSnapshotListModel#onCloneVm method while being mapped in all other fronted VM-related *ListModels (UserPortalListModel, VmListModel, TemplateListModel) and also that the 'comment' property is not being mapped in UserPortalListModel#postVmNameUniqueCheck method. Since I know that copy pasting the appropriate setter to 6 different places when adding new VM property can be tedious and very error prone I would like to ask the frontend maintainers if the above is desired behavior or just bug caused by omission. I guess onCloneVm/postVmNameUniqueCheck were simply missed while adding these properties. So yeah, if these properties can indeed be modified from the relevant dialog, then it seems like a bug. @Tomas - did I miss something? is there any reason not to map them? I don't know of any so I guess they can be added... Best regards, Martin ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
