[Users] oVirt 3.4.0 release schedule updated
oVirt team has updated the release schedule for 3.4.0 [1] These are tentative planning dates and may change General availability: 2014-02-24 oVirt 3.4 Second Test Day: 2014-02-19 RC Build: 2014-02-17 oVirt 3.4 Test Day: 2014-01-27 Beta release: 2014-01-20 Branching / Feature freeze: 2014-01-15 Alpha release: 2014-01-09 more details on test days, etc to come in the next few weeks [1] http://www.ovirt.org/OVirt_3.4_release-management#Timeline -- 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: [Users] oVirt 3.4.0 release schedule updated
Il 09/01/2014 15:02, Doron Fediuck ha scritto: > > > - Original Message - >> From: "Eli Mesika" >> To: "Sandro Bonazzola" >> Cc: "arch" , "engine-devel" , >> "vdsm-devel" , >> "VDSM Project Development" , >> Users@ovirt.org >> Sent: Thursday, January 9, 2014 10:40:28 AM >> Subject: Re: [Users] oVirt 3.4.0 release schedule updated >> >> >> >> - Original Message - >>> From: "Sandro Bonazzola" >>> To: "engine-devel" , "VDSM Project Development" >>> , >>> "vdsm-devel" , "arch" , >>> Users@ovirt.org >>> Sent: Wednesday, January 8, 2014 6:47:58 PM >>> Subject: [Users] oVirt 3.4.0 release schedule updated >>> >>> oVirt team has updated the release schedule for 3.4.0 [1] >>> >>> These are tentative planning dates and may change >>> >>> General availability: 2014-02-24 >>> oVirt 3.4 Second Test Day: 2014-02-19 >>> RC Build: 2014-02-17 >>> oVirt 3.4 Test Day: 2014-01-27 >> >> Please note that some guys from the TLV office could not attend to that due >> to an Advanced Python Course taking place (27-30 JAN) >> > > Hi Sandro, > Since there's some activity also around FOSDEM, I suggest we > will do the first test day on January 23. > > Please let me know if there are any objections. I'll update the site with new date, thanks. > >>> Beta release: 2014-01-20 >>> Branching / Feature freeze: 2014-01-15 >>> Alpha release: 2014-01-09 >>> >>> more details on test days, etc to come in the next few weeks >>> >>> [1] http://www.ovirt.org/OVirt_3.4_release-management#Timeline >>> >>> -- >>> 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 >> -- 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: [Users] oVirt 3.4.0 release schedule updated
Here is updated schedule. I've added 3.3.3 too and attached an ICS calendar with the same dates These are tentative planning dates and may change oVirt 3.4 General availability: 2014-02-24 oVirt 3.4 Second Test Day:2014-02-19 oVirt 3.4 RC Build: 2014-02-17 oVirt 3.4 Test Day: 2014-01-23 oVirt 3.4 Beta release: 2014-01-20 oVirt 3.4 Branching / Feature freeze: 2014-01-15 oVirt 3.4 Alpha release: 2014-01-09 more details on test days, etc to come in the next few weeks oVirt 3.3.3 General availability: 2014-01-28 oVirt 3.3.3 RC Build: 2014-01-21 oVirt 3.3.3 Beta release: 2014-01-13 Il 09/01/2014 15:02, Doron Fediuck ha scritto: > > > - Original Message - >> From: "Eli Mesika" >> To: "Sandro Bonazzola" >> Cc: "arch" , "engine-devel" , >> "vdsm-devel" , >> "VDSM Project Development" , >> Users@ovirt.org >> Sent: Thursday, January 9, 2014 10:40:28 AM >> Subject: Re: [Users] oVirt 3.4.0 release schedule updated >> >> >> >> - Original Message - >>> From: "Sandro Bonazzola" >>> To: "engine-devel" , "VDSM Project Development" >>> , >>> "vdsm-devel" , "arch" , >>> Users@ovirt.org >>> Sent: Wednesday, January 8, 2014 6:47:58 PM >>> Subject: [Users] oVirt 3.4.0 release schedule updated >>> >>> oVirt team has updated the release schedule for 3.4.0 [1] >>> >>> These are tentative planning dates and may change >>> >>> General availability: 2014-02-24 >>> oVirt 3.4 Second Test Day: 2014-02-19 >>> RC Build: 2014-02-17 >>> oVirt 3.4 Test Day: 2014-01-27 >> >> Please note that some guys from the TLV office could not attend to that due >> to an Advanced Python Course taking place (27-30 JAN) >> > > Hi Sandro, > Since there's some activity also around FOSDEM, I suggest we > will do the first test day on January 23. > > Please let me know if there are any objections. > >>> Beta release: 2014-01-20 >>> Branching / Feature freeze: 2014-01-15 >>> Alpha release: 2014-01-09 >>> >>> more details on test days, etc to come in the next few weeks >>> >>> [1] http://www.ovirt.org/OVirt_3.4_release-management#Timeline >>> >>> -- >>> 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 >> -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com BEGIN:VCALENDAR PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN VERSION:2.0 BEGIN:VEVENT CREATED:20140109T085926Z LAST-MODIFIED:20140109T090007Z DTSTAMP:20140109T090007Z UID:aa67201d-432b-486b-b384-3084b51ee12a SUMMARY:oVirt 3.4.0 GA DTSTART;VALUE=DATE:20140224 DTEND;VALUE=DATE:20140225 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090034Z LAST-MODIFIED:20140109T090044Z DTSTAMP:20140109T090044Z UID:f9d8197e-c3c1-4044-9127-fcdfc1dc1aaf SUMMARY:oVirt 3.4 Second Test Day DTSTART;VALUE=DATE:20140219 DTEND;VALUE=DATE:20140220 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090058Z LAST-MODIFIED:20140109T090110Z DTSTAMP:20140109T090110Z UID:ff9b1509-1db8-4af5-bb5c-900a739401cc SUMMARY:oVirt 3.4.0 RC Build DTSTART;VALUE=DATE:20140217 DTEND;VALUE=DATE:20140218 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090212Z LAST-MODIFIED:20140109T090223Z DTSTAMP:20140109T090223Z UID:873d0069-630b-40a5-ba5a-5728153fc12c SUMMARY:oVrit 3.4.0 Beta release DTSTART;VALUE=DATE:20140120 DTEND;VALUE=DATE:20140121 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090254Z LAST-MODIFIED:20140109T090308Z DTSTAMP:20140109T090308Z UID:07afe210-61a1-4113-9020-2735aefc7467 SUMMARY:oVirt 3.4.0 Alpha release DTSTART;VALUE=DATE:20140109 DTEND;VALUE=DATE:20140110 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090322Z LAST-MODIFIED:20140109T090335Z DTSTAMP:20140109T090335Z UID:869db415-7ab8-4a5e-b5f4-529e87924e89 SUMMARY:oVirt 3.4.0 Branching / Feature freeze DTSTART;VALUE=DATE:20140115 DTEND;VALUE=DATE:20140116 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090359Z LAST-MO
[Users] oVirt 3.4.0 alpha delayed
Hi, oVirt 3.4.0 alpha will be delayed due to packages dependencies issue. Maintainers are already working on this, alpha will be released just after all dependency issues will have been fixed. Details on dependency missing: on CentOS 6.5: [ovirt-3.4.0-alpha] name=Alpha builds of the oVirt 3.4 project baseurl=http://resources.ovirt.org/releases/3.4.0-alpha/rpm/EL/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0 # repoclosure -r ovirt-3.4.0-alpha -l ovirt-3.3.2 -l base -l epel -l glusterfs-epel -l updates -l extra -l glusterfs-noarch-epel -l ovirt-stable -n Reading in repository metadata - please wait Checking Dependencies Repos looked at: 8 base epel glusterfs-epel glusterfs-noarch-epel ovirt-3.3.2 ovirt-3.4.0-alpha ovirt-stable updates Num Packages in Repos: 16581 package: mom-0.3.2-20140101.git2691f25.el6.noarch from ovirt-3.4.0-alpha unresolved deps: procps-ng package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.el6.noarch from ovirt-3.4.0-alpha unresolved deps: otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.el6 package: ovirt-engine-sdk-java-3.4.0.1-1.el6.noarch from ovirt-3.4.0-alpha unresolved deps: httpcomponents-client >= 0:4.2 apache-commons-logging apache-commons-beanutils package: vdsm-hook-vhostmd-4.14.0-1.git6fdd55f.el6.noarch from ovirt-3.4.0-alpha unresolved deps: vhostmd On Fedora 19: [ovirt-3.4.0-alpha] name=Alpha builds of the oVirt 3.4 project baseurl=http://resources.ovirt.org/releases/3.4.0-alpha/rpm/Fedora/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0 # repoclosure -n -r ovirt-3.4.0-alpha -l fedora -l updates -l ovirt-stable Reading in repository metadata - please wait Checking Dependencies Repos looked at: 4 fedora ovirt-3.4.0-alpha ovirt-stable updates Num Packages in Repos: 38832 package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.fc19 package: ovirt-engine-3.4.0-0.2.master.20140109103311.git6524789.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: openstack-java-resteasy-connector >= 0:3.0.2 openstack-java-quantum-model >= 0:3.0.2 openstack-java-quantum-client >= 0:3.0.2 openstack-java-keystone-model >= 0:3.0.2 openstack-java-keystone-client >= 0:3.0.2 openstack-java-glance-model >= 0:3.0.2 openstack-java-glance-client >= 0:3.0.2 openstack-java-client >= 0:3.0.2 package: ovirt-engine-reports-3.4.0-0.2.master.20140109102135.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: ovirt-engine-dwh >= 0:3.4.0 On Fedora 20 (ovirt-stable doesn't support Fedora 20): [ovirt-3.4.0-alpha] name=Alpha builds of the oVirt 3.4 project baseurl=http://resources.ovirt.org/releases/3.4.0-alpha/rpm/Fedora/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0 # repoclosure -n -r ovirt-3.4.0-alpha -l fedora -l updates Reading in repository metadata - please wait Checking Dependencies Repos looked at: 3 fedora ovirt-3.4.0-alpha updates Num Packages in Repos: 38822 package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.fc19 package: ovirt-engine-3.4.0-0.2.master.20140109103311.git6524789.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: openstack-java-resteasy-connector >= 0:3.0.2 openstack-java-quantum-model >= 0:3.0.2 openstack-java-quantum-client >= 0:3.0.2 openstack-java-keystone-model >= 0:3.0.2 openstack-java-keystone-client >= 0:3.0.2 openstack-java-glance-model >= 0:3.0.2 openstack-java-glance-client >= 0:3.0.2 openstack-java-client >= 0:3.0.2 package: ovirt-engine-reports-3.4.0-0.2.master.20140109102135.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: ovirt-engine-dwh >= 0:3.4.0 -- 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] [QE] oVirt 3.3.3 beta status
we're going to branch and build oVirt 3.3.3 beta on Monday 2014-01-13. A bug tracker is available at [1] and it shows no bugs blocking the release the following has been proposed as blocker for 3.3.3 or 3.4.0, not targeted to a specific version yet: Bug 1035314 - vdsm-hook-nestedvt uses kvm_intel-only syntax The following is a list of the non-blocking bugs still open with target 3.3.3: Whiteboard Bug ID Summary Whiteboard Bug ID Summary infra 987982 When adding a host through the REST API, the error message says that "rootPassword" is required... infra 1017267 Plaintext user passwords in async_tasks database infra 1040022 vdsm-tool configurre errors when installing vdsm package integration 902979 ovirt-live - firefox doesn't trust the installed engine integration 1021805 [RFE] oVirt Live - use motd to show the admin password integration 1022440 [RFE] AIO - configure the AIO host to be a gluster cluster/host integration 1026930 Package virtio-win and put it in ovirt repositories integration 1026933 pre-populate ISO domain with virtio-win ISO network 906313 [oVirt-webadmin] [setupNetworks] "No valid Operation for and Unassigned Logical Networks panel" network 987916 [oVirt] [provider] Dialog doesn't update unless focus lost network 997197 Some AppErrors messages are grammatically incorrect (singular vs plural) network 1023722 [oVirt-webadmin][network] Network roles in cluster management should be radio buttons sla 1049343 [oVirt] Disabled Balloon in Add Vm storage 987917 [oVirt] [glance] API version not specified in provider dialog ux 906394 [oVirt-webadmin] [network] Loading animation in network main tab 'hosts' and 'vms' subtab is stuck... virt1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain 906257 USB Flash Drive install of ovirt-node created via dd fails 923049 ovirt-node fails to boot from local disk under UEFI mode 965583 [RFE] add shortcut key on TUI 976675 [wiki] Update contribution page 979350 Changes admin password in the first time when log in is failed while finished auto-install 979390 [RFE] Split defaults.py into smaller pieces 982232 performance page takes >1sec to load (on first load) 984441 kdump page crashed before configuring the network after ovirt-node intalled 986285 UI crashes when no bond name is given 991267 [RFE] Add TUI information to log file. 1018374 ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19: Failed on Auto-install 1018710 [RFE] Enhance API documentation 1032035 [RFE]re-write auto install function for the cim plugin 1033286 ovirt-node-plugin-vdsm can not be added to ovirt node el6 base image Maintainers: Please add the bugs to the tracker if you think that 3.3.3 should not be released without them fixed. Please re-target all bugs you don't think that should block 3.3.3. For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [2]. Maintainers are welcomed to start filling release notes, the page has been created here [3] [1] http://bugzilla.redhat.com/1050084 [2] http://www.ovirt.org/Testing/Ovirt_3.3.3_testing [3] http://www.ovirt.org/OVirt_3.3.3_release_notes 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: [Users] Unable to delete a snapshot
Il 12/01/2014 10:40, Maor Lipchuk ha scritto: > Adding Sandro to the thread > > On 01/12/2014 11:26 AM, Maor Lipchuk wrote: >> On 01/09/2014 12:29 PM, Nicolas Ecarnot wrote: >>> Hi Maor, hi everyone, >>> >>> Le 07/01/2014 04:09, Maor Lipchuk a écrit : >>>> Looking at bugzilla, it could be related to >>>> https://bugzilla.redhat.com/1029069 >>>> (based on the exception described at >>>> https://bugzilla.redhat.com/show_bug.cgi?id=1029069#c1) >>> >>> In my case, there where nothing "live" : the VM was shut down when >>> creating the snapshot as well as when tyring to delete it. >> I understand though live storage migration sub flows are, creation of >> live snapshot, so it could be related. >>> >>>> The issue there was fixed after an upgrade to 3.3.1 (as Sander mentioned >>>> it before in the mailing list) >>>> >>>> Could you give it a try and check if that works for you? >>> >>> I'm very shy with upgrading my oVirt production framework, but I began >>> to read some things to upgrade it. Maybe you can lead me to a precise >>> way to upgrade vdsm? >> Sandro, do you aware of any documentation which can help in upgrading >> ovirt, specifically VDSM? No, I'm not aware of any documentation about it. However since 3.3.1 is in ovirt-stable if you just need to update vdsm on a system I think that yum --enablerepo=ovirt-stable update "vdsm*" on that system should be enough. CCing Dan and VDSM list for confirming >>> >>>> Also it will be great if you could open a bug on that with the full >>>> VDSM, engine logs and the list of lvs. >>> >>> Done : >>> >>> https://bugzilla.redhat.com/show_bug.cgi?id=1050901 >> Thanks >>> >> >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> > -- 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] oVirt 3.4.0 alpha is now available
The oVirt team is pleased to announce that the 3.4.0 Alpha is now available in 3.4.0-alpha [1] repository for testing. Feel free to join us testing it! You'll find all needed info for installing it on the release notes page, already available on the wiki [2]. A new oVirt Node build will be available soon as well. [1] http://resources.ovirt.org/releases/3.4.0-alpha/ [2] http://www.ovirt.org/OVirt_3.4.0_release_notes -- 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: [Users] Issues installing hosted-engine with 3.4.0 alpha
setups running. > > Commands in module validate_ovirt_certs: > validate-ovirt-certs Validate vdsmcert.pem against cacert.pem. > If current cacert.pem is invalidate, it will > find a validate certificate file and replace > the old cacert.pem with it. And then persist it. > > Commands in module vdsm-id: > vdsm-id Printing host uuid > > vdsm: failed to execute unified_network_persistence_upgrade, error code 1 > vdsm start [FAILED] > > Any suggestions? > > Thanks, > Andrew > > > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] Help: Problem uploading the ISO file on engine
Il 14/01/2014 08:32, Sven Kieske ha scritto: > Hi, > > which engine version? > anything in engine.log? +1 > (I honestly don't know if there's any logging > for the iso uploader?). yes there is, in /var/log/ovirt-iso-uploader dir. > > I never encountered such a problem. Same here. Can you reproduce using -v flag when running iso uploader? > > HTH > > Am 13.01.2014 20:45, schrieb David Li: >> Hi, >> >> I copied a Centos netinstall ISO file to a directory on my engine machine to >> get ready for installation. Then I used >> >> engine-iso-uploader upload -i ISO_DOMAIN CentOS-6.4-x86_64-netinstall.iso >> >> to upload or put it into the proper ISO domain directory. However this >> command now totally stuck. Even kill -9 won't be able to do anything. >> Moreover now my ISO domain in the DC seems dead or becomes inactive too. >> >> What happened? Is there any way to recover from this point without rebooting >> everything? > -- 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] oVirt 3.3.3 beta is now available
The oVirt team is pleased to announce that the 3.3.3 Beta is now available in beta [1] repository for testing. Feel free to join us testing it! You'll find all needed info for installing it on the release notes page, already available on the wiki [2]. A new oVirt Node build will be available soon as well. [1] http://resources.ovirt.org/releases/beta/ [2] 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] ovirt 3.4 alpha repo for fedora 20 missing?
Il 14/01/2014 16:42, Jorick Astrego ha scritto: > I am trying to test the new 3.4 alpha release on fedora 20 but I'm not able > to locate the repo rpm. > > For Fedora 19 this is > http://resources.ovirt.org/releases/3.4.0-alpha/rpm/Fedora/19/noarch/ovirt-release-fedora-10-1.noarch.rpm > but for 20 this rpm > and the repodata appears to be missing. As stated in http://www.ovirt.org/Download for F19 sudo yum localinstall http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm Note that Fedora 20 is not fully supported in 3.4.0 alpha: you'll need at least to downgrade sos using the one shipped by Fedora 19. > > Kind regards, > > Jorick Astrego > Netbulae B.V. > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] Fwd: Re: Help: Problem uploading the ISO file on engine
Il 14/01/2014 17:52, David Li ha scritto: > The ovirt-iso-uploader log only has one line: > > 2014-01-13 19:08:05::INFO::engine-iso-uploader::1067::root:: Start uploading > CentOS-6.4-x86_64-netinstall.iso > > > This is version 3.3.2-1.el6 > > My immediate question is how I can kill the upload process without rebooting > the engine box? So I can try to reproduce the problem again. > It's probably in a "sleep but not interrupt" state. None of the usual kill -9 > commands worked. My NFS ISO domain has also been put in the "inactive" state > most likely due to this problem. > > I think that connectivity to NFS server may have gone down while uploading the ISO image. That may have caused NFS ISO domain change the state to "inactive" and caused iso uploader to change its execution state to "D". But IIRC in such case kill -9 should work. Federico, do you have any suggestion? > Thanks. > > David > > > - Original Message - >> From: Sandro Bonazzola >> To: david...@sbcglobal.net >> Cc: >> Sent: Tuesday, January 14, 2014 2:05 AM >> Subject: Fwd: Re: [Users] Help: Problem uploading the ISO file on engine >> >> >> >> >> ---- Messaggio originale >> Oggetto: Re: [Users] Help: Problem uploading the ISO file on engine >> Data: Tue, 14 Jan 2014 11:04:37 +0100 >> Mittente: Sandro Bonazzola >> A: Sven Kieske , "users@ovirt.org" >> >> >> Il 14/01/2014 08:32, Sven Kieske ha scritto: >>> Hi, >>> >>> which engine version? >>> anything in engine.log? >> >> +1 >> >>> (I honestly don't know if there's any logging >>> for the iso uploader?). >> >> yes there is, in /var/log/ovirt-iso-uploader dir. >> >>> >>> I never encountered such a problem. >> >> Same here. Can you reproduce using -v flag when running iso uploader? >> >> >> >>> >>> HTH >>> >>> Am 13.01.2014 20:45, schrieb David Li: >>>> Hi, >>>> >>>> I copied a Centos netinstall ISO file to a directory on my engine >> machine to get ready for installation. Then I used >>>> >>>> engine-iso-uploader upload -i ISO_DOMAIN >> CentOS-6.4-x86_64-netinstall.iso >>>> >>>> to upload or put it into the proper ISO domain directory. However this >> command now totally stuck. Even kill -9 won't be able to do anything. >> Moreover now my ISO domain in the DC seems dead or becomes inactive too. >>>> >>>> What happened? Is there any way to recover from this point without >> rebooting everything? >>> >> >> >> -- >> Sandro Bonazzola >> Better technology. Faster innovation. Powered by community collaboration. >> See how it works at redhat.com >> -- 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: [Users] [QE] oVirt 3.3.3 beta status
Hi, oVirt 3.3.3 beta has been released and is actually on QA. The bug tracker [1] shows no bugs blocking the release The following is a list of the non-blocking bugs still open with target 3.3 - 3.3.3: Whiteboard Bug ID Summary infra 987982 When adding a host through the REST API, the error message says that "rootPassword" is required... infra 1040022 vdsm-tool configurre errors when installing vdsm package integration 902979 ovirt-live - firefox doesn't trust the installed engine integration 1021805 [RFE] oVirt Live - use motd to show the admin password integration 1022440 [RFE] AIO - configure the AIO host to be a gluster cluster/host integration 1026930 Package virtio-win and put it in ovirt repositories integration 1026933 pre-populate ISO domain with virtio-win ISO network 997197 Some AppErrors messages are grammatically incorrect (singular vs plural) storage 987917 [oVirt] [glance] API version not specified in provider dialog virt1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain 906257 USB Flash Drive install of ovirt-node created via dd fails 923049 ovirt-node fails to boot from local disk under UEFI mode 965583 [RFE] add shortcut key on TUI 976675 [wiki] Update contribution page 979350 Changes admin password in the first time when log in is failed while finished auto-install 979390 [RFE] Split defaults.py into smaller pieces 982232 performance page takes >1sec to load (on first load) 984441 kdump page crashed before configuring the network after ovirt-node intalled 986285 UI crashes when no bond name is given 991267 [RFE] Add TUI information to log file. 1018374 ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19: Failed on Auto-install 1018710 [RFE] Enhance API documentation 1032035 [RFE]re-write auto install function for the cim plugin 1033286 ovirt-node-plugin-vdsm can not be added to ovirt node el6 base image Maintainers: - Please add the bugs to the tracker if you think that 3.3.3 should not be released without them fixed. - Please provide ETA on bugs you add as blockers - Please re-target all bugs you don't think that should block 3.3.3. - Please fill release notes, the page has been created here [3] For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [2]. [1] http://bugzilla.redhat.com/1050084 [2] http://www.ovirt.org/Testing/Ovirt_3.3.3_testing [3] http://www.ovirt.org/OVirt_3.3.3_release_notes 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] [QE] 3.4.0 alpha release status
Hi, oVirt 3.4.0 alpha has been released and is actually on QA. The bug tracker [1] shows the following bugs blocking the release: There are still 280 bugs [2] targeted to 3.4.0 so please review them as soon as possible Maintainers: - Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed. - Please provide ETA on bugs you add as blockers - Please start updating the target to 3.4.1 or any next release for bugs that won't be in 3.4.0: it will ease gathering the blocking bugs for next releases. - Please start filling release notes, the page has been created here [3] For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug. [1] https://bugzilla.redhat.com/1024889 [2] http://red.ht/1eIRZXM [3] http://www.ovirt.org/OVirt_3.4.0_release_notes 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: [Users] [QE] 3.4.0 alpha release status
Il 15/01/2014 12:24, Sandro Bonazzola ha scritto: > Hi, > oVirt 3.4.0 alpha has been released and is actually on QA. > > The bug tracker [1] shows the following bugs blocking the release: Sorry, missed the blocker list: network - Bug 987813 - [RFE] report BOOTPROTO and BONDING_OPTS independent of netdevice.cfg storage - Bug 1032686 - [RFE] API to save OVF on any location gluster - Bug 1038988 - Gluster brick sync does not work when host has multiple interfaces > > There are still 280 bugs [2] targeted to 3.4.0 so please review them as soon > as possible > > Maintainers: > - Please add the bugs to the tracker if you think that 3.4.0 should not be > released without them fixed. > - Please provide ETA on bugs you add as blockers > - Please start updating the target to 3.4.1 or any next release for bugs that > won't be in 3.4.0: > it will ease gathering the blocking bugs for next releases. > - Please start filling release notes, the page has been created here [3] > > > For those who want to help testing the bugs, I suggest to add yourself as QA > contact for the bug. > > > [1] https://bugzilla.redhat.com/1024889 > [2] http://red.ht/1eIRZXM > [3] http://www.ovirt.org/OVirt_3.4.0_release_notes > > > 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: [Users] Issues installing hosted-engine with 3.4.0 alpha
Il 15/01/2014 02:35, Andrew Lau ha scritto:
> I guess I spoke too soon.. Although, it allowed me to complete the setup
> prompts it now fails at "Misc Configuration"
>
> Error Logs:
>
> 2014-01-15 11:49:34 INFO
> otopi.plugins.ovirt_hosted_engine_setup.system.vdsmenv vdsmenv._connect:81
> Waiting for VDSM hardware info
> 2014-01-15 11:49:35 INFO
> otopi.plugins.ovirt_hosted_engine_setup.system.vdsmenv vdsmenv._connect:81
> Waiting for VDSM hardware info
> 2014-01-15 11:49:36 DEBUG
> otopi.plugins.ovirt_hosted_engine_setup.system.vdsmenv vdsmenv._connect:78
> {'status': {'message': 'Recovering from crash or$
> 2014-01-15 11:49:36 DEBUG otopi.context context.dumpEnvironment:456
> ENVIRONMENT DUMP - BEGIN
> 2014-01-15 11:49:36 DEBUG otopi.context context.dumpEnvironment:471 ENV
> OVEHOSTED_VDSM/vdsClient=instance:' 2014-01-15 11:49:36 DEBUG otopi.context context.dumpEnvironment:473
> ENVIRONMENT DUMP - END
> 2014-01-15 11:49:36 DEBUG otopi.context context._executeMethod:138 Stage misc
> METHOD otopi.plugins.ovirt_hosted_engine_setup.network.bridge.Plugin._m$
> 2014-01-15 11:49:36 INFO
> otopi.plugins.ovirt_hosted_engine_setup.network.bridge bridge._misc:189
> Configuring the management bridge
> 2014-01-15 11:49:37 DEBUG otopi.context context._executeMethod:152 method
> exception
> Traceback (most recent call last):
> File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in
> _executeMethod
> method['method']()
> File
> "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/network/bridge.py",
> line 194, in _misc
> ].s.getVdsCapabilities()['info']['nics'][nics]
> KeyError: 'info'
we're investigating on the issue.
> 2014-01-15 11:49:37 ERROR otopi.context context._executeMethod:161 Failed to
> execute stage 'Misc configuration': 'info'
> 2014-01-15 11:49:37 DEBUG otopi.transaction transaction.abort:131 aborting
> 'File transaction for '/etc/ovirt-hosted-engine/firewalld/hosted-console.x$
> 2014-01-15 11:49:37 DEBUG otopi.transaction transaction.abort:131 aborting
> 'File transaction for '/etc/ovirt-hosted-engine/iptables.example''
> 2014-01-15 11:49:37 DEBUG otopi.transaction transaction.abort:131 aborting
> 'File transaction for '/etc/sysconfig/iptables''
> 2014-01-15 11:49:37 DEBUG otopi.transaction transaction.abort:131 aborting
> 'File transaction for '/etc/ovirt-hosted-engine-ha/broker.conf''
> 2014-01-15 11:49:37 DEBUG otopi.context context.dumpEnvironment:456
> ENVIRONMENT DUMP - BEGIN
> 2014-01-15 11:49:37 DEBUG otopi.context context.dumpEnvironment:471 ENV
> BASE/error=bool:'True'
> 2014-01-15 11:49:37 DEBUG otopi.context context.dumpEnvironment:473
> ENVIRONMENT DUMP - END
> 2014-01-15 11:49:37 INFO otopi.context context.runSequence:395 Stage: Clean up
> 2014-01-15 11:49:37 DEBUG otopi.context context.runSequence:399 STAGE cleanup
>
>
>
> On Wed, Jan 15, 2014 at 11:27 AM, Andrew Lau <mailto:and...@andrewklau.com>> wrote:
>
> Hi,
>
> Dropping VDSM list because I'm not subscribed.
>
> Using the nightly repo it seems to be fixed. I will continue to report
> any new findings.
>
> Thanks,
> Andrew.
>
>
> On Tue, Jan 14, 2014 at 8:52 PM, Sandro Bonazzola <mailto:sbona...@redhat.com>> wrote:
>
> Il 14/01/2014 03:39, Andrew Lau ha scritto:
> > It looks like vdsm is trying to execute:
> > vdsm-tool unified_network_persistence_upgrade
> >
> > But my version of vdsm-tool has it labeled as
> "upgrade-unified-persistence"
>
> vdsm people, can you check this?
>
>
>
> >
> > On Tue, Jan 14, 2014 at 1:32 PM, Andrew Lau <mailto:and...@andrewklau.com> <mailto:and...@andrewklau.com
> <mailto:and...@andrewklau.com>>> wrote:
> >
> > Hi,
> >
> > I'm giving the new hosted-engine feature a try with the new
> 3.4.0 alpha build on centos 6.5
> >
> > hosted-engine --deply seems to fail at the 'Environment setup"
> > [ ERROR ] Failed to execute stage 'Environment setup': Command
> '/sbin/service' failed to execute
> >
> > Within the logs I believe it seems to be related to vdsm. Logs
> show "VDS daemon is not running"
> >
> > service vdsm start gives the following error:
>
[Users] [QE] oVirt bugzilla updates
Hi oVirt community, for all people interested in joining QE effort, we've created a new user in bugzilla as default QA assignee: b...@ovirt.org. If you want to be updated on QE bugs activity you can just add that user to your bugzilla account watch list: https://bugzilla.redhat.com/userprefs.cgi?tab=email Watch user list -> add "b...@ovirt.org" Any email sent by bugzilla to that user will be also sent to you. -- 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] [QE] oVirt 3.3.3 beta / RC status
Hi, oVirt 3.3.3 beta has been released and is actually on QA. We'll start composing oVirt 3.3.3 RC on 2014-01-21 12:00 UTC. The bug tracker [1] shows no bugs blocking the release The following is a list of the non-blocking bugs still open with target 3.3 - 3.3.3: Whiteboard Bug ID Summary integration 902979 ovirt-live - firefox doesn't trust the installed engine integration 1021805 [RFE] oVirt Live - use motd to show the admin password integration 1022440 [RFE] AIO - configure the AIO host to be a gluster cluster/host integration 1026930 Package virtio-win and put it in ovirt repositories integration 1026933 pre-populate ISO domain with virtio-win ISO integration 1050084 Tracker: oVirt 3.3.3 release network 997197 Some AppErrors messages are grammatically incorrect (singular vs plural) node906257 USB Flash Drive install of ovirt-node created via dd fails node923049 ovirt-node fails to boot from local disk under UEFI mode node965583 [RFE] add shortcut key on TUI node976675 [wiki] Update contribution page node979350 Changes admin password in the first time when log in is failed while finished auto-install node979390 [RFE] Split defaults.py into smaller pieces node982232 performance page takes >1sec to load (on first load) node984441 kdump page crashed before configuring the network after ovirt-node intalled node986285 UI crashes when no bond name is given node991267 [RFE] Add TUI information to log file. node1018374 ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19: Failed on Auto-install node1018710 [RFE] Enhance API documentation node1032035 [RFE]re-write auto install function for the cim plugin node1033286 ovirt-node-plugin-vdsm can not be added to ovirt node el6 base image storage 987917 [oVirt] [glance] API version not specified in provider dialog virt1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain Maintainers: - We'll start composing oVirt 3.3.3 RC on 2014-01-21 12:00 UTC: all non blockers bug still open after the build will be moved to 3.3.4. - Please add the bugs to the tracker if you think that 3.3.3 should not be released without them fixed. - Please provide ETA on bugs you add as blockers - Please re-target all bugs you don't think that should block 3.3.3. - Please fill release notes, the page has been created here [3] - Please remember to rebuild your packages before 2014-01-21 12:00 UTC if you want them to be included in 3.3.3 RC. For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [2]. Thanks to Gianluca Cecchi for his testing of oVirt 3.3.3 beta on Gluster storage! [1] http://bugzilla.redhat.com/1050084 [2] http://www.ovirt.org/Testing/Ovirt_3.3.3_testing [3] http://www.ovirt.org/OVirt_3.3.3_release_notes 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] [QE] oVirt 3.4.0 alpha / beta status
Hi, oVirt 3.4.0 alpha has been released and is actually on QA. An issue has been found in VDSM so we have updated the packages in alpha repositories for Fedora. We had an issue with nightly build for EL6 packages yesterday so EL6 repository is not yet updated. We'll try to sync it today, I'm sorry for the inconvenient. We'll start composing oVirt 3.4.0 beta on 2014-01-20 14:00 UTC from 3.4 branches. The bug tracker [1] shows the following bugs blocking the release: Whiteboard Bug ID Summary gluster 1038988 Gluster brick sync does not work when host has multiple interfaces integration 1054080 gracefully warn about unsupported upgrade from legacy releases network 1054195 [NetworkLabels] Attaching two labeled networks to a cluster result in failure of the latter There are still 280 bugs [2] targeted to 3.4.0. Excluding node and documentation bugs we still have 237 bugs [3] targeted to 3.4.0. Please review them as soon as possible. Maintainers: - Please remember to rebuild your packages before 2014-01-21 12:00 UTC if you want them to be included in 3.4.0 beta. - Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed. - Please provide ETA on blockers bugs - Please update the target to 3.4.1 or any next release for bugs that won't be in 3.4.0: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] - Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-01-23 For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug. Please also be prepared for upcoming oVirt 3.4.0 Test Day on 2014-01-23! Thanks to all people already testing 3.4.0 alpha! [1] https://bugzilla.redhat.com/1024889 [2] http://red.ht/1eIRZXM [3] http://red.ht/1auBU3r [4] http://www.ovirt.org/OVirt_3.4.0_release_notes -- 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: [Users] engine reports and dwh setup in 3.3.2
Il 17/01/2014 11:40, Gianluca Cecchi ha scritto: > On Thu, Jan 16, 2014 at 5:55 PM, Yaniv Dary wrote: > >> >> I think a this point it is safe to install. >> >>> If I can go, can I use >>> https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.3-Beta/html/Installation_Guide/Installing_and_Configuring_the_History_Database.html >>> >>> as a workflow input? >>> (with changes where needed, as rhevm-dwh --> ovirt-engine-dwh) >> >> You can try it, but not sure everything will be applicable. >> >>> >>> Let me know so that I can try >>> >>> Gianluca >>> > > dwh part went ok and ovirt_engine_history db was created. > > The reports part got error > > # ovirt-engine-reports-setup > Welcome to ovirt-engine-reports setup utility > In order to proceed the installer must stop the ovirt-engine service > Would you like to stop the ovirt-engine service (yes|no): yes > Stopping ovirt-engine... [ DONE ] > Editing XML files... [ DONE ] > Setting DB connectivity...[ DONE ] > Please choose a password for the reports admin user(s) (ovirt-admin): > Warning: Weak Password. > Retype password: > Warning: Weak Password. > Deploying Server... [ DONE ] > Updating Redirect Servlet... [ DONE ] > Importing reports... [ DONE ] > Customizing Server... [ DONE ] > global name 'preserveReportsJobs' is not defined > Error encountered while installing ovirt-engine-reports, please > consult the log file: > /var/log/ovirt-engine/ovirt-engine-reports-setup-2014_01_17_11_20_29.log > > It seems the main point in log file, as in standard output is this: > > 2014-01-17 11:22:22::ERROR::ovirt-engine-reports-setup::1196::root:: > Failed to complete the setup of the reports package! > 2014-01-17 11:22:22::DEBUG::ovirt-engine-reports-setup::1197::root:: > Traceback (most recent call last): > File "/bin/ovirt-engine-reports-setup", line 1163, in main > if preserveReportsJobs: > NameError: global name 'preserveReportsJobs' is not defined This has been fixed yesterday http://gerrit.ovirt.org/#/c/23304/ > > Let me know if you need full logs or if this is sufficient to debug > code and propose a solution to try then again. > > Gianluca > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] Issues installing hosted-engine with 3.4.0 alpha
Il 15/01/2014 14:54, Sandro Bonazzola ha scritto:
> Il 15/01/2014 02:35, Andrew Lau ha scritto:
>> I guess I spoke too soon.. Although, it allowed me to complete the setup
>> prompts it now fails at "Misc Configuration"
>>
>> Error Logs:
>>
>> 2014-01-15 11:49:34 INFO
>> otopi.plugins.ovirt_hosted_engine_setup.system.vdsmenv vdsmenv._connect:81
>> Waiting for VDSM hardware info
>> 2014-01-15 11:49:35 INFO
>> otopi.plugins.ovirt_hosted_engine_setup.system.vdsmenv vdsmenv._connect:81
>> Waiting for VDSM hardware info
>> 2014-01-15 11:49:36 DEBUG
>> otopi.plugins.ovirt_hosted_engine_setup.system.vdsmenv vdsmenv._connect:78
>> {'status': {'message': 'Recovering from crash or$
>> 2014-01-15 11:49:36 DEBUG otopi.context context.dumpEnvironment:456
>> ENVIRONMENT DUMP - BEGIN
>> 2014-01-15 11:49:36 DEBUG otopi.context context.dumpEnvironment:471 ENV
>> OVEHOSTED_VDSM/vdsClient=instance:'> $
>> 2014-01-15 11:49:36 DEBUG otopi.context context.dumpEnvironment:473
>> ENVIRONMENT DUMP - END
>> 2014-01-15 11:49:36 DEBUG otopi.context context._executeMethod:138 Stage
>> misc METHOD otopi.plugins.ovirt_hosted_engine_setup.network.bridge.Plugin._m$
>> 2014-01-15 11:49:36 INFO
>> otopi.plugins.ovirt_hosted_engine_setup.network.bridge bridge._misc:189
>> Configuring the management bridge
>> 2014-01-15 11:49:37 DEBUG otopi.context context._executeMethod:152 method
>> exception
>> Traceback (most recent call last):
>> File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in
>> _executeMethod
>> method['method']()
>> File
>> "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/network/bridge.py",
>> line 194, in _misc
>> ].s.getVdsCapabilities()['info']['nics'][nics]
>> KeyError: 'info'
>
> we're investigating on the issue.
Bug 1053420 - ovirt-hosted-engine-setup fails with vdsm issues
Fixed, will be included in the next nightly.
>
>> 2014-01-15 11:49:37 ERROR otopi.context context._executeMethod:161 Failed to
>> execute stage 'Misc configuration': 'info'
>> 2014-01-15 11:49:37 DEBUG otopi.transaction transaction.abort:131 aborting
>> 'File transaction for '/etc/ovirt-hosted-engine/firewalld/hosted-console.x$
>> 2014-01-15 11:49:37 DEBUG otopi.transaction transaction.abort:131 aborting
>> 'File transaction for '/etc/ovirt-hosted-engine/iptables.example''
>> 2014-01-15 11:49:37 DEBUG otopi.transaction transaction.abort:131 aborting
>> 'File transaction for '/etc/sysconfig/iptables''
>> 2014-01-15 11:49:37 DEBUG otopi.transaction transaction.abort:131 aborting
>> 'File transaction for '/etc/ovirt-hosted-engine-ha/broker.conf''
>> 2014-01-15 11:49:37 DEBUG otopi.context context.dumpEnvironment:456
>> ENVIRONMENT DUMP - BEGIN
>> 2014-01-15 11:49:37 DEBUG otopi.context context.dumpEnvironment:471 ENV
>> BASE/error=bool:'True'
>> 2014-01-15 11:49:37 DEBUG otopi.context context.dumpEnvironment:473
>> ENVIRONMENT DUMP - END
>> 2014-01-15 11:49:37 INFO otopi.context context.runSequence:395 Stage: Clean
>> up
>> 2014-01-15 11:49:37 DEBUG otopi.context context.runSequence:399 STAGE cleanup
>>
>>
>>
>> On Wed, Jan 15, 2014 at 11:27 AM, Andrew Lau > <mailto:and...@andrewklau.com>> wrote:
>>
>> Hi,
>>
>> Dropping VDSM list because I'm not subscribed.
>>
>> Using the nightly repo it seems to be fixed. I will continue to report
>> any new findings.
>>
>> Thanks,
>> Andrew.
>>
>>
>> On Tue, Jan 14, 2014 at 8:52 PM, Sandro Bonazzola > <mailto:sbona...@redhat.com>> wrote:
>>
>> Il 14/01/2014 03:39, Andrew Lau ha scritto:
>> > It looks like vdsm is trying to execute:
>> > vdsm-tool unified_network_persistence_upgrade
>> >
>> > But my version of vdsm-tool has it labeled as
>> "upgrade-unified-persistence"
>>
>> vdsm people, can you check this?
>>
>>
>>
>> >
>> > On Tue, Jan 14, 2014 at 1:32 PM, Andrew Lau > <mailto:and...@andrewklau.com> <mailto:and...@andrewklau.com
>> <mailto:and...@andrewklau.com>>> wrote:
>> >
>> > Hi,
>> >
>> > I'm giving the new hosted-engine featu
Re: [Users] [QE] oVirt 3.4.0 alpha / beta status
Il 17/01/2014 10:16, Sandro Bonazzola ha scritto: > Hi, > oVirt 3.4.0 alpha has been released and is actually on QA. > An issue has been found in VDSM so we have updated the packages in alpha > repositories for Fedora. > We had an issue with nightly build for EL6 packages yesterday so EL6 > repository is not yet updated. > We'll try to sync it today, I'm sorry for the inconvenient. 3.4.0 alpha repository has been refreshed also for EL6. > We'll start composing oVirt 3.4.0 beta on 2014-01-20 14:00 UTC from 3.4 > branches. > > The bug tracker [1] shows the following bugs blocking the release: > WhiteboardBug ID Summary > gluster 1038988 Gluster brick sync does not work when host has > multiple interfaces > integration 1054080 gracefully warn about unsupported upgrade from legacy > releases > network 1054195 [NetworkLabels] Attaching two labeled networks > to a cluster result in failure of the latter > > > There are still 280 bugs [2] targeted to 3.4.0. > Excluding node and documentation bugs we still have 237 bugs [3] targeted to > 3.4.0. > Please review them as soon as possible. > > Maintainers: > - Please remember to rebuild your packages before 2014-01-21 12:00 UTC if you > want them to be included in 3.4.0 beta. > - Please add the bugs to the tracker if you think that 3.4.0 should not be > released without them fixed. > - Please provide ETA on blockers bugs > - Please update the target to 3.4.1 or any next release for bugs that won't > be in 3.4.0: > it will ease gathering the blocking bugs for next releases. > - Please fill release notes, the page has been created here [4] > - Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-01-23 > > > For those who want to help testing the bugs, I suggest to add yourself as QA > contact for the bug. > Please also be prepared for upcoming oVirt 3.4.0 Test Day on 2014-01-23! > Thanks to all people already testing 3.4.0 alpha! > > [1] https://bugzilla.redhat.com/1024889 > [2] http://red.ht/1eIRZXM > [3] http://red.ht/1auBU3r > [4] http://www.ovirt.org/OVirt_3.4.0_release_notes > -- 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: [Users] engine-iso-uploader -- REST API not usable?
Il 18/01/2014 21:12, Juan Hernandez ha scritto: > On 01/18/2014 07:49 PM, Ted Miller wrote: >> I ran into this problem when I tried to use engine-iso-uploader, but >> reading on the lists makes it sound like it may be a more general >> problem. There was a bug that caused this, but that was back in the >> ver. 3.0/3.1 days, and doesn't seem common since then. >> >> Back on Dec 24 I was able to upload an ISO file OK, so I am not sure >> what has changed since then. >> >> I am running a test setup, fully up to date: >> office2a host w/ glusterfs Centos 6 >> office4a host w/ glusterfs Centos 6 >> ov-eng01 engine on Centos 6 VM (not hosted on oVirt) >> office9 KVM host (not oVirt) for ov-eng01 >> >> whether I log in to ov-eng01 by ssh or execute the command from the >> console, I get: >> >> # engine-iso-uploader list -v >> Please provide the REST API password for the admin@internal oVirt Engine >> user (CTRL+D to abort): >> ERROR: Problem connecting to the REST API. Is the service available and >> does the CA certificate exist? >> >> checking on some things suggested on a thread about engine-iso-uploader >> back in March, I get: >> >> # ls -la /etc/pki/ovirt-engine/ca.pem >> -rw-r--r--. 1 root root 4569 Nov 10 15:13 /etc/pki/ovirt-engine/ca.pem >> >> # cat >> /var/log/ovirt-engine/ovirt-iso-uploader/ovirt-iso-uploader/20140117112938.log >> 2014-01-17 11:29:44::ERROR::engine-iso-uploader::512::root:: Problem >> connecting to the REST API. Is the service available and does the CA >> certificate exist? >> >> The thread back in March gave a work-around to upload ISO images >> directly, so I am not "blocked" from uploading images, but I would like >> to get things working "right", as I am afraid the problem will "turn >> around and bite me" down the road. >> >> Ted Miller >> > > To discard an actual problem with the REST API I would suggest you to > run the following command, from the same machine: > > # curl \ > --cacert /etc/pki/ovirt-engine/ca.pem \ > --user admin@internal:your_password \ > https://your_host/api > > This should give you a XML document containing the entry point of the > API, something like this: > > > >... > > > I would also suggest to check the /etc/ovirt-engine/isouploader.conf > file, as you may have changed something there in the past. > Can you also tell us which version are you running? rpm -qa |grep ovirt and ls -lZ /root/.ssh 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] 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] [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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [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" >> To: annou...@ovirt.org, "arch" , Users@ovirt.org, >> "engine-devel" >> 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-de...@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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Engine-devel] 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"
>>> To: dougsl...@redhat.com
>>> Cc: "engine-devel" , Users@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"
>>>> To: "Eli Mesika" , "Sandro Bonazzola"
>>>>
>>>> Cc: "engine-devel" , Users@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"
>>>>>> To: "Martin Perina"
>>>>>> Cc: "engine-devel" , Users@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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [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" >> To: "Martin Perina" >> Cc: "engine-devel" , Users@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.
Re: [Users] [ANN] oVirt 3.4.0 Test Day - Tomorrow Jan 23th
Il 23/01/2014 07:45, Ramesh Nachimuthu ha scritto: > 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? Same here, if it's not already there, please open a BZ on VDSM. As temporary workaround, please use cluster with 3.3 cluster level > > > Regards, > Ramesh > - Original Message - > From: "Sandro Bonazzola" > To: "arch" , "engine-devel" , > Users@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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Upgrade 3.3 - 3.4
Il 23/01/2014 01:52, Maurice James ha scritto: > Anyone else seeing this error on upgrade from 3.3 - 3.4? > > > > [ ERROR ] Yum [u'Errors were encountered while downloading packages.', > u'ovirt-engine-backend-3.4.0-0.5.beta1.el6.noarch: failure: > noarch/ovirt-engine-backend-3.4.0-0.5.beta1.el6.noarch.rpm from > ovirt-3.4.0-prerelease: [Errno 256] No more mirrors to try.'] The rpm is there: http://resources.ovirt.org/releases/3.4.0_pre/rpm/EL/6/noarch/ovirt-engine-backend-3.4.0-0.5.beta1.el6.noarch.rpm please run # yum clean metadata and retry > > > > > > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] [ANN] oVirt 3.4.0 Test Day - Tomorrow Jan 23th
Il 23/01/2014 09:18, Ramesh ha scritto: > On 01/23/2014 12:32 PM, Sandro Bonazzola wrote: >> Il 23/01/2014 07:45, Ramesh Nachimuthu ha scritto: >>> 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? >> Same here, if it's not already there, please open a BZ on VDSM. >> As temporary workaround, please use cluster with 3.3 cluster level > I have rasied the BZ https://bugzilla.redhat.com/show_bug.cgi?id=1056918. > <https://bugzilla.redhat.com/show_bug.cgi?id=1056918> > > But I am not able to create a new Cluster with Compatibility version 3.3 in > Gluster only mode. Only compataibility version supported is 3.4. Can you try upgrading libvirt* from ftp://libvirt.org/libvirt/ or http://fedorapeople.org/groups/virt/virt-preview/fedora-19/rpms/ ? > > Regards, > Ramesh > <https://bugzilla.redhat.com/show_bug.cgi?id=1056918> >>> Regards, >>> Ramesh >>> - Original Message - >>> From: "Sandro Bonazzola" >>> To: "arch" , "engine-devel" , >>> Users@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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Cluster compatibility
Il 23/01/2014 10:49, Piotr Kliczewski ha scritto: > I wanted to install two hosts one on f19 and the second on el6. I > created additional cluster for el6. > Host installation for el6 worked well and it joined the cluster > without any issues. Whereas host in f19was successfully deployed > but it failed to join the cluster due to: > > Host fedora is compatible with versions (3.0,3.1,3.2,3.3) and cannot > join Cluster Default which is set to version 3.4. known issue, on F19 please enable fedora-virt-preview repo, update "libvirt*" and retry > > Here are the versions that I use: > > engine: > Name: ovirt-engine > Arch: noarch > Version : 3.4.0 > Release : 0.5.beta1.fc19 > Size: 1.5 M > Repo: installed > From repo : ovirt-3.4.0-prerelease > > fedora host: > Name: vdsm > Arch: x86_64 > Version : 4.14.1 > Release : 2.fc19 > Size: 2.9 M > Repo: installed > From repo : ovirt-3.4.0-prerelease > > el6 host: > Name: vdsm > Arch: x86_64 > Version : 4.14.1 > Release : 2.el6 > Size: 2.9 M > Repo: installed > From repo : ovirt-3.4.0-prerelease > > Both clusters are set to be compatible with 3.4. > > Is there anything that I am missing? > > Piotr > _______ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] Ovirt 3.3.2. and vdsm 4.14
Il 22/01/2014 18:32, Federico Alberto Sayd ha scritto: > Hello: > > Why Ovirt 3.3.2. installs vdsm 4.14 on Centos 6.5?? please yum clean all, yum update ovirt-release, and then retry. > > I am installing 5 nodes with Centos 6.5. > > I have installed two nodes, I have added: > > 1 - epel repo > (http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm) > > 2 - ovirt repo (http://ovirt.org/releases/ovirt-release-el.noarch.rpm) > > In the two first nodes Ovirt engine installed vdsm 4.13. > > Now I have installed the third node with the same repos and Ovirt installs > vdsm 4.14 and when it tries to activate the node complains about the vdsm > version, it says that vdsm version is not compatible: > > Host "my-third-node" is installed with VDSM version (4.14) and cannot join > cluster Cluster-XXX which is compatible with VDSM versions [4.13, 4.9, > 4.11, 4.12, 4.10]. > > > /etc/yum.repos.d in the trhee nodes are the same: > > CentOS-Base.repo CentOS-Debuginfo.repo CentOS-Media.repo CentOS-Vault.repo > el6-ovirt.repo epel.repo epel-testing.repo glusterfs-epel.repo > > Why the difference? It is not suppossed that oVirt 3.3.2 should install vdsm > 3.13 ?? > > Thanks, > > Federico > _______ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users -- 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: [Users] Possible problems testing 3.3.3 RC
Il 23/01/2014 12:12, Gianluca Cecchi ha scritto: > On Thu, Jan 23, 2014 at 12:08 PM, Yedidyah Bar David wrote: > >> >> Because it's in the updates repo, not sure why is that. Yaniv/Eyal? >> -- >> Didi > > Indeed > I see that > > 1) In this repo > http://resources.ovirt.org/releases/beta/rpm/Fedora/19/noarch/ > I would expect dwh for 3.4 while I have > ovirt-engine-dwh-3.3.3-1.fc19.noarch.rpm > > 2) in this repo > http://resources.ovirt.org/releases/updates-testing/rpm/Fedora/19/noarch/ > I would expect dwh for 3.3.3 while I have > ovirt-engine-dwh-3.3.3-1.fc19.noarch.rpm > ovirt-engine-dwh-3.4.0-0.2.master.20140122122024.fc19.noarch.rpm > ovirt-engine-dwh-setup-3.4.0-0.2.master.20140122122024.fc19.noarch.rpm It seems that it has been added after 3.3.3-rc announce by mistake. Will fix it > > Gianluca > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] Possible problems testing 3.3.3 RC
Il 23/01/2014 14:07, Gianluca Cecchi ha scritto: > On Thu, Jan 23, 2014 at 1:23 PM, Sandro Bonazzola wrote: >> Il 23/01/2014 12:12, Gianluca Cecchi ha scritto: > [snip] >>> 2) in this repo >>> http://resources.ovirt.org/releases/updates-testing/rpm/Fedora/19/noarch/ >>> I would expect dwh for 3.3.3 while I have >>> ovirt-engine-dwh-3.3.3-1.fc19.noarch.rpm >>> ovirt-engine-dwh-3.4.0-0.2.master.20140122122024.fc19.noarch.rpm >>> ovirt-engine-dwh-setup-3.4.0-0.2.master.20140122122024.fc19.noarch.rpm >> >> It seems that it has been added after 3.3.3-rc announce by mistake. >> Will fix it > > OK. It seems now the updates-testing repo is ok: > ovirt-engine-dwh-3.3.3-1.fc19.noarch.rpm > > upgrade went smooth. > I'm going to test. Yes, updates-testing repo is back to stable: http://jenkins.ovirt.org/job/check_repo_closure/26/ > > Gianluca > -- 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: [Users] hosted-engine setup fails on RHEL6
0-0.2.master.20140120.gitdeb0453.el6.noarch > ovirt-hosted-engine-setup-1.2.0-0.0.master.20140117.gitfaf77a5.el6.noarch > ovirt-hosted-engine-ha-1.1.0-0.1.beta1.el6.noarch > ovirt-engine-sdk-python-3.4.0.2-1.20140121.git42b7d69.el6.noarch > ovirt-release-el6-10.0.1-2.noarch > vdsm-python-zombiereaper-4.14.1-6.gite008998.el6.noarch > vdsm-python-4.14.1-6.gite008998.el6.x86_64 > vdsm-cli-4.14.1-6.gite008998.el6.noarch > vdsm-xmlrpc-4.14.1-6.gite008998.el6.noarch > vdsm-4.14.1-6.gite008998.el6.x86_64 > > > Any hint? > > > Thanks > - Frank > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] oVirt 3.4.0 beta - Hosted Engine Setup -- issues
ed 'standard' add-on utilities. > This was a > fresh install just for this test. > - 512MB /boot ext4 > - 80GB / ext4 in LVM, 220GB free in VG > - "yum -y update" performed to get all latest updates > - SElinux in permissive mode > - Hardware: > - Supermicro 1026T-URF barebones > - single CPU populated (Xeon E5630 4x2.53GHz) > - 12GB ECC DDR3 RAM > - H/W Raid with SSDs > - Networking: > - Network Manager DISABLED > - 4 GbE ports (p2p1, p2p2, em1, em2) > - all 4 ports configured in a bond (bond0) using balance-alb > - ovirtmgmt bridge pre-created with 'bond0' as the only member, assigned a > static IP address > - firewall DISABLED > - /etc/yum.repos.d/ovirt.rep has ONLY the 3.4.0 beta repo enabled: > [ovirt-3.4.0-beta] > name=3.4.0 beta testing repo for the oVirt project > baseurl=http://ovirt.org/releases/3.4.0-beta/rpm/Fedora/$releasever/ > enabled=1 > skip_if_unavailable=1 > gpgcheck=0 > - only other packages installed were "ntp" and "screen" > - performed "yum install ovirt-hosted-engine-setup" then "screen" then > "hosted-engine --deploy" > > > > Any guidance or things to test would be _greatly_ appreciated. > > Thanks! > -Brad > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users -- 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: [Users] hosted-engine setup fails on RHEL6
Il 23/01/2014 14:39, Frank Wall ha scritto:
> Hi Sandro,
>
> On Thu, Jan 23, 2014 at 02:28:29PM +0100, Sandro Bonazzola wrote:
>> Do you have the same issue you've with nightly?
>
> on BETA the hosted-engine setup fails (earlier) with another issue that seems
> to be
> fixed in NIGHTLY:
>
> 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel rhel.status:138
> check service vdsmd status
> 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel
> plugin.executeRaw:366 execute: ('/sbin/initctl', 'status', 'vdsmd'),
> executable='None', cwd='None', env=None
> 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel
> plugin.executeRaw:383 execute-result: ('/sbin/initctl', 'status', 'vdsmd'),
> rc=1
> 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel
> plugin.execute:441 execute-output: ('/sbin/initctl', 'status', 'vdsmd')
> stdout:
> 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel
> plugin.execute:446 execute-output: ('/sbin/initctl', 'status', 'vdsmd')
> stderr:
> initctl: Unknown job: vdsmd
>
can you attach full logs of this execution?
> Please don't mixup things... this was the first try on BETA. All other logs
> are from NIGHTLY :-)
>
>
>> can you attach vdsm logs?
>
> Yes, but only a few lines are logged during hosted-engine setup:
>
> MainThread::DEBUG::2014-01-23
> 14:17:37,132::supervdsmServer::424::SuperVdsm.Server::(main) Terminated
> normally
> MainThread::DEBUG::2014-01-23
> 14:17:37,885::netconfpersistence::134::root::(_getConfigs) Non-existing
> config set.
> MainThread::DEBUG::2014-01-23
> 14:17:37,885::netconfpersistence::134::root::(_getConfigs) Non-existing
> config set.
> MainThread::DEBUG::2014-01-23
> 14:17:37,900::supervdsmServer::384::SuperVdsm.Server::(main) Making sure I'm
> root - SuperVdsm
> MainThread::DEBUG::2014-01-23
> 14:17:37,900::supervdsmServer::393::SuperVdsm.Server::(main) Parsing cmd args
> MainThread::DEBUG::2014-01-23
> 14:17:37,900::supervdsmServer::396::SuperVdsm.Server::(main) Cleaning old
> socket /var/run/vdsm/svdsm.sock
> MainThread::DEBUG::2014-01-23
> 14:17:37,900::supervdsmServer::400::SuperVdsm.Server::(main) Setting up keep
> alive thread
> MainThread::DEBUG::2014-01-23
> 14:17:37,900::supervdsmServer::406::SuperVdsm.Server::(main) Creating remote
> object manager
> MainThread::DEBUG::2014-01-23
> 14:17:37,901::supervdsmServer::417::SuperVdsm.Server::(main) Started serving
> super vdsm object
> sourceRoute::DEBUG::2014-01-23
> 14:17:37,901::sourceRouteThread::56::root::(_subscribeToInotifyLoop)
> sourceRouteThread.subscribeToInotifyLoop started
>
so vdsmd never started at all?
>
>
> Thanks
> - Frank
>
--
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: [Users] oVirt 3.4 release notes and what's new section empty
Il 23/01/2014 14:49, Gianluca Cecchi ha scritto: > hello, > at http://www.ovirt.org/OVirt_3.4.0_release_notes > > the what's new section seems to be empty. Release notes page is still under writing > What major/minor features one would expect as added value passing from > 3.3.3 to 3.4? > Any other pointers? you can find a list of features here http://bit.ly/17qBn6F or here: http://www.ovirt.org/OVirt_3.4_Test_Day#oVirt_3.4_New_Features_-_Test_Status_Table > > Thanks, > Gianluca > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] oVirt 3.4.0 beta - Hosted Engine Setup -- issues
Il 23/01/2014 15:21, Brad House ha scritto: > On 01/23/2014 08:30 AM, Sandro Bonazzola wrote: >> It seems that VDSM is not working on your system. >> Can you attach vdsm logs? >> > > vdsm log is empty > > # ls -l /var/log/vdsm/vdsm.log > -rw-r--r-- 1 root root 0 Jan 20 10:13 /var/log/vdsm/vdsm.log > > > # ps -ef | grep -i vdsm > root 1628 1 0 09:16 ?00:00:00 /usr/bin/python > /usr/share/vdsm/supervdsmServer --sockfile /var/run/vdsm/svdsm.sock > > > # service vdsmd status > Redirecting to /bin/systemctl status vdsmd.service > vdsmd.service - Virtual Desktop Server Manager >Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled) >Active: failed (Result: start-limit) since Thu 2014-01-23 09:16:38 EST; > 1min 26s ago > Process: 2387 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh > --post-stop (code=exited, status=0/SUCCESS) > Process: 2380 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1 > /dev/null -2 /dev/null /usr/share/vdsm/vdsm (code=exited, status=1/FAILURE) > Process: 2328 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh > --pre-start (code=exited, status=0/SUCCESS) > > Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Unit vdsmd.service > entered failed state. > Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: vdsmd.service > holdoff time over, scheduling restart. > Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Stopping Virtual > Desktop Server Manager... > Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Starting Virtual > Desktop Server Manager... > Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: vdsmd.service > start request repeated too quickly, refusing to start. what's this . It's the first start of vdsmd! > Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Failed to start > Virtual Desktop Server Manager. > Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Unit vdsmd.service > entered failed state. > > > I've attached the supervdsm.log and > ovirt-hosted-engine-setup-20140123091611.log incase that's helpful. > > Thanks. > -Brad -- 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: [Users] oVirt 3.4.0 beta - Hosted Engine Setup -- issues
Il 23/01/2014 15:30, Brad House ha scritto: > > > On 01/23/2014 09:24 AM, Sandro Bonazzola wrote: >>> # service vdsmd status >>> >Redirecting to /bin/systemctl status vdsmd.service >>> >vdsmd.service - Virtual Desktop Server Manager >>> >Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled) >>> >Active: failed (Result: start-limit) since Thu 2014-01-23 09:16:38 >>> > EST; 1min 26s ago >>> > Process: 2387 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh >>> > --post-stop (code=exited, status=0/SUCCESS) >>> > Process: 2380 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1 >>> > /dev/null -2 /dev/null /usr/share/vdsm/vdsm (code=exited, >>> > status=1/FAILURE) >>> > Process: 2328 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh >>> > --pre-start (code=exited, status=0/SUCCESS) >>> > >>> >Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Unit >>> >vdsmd.service entered failed state. >>> >Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: vdsmd.service >>> >holdoff time over, scheduling restart. >>> >Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Stopping >>> >Virtual Desktop Server Manager... >>> >Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Starting >>> >Virtual Desktop Server Manager... >>> >Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: vdsmd.service >>> >start request repeated too quickly, refusing to start. > >> what's this . It's the first start of vdsmd! > > > I'm not sure I understand the meaning of this reply :/ Sorry it was for vdsm people. It sorted out that changing owner to vdsm:kvm on /var/log/vdsm/vdsm.log solve the issue. Investigating how owner have been set to root:root on that file. > > Thanks. > -Brad -- 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: [Users] ovirt 3.4 beta on F19: engine-setup error "Failed to execute stage 'Misc configuration': Command '/bin/systemctl' failed to execute"
Il 23/01/2014 16:07, Gianluca Cecchi ha scritto: > On Thu, Jan 23, 2014 at 3:21 PM, Jorick Astrego wrote: >> Yes that's it: >> >> Adding "--otopi-environment="OVESETUP_SYSTEM/shmmax=int:68719476736" " >> works. >> >> I never thought a known issue would crop up so soon, so I just started >> installing. >> >> Thanks >> > > hello, > is it correct to say that if I put something like this in my > /etc/sysctl.d/ovirt-engine.conf > > # cat /etc/sysctl.d/ovirt-engine.conf > > # ovirt-engine configuration. > # Put 200Mb 15/01/14 > kernel.shmmax = 209715200 > > And then > > # systemctl stop ovirt-engine > # systemctl stop postgresql > > # sysctl -p > > # sysctl -a --system | grep shmmax > (to verify new settings) > > # systemctl start postgresql > # systemctl start ovirt-engine > > Then I can run engine-setup without need of putting the env variable any more? if you're on x86_64 you can set it to 68719476736. I've asked kernel peoples and they said that arch limit is a safe value. However, I'm going to have it fixed for 3.3.3 GA and 3.4.0 GA by engine-setup. > At least it worked from me for upgrade to 3.3.3beta1 and 3.3.3rc > > Gianluca > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] Conflicts during enigne install
Il 23/01/2014 16:14, Piotr Kliczewski ha scritto: > As part of test day I wanted to install engine 3.4.0-0.5.beta1.fc20 > from ovirt-3.4.0-prerelease > and I can see following info: > > Transaction check error: > file /usr/lib/python2.7/site-packages/sos/plugins/postgresql.py > conflicts between attempted installs of > ovirt-log-collector-3.4.0-0.1.beta1.fc20.noarch and > sos-3.0-3.fc20.noarch > file /usr/lib/python2.7/site-packages/sos/plugins/postgresql.pyc > conflicts between attempted installs of > ovirt-log-collector-3.4.0-0.1.beta1.fc20.noarch and > sos-3.0-3.fc20.noarch > file /usr/lib/python2.7/site-packages/sos/plugins/postgresql.pyo > conflicts between attempted installs of > ovirt-log-collector-3.4.0-0.1.beta1.fc20.noarch and > sos-3.0-3.fc20.noarc > https://bugzilla.redhat.com/show_bug.cgi?id=1037663 Sorry, F20 is not supported yet. > Thanks, > Piotr > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] [Engine-devel] [ANN] oVirt 3.4.0 Test Day - Tomorrow Jan 23th
Il 22/01/2014 14:07, Sandro Bonazzola ha scritto: > Hi all, > tomorrow Jan 23th we'll have oVirt 3.4.0 test day. Hi all, Just wanted to say a big THANK YOU to all participants! -- 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: [Users] Centos 6.5: mom spam
Il 23/01/2014 22:23, Adam Litke ha scritto:
> On 23/01/14 23:02 +0200, Itamar Heim wrote:
>> On 01/23/2014 08:04 PM, Adam Litke wrote:
>>> On 23/01/14 10:43 -0300, Federico Alberto Sayd wrote:
>>>> On 22/01/14 21:32, Dan Kenigsberg wrote:
>>>>> On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote:
>>>>>> On 22/01/14 12:13, Dan Kenigsberg wrote:
>>>>>
>>>>>
>>>>>> The supervdsm.log whith the lines logged yesterday:
>>>>>>
>>>>>> http://pastebin.com/kpXrRd2w
>>>>>>
>>>>> On an unrelated matter: this log includes
>>>>>
>>>>> MainProcess|PolicyEngine::DEBUG::2014-01-21
>>>>> 13:13:41,187::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper)
>>>>> call
>>>>> ksmTune with ({},) {}
>>>>> MainProcess|PolicyEngine::DEBUG::2014-01-21
>>>>> 13:13:41,188::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper)
>>>>> return ksmTune with None
>>>>> MainProcess|PolicyEngine::DEBUG::2014-01-21
>>>>> 13:13:51,220::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper)
>>>>> call
>>>>> ksmTune with ({},) {}
>>>>> MainProcess|PolicyEngine::DEBUG::2014-01-21
>>>>> 13:13:51,220::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper)
>>>>> return ksmTune with None
>>>>>
>>>>> spam every 10 seconds. Federico, which version of mom do you have
>>>>> installed? I
>>>>> thought we have solved a similar issue in the past.
>>>>>
>>>>>
>>>> mom-0.3.2-6.el6.noarch
>>>
>>> This is the upstream version of mom which (sadly) is far too old and
>>> is missing a bunch of features. For Fedora, we are building master
>>> and releasing versions like mom-0.3.2-20140120.gitfd877c5.fc20 [1]
>>> which have lots of ovirt-specific fixes applied.
>>>
>>> The fix is to have someone rebuild the mom RPM for el6 since the last
>>> refresh happened on August 13 (!). For now, please try to upgrade to
>>> this build of master [2].
>>
>> any reason we don't build it via jenkins to resources.ovirt.org like other
>> rpms?
>
> Yes, because (up until now) the mom build system was not compatible
> with other oVirt projects. That was fixed this week [1] so now we can
> release proper RPMs into the oVirt repositories. Next I want to do a
> MOM version bump and synchronize the official Fedora packages with
> what we have in oVirt.
>
> Any opinion on whether we should adopt the current MOM master (build
> system rewrite) this late in the 3.4 release process? If so, I will
> work with Sandro to make sure that rc1 has it updated. Othewise, we
> can do that for 3.4.1.
3.4.0 beta1 has mom-0.3.2-20140120.gitfd877c5.fc19.noarch.rpm
built by jenkins http://jenkins.ovirt.org/view/Packaging/job/mom_create-rpms/35/
new build system is fine for me, I don't see any technical reason for not
including current MOM master in 3.4.0 RC.
>
>>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
--
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: [Users] Hosted-Engine startup problem
Il 24/01/2014 09:11, Sebastian Classen ha scritto: > Hi, > > we installes ovirt beta with hosted-engine. After Setup was complete the > engine VM reboots and never came up again. It looks like the host is unable > to find the VM. As requested in IRC I attached the relevant logs. > > Please CC me, as I'm not subscribed. It seems like Bug 1055059 - The --vm-start function does not call the createvm command but --vm-start-paused does Suggested workaround is: # hosted-engine --vm-start-paused # virsh resume HostedEngine We're still investigating. > > Greets > Sebastian. > > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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] ovirt-3.3.3 release postponed due to blockers
Hi, oVirt 3.3.3 release need to be postponed. A recent release of python-cpopen-1.3 is breaking dependency resolution on EL6 and F19 so vdsm can't be installed and node can't be composed. A recent change in vdsm-python-cpopen added the needed conflict against python-cpopen and removed Provides / Obsoletes on python-cpopen. But no new releases of python-cpopen is available fixing the correct Provides / Obsoletes pair. oVirt 3.3.2 / stable is affected too. Please fix Bug 1056470 - python-cpopen-1.3 is not providing obsoleted package. Bug 1056464 - python-cpopen-1.3 is not providing obsoleted package. ASAP. -- 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: [Users] ovirt-3.3.3 release postponed due to blockers
Il 28/01/2014 14:26, Sven Kieske ha scritto: > Hi, > > I do not see any Bug tracking this behaviour on EL6. > Is there none needed or will this not get resolved for EL6? the rpm built for Fedora is the same build for EPEL so I think it may be enough having the one opened against Fedora. > Is there a known workaround? You can manually install vdsm-python-cpopen, this will introduce conflict on python-cpopen which shouldn't be pulled in anymore > > I already asked this in a different BZ, I think: > > Is the "full blown host" node install for EL6 > also affected? Fabian? > > I did not get any reply to this question. > > I hope someone can share some light on this. > > Thank you. > > Am 28.01.2014 13:55, schrieb Sandro Bonazzola: >> Hi, >> oVirt 3.3.3 release need to be postponed. >> A recent release of python-cpopen-1.3 is breaking dependency resolution on >> EL6 and F19 so vdsm can't be installed and node can't be composed. >> A recent change in vdsm-python-cpopen added the needed conflict against >> python-cpopen and removed Provides / Obsoletes on python-cpopen. >> But no new releases of python-cpopen is available fixing the correct >> Provides / Obsoletes pair. >> >> oVirt 3.3.2 / stable is affected too. >> >> Please fix >> Bug 1056470 - python-cpopen-1.3 is not providing obsoleted package. >> Bug 1056464 - python-cpopen-1.3 is not providing obsoleted package. >> ASAP. >> >> > -- 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: [Users] ovirt-3.3.3 release postponed due to blockers
Il 29/01/2014 09:21, Sven Kieske ha scritto: > Hi, > > I wanted to try it the other way around, installing vdsm-python-cpopen > and check if it runs without python-cpopen . > > But that leads me to a question: > > Is there any difference between these packages beside their different > name? > > If yes, what is the difference and which package should be installed? > I no, why is there a packet vdsm-python-cpopen ? CCing VDSM > > Thank you! > > > Am 28.01.2014 20:14, schrieb Trey Dockendorf: >> I found manually installing python-cpopen before adding a node in the >> engine is a viable workaround. This was on EL6.5 >> >> - Trey > -- 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: [Users] ovirt-3.3.3 release postponed due to blockers
Il 30/01/2014 10:20, Dan Kenigsberg ha scritto: > On Thu, Jan 30, 2014 at 08:52:36AM +, Sven Kieske wrote: >> Hi, >> >> any news regarding my questions? >> >> Am 29.01.2014 09:23, schrieb Sandro Bonazzola: >>> Il 29/01/2014 09:21, Sven Kieske ha scritto: >>>> Hi, >>>> >>>> I wanted to try it the other way around, installing vdsm-python-cpopen >>>> and check if it runs without python-cpopen . >>>> >>>> But that leads me to a question: >>>> >>>> Is there any difference between these packages beside their different >>>> name? >>>> >>>> If yes, what is the difference and which package should be installed? >>>> I no, why is there a packet vdsm-python-cpopen ? >>> >>> CCing VDSM > > python-cpopen includes some improvements and bug fixes, that are going > to be needed in ovirt-3.4. vdsm-python-cpopen is shipped by ovirt-3.3. > > python-cpopen wast intended to deprecate and replace vdsm-python-cpopen, > but we have had way too many issues trying to do that properly in > rpm/yum. Most of the bugs are ours, at least one is yum's. > > At the moment, the existence of python-cpopen in Fedora confuses `yum > install vdsm`. > > To avoid this unfortunate delay, we can either include python-cpopen in > ovirt-stable or exclude vdsm-python-cpopen from there. Both options are > unfavorable, but so is continuing to wait. If it's enough just to add python-cpopen to ovirt-stable, I'm fine with that. I just need the link to the build to be included there. > > Regards, > Dan. > -- 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: [Users] ovirt-3.3.3 release postponed due to blockers
Il 30/01/2014 16:13, Yaniv Bronheim ha scritto: > Hey, > > we found this yum bug and still struggling with more issuing according to the > relation between those packages > > if we drop vdsm-python-cpopen the requirement in vdsm takes python-cpopen > instead. > in python-cpopen we have the same code base and it provides all > vdsm-ptyhon-cpopen provides, so shouldn't be any issues with dropping it from > the repository > > is it possible to ship 3.3.3 release that way ? we don't need to change the > requirement in the code, if python-cpopen 1.3-1 is part of the release, it > will be taken by vdsm spec (tried with vdsm 4.13.3-2 with the available > cpopen 1.3-1) > I can't release 3.3.3 that way. We're keeping rolling releases on stable repository so if I don't provide 4.13.3-2, previous one will still be available. > Sven, for your question, install python-cpopen 1.3-1 for both 3.3 and 3.4 > releases that you use, and the upgrade\downgrade should not raise any > dependencies issues afaic > > Yaniv Bronhaim. > > > > - Original Message - >> From: "Dan Kenigsberg" >> To: "Sandro Bonazzola" , ybron...@redhat.com >> Cc: "Sven Kieske" , "Trey Dockendorf" >> , "users" , "VDSM >> Project Development" >> Sent: Thursday, January 30, 2014 4:02:13 PM >> Subject: Re: [Users] ovirt-3.3.3 release postponed due to blockers >> >> On Thu, Jan 30, 2014 at 10:27:34AM +0100, Sandro Bonazzola wrote: >>> Il 30/01/2014 10:20, Dan Kenigsberg ha scritto: >>>> On Thu, Jan 30, 2014 at 08:52:36AM +, Sven Kieske wrote: >>>>> Hi, >>>>> >>>>> any news regarding my questions? >>>>> >>>>> Am 29.01.2014 09:23, schrieb Sandro Bonazzola: >>>>>> Il 29/01/2014 09:21, Sven Kieske ha scritto: >>>>>>> Hi, >>>>>>> >>>>>>> I wanted to try it the other way around, installing vdsm-python-cpopen >>>>>>> and check if it runs without python-cpopen . >>>>>>> >>>>>>> But that leads me to a question: >>>>>>> >>>>>>> Is there any difference between these packages beside their different >>>>>>> name? >>>>>>> >>>>>>> If yes, what is the difference and which package should be installed? >>>>>>> I no, why is there a packet vdsm-python-cpopen ? >>>>>> >>>>>> CCing VDSM >>>> >>>> python-cpopen includes some improvements and bug fixes, that are going >>>> to be needed in ovirt-3.4. vdsm-python-cpopen is shipped by ovirt-3.3. >>>> >>>> python-cpopen wast intended to deprecate and replace vdsm-python-cpopen, >>>> but we have had way too many issues trying to do that properly in >>>> rpm/yum. Most of the bugs are ours, at least one is yum's. >>>> >>>> At the moment, the existence of python-cpopen in Fedora confuses `yum >>>> install vdsm`. >>>> >>>> To avoid this unfortunate delay, we can either include python-cpopen in >>>> ovirt-stable or exclude vdsm-python-cpopen from there. Both options are >>>> unfavorable, but so is continuing to wait. >>> >>> If it's enough just to add python-cpopen to ovirt-stable, I'm fine with >>> that. >>> I just need the link to the build to be included there. >> >> Yaniv, have you tried if shipping python-cpopen hides this issue? >> >> http://kojipkgs.fedoraproject.org//packages/python-cpopen/1.3/1.fc20/x86_64/python-cpopen-1.3-1.fc20.x86_64.rpm >> http://kojipkgs.fedoraproject.org//packages/python-cpopen/1.3/1.fc19/x86_64/python-cpopen-1.3-1.fc19.x86_64.rpm >> http://kojipkgs.fedoraproject.org//packages/python-cpopen/1.3/1.el6/ppc64/python-cpopen-1.3-1.el6.ppc64.rpm >> >> Dropping vdsm-python-cpopen from a stable version seems impolite, but >> should work, too. >> -- 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: [Users] ovirt-3.3.3 release postponed due to blockers
Il 30/01/2014 22:38, Robert Story ha scritto: > Can we revert these packages to previous versions in the 3.3.2 stable repo > so those of us who want/need to install new hosts in our clusters aren't > dead in the water waiting for 3.3.3? Hi Robert, I think you can still install 3.3.2 on your clusters with the requirement of adding manually oython-cpopen before trying to install vdsm. About 3.3.3, I think vdsm should really drop dependency on vdsm-python-cpopen: it's a package obsoleted by python-cpopen so there's no point in still requiring it especially if keeping that requirement still break dependency resolution. > > On Thu, 30 Jan 2014 16:26:51 +0100 Sandro wrote: > SB> Il 30/01/2014 16:13, Yaniv Bronheim ha scritto: > SB> > Hey, > SB> > > SB> > we found this yum bug and still struggling with more issuing > SB> > according to the relation between those packages > SB> > > SB> > if we drop vdsm-python-cpopen the requirement in vdsm takes > SB> > python-cpopen instead. in python-cpopen we have the same code base > SB> > and it provides all vdsm-ptyhon-cpopen provides, so shouldn't be any > SB> > issues with dropping it from the repository > SB> > > SB> > is it possible to ship 3.3.3 release that way ? we don't need to > SB> > change the requirement in the code, if python-cpopen 1.3-1 is part of > SB> > the release, it will be taken by vdsm spec (tried with vdsm 4.13.3-2 > SB> > with the available cpopen 1.3-1) > SB> > > SB> > SB> I can't release 3.3.3 that way. > SB> We're keeping rolling releases on stable repository so if I don't > SB> provide 4.13.3-2, previous one will still be available. > > > Robert > > -- > Senior Software Engineer @ Parsons > -- 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: [Users] ovirt-3.3.3 release postponed due to blockers
Il 31/01/2014 11:17, Dan Kenigsberg ha scritto: > On Fri, Jan 31, 2014 at 09:36:48AM +0100, Sandro Bonazzola wrote: >> Il 30/01/2014 22:38, Robert Story ha scritto: >>> Can we revert these packages to previous versions in the 3.3.2 stable repo >>> so those of us who want/need to install new hosts in our clusters aren't >>> dead in the water waiting for 3.3.3? >> >> Hi Robert, I think you can still install 3.3.2 on your clusters with the >> requirement of adding >> manually oython-cpopen before trying to install vdsm. >> >> About 3.3.3, I think vdsm should really drop dependency on >> vdsm-python-cpopen: >> it's a package obsoleted by python-cpopen so there's no point in still >> requiring it especially if keeping that requirement still break dependency >> resolution. > > I really wanted to avoid eliminating a subpackage during a micro > release. That's impolite and surprising. I'm not telling you to not provide vdsm-python-cpopen while you build vdsm. I'm telling you to not require it. You can still build it and let it to be unused. Just treat vdsm-python-cpopen as something not provided anymore by the distro while python-cpopen is the new one replacing it. > But given the awkward yum bug, persistent dependency problems, and > the current release delay, I give up. > > Let's eliminate vdsm-python-cpopen from ovirt-3.3 branch, and require > python-cpopen. Yaniv, Douglas: could you handle it? > -- 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: [Users] ovirt-3.3.3 release postponed due to blockers
Il 02/02/2014 00:05, Dan Kenigsberg ha scritto: > On Fri, Jan 31, 2014 at 04:16:54PM -0500, Douglas Schilling Landgraf wrote: >> On 01/31/2014 05:17 AM, Dan Kenigsberg wrote: >>> On Fri, Jan 31, 2014 at 09:36:48AM +0100, Sandro Bonazzola wrote: >>>> Il 30/01/2014 22:38, Robert Story ha scritto: >>>>> Can we revert these packages to previous versions in the 3.3.2 stable repo >>>>> so those of us who want/need to install new hosts in our clusters aren't >>>>> dead in the water waiting for 3.3.3? >>>> >>>> Hi Robert, I think you can still install 3.3.2 on your clusters with the >>>> requirement of adding >>>> manually oython-cpopen before trying to install vdsm. >>>> >>>> About 3.3.3, I think vdsm should really drop dependency on >>>> vdsm-python-cpopen: >>>> it's a package obsoleted by python-cpopen so there's no point in still >>>> requiring it especially if keeping that requirement still break dependency >>>> resolution. >>> >>> I really wanted to avoid eliminating a subpackage during a micro >>> release. That's impolite and surprising. >>> But given the awkward yum bug, persistent dependency problems, and >>> the current release delay, I give up. >>> >>> Let's eliminate vdsm-python-cpopen from ovirt-3.3 branch, and require >>> python-cpopen. Yaniv, Douglas: could you handle it? >>> >> >> Sure. Done: http://gerrit.ovirt.org/#/c/23942/ > > Acked. Could you cherry-pick it into dist-git and rebuild the > ovirt-3.3.3 candidate (and without other changes that can wait for > ovirt-3.3.4). > Let me know where I can get the new rpms, so I can add them to 3.3.3 repo and release :-) -- 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] oVirt 3.3.3 release
The oVirt development team is very happy to announce the general availability of oVirt 3.3.3 as of February 3rd 2013. This release solidifies oVirt as a leading KVM management application and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5 (or similar). This release of oVirt includes numerous bug fixes. See the release notes [1] for a list of the new features and bugs fixed. IMPORTANT NOTE: If you're upgrading from a previous version, please update ovirt-release to the latest version (10.0.1-3) and verify you have the correct repositories enabled by running the following commands # yum update ovirt-release # yum repolist enabled before upgrading with the usual procedure. You should see the ovirt-3.3.3 and ovirt-stable repositories listed in the output of the repolist command. A new oVirt Node build will be available soon as well. [1] 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] [QE] oVirt 3.4.0 beta status
Hi, oVirt 3.4.0 beta has been released and is actually on QA. We're going to tart composing oVirt 3.4.0 beta2 this Thursday 2014-02-06 09:00 UTC from 3.4 branches. This build will be used for a second Test Day scheduled for 2014-02-11. The bug tracker [1] shows the following bugs blocking the release: Whiteboard Bug ID Status Summary gluster 1038988 POSTGluster brick sync does not work when host has multiple interfaces gluster 1059606 POSTErrors in rebalance and remove-brick status and sync integration 1054080 POSTgracefully warn about unsupported upgrade from legacy releases integration 1058018 POSTupgrade from 3.3 overwrites exports with acl None There are still 393 bugs [2] targeted to 3.4.0. Excluding node and documentation bugs we still have 238 bugs [3] targeted to 3.4.0. Please review them as soon as possible. Maintainers: - Please remember to rebuild your packages before 2014-02-06 09:00 UTC if you want them to be included in 3.4.0 beta. - Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed. - Please provide ETA on blockers bugs - Please update the target to 3.4.1 or any next release for bugs that won't be in 3.4.0: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] - Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-02-11 For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug. Please also be prepared for upcoming oVirt 3.4.0 Test Day on 2014-02-11! Thanks to all people already testing 3.4.0 beta! [1] https://bugzilla.redhat.com/1024889 [2] http://red.ht/1eIRZXM [3] http://red.ht/1auBU3r [4] http://www.ovirt.org/OVirt_3.4.0_release_notes -- 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: [Users] [QE] oVirt 3.4.0 beta status
Il 04/02/2014 13:30, Gianluca Cecchi ha scritto: > On Tue, Feb 4, 2014 at 1:03 PM, Sandro Bonazzola wrote: >> Hi, >> oVirt 3.4.0 beta has been released and is actually on QA. >> We're going to tart composing oVirt 3.4.0 beta2 this Thursday 2014-02-06 >> 09:00 UTC from 3.4 branches. >> This build will be used for a second Test Day scheduled for 2014-02-11. > > Is beta2 expected to be available to run on Fedora 20, engine and hosts? I don't think so. I've opened a tracker for F20 support related issues here: https://bugzilla.redhat.com/show_bug.cgi?id=1060198 > Thanks, > Gianluca > -- 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: [Users] ovirt engine and vdsm on same node
Il 05/02/2014 09:18, Hans Emmanuel ha scritto: > Can we install ovirt engine and vdsm on same node ? Sure, you can use all-in-one plugin for having both running on the same node. In 3.4.0 you'll be able also to run ovirt engine inside a VM using hosted-engine feature. > If so any down side ? You'll have less resources available for VMs on the host running the engine. > > -- > *Hans Emmanuel* > > /NOthing to FEAR but something to FEEL../ > > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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] [ANN] oVirt 3.4.0 beta2 is now available
The oVirt team is pleased to announce that the 3.4.0 second beta release is now available 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. The existing repository ovirt-3.4.0-prerelease has been updated 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 next week test day [2] scheduled for 2014-02-11! [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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [ANN] oVirt 3.4.0 beta2 is now available
Il 07/02/2014 18:01, Markus Stockhausen ha scritto: >> Von: users-boun...@ovirt.org [users-boun...@ovirt.org]" im Auftrag von >> "Sandro Bonazzola [sbona...@redhat.com] >> Gesendet: Freitag, 7. Februar 2014 11:36 >> An: annou...@ovirt.org; Users@ovirt.org; engine-devel; arch; VDSM Project >> Development >> Betreff: [Users] [ANN] oVirt 3.4.0 beta2 is now available >> >> The oVirt team is pleased to announce that the 3.4.0 second beta release is >> now available 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. >> The existing repository ovirt-3.4.0-prerelease has been updated 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 next week test day >> [2] scheduled for 2014-02-11! >> >> >> [1] http://www.ovirt.org/OVirt_3.4.0_release_notes >> [2] http://www.ovirt.org/OVirt_3.4_Test_Day >> >> -- >> Sandro Bonazzola > > Hello Sandro, > > may I politely ask to set BZ 1062615 for target release 3.4.0 - and as a > blocker too? Hi, The VDSM maintainer has targeted BZ 1062615 for 3.4.1 so it has not been considered as blocker for 3.4.0. Dan, any chance of having this fixed in 3.4.0? > Dan's information suggest that it is still existent in 3.4.0 beta2. Maybe > someone can > proove it in a beta environment too and update the bug. > > It seems as if Ovirt does not remember timezone/clock settings of a Windows > VM. > As a side effect a VM may always come up with a predefined time gap until the > the ntp client wil fix the time. If that gap is too large we could suffer > from some > unwanted side effects > > - ntp time sync may not work because of too high gap > - kerberos authentication may fail because of too high gap > > Markus > -- 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] [ANN] oVirt 3.4.0 beta 2 Test Day - Today Feb 11th
Hi all, today Feb 11th we have oVirt 3.4.0 beta 2 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 for running the engine due to various issues (sos, jboss) but may be used as hypervisor. Latest RPMs repository to be enabled for testing the release are listed in the release notes page [2]. Note: on Fedora you'll need to enable fedora-virt-preview repository for getting latest libvirt rpms. Note: on EL6 you'll need to enable EPEL repository. 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-2 [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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [ANN] oVirt 3.4.0 beta 2 Test Day - Today Feb 11th
Il 11/02/2014 09:12, Justin Clacherty ha scritto: > Have the release notes been updated for beta 2? It's not immediately obvious > from reading the release notes that they are in reference to beta 2 and not > beta 1. I've just updated release notes page to make it clear they reference second beta. > I ask because some of the known issues here were present last test day. Yes and sadly some of the known issues are not fixed yet. Known issues EL >= 6.5 or cloud-init >= 0.7.2 are needed for cloud-init feature support (BZ 1029885) all-in-one requiures fedora-virt-preview repo as in the next item For using Fedora 19 as node on 3.4 clusters you need to enable fedora-virt-preview repository (BZ 1056918) Node Needs to be booted in permissive mode by appending: enforcing=0 engine-setup: upgrade from 3.3 overwrites exports with acl None (BZ 1058018) > > Cheers, > Justin. > > > From: users-boun...@ovirt.org [users-boun...@ovirt.org] on behalf of Sandro > Bonazzola [sbona...@redhat.com] > Sent: Tuesday, 11 February 2014 6:01 PM > To: Users@ovirt.org > Subject: [Users] [ANN] oVirt 3.4.0 beta 2 Test Day - Today Feb 11th > > Hi all, > today Feb 11th we have oVirt 3.4.0 beta 2 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 for running the engine due > to various issues (sos, jboss) but may be used as hypervisor. > > > Latest RPMs > repository to be enabled for testing the release are listed in the > release notes page [2]. > Note: on Fedora you'll need to enable fedora-virt-preview repository for > getting latest libvirt rpms. > Note: on EL6 you'll need to enable EPEL repository. > > 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-2 > [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 > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] [ANN] oVirt 3.4.0 beta 2 Test Day - Today Feb 11th
Il 11/02/2014 11:07, Justin Clacherty ha scritto: > The link to the Node ISO on http://www.ovirt.org/OVirt_3.4_TestDay is down. > Do you have the correct link? Updated with latest available Node ISO. Fabian, if you're going to resping it please announce it here and update test day page. > > -Original Message----- > From: Sandro Bonazzola [mailto:sbona...@redhat.com] > Sent: Tuesday, 11 February 2014 6:33 PM > To: Justin Clacherty; Users@ovirt.org > Subject: Re: [Users] [ANN] oVirt 3.4.0 beta 2 Test Day - Today Feb 11th > > Il 11/02/2014 09:12, Justin Clacherty ha scritto: >> Have the release notes been updated for beta 2? It's not immediately >> obvious from reading the release notes that they are in reference to beta 2 >> and not beta 1. > > I've just updated release notes page to make it clear they reference second > beta. > > >> I ask because some of the known issues here were present last test day. > > Yes and sadly some of the known issues are not fixed yet. > > > Known issues > EL >= 6.5 or cloud-init >= 0.7.2 are needed for cloud-init feature > support (BZ 1029885) > all-in-one requiures fedora-virt-preview repo as in the next item > For using Fedora 19 as node on 3.4 clusters you need to enable > fedora-virt-preview repository (BZ 1056918) > Node > Needs to be booted in permissive mode by appending: enforcing=0 > engine-setup: upgrade from 3.3 overwrites exports with acl None (BZ > 1058018) > >> >> Cheers, >> Justin. >> >> >> From: users-boun...@ovirt.org [users-boun...@ovirt.org] on behalf of >> Sandro Bonazzola [sbona...@redhat.com] >> Sent: Tuesday, 11 February 2014 6:01 PM >> To: Users@ovirt.org >> Subject: [Users] [ANN] oVirt 3.4.0 beta 2 Test Day - Today Feb 11th >> >> Hi all, >> today Feb 11th we have oVirt 3.4.0 beta 2 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 for running the engine due >> to various issues (sos, jboss) but may be used as hypervisor. >> >> >> Latest RPMs >> repository to be enabled for testing the release are listed in the >> release notes page [2]. >> Note: on Fedora you'll need to enable fedora-virt-preview repository for >> getting latest libvirt rpms. >> Note: on EL6 you'll need to enable EPEL repository. >> >> 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-2 >> [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 >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > -- 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] ERRORS and WARNINGS in engine.log on a just started system
Installed 3.3.3 all-in-one
upgraded to 3.4.0 beta2
created a VM
stopped the engine.
cleaned logs.
started the engine:
engine.log:2014-02-11 13:35:19,573 ERROR
[org.ovirt.engine.core.dal.dbbroker.generic.DBConfigUtils] (MSC service thread
1-1) Could not parse option
AutoRecoveryAllowedTypes value.
engine.log:2014-02-11 13:36:03,344 ERROR
[org.ovirt.engine.core.utils.servlet.ServletUtils] (ajp--127.0.0.1-8702-2)
Can't read file
"/var/lib/ovirt-engine/reports.xml" for request
"/ovirt-engine/services/reports-ui", will send a 404 error response.
I don't have DWH or reports here.
# grep WARN engine.log server.log |wc -l
178
Warnings are like:
server.log:2014-02-11 13:35:18,914 WARN [org.jboss.as.dependency.private] (MSC
service thread 1-9) JBAS018567: Deployment
"deployment.engine.ear.restapi.war" is using a private module
("org.yaml.snakeyaml:main") which may be changed or removed in future versions
without
notice.
server.log:2014-02-11 13:35:18,915 WARN [org.jboss.as.dependency.private] (MSC
service thread 1-6) JBAS018567: Deployment
"deployment.engine.ear.webadmin.war" is using a private module
("org.codehaus.jackson.jackson-xc:main") which may be changed or removed in
future
versions without notice.
Can't we get rid of those?
--
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] oVirt upcoming release schedule update
oVirt team has updated the release schedule for upcoming releases. These are tentative planning dates and may change. 2014-02-17 - oVirt 3.4.0 RC Build 2014-02-18 - oVirt 3.3.4 beta 2014-02-19 - oVirt 3.4 Third Test Day 2014-02-24 - oVirt 3.4.0 GA 2014-02-25 - oVirt 3.3.4 RC 2014-03-04 - oVirt 3.3.4 GA 2014-05-01 - oVirt 3.5.0 Feature Freeze 2014-05-15 - oVirt 3.5.0 stable branching 2014-06-10 - oVirt 3.5.0 GA More details on test days, etc to come in the next few weeks. You'll find an updated ICS calendar attached to this email. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com BEGIN:VCALENDAR PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN VERSION:2.0 BEGIN:VEVENT CREATED:20140109T085926Z LAST-MODIFIED:20140109T090007Z DTSTAMP:20140109T090007Z UID:aa67201d-432b-486b-b384-3084b51ee12a SUMMARY:oVirt 3.4.0 GA DTSTART;VALUE=DATE:20140224 DTEND;VALUE=DATE:20140225 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090058Z LAST-MODIFIED:20140109T090110Z DTSTAMP:20140109T090110Z UID:ff9b1509-1db8-4af5-bb5c-900a739401cc SUMMARY:oVirt 3.4.0 RC Build DTSTART;VALUE=DATE:20140217 DTEND;VALUE=DATE:20140218 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090212Z LAST-MODIFIED:20140109T090223Z DTSTAMP:20140109T090223Z UID:873d0069-630b-40a5-ba5a-5728153fc12c SUMMARY:oVrit 3.4.0 Beta release DTSTART;VALUE=DATE:20140120 DTEND;VALUE=DATE:20140121 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090322Z LAST-MODIFIED:20140109T090335Z DTSTAMP:20140109T090335Z UID:869db415-7ab8-4a5e-b5f4-529e87924e89 SUMMARY:oVirt 3.4.0 Branching / Feature freeze DTSTART;VALUE=DATE:20140115 DTEND;VALUE=DATE:20140116 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090359Z LAST-MODIFIED:20140109T090410Z DTSTAMP:20140109T090410Z UID:d3acbe18-57c5-4fe4-9021-20991249d08b SUMMARY:oVirt 3.3.3 GA DTSTART;VALUE=DATE:20140128 DTEND;VALUE=DATE:20140129 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090427Z LAST-MODIFIED:20140109T090438Z DTSTAMP:20140109T090438Z UID:e420a328-285b-418f-b4d5-2c98bd5ea84f SUMMARY:oVirt 3.3.3 RC DTSTART;VALUE=DATE:20140121 DTEND;VALUE=DATE:20140122 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090454Z LAST-MODIFIED:20140109T090504Z DTSTAMP:20140109T090504Z UID:7f9addb5-3a9a-47b4-a0ab-228d59f6cc01 SUMMARY:oVirt 3.3.3 beta DTSTART;VALUE=DATE:20140113 DTEND;VALUE=DATE:20140114 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090129Z LAST-MODIFIED:20140109T141806Z DTSTAMP:20140109T141806Z UID:694ba717-4fb0-467b-929f-f9192679b92b SUMMARY:oVirt 3.4 Test Day DTSTART;VALUE=DATE:20140123 DTEND;VALUE=DATE:20140124 TRANSP:TRANSPARENT SEQUENCE:1 X-MOZ-GENERATION:1 END:VEVENT BEGIN:VEVENT CREATED:20140109T090254Z LAST-MODIFIED:20140110T120011Z DTSTAMP:20140110T120011Z UID:07afe210-61a1-4113-9020-2735aefc7467 SUMMARY:oVirt 3.4.0 Alpha release DTSTART;VALUE=DATE:20140113 DTEND;VALUE=DATE:20140114 TRANSP:TRANSPARENT SEQUENCE:1 X-MOZ-GENERATION:1 END:VEVENT BEGIN:VEVENT CREATED:20140109T090034Z LAST-MODIFIED:20140207T162345Z DTSTAMP:20140207T162345Z UID:f9d8197e-c3c1-4044-9127-fcdfc1dc1aaf SUMMARY:oVirt 3.4 Third Test Day DTSTART;VALUE=DATE:20140219 DTEND;VALUE=DATE:20140220 TRANSP:TRANSPARENT X-MOZ-GENERATION:1 END:VEVENT BEGIN:VEVENT CREATED:20140207T162249Z LAST-MODIFIED:20140212T152724Z DTSTAMP:20140212T152724Z UID:d84f83fe-7039-4c00-b4e1-432340f92764 SUMMARY:oVirt 3.4 Second Test day DTSTART;VALUE=DATE:20140211 DTEND;VALUE=DATE:20140212 SEQUENCE:1 X-MOZ-GENERATION:2 END:VEVENT BEGIN:VEVENT CREATED:20140212T152742Z LAST-MODIFIED:20140212T152757Z DTSTAMP:20140212T152757Z UID:49de31f1-9023-432c-9505-853601988a4f SUMMARY:oVirt 3.4.0 beta2 release DTSTART;VALUE=DATE:20140207 DTEND;VALUE=DATE:20140208 TRANSP:TRANSPARENT SEQUENCE:1 X-MOZ-GENERATION:1 END:VEVENT BEGIN:VEVENT CREATED:20140212T152830Z LAST-MODIFIED:20140212T152845Z DTSTAMP:20140212T152845Z UID:5a55b509-477a-46de-89d8-4ba60429f0bd SUMMARY:oVirt 3.3.4 beta DTSTART;VALUE=DATE:20140218 DTEND;VALUE=DATE:20140219 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140212T152849Z LAST-MODIFIED:20140212T152907Z DTSTAMP:20140212T152907Z UID:c7aa12cb-a0d8-4e07-8296-f00de68209ba SUMMARY:oVirt 3.3.4 RC DTSTART;VALUE=DATE:20140225 DTEND;VALUE=DATE:20140226 TRANSP:TRANSPARENT SEQUENCE:1 X-MOZ-GENERATION:1 END:VEVENT BEGIN:VEVENT CREATED:20140212T152914Z LAST-MODIFIED:20140212T152922Z DTSTAMP:20140212T152922Z UID:43e50b92-251e-4749-b069-91b5f2f6792b SUMMARY:oVirt 3.3.4 GA DTSTART;VALUE=DATE:20140304 DTEND;VALUE=DATE:20140305 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140212T160339Z LAST-MODIFIED:20140212T160352Z DTSTAMP:20140212T160352Z UID:1c5a82fe-1c6f-474b-b152-134c5ee418e3 SUMMARY:oVirt 3.5.0 Feature Freeze DTSTART;VALUE=DATE:20140501 DTEND;VALUE=DATE:20140502 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140212T160417Z LAST-MODIFIED:20140212T160423Z DTSTAMP:20140212T160423Z UID:2be0ee2c
Re: [Users] ovirt test day 2
Il 13/02/2014 02:44, Yair Zaslavsky ha scritto: > > Hi, > I tested the following: > > https://bugzilla.redhat.com/1053646easily collapsible left-pane - was > not included in test day 1 (I was supposed to test it back then) - works fine. > > https://bugzilla.redhat.com/1054209 - read only disks - works fine. Can you move above bugs to verified and add yourself as QA contact then? Thanks. > > https://bugzilla.redhat.com/1054219 - Only comment is - IMHO it should be > considered having disks marked as read only (where applicable) in templates > -> disks and perhaps also when showing the disks of each snapshot. > > other bugs opened: > https://bugzilla.redhat.com/show_bug.cgi?id=1064601 > > > Yair > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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] [QE] oVirt 3.3.4 beta status
Hi, we're going to branch and build oVirt 3.3.4 beta on Tue 2014-02-18 09:00 UTC. Repository composition will follow as soon as all packages will be built. A bug tracker is available at [1] and it shows no bugs blocking the release The following is a list of the non-blocking bugs still open with target 3.3.4: Whiteboard Bug ID Summary infra 1053576 [abrt] vdsm-python: libvirt.py:102:openAuth:libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock'... integration 1026930 Package virtio-win and put it in ovirt repositories integration 1026933 pre-populate ISO domain with virtio-win ISO network 997197 Some AppErrors messages are grammatically incorrect (singular vs plural) network 1064489 do not report negative rx/tx rate when Linux counters wrap node923049 ovirt-node fails to boot from local disk under UEFI mode node965583 [RFE] add shortcut key on TUI node976675 [wiki] Update contribution page node979350 Changes admin password in the first time when log in is failed while finished auto-install node979390 [RFE] Split defaults.py into smaller pieces node982232 performance page takes >1sec to load (on first load) node984441 kdump page crashed before configuring the network after ovirt-node intalled node986285 UI crashes when no bond name is given node991267 [RFE] Add TUI information to log file. node1018374 ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19: Failed on Auto-install node1018710 [RFE] Enhance API documentation node1032035 [RFE]re-write auto install function for the cim plugin node1033286 ovirt-node-plugin-vdsm can not be added to ovirt node el6 base image storage 987917 [oVirt] [glance] API version not specified in provider dialog virt1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain Maintainers / Assignee: Please add the bugs to the tracker if you think that 3.3.4 should not be released without them fixed. Please re-target all bugs you don't think that should block 3.3.4. For those who want to help testing the bugs, I suggest to add yourself to the testing page [2]. Maintainers are welcomed to start filling release notes, the page has been created here [3] [1] http://bugzilla.redhat.com/1064462 [2] http://www.ovirt.org/Testing/Ovirt_3.3.4_testing [3] http://www.ovirt.org/OVirt_3.3.4_release_notes 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] [QE] oVirt 3.4.0 RC status
Hi, oVirt 3.4.0 beta2 has been released and is actually on QA. We're going to tart composing oVirt 3.4.0 RC this Monday 2014-02-17 09:00 UTC from 3.4 branches. This build will be used for a third Test Day scheduled for Wed 2014-02-19. The bug tracker [1] shows the following bugs blocking the release: Whiteboard Bug ID Status Summary integration 1058018 POSTupgrade from 3.3 overwrites exports with acl None storage 1057761 NEW Can't discover iSCSI target virt1062615 POSTutc_diff not updated according to a change in VM settings There are still 376 bugs [2] targeted to 3.4.0. Excluding node and documentation bugs we still have 252 bugs [3] targeted to 3.4.0. Please review them as soon as possible. Maintainers / Assignee: - Please remember to rebuild your packages before 2014-02-17 09:00 UTC if you want them to be included in 3.4.0 RC. - Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed. - Please provide ETA on blockers bugs - Please update the target to 3.4.1 or any next release for bugs that won't be in 3.4.0: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] - Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-02-19 Be prepared for upcoming oVirt 3.4.0 Test Day on 2014-02-19! Thanks to all people already testing 3.4.0 beta 2! [1] https://bugzilla.redhat.com/1024889 [2] http://red.ht/1eIRZXM [3] http://red.ht/1auBU3r [4] http://www.ovirt.org/OVirt_3.4.0_release_notes -- 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] Postponing 3.4.0 RC and test day
Hi, we're postponing 3.4.0 RC build and test day to next week due to recent blockers opened on 3.4.0. We actually have bug count 361 out of which 19 urgent, 64 high. We're going to build a 3.4.0 beta3 later today once Bug 1066466 - Disk name doesn't get assigned automatically after a CREATE command. will be fixed. -- 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] oVirt upcoming release schedule update
oVirt team has updated the release schedule for upcoming releases. These are tentative planning dates and may change. 2014-02-18 - oVirt 3.4.0 beta3 2014-02-18 - oVirt 3.3.4 beta 2014-02-24 - oVirt 3.4.0 RC Build 2014-02-25 - oVirt 3.3.4 RC 2014-02-27 - oVirt 3.4 Third Test Day 2014-03-03 - oVirt 3.4.0 GA 2014-03-04 - oVirt 3.3.4 GA 2014-05-01 - oVirt 3.5.0 Feature Freeze 2014-05-15 - oVirt 3.5.0 stable branching 2014-07-01 - oVirt 3.5.0 GA More details on test days, etc to come in the next few weeks. You'll find an updated ICS calendar attached to this email. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com BEGIN:VCALENDAR PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN VERSION:2.0 BEGIN:VEVENT CREATED:20140109T090212Z LAST-MODIFIED:20140109T090223Z DTSTAMP:20140109T090223Z UID:873d0069-630b-40a5-ba5a-5728153fc12c SUMMARY:oVrit 3.4.0 Beta release DTSTART;VALUE=DATE:20140120 DTEND;VALUE=DATE:20140121 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090322Z LAST-MODIFIED:20140109T090335Z DTSTAMP:20140109T090335Z UID:869db415-7ab8-4a5e-b5f4-529e87924e89 SUMMARY:oVirt 3.4.0 Branching / Feature freeze DTSTART;VALUE=DATE:20140115 DTEND;VALUE=DATE:20140116 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090359Z LAST-MODIFIED:20140109T090410Z DTSTAMP:20140109T090410Z UID:d3acbe18-57c5-4fe4-9021-20991249d08b SUMMARY:oVirt 3.3.3 GA DTSTART;VALUE=DATE:20140128 DTEND;VALUE=DATE:20140129 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090427Z LAST-MODIFIED:20140109T090438Z DTSTAMP:20140109T090438Z UID:e420a328-285b-418f-b4d5-2c98bd5ea84f SUMMARY:oVirt 3.3.3 RC DTSTART;VALUE=DATE:20140121 DTEND;VALUE=DATE:20140122 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090454Z LAST-MODIFIED:20140109T090504Z DTSTAMP:20140109T090504Z UID:7f9addb5-3a9a-47b4-a0ab-228d59f6cc01 SUMMARY:oVirt 3.3.3 beta DTSTART;VALUE=DATE:20140113 DTEND;VALUE=DATE:20140114 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T090129Z LAST-MODIFIED:20140109T141806Z DTSTAMP:20140109T141806Z UID:694ba717-4fb0-467b-929f-f9192679b92b SUMMARY:oVirt 3.4 Test Day DTSTART;VALUE=DATE:20140123 DTEND;VALUE=DATE:20140124 TRANSP:TRANSPARENT SEQUENCE:1 X-MOZ-GENERATION:1 END:VEVENT BEGIN:VEVENT CREATED:20140109T090254Z LAST-MODIFIED:20140110T120011Z DTSTAMP:20140110T120011Z UID:07afe210-61a1-4113-9020-2735aefc7467 SUMMARY:oVirt 3.4.0 Alpha release DTSTART;VALUE=DATE:20140113 DTEND;VALUE=DATE:20140114 TRANSP:TRANSPARENT SEQUENCE:1 X-MOZ-GENERATION:1 END:VEVENT BEGIN:VEVENT CREATED:20140207T162249Z LAST-MODIFIED:20140212T152724Z DTSTAMP:20140212T152724Z UID:d84f83fe-7039-4c00-b4e1-432340f92764 SUMMARY:oVirt 3.4 Second Test day DTSTART;VALUE=DATE:20140211 DTEND;VALUE=DATE:20140212 SEQUENCE:1 X-MOZ-GENERATION:2 END:VEVENT BEGIN:VEVENT CREATED:20140212T152742Z LAST-MODIFIED:20140212T152757Z DTSTAMP:20140212T152757Z UID:49de31f1-9023-432c-9505-853601988a4f SUMMARY:oVirt 3.4.0 beta2 release DTSTART;VALUE=DATE:20140207 DTEND;VALUE=DATE:20140208 TRANSP:TRANSPARENT SEQUENCE:1 X-MOZ-GENERATION:1 END:VEVENT BEGIN:VEVENT CREATED:20140212T152830Z LAST-MODIFIED:20140212T152845Z DTSTAMP:20140212T152845Z UID:5a55b509-477a-46de-89d8-4ba60429f0bd SUMMARY:oVirt 3.3.4 beta DTSTART;VALUE=DATE:20140218 DTEND;VALUE=DATE:20140219 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140212T152849Z LAST-MODIFIED:20140212T152907Z DTSTAMP:20140212T152907Z UID:c7aa12cb-a0d8-4e07-8296-f00de68209ba SUMMARY:oVirt 3.3.4 RC DTSTART;VALUE=DATE:20140225 DTEND;VALUE=DATE:20140226 TRANSP:TRANSPARENT SEQUENCE:1 X-MOZ-GENERATION:1 END:VEVENT BEGIN:VEVENT CREATED:20140212T152914Z LAST-MODIFIED:20140212T152922Z DTSTAMP:20140212T152922Z UID:43e50b92-251e-4749-b069-91b5f2f6792b SUMMARY:oVirt 3.3.4 GA DTSTART;VALUE=DATE:20140304 DTEND;VALUE=DATE:20140305 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140212T160339Z LAST-MODIFIED:20140212T160352Z DTSTAMP:20140212T160352Z UID:1c5a82fe-1c6f-474b-b152-134c5ee418e3 SUMMARY:oVirt 3.5.0 Feature Freeze DTSTART;VALUE=DATE:20140501 DTEND;VALUE=DATE:20140502 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140212T160417Z LAST-MODIFIED:20140212T160423Z DTSTAMP:20140212T160423Z UID:2be0ee2c-916d-4e49-abc4-1675c7565c12 SUMMARY:oVirt 3.5.0 stable branching DTSTART;VALUE=DATE:20140515 DTEND;VALUE=DATE:20140516 TRANSP:TRANSPARENT END:VEVENT BEGIN:VEVENT CREATED:20140109T085926Z LAST-MODIFIED:20140217T092455Z DTSTAMP:20140217T092455Z UID:aa67201d-432b-486b-b384-3084b51ee12a SUMMARY:oVirt 3.4.0 GA DTSTART;VALUE=DATE:20140303 DTEND;VALUE=DATE:20140304 TRANSP:TRANSPARENT SEQUENCE:1 X-MOZ-GENERATION:1 END:VEVENT BEGIN:VEVENT CREATED:20140217T092456Z LAST-MODIFIED:20140218T122158Z DTSTAMP:20140218T122158Z UID:9cf77356-c96c-4f99-a02b-5513894f00a8 SUMMARY:oVirt 3.4.0 RC DTSTART;VALUE=DATE:20140224 DTEND;VALUE=DATE:20140225 X-MOZ-GENERATION:1 END:VEVENT BEGIN:VEVENT CREATED:20140109T090034Z LAST-MODIFIED:20140218T12
Re: [Users] oVirt upcoming release schedule update
Il 18/02/2014 14:38, Jorick Astrego ha scritto: > Hi Maurice, > > It appears the beta3 rpm's are already uploaded but I had to add the > following to the ovirt.repo to enable the updates: > > [ovirt-3.4.0-beta3] > name=Beta3 builds of the oVirt project > baseurl=http://ovirt.org/releases/3.4.0-beta3/rpm/Fedora/$releasever/ > enabled=1 > skip_if_unavailable=1 > gpgcheck=0 > http://resources.ovirt.org/releases/3.4.0-beta3/ > The repo has been uploaded for integration testing, and it failed so we did not announce it. We're going to respin it. We'll announce 3.4.0 beta3 once it passes our tests, please be patient :-) > Kind regards, > > Jorick Astrego > Netbulae > > > On Tue, 2014-02-18 at 05:37 -0500, Maurice James wrote: >> What is the status of the RC build for 2.4.0? >> >> -Original Message- >> From: users-boun...@ovirt.org <mailto:users-boun...@ovirt.org> >> [mailto:users-boun...@ovirt.org] On Behalf Of >> Sandro Bonazzola >> Sent: Wednesday, February 12, 2014 11:11 AM >> To: Users@ovirt.org <mailto:Users@ovirt.org>; arch >> Subject: [Users] oVirt upcoming release schedule update >> >> oVirt team has updated the release schedule for upcoming releases. >> >> These are tentative planning dates and may change. >> >> 2014-02-17 - oVirt 3.4.0 RC Build >> 2014-02-18 - oVirt 3.3.4 beta >> 2014-02-19 - oVirt 3.4 Third Test Day >> 2014-02-24 - oVirt 3.4.0 GA >> 2014-02-25 - oVirt 3.3.4 RC >> 2014-03-04 - oVirt 3.3.4 GA >> 2014-05-01 - oVirt 3.5.0 Feature Freeze >> 2014-05-15 - oVirt 3.5.0 stable branching >> 2014-06-10 - oVirt 3.5.0 GA >> >> More details on test days, etc to come in the next few weeks. >> You'll find an updated ICS calendar attached to this email. >> 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: [Users] oVirt upcoming release schedule update
Il 18/02/2014 11:37, Maurice James ha scritto: > What is the status of the RC build for 2.4.0? Supposing you're targeting 3.4.0, We're postponing RC by one week for fixing remaining blockers. I sent an update today to this schedule. > > -Original Message- > From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of > Sandro Bonazzola > Sent: Wednesday, February 12, 2014 11:11 AM > To: Users@ovirt.org; arch > Subject: [Users] oVirt upcoming release schedule update > > oVirt team has updated the release schedule for upcoming releases. > > These are tentative planning dates and may change. > > 2014-02-17 - oVirt 3.4.0 RC Build > 2014-02-18 - oVirt 3.3.4 beta > 2014-02-19 - oVirt 3.4 Third Test Day > 2014-02-24 - oVirt 3.4.0 GA > 2014-02-25 - oVirt 3.3.4 RC > 2014-03-04 - oVirt 3.3.4 GA > 2014-05-01 - oVirt 3.5.0 Feature Freeze > 2014-05-15 - oVirt 3.5.0 stable branching > 2014-06-10 - oVirt 3.5.0 GA > > More details on test days, etc to come in the next few weeks. > You'll find an updated ICS calendar attached to this email. > 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] oVirt 3.3.4 beta is now available
The oVirt team is pleased to announce that the 3.3.4 Beta is now available in beta [1] repository for testing. Feel free to join us testing it! You'll find all needed info for installing it on the release notes page, already available on the wiki [2]. A new oVirt Node build will be available soon as well. [1] http://resources.ovirt.org/releases/beta/ [2] http://www.ovirt.org/OVirt_3.3.4_release_notes -- 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] [ANN] oVirt 3.4.0 beta3 is now available
The oVirt team is pleased to announce that the 3.4.0 third beta release is now available 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. The existing repository ovirt-3.4.0-prerelease has been updated 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 before we'll compose RC build for next week test day [2] scheduled for 2014-02-27! [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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] [QE] oVirt 3.3.4 beta / RC status
Hi, we've released oVirt 3.3.4 beta on Wed 2014-02-19. We're going to start building 3.3.4 RC on 2014-02-25 09:00 UTC repository composition will follow as soon as all packages will be built. A bug tracker is available at [1] and it shows no bugs blocking the release The following is a list of the non-blocking bugs still open with target 3.3.4: Whiteboard Bug ID Summary infra 1053576 ASSIGNED[abrt] vdsm-python: libvirt.py:102:openAuth:libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory integration 1026930 NEW Package virtio-win and put it in ovirt repositories integration 1026933 NEW pre-populate ISO domain with virtio-win ISO network 987917 NEW [oVirt] [glance] API version not specified in provider dialog network 997197 NEW Some AppErrors messages are grammatically incorrect (singular vs plural) 1066654 NEW engine-cleanup does not cleanup everything Maintainers / Assignee: Please add the bugs to the tracker if you think that 3.3.4 should not be released without them fixed. Please re-target all bugs you don't think that should block 3.3.4. Bugs still targeted to 3.3.4 after RC announce will be re-targeted to 3.4.1 For those who want to help testing the bugs, I suggest to add yourself to the testing page [2]. Maintainers are welcomed to start filling release notes, the page has been created here [3] [1] http://bugzilla.redhat.com/1064462 [2] http://www.ovirt.org/Testing/Ovirt_3.3.4_testing [3] http://www.ovirt.org/OVirt_3.3.4_release_notes 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] [QE] oVirt 3.4.0 RC status
Hi, oVirt 3.4.0 beta3 has been released and is actually on QA. We're going to start building oVirt 3.4.0 RC this Monday 2014-02-24 09:00 UTC from 3.4 branches. repository composition will follow as soon as all packages will be built. This build will be used for a third Test Day scheduled for Wed 2014-02-27. The bug tracker [1] shows the following bugs blocking the release: Whiteboard Bug ID Status Summary infra 1055881 POSTREST API: Search for an user in active directory by upn doesn't return any results ... infra 1059258 POSTREST API: Create user user@domain actually creates user only infra 1060528 POSTError response to DELETE request of 'Everyone' group doesn't contains 'detail' field infra 1064829 POSTRegression: Add data center permission to user causes to internal error integration 1058018 POSTupgrade from 3.3 overwrites exports with acl None network 1066953 POSTCannot edit network is "setup networks" dialog network 1066956 POSTCannot create a bond in 'Setup networks' dialog storage 1057761 NEW Can't discover iSCSI target storage 1066466 POSTDisk name doesn't get assigned automatically after a CREATE command. ux 1066489 POSTEvent list not updating when events happen. ux 1066827 NEW [webadmin] incorrect behavior of manual refresh in Host Main Tab virt1062615 POSTutc_diff not updated according to a change in VM settings Maintainers / Assignee: - Please provide ETA on blockers bugs - Please fix them ASAP There are still 347 bugs [2] targeted to 3.4.0. Excluding node and documentation bugs we still have 222 bugs [3] targeted to 3.4.0. Please review them as soon as possible. Maintainers / Assignee: - Please remember to rebuild your packages before 2014-02-24 09:00 UTC if you want them to be included in 3.4.0 RC. - Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed. - Please update the target to 3.4.1 or any next release for bugs that won't be in 3.4.0: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] - Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-02-27 Be prepared for upcoming oVirt 3.4.0 Test Day on 2014-02-27! Thanks to all people already testing 3.4.0 beta 3! [1] https://bugzilla.redhat.com/1024889 [2] http://red.ht/1eIRZXM [3] http://red.ht/1auBU3r [4] http://www.ovirt.org/OVirt_3.4.0_release_notes -- 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: [Users] "Last Updated" shows current time instead of last update
Il 20/02/2014 15:27, Yedidyah Bar David ha scritto:
> - Original Message -
>> From: "Nir Soffer"
>> To: "Yedidyah Bar David"
>> Cc: "infra" , "users"
>> Sent: Thursday, February 20, 2014 12:15:42 PM
>> Subject: Re: [Users] "Last Updated" shows current time instead of last update
>>
>> - Original Message -
>>> From: "Yedidyah Bar David"
>>> To: "infra" , "users"
>>> Sent: Monday, February 17, 2014 2:43:42 PM
>>> Subject: [Users] "Last Updated" shows current time instead of last update
>>>
>>> Hi all,
>>>
>>> Sorry for cross-posting. Not sure what's the correct address to discuss
>>> this.
>>>
>>> Almost all of the pages on the ovirt.org wiki that have "Last Updated:",
>>> actually have:
>>>
>>> Last updated: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}
>>>
>>> thus showing the current date and not the last change date. When searching
>>> google you see the last time its robot happened to fetch the page.
>>>
>>> See e.g. [1] for a (possibly non-complete) list.
>>>
>>> Not sure if that's intended or not, but I personally find it useless and
>>> misleading.
>>
>> This is indeed useless and wrong and should be removed.
>>
>> Does this work?
>>
>> Last updated on {{REVISIONDAY}}/{{REVISIONMONTH}}/{{REVISIONYEAR}} by
>> {{REVISIONUSER}}
>
> If I Edit, then Show preview, it's already updated, even before Save page.
> I personally find it a bit weird. Anyway, I did this on a test page and it
> seems to work, but I have to wait a day to make sure the date does not
> change...
>
> In any case, it does affect performance. Not sure it's very significant,
> though.
>
> I now changed the following pages (picked up randomly):
>
> http://www.ovirt.org/Features/Minimum_guaranteed_memory
> http://www.ovirt.org/Features/MultiHostNetworkConfiguration
> http://www.ovirt.org/Features/Node/PluginLiveInstall
> http://www.ovirt.org/Features/Node/PackageRefactoring
> http://www.ovirt.org/Features/Automatic_scaling
>
> I changed it to:
>
> Last updated on {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY}} by
> {{REVISIONUSER}}
>
> That is, ISO date.
>
> If we do not see a significant impact in a few days, we should probably edit
> all pages, probably with some bot.
>
+1
--
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: [Users] repo status
Il 20/02/2014 17:46, Jimmy Dorff ha scritto: > What is going on with the EL repos. I'm getting this message: > > http://resources.ovirt.org/releases/3.3.3/rpm/Fedora/6.5/repodata/repomd.xml: > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not > Found" > Trying other mirror. > http://ovirt.org/releases/stable/rpm/Fedora/6.5/repodata/repomd.xml: [Errno > 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found" > Trying other mirror. > > This is on a fresh install with only EPEL and > http://resources.ovirt.org/releases/ovirt-release-el.noarch.rpm It seems we've a bug in latest ovirt-release rpm. Can you attach the content of /etc/system-release on your system? To workaround your issue, please install http://resources.ovirt.org/releases/3.3.3/rpm/EL/6/noarch/ovirt-release-el6-10.0.1-3.noarch.rpm Thanks, > > > Thanks, > Jimmy > > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] problems installing ovirt-engine beta3
Il 21/02/2014 10:50, Jorick Astrego ha scritto: > Hi, > > I noticed the known issue with shmmax has been removed from the test day > page. But I'm having the same error as before only know the workaround > doesn't work anymore: Can you attach # sysctl --system and # rpm -qv ovirt-engine-setup ? and the full error you get? > > > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] Problems with Scientific Linux and ovirt-release-11.0.0
Il 21/02/2014 06:49, Jimmy Dorff ha scritto: > Hi Folks, > > I've found a bug in ovirt-release-11.0.0. In ovirt-release.spec > #Handling EL exception only (for now) > if grep -qFi 'CentOS' /etc/system-release; then > DIST=EL > elif grep -qFi 'Red Hat' /etc/system-release; then > DIST=EL > fi > > This causes all kinds unhappiness on Scientific Linux :) Perhaps another elif > line can be added. Sure, can you send /etc/system-release content? > > Cheers, > Jimmy Dorff > > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] Problems with Scientific Linux and ovirt-release-11.0.0
Il 21/02/2014 07:34, Meital Bourvine ha scritto: > Hi Jimmy, > > As far as I know, scientific linux isn't supported by ovirt. IIUC it's based on CentOS / RHEL so it may work. Let us know if you've issues :-) > > But you can always try submitting a patch ;) > > - Original Message - >> From: "Jimmy Dorff" >> To: users@ovirt.org >> Sent: Friday, February 21, 2014 7:49:59 AM >> Subject: [Users] Problems with Scientific Linux and ovirt-release-11.0.0 >> >> Hi Folks, >> >> I've found a bug in ovirt-release-11.0.0. In ovirt-release.spec >> #Handling EL exception only (for now) >> if grep -qFi 'CentOS' /etc/system-release; then >> DIST=EL >> elif grep -qFi 'Red Hat' /etc/system-release; then >> DIST=EL >> fi >> >> This causes all kinds unhappiness on Scientific Linux :) Perhaps another >> elif line can be added. >> >> Cheers, >> Jimmy Dorff >> >> >> ___ >> 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 > -- 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: [Users] engine-image-uploader
Il 10/02/2014 00:12, Itamar Heim ha scritto:> On 02/10/2014 01:08 AM, Maurice James wrote: >> I got the ovf from the turnkey linux site. It's a Drupal appliance > > I assume its not an "ovirt ovf"... just export a VM from ovirt to have the > right ovf format, then edit it probably. > another option, push the disk image to glance, then import just the disk via > glance (no need for the ovf) Looking at http://www.turnkeylinux.org/docs/builds For using it on oVirt you should use Generic ISO (Any virtual machine (e.g., KVM) that can install from CD or CD image.) uploading it with engine-iso-uploader. OVF provided are for other virtualization systems and need to be converted first. You can try also to contact turnkeylinux asking to provide also ovirt compatible OVF images. > >> >> -Original Message- >> From: Itamar Heim [mailto:ih...@redhat.com] >> Sent: Sunday, February 09, 2014 4:56 PM >> To: Maurice James; 'users' >> Subject: Re: [Users] engine-image-uploader >> >> On 02/09/2014 11:05 PM, Maurice James wrote: >>> What does the following error mean? >>> >>> There should only be one Name element in the OVF XML's Content section. >>> >>> I ran the following command >>> >>> engine-image-uploader -e SaturnExport -N Drupal2 upload >>> turnkey-drupal7-13.0-wheezy-amd64.tar.gz >>> >>> >>> >>> ___ >>> Users mailing list >>> Users@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >> >> where did the OVF come from? >> please note OVF isn't really compatible between different vendors. i.e., you >> need an "ovirt ovf" file/format. >> exporting a similar vm/disk configuration will give you a hint at the >> expected ovf format (well, format is the same, more like fields) for ovirt >> > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users -- 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: [Users] ovirt.repo for el contains fedora references .....
Il 18/02/2014 23:03, James James ha scritto: > Hi, > > I want to install this rpm > http://resources.ovirt.org/releases/ovirt-release-el.noarch.rpm on my > redhat-like server but the > /etc/yum.repos.d/ovirt.repo contains : you're running an unsupported distribution, can you please attach the content of your /etc/system-release file? Can you also tell us if oVirt was working on your system before we unified ovirt-release rpm? > > [ovirt-stable] > name=oVirt Latest Releases > baseurl=http://ovirt.org/releases/stable/rpm/Fedora/$releasever/ > enabled=1 > skip_if_unavailable=1 > gpgcheck=0 > > [ovirt-3.3.3] > name=oVirt 3.3.3 Release > baseurl=http://resources.ovirt.org/releases/3.3.3/rpm/Fedora/$releasever/ > enabled=1 > skip_if_unavailable=1 > gpgcheck=0 > > [ovirt-updates-testing] > name=oVirt 3.3.z Latest Pre Releases (Release Candidate) > baseurl=http://ovirt.org/releases/updates-testing/rpm/Fedora/$releasever/ > enabled=0 > skip_if_unavailable=1 > gpgcheck=0 > > [ovirt-beta] > name=oVirt 3.3.z Beta Test Releases > baseurl=http://ovirt.org/releases/beta/rpm/Fedora/$releasever/ > enabled=0 > skip_if_unavailable=1 > gpgcheck=0 > > > Is it normal ? > > Regards. > > > > _______ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] Yum Installation Problems (ovirt 3.3, CentOS 6.5)
Il 18/02/2014 22:32, Jon Forrest ha scritto: > I have a brand new CentOS 6.5 x86_64 installation with all the updates > as of today installed. > I want to create a test All-In-One node, so I follow the documentation and run > > yum install epel-release-6-8.noarch.rpm > yum localinstall http://ovirt.org/releases/ovirt-release-el.noarch.rpm > > These work fine. I then run > > yum install ovirt-engine-setup-plugin-allinone -y Can you please post the output of yum repolist enabled ? > > and I get > > Error: Package: libvirt-lock-sanlock-0.10.2-29.el6_5.3.x86_64 (updates) >Requires: libsanlock_client.so.1()(64bit) > Error: Package: libvirt-lock-sanlock-0.10.2-29.el6_5.3.x86_64 (updates) >Requires: sanlock >= 2.4 > Error: Package: vdsm-4.13.3-3.el6.x86_64 (ovirt-3.3.3) >Requires: sanlock >= 2.3-4 > Error: Package: vdsm-4.13.3-3.el6.x86_64 (ovirt-3.3.3) >Requires: sanlock-python > > Is this expected? What's weird is that IIRC I did the same thing last > week without problems. > Should I just grab newer versions of libvirt? > > Thanks, > Jon Forrest > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] Asking for advice on hosted engine
Il 17/02/2014 10:20, Giorgio Bersano ha scritto: > Hello everybody, > I discovered oVirt a couple of months ago when I was looking for the > best way to manage our small infrastructure. I have read any document > I considered useful but I would like to receive advice from the many > experts that are on this list. > > I think it worths an introduction (I hope doesn't get you bored). > > I work in a small local government entity and I try to manage > effectively our limited resources. > We have many years of experience with Linux and especially with CentOS > which we have deployed on PC (i.e. for using as firewall in remote > locations) and moreover on servers. > > We have been using Xen virtualization from the early days of CentOS 5 > and we have built our positive experience on KVM too. > I have to say that libvirt in a small environment like ours is really > a nice tool. > So nothing to regret. > > Trying to go a little further, as already said, I stumbled upon oVirt > and I've found the project intriguing. > > At the moment we are thinking of deploying it on a small environment > of four very similar servers each having: > - a couple of Xeon E5504 > - 6 x 1Gb ethernet interfaces > - 40 GB of RAM > two of them have 72 GB of disk (mirrored) > two of them have almost 500GB of useful RAID array > > Moreover we have an HP iSCSI storage that should easily satisfy our > current storage requirement. > > So, given our small server pool, the necessity of another host just to > run the supervisor seems a requirement too high. > > Enter "hosted engine" and the picture takes brighter colors. Well, I'm > usually not the adventurous guy but after experimenting a little with > oVirt 3.4 I developed better confidence. > We would want to install the engine over the two hosts with smaller disks. > > For what I know, installing hosted engine mandates NFS storage. But we > want this to be highly available too, and possibly to have it on the > very same hosts. > > Here is my solution: make a gluster replicated volume across the two > hosts and take advantage of that NFS server. > Then I put 127.0.0.1 as the address of the NFS server in the > hosted-engine-setup so the host is always able to reach the storage > server (itself). > GlusterFS configuration is done outside of oVirt that, regarding > engine's storage, doesn't even know that it's a gluster thing. > > Relax, we've finally reached the point where I'm asking advice :-) > > Storage and virtualization experts, do you see in this configuration > any pitfall that I've overlooked given my inexperience in oVirt, > Gluster, NFS or clustered filesystems? > Do you think that not only it's feasable (I know it is, I made it and > it's working now) but it's also reliable and dependable and I'm not > risking my neck on this setup? I'm not sure about how reliable may be the sanlock protection of the hosted engine image over a gluster volume. Maybe Federico can tell you more about this. > > I've obviously made some test but I'm not at the confidence level of > saying that all is right in the way it is designed. > > OK, I think I've already written too much, better I stop and humbly > wait for your opinion but I'm obviously here if any clarification by > my part is needed. > > Thank you very much for reading until this point. > Best Regards, > Giorgio. > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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: [Users] Problems with Scientific Linux and ovirt-release-11.0.0
Il 21/02/2014 16:25, Jimmy Dorff ha scritto: > On 2/21/14, 2:31 AM, Sandro Bonazzola wrote: >> Il 21/02/2014 07:34, Meital Bourvine ha scritto: >>> Hi Jimmy, >>> >>> As far as I know, scientific linux isn't supported by ovirt. >> >> IIUC it's based on CentOS / RHEL so it may work. >> Let us know if you've issues :-) >> >> >>> >>> But you can always try submitting a patch ;) >>> > > SL works fine with ovirt. If you want to "support it", here is a patch. http://gerrit.ovirt.org/24869 If you've an account on gerrit you can review / verify it. > > *** a/ovirt-release.spec2014-02-21 10:10:00.0 -0500 > --- b/ovirt-release.spec2014-02-21 10:10:55.0 -0500 > *** > *** 73,76 > --- 73,78 > elif grep -qFi 'Red Hat' /etc/system-release; then > DIST=EL > + elif grep -qFi 'Scientific Linux' /etc/system-release; then > + DIST=EL > fi > > > If you don't support Scientific Linux, then I would recommend not defaulting > the DIST to Fedora and instead searching for the specific supported > releases and error out otherwise. > > Future-wise, Scientific Linux *may* become a "CentOS variant" in Red Hat's > CentOS. > > Cheers, > Jimmy > -- 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: [Users] Problems with Scientific Linux and ovirt-release-11.0.0
Il 21/02/2014 19:10, Jimmy Dorff ha scritto: > Hi Sandro, > > Dave Neary's comment is good. Here is a new patch: > > *** a/ovirt-release.spec2014-02-21 10:10:00.0 -0500 > --- b/ovirt-release.spec2014-02-21 13:01:35.856636466 -0500 > *** > *** 69,75 > #Fedora is good for both Fedora and Generic (and probably other based on > Fedora) > #Handling EL exception only (for now) > ! if grep -qFi 'CentOS' /etc/system-release; then > ! DIST=EL > ! elif grep -qFi 'Red Hat' /etc/system-release; then > DIST=EL > fi > --- 69,73 > #Fedora is good for both Fedora and Generic (and probably other based on > Fedora) > #Handling EL exception only (for now) > ! if rpm --eval "%dist" | grep -qFi 'el'; then Missing escape: %%dist pushed a new patchset, please review it on gerrit:http://gerrit.ovirt.org/24869 and verify it on Scientific Linux : http://jenkins.ovirt.org/job/ovirt-release_gerrit/30/artifact/exported-artifacts/ovirt-release-11.0.1-1.noarch.rpm > DIST=EL > fi > > Might be faster for you to submit cause I'm not familiar with gerrit, but I > can login with my Fedora FAS account. > > Cheers, > Jimmy > > > > On 2/21/14, 8:17 AM, Sandro Bonazzola wrote: >> Il 21/02/2014 16:25, Jimmy Dorff ha scritto: >>> On 2/21/14, 2:31 AM, Sandro Bonazzola wrote: >>>> Il 21/02/2014 07:34, Meital Bourvine ha scritto: >>>>> Hi Jimmy, >>>>> >>>>> As far as I know, scientific linux isn't supported by ovirt. >>>> >>>> IIUC it's based on CentOS / RHEL so it may work. >>>> Let us know if you've issues :-) >>>> >>>> >>>>> >>>>> But you can always try submitting a patch ;) >>>>> >>> >>> SL works fine with ovirt. If you want to "support it", here is a patch. >> >> http://gerrit.ovirt.org/24869 >> If you've an account on gerrit you can review / verify it. >> >>> >>> *** a/ovirt-release.spec2014-02-21 10:10:00.0 -0500 >>> --- b/ovirt-release.spec2014-02-21 10:10:55.0 -0500 >>> *** >>> *** 73,76 >>> --- 73,78 >>>elif grep -qFi 'Red Hat' /etc/system-release; then >>>DIST=EL >>> + elif grep -qFi 'Scientific Linux' /etc/system-release; then >>> + DIST=EL >>>fi >>> >>> >>> If you don't support Scientific Linux, then I would recommend not >>> defaulting the DIST to Fedora and instead searching for the specific >>> supported >>> releases and error out otherwise. >>> >>> Future-wise, Scientific Linux *may* become a "CentOS variant" in Red Hat's >>> CentOS. >>> >>> Cheers, >>> Jimmy >>> >> >> > -- 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] Postponing oVirt 3.4.0 RC build, Test Day and GA
Hi, we still have 3 blockers on POST so we're postponing RC build until all of them will be in MODIFIED state. Here is the list of blockers still open: Whiteboard Bug ID Status Summary infra 1055881 POSTREST API: Search for an user in active directory by upn doesn't return any results... infra 1059258 POSTREST API: Create user user@domain actually creates user only virt1062615 POSTutc_diff not updated according to a change in VM settings We're postponing Test Day too, scheduling it for next week on 2014-03-06. oVirt 3.4.0 GA have been postponed by one week, new tentative date is 2014-03-11. -- 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: [Users] oVirt 3.5 planning
Il 25/02/2014 15:39, Gianluca Cecchi ha scritto: >>>> 2014-02-24 17:59 GMT+01:00 Itamar Heim : >>>>> >>>>> with oVirt 3.4 getting close to GA with many many great features, time >>>>> to collect requests for 3.5... > > Signed rpms as in: > http://lists.ovirt.org/pipermail/users/2014-January/019627.html > and the mentioned ticket inside Dan answer: > https://fedorahosted.org/ovirt/ticket/99 > > Hopefully in 3.4 too... ;-) We're already working on it, I hope we'll have 3.4.0 rpm signed. > > Gianluca > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- 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] oVirt 3.3.4 Release Candidate is now available
The oVirt team is pleased to announce that the 3.3.4 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. Release notes for this update will be updated soon on the wiki [3]. [1] http://resources.ovirt.org/releases/updates-testing [2] http://www.ovirt.org/Testing/Ovirt_3.3.4_testing [3] http://www.ovirt.org/OVirt_3.3.4_release_notes -- 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: [Users] Fresh installation of ovirt-engine
Il 27/02/2014 22:18, Itamar Heim ha scritto: > On 02/27/2014 06:14 PM, Andy Michielsen wrote: >> Hello, >> >> I just finnished an installation of a ovirt-engine and changed the >> ISO_DOMAIN path to /exports/iso as this is my 1Tb diskspace. >> >> But now I see that the nfs share created is /var/lib/exports/iso. I >> would expect it to be /export/iso but that doesn't seem to be the case. >> >> Doe I need to modify this manualy or did I do something wrong. So you used default /var/lib/exports/iso while running engine setup and then changed it manually from the web app? Can you upload your setup logs (for example on http://www.fpaste.org/) so we can take a look? >> >> Kind regards. >> >> >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> > > didi/sandro - thoughts? -- 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: [Users] The purpose of "Wipe on delete" ?
Il 27/02/2014 22:16, Dafna Ron ha scritto: > wipe = writing zero's on the space allocated to that disk to make sure any > data once written will be deleted permanently. > > so it's a security vs speed decision on using this option - since we zeroing > the disk to make sure any information once written will be overwritten, > a delete of a large disk can take a while. I think this may be not really useful, zeroing files on modern file systems can't grant any kind of security improvement. According to shred man page: CAUTION: Note that shred relies on a very important assumption: that the file system overwrites data in place. This is the traditional way to do things, but many modern file system designs do not satisfy this assumption. The following are examples of file systems on which shred is not effective, or is not guaranteed to be effective in all file system modes: * log-structured or journaled file systems, such as those supplied with AIX and Solaris (and JFS, ReiserFS, XFS, Ext3, etc.) * file systems that write redundant data and carry on even if some writes fail, such as RAID-based file systems * file systems that make snapshots, such as Network Appliance's NFS server * file systems that cache in temporary locations, such as NFS version 3 clients * compressed file systems In the case of ext3 file systems, the above disclaimer applies (and shred is thus of limited effectiveness) only in data=journal mode, which journals file data in addition to just metadata. In both the data=ordered (default) and data=writeback modes, shred works as usual. Ext3 journaling modes can be changed by adding the data=something option to the mount options for a particular file system in the /etc/fstab file, as documented in the mount man page (man mount). In addition, file system backups and remote mirrors may contain copies of the file that cannot be removed, and that will allow a shredded file to be recovered later. > > Dafna > > > > > On 02/27/2014 04:14 PM, Richard Davis wrote: >> Hi >> >> What is the purpose of the "Wipe on delete" option for a VM disk ? >> Why would you not want data wiped on delete if the alternative is to leave >> LV metadata and other data languishing on the SD ? >> >> >> Thanks >> >> Rich >> _______ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users > > -- 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: [Users] Fresh installation of ovirt-engine
Il 28/02/2014 09:13, Andy Michielsen ha scritto: > Hello, > > No I did the change during the execution of the engine-setup script. When it > want's to create an ISO_DOMAIN it suggest /var/lib/exports/iso and I > changed it to /exports/iso. > > But when everything is finnished and I check with showmount -e it > tells me that it is exporting /var/lib/exports/iso. Can you upload your setup logs (for example on http://www.fpaste.org/) so we can take a look? > > Kind regards. > > > > > 2014-02-28 8:26 GMT+01:00 Sandro Bonazzola <mailto:sbona...@redhat.com>>: > > Il 27/02/2014 22:18, Itamar Heim ha scritto: > > On 02/27/2014 06:14 PM, Andy Michielsen wrote: > >> Hello, > >> > >> I just finnished an installation of a ovirt-engine and changed the > >> ISO_DOMAIN path to /exports/iso as this is my 1Tb diskspace. > >> > >> But now I see that the nfs share created is /var/lib/exports/iso. I > >> would expect it to be /export/iso but that doesn't seem to be the case. > >> > >> Doe I need to modify this manualy or did I do something wrong. > > So you used default /var/lib/exports/iso while running engine setup and > then changed it manually from the web app? > Can you upload your setup logs (for example on http://www.fpaste.org/) so > we can take a look? > > > >> > >> Kind regards. > >> > >> > >> ___ > >> Users mailing list > >> Users@ovirt.org <mailto:Users@ovirt.org> > >> http://lists.ovirt.org/mailman/listinfo/users > >> > > > > didi/sandro - thoughts? > > > > > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com <http://redhat.com> > > -- 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: [Users] Fresh installation of ovirt-engine
Il 28/02/2014 09:45, Andy Michielsen ha scritto: > Hello, > > I check this logfile myself and it doesn't mention my /exports/iso input at > all. I posted the log on http://www.fpaste.org/ Ehm, paste number / full url of the paste? > > Kind regards. > > > 2014-02-28 9:16 GMT+01:00 Sandro Bonazzola <mailto:sbona...@redhat.com>>: > > Il 28/02/2014 09:13, Andy Michielsen ha scritto: > > Hello, > > > > No I did the change during the execution of the engine-setup script. > When it want's to create an ISO_DOMAIN it suggest /var/lib/exports/iso and I > > changed it to /exports/iso. > > > > But when everything is finnished and I check with showmount -e > it tells me that it is exporting /var/lib/exports/iso. > > Can you upload your setup logs (for example on http://www.fpaste.org/) so > we can take a look? > > > > > Kind regards. > > > > > > > > > > 2014-02-28 8:26 GMT+01:00 Sandro Bonazzola <mailto:sbona...@redhat.com> <mailto:sbona...@redhat.com > <mailto:sbona...@redhat.com>>>: > > > > Il 27/02/2014 22:18, Itamar Heim ha scritto: > > > On 02/27/2014 06:14 PM, Andy Michielsen wrote: > > >> Hello, > > >> > > >> I just finnished an installation of a ovirt-engine and changed > the > > >> ISO_DOMAIN path to /exports/iso as this is my 1Tb diskspace. > > >> > > >> But now I see that the nfs share created is > /var/lib/exports/iso. I > > >> would expect it to be /export/iso but that doesn't seem to be > the case. > > >> > > >> Doe I need to modify this manualy or did I do something wrong. > > > > So you used default /var/lib/exports/iso while running engine setup > and then changed it manually from the web app? > > Can you upload your setup logs (for example on > http://www.fpaste.org/) so we can take a look? > > > > > > >> > > >> Kind regards. > > >> > > >> > > >> ___ > > >> Users mailing list > > >> Users@ovirt.org <mailto:Users@ovirt.org> <mailto:Users@ovirt.org > <mailto:Users@ovirt.org>> > > >> http://lists.ovirt.org/mailman/listinfo/users > > >> > > > > > > didi/sandro - thoughts? > > > > > > > > > > > > > > > > -- > > Sandro Bonazzola > > Better technology. Faster innovation. Powered by community > collaboration. > > See how it works at redhat.com <http://redhat.com> > <http://redhat.com> > > > > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com <http://redhat.com> > > -- 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: [Users] Fresh installation of ovirt-engine
Il 28/02/2014 09:46, Sven Kieske ha scritto: > Sounds like a bug to me. > You should file a bugreport at bugzilla.redhat.com to track it. Let's start to check what's in the logs :-) > > Am 28.02.2014 09:13, schrieb Andy Michielsen: >> Hello, >> >> No I did the change during the execution of the engine-setup script. When >> it want's to create an ISO_DOMAIN it suggest /var/lib/exports/iso and I >> changed it to /exports/iso. >> >> But when everything is finnished and I check with showmount -e it >> tells me that it is exporting /var/lib/exports/iso. >> >> Kind regards. > -- 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: [Users] Fresh installation of ovirt-engine
Il 28/02/2014 10:11, Andy Michielsen ha scritto: > Hello, > > Hope this works. 16:29:32 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:215 DIALOG:SEND Local ISO domain path [/var/lib/exports/iso]: 2014-02-27 16:29:42 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:215 DIALOG:RECEIVE/exports/iso 2014-02-27 16:29:42 DEBUG otopi.ovirt_engine_setup.domains domains.check_valid_path:90 validate '/exports/iso' as a valid mount point 2014-02-27 16:29:42 DEBUG otopi.ovirt_engine_setup.domains domains.check_base_writable:104 Attempting to write temp file to /exports/iso 2014-02-27 16:29:42 DEBUG otopi.ovirt_engine_setup.domains domains.check_available_space:122 Checking available space on /exports/iso 2014-02-27 16:29:42 DEBUG otopi.ovirt_engine_setup.domains domains.check_available_space:129 Available space on /exports/iso is 950698Mb 2014-02-27 16:29:42 ERROR otopi.plugins.ovirt_engine_setup.config.iso_domain iso_domain._customization:342 Cannot access mount point /exports/iso: Error: directory /exports/iso is not empty 2014-02-27 16:29:42 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:215 DIALOG:SEND Local ISO domain path [/var/lib/exports/iso]: 2014-02-27 16:30:55 DEBUG otopi.ovirt_engine_setup.domains domains.check_valid_path:90 validate '/var/lib/exports/iso' as a valid mount point 2014-02-27 16:30:55 DEBUG otopi.ovirt_engine_setup.domains domains.check_base_writable:104 Attempting to write temp file to /var/lib 2014-02-27 16:30:55 DEBUG otopi.ovirt_engine_setup.domains domains.check_available_space:122 Checking available space on /var/lib 2014-02-27 16:30:55 DEBUG otopi.ovirt_engine_setup.domains domains.check_available_space:129 Available space on /var/lib is 17352Mb 2014-02-27 16:30:55 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:215 DIALOG:SEND Local ISO domain name [ISO_DOMAIN]: 2014-02-27 16:30:58 DEBUG otopi.context context.dumpEnvironment:441 ENVIRONMENT DUMP - BEGIN 2014-02-27 16:30:58 DEBUG otopi.context context.dumpEnvironment:456 ENV OVESETUP_CONFIG/isoDomainMountPoint=str:'/var/lib/exports/iso' 2014-02-27 16:30:58 DEBUG otopi.context context.dumpEnvironment:456 ENV OVESETUP_CONFIG/isoDomainName=str:'ISO_DOMAIN' Setup proposed /var/lib/exports/iso You specifed /exports/iso as mount point and failed validation Setup failed validation and proposed again /var/lib/exports/iso It has been accepted Setup successfully validated /var/lib/exports/iso I think there's no bug here. > > Kind regards. > > > 2014-02-28 9:47 GMT+01:00 Sandro Bonazzola <mailto:sbona...@redhat.com>>: > > Il 28/02/2014 09:45, Andy Michielsen ha scritto: > > Hello, > > > > I check this logfile myself and it doesn't mention my /exports/iso > input at all. I posted the log on http://www.fpaste.org/ > > Ehm, paste number / full url of the paste? > > > > > > Kind regards. > > > > > > 2014-02-28 9:16 GMT+01:00 Sandro Bonazzola <mailto:sbona...@redhat.com> <mailto:sbona...@redhat.com > <mailto:sbona...@redhat.com>>>: > > > > Il 28/02/2014 09:13, Andy Michielsen ha scritto: > > > Hello, > > > > > > No I did the change during the execution of the engine-setup > script. When it want's to create an ISO_DOMAIN it suggest > /var/lib/exports/iso and I > > > changed it to /exports/iso. > > > > > > But when everything is finnished and I check with showmount -e > it tells me that it is exporting /var/lib/exports/iso. > > > > Can you upload your setup logs (for example on > http://www.fpaste.org/) so we can take a look? > > > > > > > > Kind regards. > > > > > > > > > > > > > > > 2014-02-28 8:26 GMT+01:00 Sandro Bonazzola <mailto:sbona...@redhat.com> <mailto:sbona...@redhat.com > <mailto:sbona...@redhat.com>> <mailto:sbona...@redhat.com > <mailto:sbona...@redhat.com> > > <mailto:sbona...@redhat.com <mailto:sbona...@redhat.com>>>>: > > > > > > Il 27/02/2014 22:18, Itamar Heim ha scritto: > > > > On 02/27/2014 06:14 PM, Andy Michielsen wrote: > > > >> Hello, > > > >> > > > >> I just finnished an installation of a ovirt-engine and > changed the > > > >> ISO_DOMAIN path to /exports/iso as this is my 1Tb > diskspace. > > > >> > &
[Users] [ANN] oVirt 3.4.0 Release Candidate is now available
The oVirt team is pleased to announce that the 3.4.0 Release Candidate is now available 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. The existing repository ovirt-3.4.0-prerelease has been updated for delivering this release candidate and future refreshes until final release. An oVirt Node iso is already available, unchanged from third beta. You're welcome to join us testing this release candidate in next week test day [2] scheduled for 2014-03-06! [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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] hosted-engine rebooting in the middle of setup
Il 02/03/2014 10:32, Yedidyah Bar David ha scritto: > - Original Message - >> From: "Darrell Budic" >> To: "Sandro Bonazzola" >> Cc: annou...@ovirt.org, "engine-devel" , "arch" >> , Users@ovirt.org, "VDSM >> Project Development" >> Sent: Saturday, March 1, 2014 1:56:23 AM >> Subject: Re: [vdsm] [Users] [ANN] oVirt 3.4.0 Release Candidate is now >> available >> >> Started testing this on two self-hosted clusters, with mixed results. There >> were updates from 3.4.0 beta 3. Did you set the clusters in global maintenance before starting the upgrade? >> >> On both, got informed the system was going to reboot in 2 minutes while it >> was still installing yum updates. >> >> On the faster system, the whole update process finished before the 2 minutes >> were up, the VM restarted, and all appears normal. >> >> On the other, slower cluster, the 2 minutes hit while the yum updates were >> still being installed, and the system rebooted. It continued rebooting every >> 3 minutes or so, and the engine console web pages are not available because >> the engine doesn’t start. it did this at least 3 times before I went ahead >> and reran engine-setup, which completed successfully. The system stopped >> restarting and the web interface was available again. A quick perusal of >> system logs and engine-setup logs didn’t reveal what requested the reboot. >> >> That was rather impolite of something to do that without warning :) At least >> it was recoverable. Seems like scheduling the reboot while the yum updates >> were still running seems like a poor idea as well. > > Can you please post relevant logs? > hosts: /var/log/ovirt-hosted-engine-setup/*, > /var/log/ovirt-hosted-engine-ha/*, > /var/log/vdsm/* > engine: /var/log/ovirt-engine/setup/*, /var/log/ovirt-engine/* > > You can of course open a bug on bugzilla and attach there logs if you want. > > Thanks, and thanks for the report! > -- 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: [Users] hosted engine issues
Il 03/03/2014 11:33, René Koch ha scritto:
> Hi,
>
> I have some issues with hosted engine (oVirt 3.4 prerelease repo on CentOS
> 6.5).
> My setups is the following:
> 2 hosts (will be 4 in the future) with 4 GlusterFS shares:
> - engine (for hosted engine)
> - iso (for ISO domain)
> - ovirt (oVirt storage domain)
>
> I had a split-brain situation today (after rebooting both nodes) on
> hosted-engine.lockspace file on engine GlusterFS volume which I resolved.
How did you solved it? By switching to NFS only?
> hosted engine used engine share via NFS (TCP) as glusterfs isn't supported
> for oVirt hosted engine, yet. I'll switch to GlusterFS as soon as oVirt
> will support it (I hope this will be soon as RHEV 3.3 is already supporting
> GlusterFS for hosted engine).
>
>
> First of all ovirt-ha-agent fails to start on both nodes:
>
> # service ovirt-ha-agent start
> Starting ovirt-ha-agent: [ OK ]
> # service ovirt-ha-agent status
> ovirt-ha-agent dead but subsys locked
>
>
> MainThread::INFO::2014-03-03
> 11:20:39,539::agent::52::ovirt_hosted_engine_ha.agent.agent.Agent::(run)
> ovirt-hosted-engine-ha agent 1.1.0 started
> MainThread::INFO::2014-03-03
> 11:20:39,590::hosted_engine::223::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_hostname)
> Found
> certificate common name: 10.0.200.101
> MainThread::CRITICAL::2014-03-03
> 11:20:39,590::agent::103::ovirt_hosted_engine_ha.agent.agent.Agent::(run)
> Could not start ha-agent
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
> line 97, in run
> self._run_agent()
> File
> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
> line 154, in _run_agent
> hosted_engine.HostedEngine(self.shutdown_requested).start_monitoring()
> File
> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
> line 152, in __init__
> "STOP_VM": self._stop_engine_vm
> File
> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/state_machine.py",
> line 56, in __init__
> logger, actions)
> File
> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/lib/fsm/machine.py",
> line 93, in __init__
> self._logger = FSMLoggerAdapter(logger, self)
> File
> "/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/lib/fsm/machine.py",
> line 16, in __init__
> super(FSMLoggerAdapter, self).__init__(logger, None)
> TypeError: super() argument 1 must be type, not classobj
>
>
>
> If I want to start my hosted engine, I receive the following error in vdsm
> logs, which makes absolutly no sense to me, as there is plenty of disk
> space available:
>
> Thread-62::DEBUG::2014-03-03
> 11:24:46,282::libvirtconnection::124::root::(wrapper) Unknown libvirterror:
> ecode: 38 edom: 42 level: 2 message: Failed
> to acquire lock: No space left on device
seems like a vdsm failure in starting monitor the hosted engine storage domain.
Can you attach vdsm logs?
> Thread-62::DEBUG::2014-03-03
> 11:24:46,282::vm::2252::vm.Vm::(_startUnderlyingVm)
> vmId=`f26dd37e-13b5-430c-b2f2-ecd098b82a91`::_ongoingCreations released
> Thread-62::ERROR::2014-03-03
> 11:24:46,283::vm::2278::vm.Vm::(_startUnderlyingVm)
> vmId=`f26dd37e-13b5-430c-b2f2-ecd098b82a91`::The vm start process failed
> Traceback (most recent call last):
> File "/usr/share/vdsm/vm.py", line 2238, in _startUnderlyingVm
> self._run()
> File "/usr/share/vdsm/vm.py", line 3159, in _run
> self._connection.createXML(domxml, flags),
> File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line
> 92, in wrapper
> ret = f(*args, **kwargs)
> File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2665, in
> createXML
> if ret is None:raise libvirtError('virDomainCreateXML() failed',
> conn=self)
> libvirtError: Failed to acquire lock: No space left on device
> Thread-62::DEBUG::2014-03-03 11:24:46,286::vm::2720::vm.Vm::(setDownStatus)
> vmId=`f26dd37e-13b5-430c-b2f2-ecd098b82a91`::Changed state to Down: Failed
> to acquire lock: No space left on device
>
> # df -h | grep engine
> ovirt-host01:/engine 281G 21G 261G 8%
> /rhev/data-center/mnt/ovirt-host01:_engine
>
> # sudo -u vdsm dd if=/dev/zero
> of=/rhev/data-center/mnt/ovirt-host01:_engine/2851af27-8744-445d-9fb1-a0d083c8dc82/images/0e4d270f-2f7e-4b2b-847f-f114a4ba9bdc/test
> bs=512 count=100
> 100+0 records in
> 100+0 records out
> 51200 bytes (51 kB) copie
