[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_mast... [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
On 4 May 2015, at 13:26, Sandro Bonazzola <sbonazzo@redhat.com> 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_mast... [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
Hi, IMO we should add a warning to release notes that oVirt 3.6 Alpha requires OpenJDK 1.7 for engine and it will not work with OpenJDK 1.8 (even though our current packaging requirements allows OpenJDK 1.8). Thanks Martin ----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: devel@ovirt.org, Users@ovirt.org Sent: Monday, May 4, 2015 1:26:07 PM Subject: [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_mast... [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
Il 06/05/2015 10:47, Martin Perina ha scritto:
Hi,
IMO we should add a warning to release notes that oVirt 3.6 Alpha requires OpenJDK 1.7 for engine and it will not work with OpenJDK 1.8 (even though our current packaging requirements allows OpenJDK 1.8).
You're welcome to add notes to http://www.ovirt.org/OVirt_3.6_Release_Notes :-) This one, I'll add myself.
Thanks
Martin
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: devel@ovirt.org, Users@ovirt.org Sent: Monday, May 4, 2015 1:26:07 PM Subject: [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_mast... [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
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Martin Perina" <mperina@redhat.com> Cc: Users@ovirt.org, devel@ovirt.org Sent: Wednesday, May 6, 2015 12:19:17 PM Subject: Re: [ovirt-users] [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
Il 06/05/2015 10:47, Martin Perina ha scritto:
Hi,
IMO we should add a warning to release notes that oVirt 3.6 Alpha requires OpenJDK 1.7 for engine and it will not work with OpenJDK 1.8 (even though our current packaging requirements allows OpenJDK 1.8).
You're welcome to add notes to http://www.ovirt.org/OVirt_3.6_Release_Notes :-) This one, I'll add myself.
Already done, under Known Issues. -- Didi
----- Original Message -----
From: "Yedidyah Bar David" <didi@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Martin Perina" <mperina@redhat.com>, Users@ovirt.org, devel@ovirt.org Sent: Wednesday, May 6, 2015 11:46:13 AM Subject: Re: [ovirt-users] [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Martin Perina" <mperina@redhat.com> Cc: Users@ovirt.org, devel@ovirt.org Sent: Wednesday, May 6, 2015 12:19:17 PM Subject: Re: [ovirt-users] [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
Il 06/05/2015 10:47, Martin Perina ha scritto:
Hi,
IMO we should add a warning to release notes that oVirt 3.6 Alpha requires OpenJDK 1.7 for engine and it will not work with OpenJDK 1.8 (even though our current packaging requirements allows OpenJDK 1.8).
You're welcome to add notes to http://www.ovirt.org/OVirt_3.6_Release_Notes :-) This one, I'll add myself.
Already done, under Known Issues. -- Didi
Well, I wouldn't say that it's a known issue, because we never said that oVirt can be executed on different JDK than 1.7, but ok. Martin
----- Original Message -----
From: "Martin Perina" <mperina@redhat.com> To: "Yedidyah Bar David" <didi@redhat.com> Cc: Users@ovirt.org, devel@ovirt.org Sent: Wednesday, May 6, 2015 1:40:54 PM Subject: Re: [ovirt-users] [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
----- Original Message -----
From: "Yedidyah Bar David" <didi@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Martin Perina" <mperina@redhat.com>, Users@ovirt.org, devel@ovirt.org Sent: Wednesday, May 6, 2015 11:46:13 AM Subject: Re: [ovirt-users] [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Martin Perina" <mperina@redhat.com> Cc: Users@ovirt.org, devel@ovirt.org Sent: Wednesday, May 6, 2015 12:19:17 PM Subject: Re: [ovirt-users] [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
Il 06/05/2015 10:47, Martin Perina ha scritto:
Hi,
IMO we should add a warning to release notes that oVirt 3.6 Alpha requires OpenJDK 1.7 for engine and it will not work with OpenJDK 1.8 (even though our current packaging requirements allows OpenJDK 1.8).
You're welcome to add notes to http://www.ovirt.org/OVirt_3.6_Release_Notes :-) This one, I'll add myself.
Already done, under Known Issues. -- Didi
Well, I wouldn't say that it's a known issue, because we never said that oVirt can be executed on different JDK than 1.7, but ok.
More like a release note.
Martin
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
----- Original Message -----
From: "Oved Ourfali" <ovedo@redhat.com> To: "Martin Perina" <mperina@redhat.com> Cc: "Yedidyah Bar David" <didi@redhat.com>, Users@ovirt.org, devel@ovirt.org Sent: Wednesday, May 6, 2015 1:44:39 PM Subject: Re: [ovirt-users] [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
----- Original Message -----
From: "Martin Perina" <mperina@redhat.com> To: "Yedidyah Bar David" <didi@redhat.com> Cc: Users@ovirt.org, devel@ovirt.org Sent: Wednesday, May 6, 2015 1:40:54 PM Subject: Re: [ovirt-users] [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
----- Original Message -----
From: "Yedidyah Bar David" <didi@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Martin Perina" <mperina@redhat.com>, Users@ovirt.org, devel@ovirt.org Sent: Wednesday, May 6, 2015 11:46:13 AM Subject: Re: [ovirt-users] [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Martin Perina" <mperina@redhat.com> Cc: Users@ovirt.org, devel@ovirt.org Sent: Wednesday, May 6, 2015 12:19:17 PM Subject: Re: [ovirt-users] [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
Il 06/05/2015 10:47, Martin Perina ha scritto:
Hi,
IMO we should add a warning to release notes that oVirt 3.6 Alpha requires OpenJDK 1.7 for engine and it will not work with OpenJDK 1.8 (even though our current packaging requirements allows OpenJDK 1.8).
You're welcome to add notes to http://www.ovirt.org/OVirt_3.6_Release_Notes :-) This one, I'll add myself.
Already done, under Known Issues. -- Didi
Well, I wouldn't say that it's a known issue, because we never said that oVirt can be executed on different JDK than 1.7, but ok.
More like a release note.
Well, you are both welcome to edit :-) IMHO it's a Known Issue that a naive attempt to install the engine on an up-to-date EL6 will result in a non-functioning engine. The rest is details. Best, -- Didi
----- Original Message -----
From: "Yedidyah Bar David" <didi@redhat.com> To: "Oved Ourfali" <ovedo@redhat.com> Cc: Users@ovirt.org, devel@ovirt.org Sent: Wednesday, May 6, 2015 2:21:39 PM Subject: Re: [ovirt-users] [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
----- Original Message -----
From: "Oved Ourfali" <ovedo@redhat.com> To: "Martin Perina" <mperina@redhat.com> Cc: "Yedidyah Bar David" <didi@redhat.com>, Users@ovirt.org, devel@ovirt.org Sent: Wednesday, May 6, 2015 1:44:39 PM Subject: Re: [ovirt-users] [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
----- Original Message -----
From: "Martin Perina" <mperina@redhat.com> To: "Yedidyah Bar David" <didi@redhat.com> Cc: Users@ovirt.org, devel@ovirt.org Sent: Wednesday, May 6, 2015 1:40:54 PM Subject: Re: [ovirt-users] [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
----- Original Message -----
From: "Yedidyah Bar David" <didi@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Martin Perina" <mperina@redhat.com>, Users@ovirt.org, devel@ovirt.org Sent: Wednesday, May 6, 2015 11:46:13 AM Subject: Re: [ovirt-users] [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Martin Perina" <mperina@redhat.com> Cc: Users@ovirt.org, devel@ovirt.org Sent: Wednesday, May 6, 2015 12:19:17 PM Subject: Re: [ovirt-users] [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
Il 06/05/2015 10:47, Martin Perina ha scritto:
Hi,
IMO we should add a warning to release notes that oVirt 3.6 Alpha requires OpenJDK 1.7 for engine and it will not work with OpenJDK 1.8 (even though our current packaging requirements allows OpenJDK 1.8).
You're welcome to add notes to http://www.ovirt.org/OVirt_3.6_Release_Notes :-) This one, I'll add myself.
Already done, under Known Issues. -- Didi
Well, I wouldn't say that it's a known issue, because we never said that oVirt can be executed on different JDK than 1.7, but ok.
More like a release note.
Well, you are both welcome to edit :-)
IMHO it's a Known Issue that a naive attempt to install the engine on an up-to-date EL6 will result in a non-functioning engine. The rest is details.
Now added 'yum install java-1.7.0-openjdk' to installation instructions. Best, -- Didi
On May 6, 2015 4:47 AM, "Martin Perina" <mperina@redhat.com> wrote:
Hi,
IMO we should add a warning to release notes that oVirt 3.6 Alpha requires OpenJDK 1.7 for engine and it will not work with OpenJDK 1.8 (even though our current packaging requirements allows OpenJDK 1.8).
Why is it not considered a bug that our packaging requirements allow a version of OpenJDK that we know will not work? Fixing the package requirements to exclude 1.8 would go a long way toward preventing failed installations (or make failures more obvious). Is there a bug open to track fixing oVirt to work with OpenJDK 1.8? -Bob
Thanks
Martin
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: devel@ovirt.org, Users@ovirt.org Sent: Monday, May 4, 2015 1:26:07 PM Subject: [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_mast...
[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
----- Original Message -----
From: "Bob Doolittle" <bob@doolittle.us.com> To: "Martin Perina" <mperina@redhat.com> Cc: devel@ovirt.org, "Sandro Bonazzola" <sbonazzo@redhat.com>, Users@ovirt.org Sent: Wednesday, May 6, 2015 1:33:03 PM Subject: Re: [ovirt-devel] [QE][VOTE][ACTION REQUIRED] oVirt 3.6.0 Alpha release this week
On May 6, 2015 4:47 AM, "Martin Perina" <mperina@redhat.com> wrote:
Hi,
IMO we should add a warning to release notes that oVirt 3.6 Alpha requires OpenJDK 1.7 for engine and it will not work with OpenJDK 1.8 (even though our current packaging requirements allows OpenJDK 1.8).
Why is it not considered a bug that our packaging requirements allow a version of OpenJDK that we know will not work? Fixing the package requirements to exclude 1.8 would go a long way toward preventing failed installations (or make failures more obvious).
Is there a bug open to track fixing oVirt to work with OpenJDK 1.8?
When we will move to WildFly [1], we could use also OpenJDK 1.8, but not before. Martin [1] https://bugzilla.redhat.com/show_bug.cgi?id=1121327
-Bob
Thanks
Martin
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: devel@ovirt.org, Users@ovirt.org Sent: Monday, May 4, 2015 1:26:07 PM Subject: [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_mast...
[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
This is a multi-part message in MIME format. --------------000302040302020901000100 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Hi=2C Looking forward to bz 1049994 Allow choosing network interface for gluster domain traffic=2E Currently I have the bricks on a different storage network and can=27t get= the volume details or profile it=2E Will this be handled in 3=2E6 properly=3F I don=27t see any changes in gerr= it regarding this=2C but I can be ovelooking it=2E The errors I get currently=3A Could not fetch brick profile stats 2015-05-06 10=3A34=3A22=2C430 ERROR =5Borg=2Eovirt=2Eengine=2Ecore=2Ebll=2Egluster=2EGetGlusterVolumeProfil= eInfoQuery=5D =28ajp--127=2E0=2E0=2E1-8702-27=29 Query GetGlusterVolumeProfileInfoQue= ry failed=2E Exception message is null =3A java=2Elang=2ENullPointerExcept= ion=3A java=2Elang=2ENullPointerException and Error in fetching the brick details=2C please try again=2E 2015-05-06 10=3A36=3A14=2C205 ERROR =5Borg=2Eovirt=2Eengine=2Ecore=2Ebll=2Egluster=2EGetGlusterVolumeAdvanc= edDetailsQuery=5D =28ajp--127=2E0=2E0=2E1-8702-55=29 Query GetGlusterVolumeAdvancedDetail= sQuery failed=2E Exception message is VdcBLLException=3A Volume status failed= error=3A Staging failed on *=2E*=2E*=2E*=2E Error=3A No brick glustertest1=2Enetbulae=2Etest/gluster/brick1 in volume data Staging failed on *=2E*=2E*=2E*=2E Error=3A No brick=20 glustertest1=2Enetbulae=2Etest=3A/gluster/brick1 in volume data return code=3A -1 =28Failed with error GlusterVolumeStatusFailed and code 4157=29 =3A org=2Eovirt=2Eengine=2Ecore=2Ecommon=2Eerrors=2EVdcBLL= Exception=3A VdcBLLException=3A Volume status failed error=3A Staging failed on *=2E*=2E*=2E*=2E Error=3A No brick=20 glustertest1=2Enetbulae=2Etest=3A/gluster/brick1 in volume data Staging failed on *=2E*=2E*=2E*=2E Error=3A No brick=20 glustertest1=2Enetbulae=2Etest=3A/gluster/brick1 in volume data return code=3A -1 =28Failed with error GlusterVolumeStatusFailed and code 4157=29=3A org=2Eovirt=2Eengine=2Ecore=2Ecommon=2Eerrors=2EVdcBLLE= xception=3A VdcBLLException=3A Volume status failed error=3A Staging failed on *=2E*=2E*=2E*=2E Error=3A No brick=20 glustertest1=2Enetbulae=2Etest=3A/gluster/brick1 in volume data Staging failed on *=2E*=2E*=2E*=2E Error=3A No brick=20 glustertest1=2Enetbulae=2Etest=3A/gluster/brick1 in volume data return code=3A -1 =28Failed with error GlusterVolumeStatusFailed and code 4157=29 Met vriendelijke groet=2C With kind regards=2C Jorick Astrego Netbulae Virtualization Experts=20 ---------------- =09Tel=3A 053 20 30 270 =09info=40netbulae=2Eeu =09Staalsteden 4-3A =09KvK= 08198180 =09Fax=3A 053 20 30 271 =09www=2Enetbulae=2Eeu =097547 TA Enschede =09BTW= NL821234584B01 ---------------- --------------000302040302020901000100 Content-Type: text/html; charset="windows-1252" Content-Transfer-Encoding: quoted-printable =3Chtml=3E =3Chead=3E =3Cmeta content=3D=22text/html=3B charset=3Dwindows-1252=22 http-equiv=3D=22Content-Type=22=3E =3C/head=3E =3Cbody bgcolor=3D=22=23FFFFFF=22 text=3D=22=23000000=22=3E Hi=2C=3Cbr=3E =3Cbr=3E Looking forward to =3Cmeta http-equiv=3D=22content-type=22 content=3D=22text/html=3B charset=3Dwindows-1252=22=3E =3Cmeta name=3D=22generator=22 content=3D=22Sheets=22=3E =3Cstyle type=3D=22text/css=22=3E=3C!--td =7Bborder=3A 1px solid =23ccc= =3B=7Dbr =7Bmso-data-placement=3Asame-cell=3B=7D--=3E=3C/style=3Ebz 1049994=A0=A0=A0 Allow choosing network interface for gluster domain traffic=2E=3Cbr=3E =3Cbr=3E Currently I have the bricks on a different storage network and can=27t= get the volume details or profile it=2E =3Cbr=3E =3Cbr=3E Will this be handled in 3=2E6 properly=3F I don=27t see any changes in= gerrit regarding this=2C but I can be ovelooking it=2E=3Cbr=3E =3Cbr=3E The errors I get currently=3A=3Cbr=3E =3Cbr=3E =3Cblockquote=3ECould not fetch brick profile stats=3Cbr=3E =3C/blockquote=3E =3Cblockquote=3E2015-05-06 10=3A34=3A22=2C430 ERROR =5Borg=2Eovirt=2Eengine=2Ecore=2Ebll=2Egluster=2EGetGlusterVolumeProf= ileInfoQuery=5D =28ajp--127=2E0=2E0=2E1-8702-27=29 Query GetGlusterVolumeProfileInfoQ= uery failed=2E Exception message is null =3A java=2Elang=2ENullPointerException=3A java=2Elang=2ENullPointerExcept= ion=3Cbr=3E =3Cbr=3E =3C/blockquote=3E and=3Cbr=3E =3Cblockquote=3EError in fetching the brick details=2C please try again= =2E=3Cbr=3E =3Cbr=3E 2015-05-06 10=3A36=3A14=2C205 ERROR =5Borg=2Eovirt=2Eengine=2Ecore=2Ebll=2Egluster=2EGetGlusterVolumeAdva= ncedDetailsQuery=5D =28ajp--127=2E0=2E0=2E1-8702-55=29 Query GetGlusterVolumeAdvancedDetailsQuery failed=2E Exception message is= VdcBLLException=3A Volume status failed=3Cbr=3E error=3A Staging failed on *=2E*=2E*=2E*=2E Error=3A No brick glustertest1=2Enetbulae=2Etest/gluster/brick1 in volume data=3Cbr=3E= Staging failed on *=2E*=2E*=2E*=2E Error=3A No brick=A0 glustertest1=2Enetbulae=2Etest=3A/gluster/brick1 in volume data=3Cbr= =3E return code=3A -1 =28Failed with error GlusterVolumeStatusFailed and= code 4157=29 =3A org=2Eovirt=2Eengine=2Ecore=2Ecommon=2Eerrors=2EVdcB= LLException=3A VdcBLLException=3A Volume status failed=3Cbr=3E error=3A Staging failed on *=2E*=2E*=2E*=2E Error=3A No brick=A0 glustertest1=2Enetbulae=2Etest=3A/gluster/brick1 in volume data=3Cbr= =3E Staging failed on *=2E*=2E*=2E*=2E Error=3A No brick=A0 glustertest1=2Enetbulae=2Etest=3A/gluster/brick1 in volume data=3Cbr= =3E return code=3A -1 =28Failed with error GlusterVolumeStatusFailed and= code 4157=29=3A org=2Eovirt=2Eengine=2Ecore=2Ecommon=2Eerrors=2EVdcBL= LException=3A VdcBLLException=3A Volume status failed=3Cbr=3E error=3A Staging failed on *=2E*=2E*=2E*=2E Error=3A No brick=A0 glustertest1=2Enetbulae=2Etest=3A/gluster/brick1 in volume data=3Cbr= =3E Staging failed on *=2E*=2E*=2E*=2E Error=3A No brick=A0 glustertest1=2Enetbulae=2Etest=3A/gluster/brick1 in volume data=3Cbr= =3E return code=3A -1 =28Failed with error GlusterVolumeStatusFailed and= code 4157=29=3Cbr=3E =3C/blockquote=3E =3Cblockquote=3E=3Cbr=3E =3C/blockquote=3E =20= =3CBR /=3E =3CBR /=3E =3Cb style=3D=22color=3A=23604c78=22=3E=3C/b=3E=3Cbr=3E=3Cspan style=3D=22c= olor=3A=23604c78=3B=22=3E=3Cfont color=3D=22000000=22=3E=3Cspan style=3D=22= mso-fareast-language=3Aen-gb=3B=22 lang=3D=22NL=22=3EMet vriendelijke groet= =2C With kind regards=2C=3Cbr=3E=3Cbr=3E=3C/span=3EJorick Astrego=3C/font= =3E=3C/span=3E=3Cb style=3D=22color=3A=23604c78=22=3E=3Cbr=3E=3Cbr=3ENetbul= ae Virtualization Experts =3C/b=3E=3Cbr=3E=3Chr style=3D=22border=3Anone=3B= border-top=3A1px solid =23ccc=3B=22=3E=3Ctable style=3D=22width=3A 522px=22= =3E=3Ctbody=3E=3Ctr=3E=3Ctd style=3D=22width=3A 130px=3Bfont-size=3A 10px= =22=3ETel=3A 053 20 30 270=3C/td=3E =3Ctd style=3D=22width=3A 130px=3Bf= ont-size=3A 10px=22=3Einfo=40netbulae=2Eeu=3C/td=3E =3Ctd style=3D=22wid= th=3A 130px=3Bfont-size=3A 10px=22=3EStaalsteden 4-3A=3C/td=3E =3Ctd sty= le=3D=22width=3A 130px=3Bfont-size=3A 10px=22=3EKvK 08198180=3C/td=3E=3C/tr= =3E=3Ctr=3E =3Ctd style=3D=22width=3A 130px=3Bfont-size=3A 10px=22=3EFax= =3A 053 20 30 271=3C/td=3E =3Ctd style=3D=22width=3A 130px=3Bfont-size= =3A 10px=22=3Ewww=2Enetbulae=2Eeu=3C/td=3E =3Ctd style=3D=22width=3A 130= px=3Bfont-size=3A 10px=22=3E7547 TA Enschede=3C/td=3E =3Ctd style=3D=22w= idth=3A 130px=3Bfont-size=3A 10px=22=3EBTW NL821234584B01=3C/td=3E=3C/tr=3E= =3C/tbody=3E=3C/table=3E=3Cbr=3E=3Chr style=3D=22border=3Anone=3Bborder-top= =3A1px solid =23ccc=3B=22=3E=3CBR /=3E =3C/body=3E =3C/html=3E --------------000302040302020901000100--
This is a multi-part message in MIME format. --------------090006090607030504020009 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 05/06/2015 05:33 PM, Jorick Astrego wrote:
Hi,
Looking forward to bz 1049994 Allow choosing network interface for gluster domain traffic.
Currently I have the bricks on a different storage network and can't get the volume details or profile it.
Will this be handled in 3.6 properly? I don't see any changes in gerrit regarding this, but I can be ovelooking it.
The errors I get currently:
Could not fetch brick profile stats
2015-05-06 10:34:22,430 ERROR [org.ovirt.engine.core.bll.gluster.GetGlusterVolumeProfileInfoQuery] (ajp--127.0.0.1-8702-27) Query GetGlusterVolumeProfileInfoQuery failed. Exception message is null : java.lang.NullPointerException: java.lang.NullPointerException
and
Error in fetching the brick details, please try again.
2015-05-06 10:36:14,205 ERROR [org.ovirt.engine.core.bll.gluster.GetGlusterVolumeAdvancedDetailsQuery] (ajp--127.0.0.1-8702-55) Query GetGlusterVolumeAdvancedDetailsQuery failed. Exception message is VdcBLLException: Volume status failed error: Staging failed on *.*.*.*. Error: No brick glustertest1.netbulae.test/gluster/brick1 in volume data Staging failed on *.*.*.*. Error: No brick glustertest1.netbulae.test:/gluster/brick1 in volume data return code: -1 (Failed with error GlusterVolumeStatusFailed and code 4157) : org.ovirt.engine.core.common.errors.VdcBLLException: VdcBLLException: Volume status failed error: Staging failed on *.*.*.*. Error: No brick glustertest1.netbulae.test:/gluster/brick1 in volume data Staging failed on *.*.*.*. Error: No brick glustertest1.netbulae.test:/gluster/brick1 in volume data return code: -1 (Failed with error GlusterVolumeStatusFailed and code 4157): org.ovirt.engine.core.common.errors.VdcBLLException: VdcBLLException: Volume status failed error: Staging failed on *.*.*.*. Error: No brick glustertest1.netbulae.test:/gluster/brick1 in volume data Staging failed on *.*.*.*. Error: No brick glustertest1.netbulae.test:/gluster/brick1 in volume data return code: -1 (Failed with error GlusterVolumeStatusFailed and code 4157)
Met vriendelijke groet, With kind regards,
Jorick Astrego*
Netbulae Virtualization Experts * ------------------------------------------------------------------------ Tel: 053 20 30 270 info@netbulae.eu Staalsteden 4-3A KvK 08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01
------------------------------------------------------------------------
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Hi,
Can you please check what does your gluster peer status on each of your nodes return? I guess they are in disconnected state and that is the reason you are not able to view these details. Thanks kasturi --------------090006090607030504020009 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit <html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 05/06/2015 05:33 PM, Jorick Astrego wrote:<br> </div> <blockquote cite="mid:554A031A.1060200@netbulae.eu" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> Hi,<br> <br> Looking forward to <meta http-equiv="content-type" content="text/html; charset=windows-1252"> <meta name="generator" content="Sheets"> <style type="text/css"><!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}--></style>bz 1049994 Allow choosing network interface for gluster domain traffic.<br> <br> Currently I have the bricks on a different storage network and can't get the volume details or profile it. <br> <br> Will this be handled in 3.6 properly? I don't see any changes in gerrit regarding this, but I can be ovelooking it.<br> <br> The errors I get currently:<br> <br> <blockquote>Could not fetch brick profile stats<br> </blockquote> <blockquote>2015-05-06 10:34:22,430 ERROR [org.ovirt.engine.core.bll.gluster.GetGlusterVolumeProfileInfoQuery] (ajp--127.0.0.1-8702-27) Query GetGlusterVolumeProfileInfoQuery failed. Exception message is null : java.lang.NullPointerException: java.lang.NullPointerException<br> <br> </blockquote> and<br> <blockquote>Error in fetching the brick details, please try again.<br> <br> 2015-05-06 10:36:14,205 ERROR [org.ovirt.engine.core.bll.gluster.GetGlusterVolumeAdvancedDetailsQuery] (ajp--127.0.0.1-8702-55) Query GetGlusterVolumeAdvancedDetailsQuery failed. Exception message is VdcBLLException: Volume status failed<br> error: Staging failed on *.*.*.*. Error: No brick glustertest1.netbulae.test/gluster/brick1 in volume data<br> Staging failed on *.*.*.*. Error: No brick glustertest1.netbulae.test:/gluster/brick1 in volume data<br> return code: -1 (Failed with error GlusterVolumeStatusFailed and code 4157) : org.ovirt.engine.core.common.errors.VdcBLLException: VdcBLLException: Volume status failed<br> error: Staging failed on *.*.*.*. Error: No brick glustertest1.netbulae.test:/gluster/brick1 in volume data<br> Staging failed on *.*.*.*. Error: No brick glustertest1.netbulae.test:/gluster/brick1 in volume data<br> return code: -1 (Failed with error GlusterVolumeStatusFailed and code 4157): org.ovirt.engine.core.common.errors.VdcBLLException: VdcBLLException: Volume status failed<br> error: Staging failed on *.*.*.*. Error: No brick glustertest1.netbulae.test:/gluster/brick1 in volume data<br> Staging failed on *.*.*.*. Error: No brick glustertest1.netbulae.test:/gluster/brick1 in volume data<br> return code: -1 (Failed with error GlusterVolumeStatusFailed and code 4157)<br> </blockquote> <blockquote><br> </blockquote> <br> <br> <br> <span style="color:#604c78;"><font color="000000"><span style="mso-fareast-language:en-gb;" lang="NL">Met vriendelijke groet, With kind regards,<br> <br> </span>Jorick Astrego</font></span><b style="color:#604c78"><br> <br> Netbulae Virtualization Experts </b><br> <hr style="border:none;border-top:1px solid #ccc;"> <table style="width: 522px"> <tbody> <tr> <td style="width: 130px;font-size: 10px">Tel: 053 20 30 270</td> <td style="width: 130px;font-size: 10px"><a class="moz-txt-link-abbreviated" href="mailto:info@netbulae.eu">info@netbulae.eu</a></td> <td style="width: 130px;font-size: 10px">Staalsteden 4-3A</td> <td style="width: 130px;font-size: 10px">KvK 08198180</td> </tr> <tr> <td style="width: 130px;font-size: 10px">Fax: 053 20 30 271</td> <td style="width: 130px;font-size: 10px"><a class="moz-txt-link-abbreviated" href="http://www.netbulae.eu">www.netbulae.eu</a></td> <td style="width: 130px;font-size: 10px">7547 TA Enschede</td> <td style="width: 130px;font-size: 10px">BTW NL821234584B01</td> </tr> </tbody> </table> <br> <hr style="border:none;border-top:1px solid #ccc;"><br> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a></pre> </blockquote> Hi,<br> <br> Can you please check what does your gluster peer status on each of your nodes return? I guess they are in disconnected state and that is the reason you are not able to view these details.<br> <br> Thanks<br> kasturi<br> <blockquote cite="mid:554A031A.1060200@netbulae.eu" type="cite"> <pre wrap=""> </pre> </blockquote> <br> </body> </html> --------------090006090607030504020009--
participants (8)
-
Bob Doolittle -
Jorick Astrego -
knarra -
Martin Perina -
Michal Skrivanek -
Oved Ourfali -
Sandro Bonazzola -
Yedidyah Bar David