Re: [ovirt-devel] Java 1.8
On 05/05/2015 09:15 AM, Yedidyah Bar David wrote: - Original Message - From: "knarra" To: devel@ovirt.org Cc: "Stanislav Graf" Sent: Tuesday, May 5, 2015 8:50:38 AM Subject: [ovirt-devel] ovirt-engine replies with 503 Service Temporarily Unavailable on fresh install Hi, >From last Tuesday (Apr-28), I'm experiencing "ovirt-engine replies with 503 Service Temporarily Unavailable on fresh install" https://bugzilla.redhat.com/show_bug.cgi?id=1217023 I tried to completely reinstall before filing BZ and the issue was reproducible. I also updated today my install with latest, still the same. Am I alone who is hit by this BZ? Anything I could try? Should I reinstall again tomorrow? I saw something similar at my dev env and only after I drop-create my db it was solved. if I'll see it again I'll report on the bz. The mentioned bug does not seem very relevant. After checking with Kasturi, it seems that he is trying to run it with java-1.8.0-openjdk on RHEL6.6. EAP 6.4 supports jdk8, jboss-as-7.1.1 doesn't(will fail to load) For now, unless you care about this, just remove and install 1.7. fair, but I don't think is related to the DB problem he is seeing. Until the situation with 1.8 stabilizes, we might want to do something, not sure exactly what - perhaps change the script java-home to not accept 1.8 for now (and people that want to test that will have to override by having there a trivial java-home.local pointing at their 1.8 home), or make engine-setup notice and prompt, whatever. for overriding jdk use : OVIRT_ENGINE_JAVA_HOME=/path/to/jdk/home OVIRT_ENGINE_JAVA_HOME_FORCE=1 ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Java 1.8 (was: ovirt-engine replies with 503 Service Temporarily Unavailable on fresh install)
if I'm not wrong, this is not strictly java 8 issue. There are also java 7 versions behaving like this (jboss did not start on fresh install, peaking cpu usage) m. - Original Message - > - Original Message - > > From: "knarra" > > To: devel@ovirt.org > > Cc: "Stanislav Graf" > > Sent: Tuesday, May 5, 2015 8:50:38 AM > > Subject: [ovirt-devel] ovirt-engine replies with 503 Service Temporarily > > Unavailable on fresh install > > > > > > Hi, > > > > >From last Tuesday (Apr-28), I'm experiencing > > "ovirt-engine replies with 503 Service Temporarily Unavailable on fresh > > install" https://bugzilla.redhat.com/show_bug.cgi?id=1217023 I tried to > > completely reinstall before filing BZ and the issue was reproducible. I > > also > > updated today my install with latest, still the same. > > > > Am I alone who is hit by this BZ? Anything I could try? Should I reinstall > > again tomorrow? > > The mentioned bug does not seem very relevant. > > After checking with Kasturi, it seems that he is trying to run it with > java-1.8.0-openjdk on RHEL6.6. > > For now, unless you care about this, just remove and install 1.7. > > Until the situation with 1.8 stabilizes, we might want to do something, not > sure exactly what - perhaps change the script java-home to not accept 1.8 > for now (and people that want to test that will have to override by having > there > a trivial java-home.local pointing at their 1.8 home), or make engine-setup > notice and prompt, whatever. > -- > Didi > ___ > Devel mailing list > Devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Java 1.8
Il 05/05/2015 08:15, Yedidyah Bar David ha scritto: > - Original Message - >> From: "knarra" >> To: devel@ovirt.org >> Cc: "Stanislav Graf" >> Sent: Tuesday, May 5, 2015 8:50:38 AM >> Subject: [ovirt-devel] ovirt-engine replies with 503 Service Temporarily >> Unavailable on fresh install >> >> >> Hi, >> >> >From last Tuesday (Apr-28), I'm experiencing >> "ovirt-engine replies with 503 Service Temporarily Unavailable on fresh >> install" https://bugzilla.redhat.com/show_bug.cgi?id=1217023 I tried to >> completely reinstall before filing BZ and the issue was reproducible. I also >> updated today my install with latest, still the same. >> >> Am I alone who is hit by this BZ? Anything I could try? Should I reinstall >> again tomorrow? > > The mentioned bug does not seem very relevant. > > After checking with Kasturi, it seems that he is trying to run it with > java-1.8.0-openjdk on RHEL6.6. > > For now, unless you care about this, just remove and install 1.7. > > Until the situation with 1.8 stabilizes, we might want to do something, not > sure exactly what - perhaps change the script java-home to not accept 1.8 > for now (and people that want to test that will have to override by having > there > a trivial java-home.local pointing at their 1.8 home), or make engine-setup > notice and prompt, whatever. > Adding Oved: are we going to use 1.7 or 1.8 on EL6/EL7 ? On Fedora we only have 1.8 so there we can't enforce 1.7. Maybe we can use a config file enforcing the java home on EL6/7 as we do with JBoss. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] Java 1.8 (was: ovirt-engine replies with 503 Service Temporarily Unavailable on fresh install)
- Original Message - > From: "knarra" > To: devel@ovirt.org > Cc: "Stanislav Graf" > Sent: Tuesday, May 5, 2015 8:50:38 AM > Subject: [ovirt-devel] ovirt-engine replies with 503 Service Temporarily > Unavailable on fresh install > > > Hi, > > >From last Tuesday (Apr-28), I'm experiencing > "ovirt-engine replies with 503 Service Temporarily Unavailable on fresh > install" https://bugzilla.redhat.com/show_bug.cgi?id=1217023 I tried to > completely reinstall before filing BZ and the issue was reproducible. I also > updated today my install with latest, still the same. > > Am I alone who is hit by this BZ? Anything I could try? Should I reinstall > again tomorrow? The mentioned bug does not seem very relevant. After checking with Kasturi, it seems that he is trying to run it with java-1.8.0-openjdk on RHEL6.6. For now, unless you care about this, just remove and install 1.7. Until the situation with 1.8 stabilizes, we might want to do something, not sure exactly what - perhaps change the script java-home to not accept 1.8 for now (and people that want to test that will have to override by having there a trivial java-home.local pointing at their 1.8 home), or make engine-setup notice and prompt, whatever. -- Didi ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] ovirt-engine replies with 503 Service Temporarily Unavailable on fresh install
On 05-05-2015 2:50, knarra wrote: Hi, >From last Tuesday (Apr-28), I'm experiencing "ovirt-engine replies with 503 Service Temporarily Unavailable on fresh install" https://bugzilla.redhat.com/show_bug.cgi?id=1217023 I tried to completely reinstall before filing BZ and the issue was reproducible. I also updated today my install with latest, still the same. Am I alone who is hit by this BZ? Anything I could try? Should I reinstall again tomorrow? can some one please help with this issue. Hi, I just got an SQL error in engine.log after upgrading to latest nightbuild: 2015-05-05 02:31:49,855 WARN [org.ovirt.engine.core.bll.IconLoader] (MSC service thread 1-3) [] org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar [select * from getvmiconbyvmicondataurl()]; nested exception is org.postgresql.util.PSQLException: _*ERROR: function getvmiconbyvmicondataurl() does not exist*_ Hint: No function matches the given name and argument types. You might need to add explicit type casts. Position: 16 Since this is the second time I have problems with the DB update script, I did an "engine-cleanup" and reinstalled from scratch. Problem solved. In case you are experiencing the same issue, please provide more details so the update script can be properly fixed. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] ovirt-engine replies with 503 Service Temporarily Unavailable on fresh install
Hi, From last Tuesday (Apr-28), I'm experiencing "ovirt-engine replies with 503 Service Temporarily Unavailable on fresh install" https://bugzilla.redhat.com/show_bug.cgi?id=1217023 I tried to completely reinstall before filing BZ and the issue was reproducible. I also updated today my install with latest, still the same. Am I alone who is hit by this BZ? Anything I could try? Should I reinstall again tomorrow? can some one please help with this issue. Thanks kasturi ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [vdsm] VmDevices rework
On Mon, May 04, 2015 at 05:21:29AM -0400, Martin Polednik wrote: > > > - Original Message - > > From: "Dan Kenigsberg" > > To: "Martin Polednik" > > Cc: devel@ovirt.org > > Sent: Friday, May 1, 2015 5:06:04 PM > > Subject: Re: [ovirt-devel] [vdsm] VmDevices rework > > > > On Tue, Apr 28, 2015 at 04:28:12AM -0400, Martin Polednik wrote: > > > Hello everyone, > > > > > > I have started working on line of patches that deal with current state of > > > VM devices > > > in VDSM. There is a wiki page at [1] describing the issues, phases and > > > final goals > > > for this work. Additionally, there is formal naming system for code > > > related > > > to > > > devices. I would love to hear your opinions and comments about this > > > effort! > > > (and please note that this is very long term work) > > > > > > [1] http://www.ovirt.org/Feature/VmDevices_rework > > > > Hi Martin, > > > > It's a great and just initiative. Renaming is good, but I'd like to hear > > more about your final goal - besides the hope that it the code is > > shorter. > > > > In my opion you should state your high-level goal explicitly: > > device_object should be self-sufficient regarding: initiation, state > > change, stat extraction and stat reporting. > > > > Comments: > > 1. We want to drop the legacy conf support. In > >https://gerrit.ovirt.org/40104 we have removed support of engine<3.3 > >so production environment does not need it any more. > > > >There might be an issue with command-line test scripts, though that > >might be abusing the legacy args. At the very least it should be > >marked as deprecated. > > Therefore, the move still makes sense, as for the deprecation - I fully > agree. Will try to figure a nice way to mention it (logging and docs I guess). At the very least, you should mark any use of legacy with a log ERROR. > > > 2. dev_map is an unfortunate historical mistake. The fact that it is a > >map of device type to device_object lists helps no one. It > >should be hidden behind one or two lookup functions. Each object > >class should be able to iterate its instances, and add filtering on > >top of that. > > Interesting point, but you still need to somehow store the device > instances. Having the implementation hidden is fine (and the _device name > already suggests that) but it still needs to exist. Of course. And you may keep the current mapping for the mean while. But it should be layered away by a set of accessors. > > > 3. A definition like "Type of the device is dev_type" does not help for > >someone who knows what is dev_type. Please give examples. > >The "formal naming system" could use some wiki styling. > > Will work on that! > > > 4. I did not understand "Libvirt XML parsing and processing is dumb - > >missing orchestration object to delegate XML chunks to devices themself" > > Too terse indeed, will try to rephrase. The issue is the fact that each > dev_type > parsing iterates over all device elements in XML, leading to O(n^2) complexity > just for the parsing. The it's not XML parsing per se, but the convesion of the data into objects. Please explain this issue on wiki. > > > 5. It seems that you have further "phases" planned, but not written. > >Could you provide at least the title, or "charter" of each phase? 1.1 > >is about renaming. 1.2 is about legacy. Do you have phases 2, 3..? > > Still in process of figuring out the naming of the phases and their order, > I'll try to add them when it makes sense (I just can't spit 10 names out of > my head right now that would make sense in a long term). > > > Death (or at least diet) to vm.py! > > +1 :) Thanks for the review! ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Sanlock - "Add_lockspace fail" - WAS: "Please activate the master Storage Domain first"
> > May 1 17:26:37 h5 sanlock[637]: 2015-05-01 17:26:37-0300 9118 > > [643]: s909 add_lockspace fail result -5 > > May 1 17:26:46 h5 sanlock[637]: 2015-05-01 17:26:46-0300 9128 > > [12892]: read_sectors delta_leader offset 512 rv -5 > > > > /rhev/data-center/mnt/glusterSD/h4.imatronix.com:vdisks/ba7be27f-aee5-4436-ae9a-0764f551f9a7/dom_md/ids > > David, can you explain what is the meaning of "rv -5"? EIO is returned when sanlock reads the file. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] oVirt Node Weekly Meeting Minutes - 2015-05-04
= #ovirt: oVirt Node Weekly Meeting = Meeting started by fabiand at 14:04:15 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2015/ovirt.2015-05-04-14.04.log.html . Meeting summary --- * Agenda (fabiand, 14:04:29) * ovirt-node in Fedora (fabiand, 14:04:41) * Other Items (fabiand, 14:04:44) * ovirt-node in Fedora (fabiand, 14:06:01) * ovirt-node has been orphaned in Fedora as of last week. (fabiand, 14:06:26) * Other Items (fabiand, 14:07:38) * el7 Node builds are broken due to gluster changes (fabiand, 14:09:23) * Jenkins el7/master job needs an update to fix the glusterfs issue (fabiand, 14:12:03) * ACTION: rbarry to work with tlitovsk to sort out the glusterfs issue on el7/master (fabiand, 14:13:45) Meeting ended at 14:15:17 UTC. Action Items * rbarry to work with tlitovsk to sort out the glusterfs issue on el7/master Action Items, by person --- * rbarry * rbarry to work with tlitovsk to sort out the glusterfs issue on el7/master * tlitovsk * rbarry to work with tlitovsk to sort out the glusterfs issue on el7/master * **UNASSIGNED** * (none) People Present (lines said) --- * fabiand (41) * tlitovsk (10) * sbonazzo (4) * ovirtbot (2) * rbarry (1) * amureini (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] oVirt Node Weekly Meeting Minutes - 2015-04-27
= #ovirt: oVirt Node Weekly Meeting = Meeting started by fabiand at 14:01:12 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2015/ovirt.2015-04-27-14.01.log.html . Meeting summary --- * Agenda (fabiand, 14:01:25) * Other Items (fabiand, 14:01:31) * Other Items (fabiand, 14:01:37) * LINK: https://gerrit.ovirt.org/#/c/39304/ (fabiand, 14:03:23) * ACTION: fabiand and tlitovsk to review https://gerrit.ovirt.org/#/c/39304/ (fabiand, 14:04:35) Meeting ended at 14:02:23 UTC. Action Items * fabiand and tlitovsk to review https://gerrit.ovirt.org/#/c/39304/ Action Items, by person --- * fabiand * fabiand and tlitovsk to review https://gerrit.ovirt.org/#/c/39304/ * tlitovsk * fabiand and tlitovsk to review https://gerrit.ovirt.org/#/c/39304/ * **UNASSIGNED** * (none) People Present (lines said) --- * alonbl (46) * kripper (33) * sbonazzo (33) * didi (29) * mr_chris (29) * fabiand (24) * YamakasY (23) * wakemaster (21) * feldspar (18) * fsimonce (16) * danken (11) * PA_dot (9) * oved (7) * jvandewege (7) * bkp (7) * evilissimo2 (6) * eedri|lunch (6) * alonbl_ (6) * kripper1 (5) * glafouille (4) * dcaro (4) * nsoffer (4) * rbarry (3) * mvk (3) * ovirtbot (3) * dougsland (2) * Svedrin (2) * loganmc10 (2) * stefanlsd (2) * tools (2) * ade (2) * atkachuk (2) * tlitovsk (2) * wilsonwr (2) * Atonaby (2) * z3d3 (2) * sbonazzo|mtg (2) * dyasny (1) * tal (1) * eedri|mtg (1) * tlitovsk_ (1) * ewoud (1) * nostradamuz (1) * karimb (1) * mtayer (1) * prussell (1) * lvernia (1) * jflorian-local (1) * Dw_Sn (1) * pdangur (1) * masayag (1) * bkorren (1) * gotgnu (1) * sudoshred (1) * bazulay (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
On 4 May 2015, at 13:26, Sandro Bonazzola wrote: > Hi, > just a quick reminder that oVirt 3.6.0 Alpha is scheduled for May 6th[1]. > > > ACTION: Maintainers, please check Alpha Release Criteria[2] to ensure we can > release this Alpha on Wednesday. >MUST: All sources must be available on ovirt.org >MUST: All packages listed by subprojects must be available in the > repository >MUST: All accepted features must be substantially complete and in a > testable state and enabled by default -- if so specified by the change > > About this last "MUST" I think that we should drop it having changed the > release process after release criteria discussion and move it to beta release > criteria. I agree. It's more than a month till FC so I expect quite a few features are not completed yet > > VOTE: please ack for moving "MUST: All accepted features must be > substantially complete and in a testable state and enabled by default -- if so > specified by the change" to beta release criteria > > ACTION: Maintainers: please send a list of the packages provided by your > sub-project. > If no list will be provided, the list will be taken by the jenkins nightly > publisher job[3] used for publishing ovirt-master-snapshot. > > ACTION: Maintainers and QE: please fill the Test Day wiki page[4] > > > [1] http://www.ovirt.org/OVirt_3.6_Release_Management#Key_Milestones > [2] http://www.ovirt.org/OVirt_3.6_Release_Management#Alpha_Release_Criteria > [3] > http://jenkins.ovirt.org/view/Publishers/job/publish_ovirt_rpms_nightly_master/ > [4] http://www.ovirt.org/OVirt_3.6_Test_Day > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > ___ > Devel mailing list > Devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
Hi, just a quick reminder that oVirt 3.6.0 Alpha is scheduled for May 6th[1]. ACTION: Maintainers, please check Alpha Release Criteria[2] to ensure we can release this Alpha on Wednesday. MUST: All sources must be available on ovirt.org MUST: All packages listed by subprojects must be available in the repository MUST: All accepted features must be substantially complete and in a testable state and enabled by default -- if so specified by the change About this last "MUST" I think that we should drop it having changed the release process after release criteria discussion and move it to beta release criteria. VOTE: please ack for moving "MUST: All accepted features must be substantially complete and in a testable state and enabled by default -- if so specified by the change" to beta release criteria ACTION: Maintainers: please send a list of the packages provided by your sub-project. If no list will be provided, the list will be taken by the jenkins nightly publisher job[3] used for publishing ovirt-master-snapshot. ACTION: Maintainers and QE: please fill the Test Day wiki page[4] [1] http://www.ovirt.org/OVirt_3.6_Release_Management#Key_Milestones [2] http://www.ovirt.org/OVirt_3.6_Release_Management#Alpha_Release_Criteria [3] http://jenkins.ovirt.org/view/Publishers/job/publish_ovirt_rpms_nightly_master/ [4] http://www.ovirt.org/OVirt_3.6_Test_Day -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [vdsm] VmDevices rework
- Original Message - > From: "Dan Kenigsberg" > To: "Martin Polednik" > Cc: devel@ovirt.org > Sent: Friday, May 1, 2015 5:06:04 PM > Subject: Re: [ovirt-devel] [vdsm] VmDevices rework > > On Tue, Apr 28, 2015 at 04:28:12AM -0400, Martin Polednik wrote: > > Hello everyone, > > > > I have started working on line of patches that deal with current state of > > VM devices > > in VDSM. There is a wiki page at [1] describing the issues, phases and > > final goals > > for this work. Additionally, there is formal naming system for code related > > to > > devices. I would love to hear your opinions and comments about this effort! > > (and please note that this is very long term work) > > > > [1] http://www.ovirt.org/Feature/VmDevices_rework > > Hi Martin, > > It's a great and just initiative. Renaming is good, but I'd like to hear > more about your final goal - besides the hope that it the code is > shorter. > > In my opion you should state your high-level goal explicitly: > device_object should be self-sufficient regarding: initiation, state > change, stat extraction and stat reporting. > > Comments: > 1. We want to drop the legacy conf support. In >https://gerrit.ovirt.org/40104 we have removed support of engine<3.3 >so production environment does not need it any more. > >There might be an issue with command-line test scripts, though that >might be abusing the legacy args. At the very least it should be >marked as deprecated. Therefore, the move still makes sense, as for the deprecation - I fully agree. Will try to figure a nice way to mention it (logging and docs I guess). > 2. dev_map is an unfortunate historical mistake. The fact that it is a >map of device type to device_object lists helps no one. It >should be hidden behind one or two lookup functions. Each object >class should be able to iterate its instances, and add filtering on >top of that. Interesting point, but you still need to somehow store the device instances. Having the implementation hidden is fine (and the _device name already suggests that) but it still needs to exist. > 3. A definition like "Type of the device is dev_type" does not help for >someone who knows what is dev_type. Please give examples. >The "formal naming system" could use some wiki styling. Will work on that! > 4. I did not understand "Libvirt XML parsing and processing is dumb - >missing orchestration object to delegate XML chunks to devices themself" Too terse indeed, will try to rephrase. The issue is the fact that each dev_type parsing iterates over all device elements in XML, leading to O(n^2) complexity just for the parsing. > 5. It seems that you have further "phases" planned, but not written. >Could you provide at least the title, or "charter" of each phase? 1.1 >is about renaming. 1.2 is about legacy. Do you have phases 2, 3..? Still in process of figuring out the naming of the phases and their order, I'll try to add them when it makes sense (I just can't spit 10 names out of my head right now that would make sense in a long term). > Death (or at least diet) to vm.py! +1 :) Thanks for the review! > Dan. > > ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] No package vdsm available
On 05/04/2015 11:57 AM, Sandro Bonazzola wrote: Il 04/05/2015 07:16, knarra ha scritto: Hi, I am trying to install vdsm on RHEL6.6 machine. When i run the command 'yum install vdsm' the ouput says "No Package vdsm available" Hi, VDSM is not built anymore for RHEL 6.6 and won't be available in 3.6. VDSM for el6 will still be available in 3.5 version but for taking advantage of 3.6 features you'll need to upgrade your system to el7. Thank you Sandro. Following are the repos enabled in my sytem. -rw-r--r--. 1 root root 957 Nov 5 2012 epel.repo -rw-r--r--. 1 root root 1056 Nov 5 2012 epel-testing.repo -rw-r--r--. 1 root root 2550 Apr 22 19:15 ovirt-master-dependencies.repo -rw-r--r--. 1 root root 609 Apr 22 18:44 ovirt-master-snapshot.repo -rw-r--r--. 1 root root 358 Apr 22 18:09 redhat.repo -rw-r--r--. 1 root root 529 Sep 15 2014 rhel-source.repo can some one please help me to resolve this issue. Thanks kasturi. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
