Release #5694

Release #5058: gCube Release 4.2.0

Release #5698: org.gcube.portlets-admin.4-2-0

org.gcube.portlets-admin.users-management-portlet.3-2-0

Added by Panagiota Koltsida over 3 years ago. Updated about 3 years ago.

Status:ReleasedStart date:Nov 09, 2016
Priority:NormalDue date:
Assignee:Panagiota Koltsida
Category:-
Sprint:gCube Release 4.2.0
Wiki Updates: Version Control System:
Type: Building System:
Milestones:
Duration:

Description

Added a requested functionality
Adding Parent task the "gCube release 4.2" until the subssytem's release ticket will be available

MisterBlue.tar.gz (1.93 MB) Maria Di Girolamo, Dec 06, 2016 04:32 PM

History

#1 Updated by Maria Di Girolamo over 3 years ago

Dear p.koltsida@di.uoa.gr,
before to create the ticket release for the configuration component, it's necessary to create the release ticket for its subsystem (if it doesn't exist).

To clarify this , I've copied the first steps about the Major/Minor Release Cycle documentation(https://wiki.gcube-system.org/gcube/Major/Minor_Release_Cycle_procedure) :

1) Dev creates a CRT to advertise the release on the Tracking System. This is useful for other Developers that depends on the component to know that their components might need an update in the release. {name: , status: New, sprint: , Assignee: , Parent Task: }. The status of the CRT is New at this time and the ECC is not yet available.

2) If SRT does not exists when CRT is created (i.e. first component released in the Subsystem), Dev also creates the SRT: {name: , status: New, sprint: , Assignee: , Parent Task: }.

Please , could you create the SRT (parent task for this ticket, #5694)?

Please, don't exitate to contact me or the subsystem manager for any clarification.

#2 Updated by Panagiota Koltsida over 3 years ago

  • Parent task changed from #5058 to #5698
  • Status changed from Available to New

#3 Updated by Panagiota Koltsida over 3 years ago

@mariaantonietta.digirolamo@eng.it required actions have been done. Thanks for pointing out

#4 Updated by Maria Di Girolamo over 3 years ago

Dear Giota,
please,let me know if this cnfiguration can be available in the release 4.2.0.
(so the subsystem manager can be create a new configuration for its sustyme)

#5 Updated by Panagiota Koltsida over 3 years ago

@mariaantonietta.digirolamo@eng.it , as you can see this is already attached to the subsystems' 4.2 release ticket (created by me), so yes it should be included there

#6 Updated by Maria Di Girolamo over 3 years ago

  • Status changed from New to Available

#7 Updated by Massimiliano Assante over 3 years ago

  • Assignee changed from Massimiliano Assante to Panagiota Koltsida
  • Status changed from Available to Under Integration

#8 Updated by Maria Di Girolamo over 3 years ago

  • Status changed from Under Integration to Build Issue

The BUILD_3 fails due to the compilation error as reported at:
http://eticsbuild2.research-infrastructures.eu/BuildReport/bdownload/AllBuilds/org.gcube.4-2-0/BUILD_3/reports/reportModuleDetail-org.gcube.portlets-admin.users-management-portlet.html.
Please, could you check the error?

<<
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /home/gbuilder/workspace/org.gcube.portlets-admin.users-management-portlet/src/main/java/org/gcube/portlets/admin/usersmanagementportlet/UsersManagementPortletHome.java:[215,10] error: cannot find symbol
[ERROR] symbol: method addRecipientInBCC(String)
location: variable en of type EmailNotification
/home/gbuilder/workspace/org.gcube.portlets-admin.users-management-portlet/src/main/java/org/gcube/portlets/admin/usersmanagementportlet/UsersManagementPortletHome.java:[294,10] error: cannot find symbol
[INFO] 2 errors ....

#9 Updated by Panagiota Koltsida over 3 years ago

The library that contains the non available method must be also released.
@massimiliano.assante@isti.cnr.it , could you please release it?

#11 Updated by Maria Di Girolamo about 3 years ago

  • Status changed from Build Issue to Under Integration

#12 Updated by Massimiliano Assante about 3 years ago

  • Status changed from Under Integration to Deployed on Preprod

#13 Updated by Maria Di Girolamo about 3 years ago

  • Status changed from Deployed on Preprod to Test Issue

Hi Giota,
The test should be passed except for the step#2 (Submit a request to a VRE and accept / reject this request).
It's no possible to verify the request submitted by mister.white . mister.white try to join to the Dorne VRE but he cannot.

I used as user-test mister pink, Dorne VRE to test user-management-portlet and the old test-plan.
Please , let me know if I wrong something.

You can find the results at: https://goo.gl/Gm49Bl.

#14 Updated by Panagiota Koltsida about 3 years ago

Hi @mariaantonietta.digirolamo@eng.it thanks for testing the portlet. To be honest I have just commited an update to include a feature requested by Leonardo and I would like to deploy this version on pre-prod.

On the other site, if I understood well the problem was related to the submission of request on this VRE? Is this correct? If yes, then we sould involve also @massimiliano.assante@isti.cnr.it in this discussion.
Please let me know.

#15 Updated by Maria Di Girolamo about 3 years ago

Hi p.koltsida@di.uoa.gr,

I have just commited an update to include a feature requested by Leonardo and I would like to deploy this version on pre-prod.
I'll wait that the portlet will be re-deployed in pre-prod.

if I understood well the problem was related to the submission of request on this VRE? Is this correct? If yes, then we sould involve also >>@massimiliano.assante@isti.cnr.it in this discussion.
Yes the problem is related to the submission of request on Dorne VRE.

Please, let me know when I'll test this portlet (after the solution of all issues or feature).
Thank you Maria.

#16 Updated by Panagiota Koltsida about 3 years ago

Hi Maria, I think @massimiliano.assante@isti.cnr.it has already deployed the new version.
You can test it again and please let us know if you experiencing problems making a request for registering to the VRE or managing the request

#17 Updated by Massimiliano Assante about 3 years ago

yes I did deploy the new version

#18 Updated by Massimiliano Assante about 3 years ago

  • Status changed from Test Issue to Deployed on Preprod

#19 Updated by Maria Di Girolamo about 3 years ago

  • Status changed from Deployed on Preprod to Tested on Preprod

Test passed . The results are shared at : https://goo.gl/9unr8V.

#20 Updated by Massimiliano Assante about 3 years ago

  • Priority changed from Normal to Urgent
  • Status changed from Tested on Preprod to Test Issue

There is a bug in production (https://support.d4science.org/issues/6128) on user assignments to groups that is not captured by any functional test steps, the functional test plan must be upgraded accordingly.

#21 Updated by Massimiliano Assante about 3 years ago

Cross VRE user assignments to roles and groups should be added to the functional test plan of this portlet.

Steps to reproduce the issue and a video showing the issue in preprod http://www.screencast.com/t/Z2XU8eK8uhf :

Assante has no groups in preVRE and Dorne
Assign CNR Group to Assante in Dorne
Assign CNR Group to Assante in preVRE
Go back to Dorne
in Dorne Assante has no groups, but in 2. we added him to CNR

#22 Updated by Maria Di Girolamo about 3 years ago

  • Priority changed from Urgent to Immediate

Please, p.koltsida@di.uoa.gr, could you update the test-plan as requested by massimiliano.assante@isti.cnr.it.
So I can repeat a valid test for this configuration.

#23 Updated by Maria Di Girolamo about 3 years ago

If the issue (https://support.d4science.org/issues/6128#change-32801) is solved , please let me know the test-plan is updated.

Thank you, Maria.

#24 Updated by Massimiliano Assante about 3 years ago

  • Status changed from Test Issue to Deployed on Preprod

The updated version build last night is available

#25 Updated by Panagiota Koltsida about 3 years ago

Test has been updated to include the scenario which produced the reported bug

#26 Updated by Maria Di Girolamo about 3 years ago

  • Status changed from Deployed on Preprod to Test Issue

It seems that the portlet doesn't work properly.
The portlet seems not work properly.

When I access to accept a request by mister brown , it seems ok .
But when enter as mister brown the VRE is missing.

I repeat the test for mister blue and is the same.
Another test I've repeat with two request , I want to accept mister blue and rejected mister brown.
After I accept mister blue the windown is closed and no request is appear in the Administration Menu (this is not correct because it should be the pending request of mister blue).

Another strange behaviour if I return in the pre-VRE and click in the Administration menu I'm not able to click in one voice of drop-down menu
.

#27 Updated by Panagiota Koltsida about 3 years ago

Ciao @mariaantonietta.digirolamo@eng.it ,
could you specify which is the VRE/scope that you are using?

In addition about the multiple requests and just for clarification. Are you sure you don't use the 'Accept All' right? I'm testing in my development portal with no problems. I have to check the versions then.

As for the third issue, this is related to the portal's theme and @massimiliano.assante@isti.cnr.it should be notified. Indeed, sometimes I'm also experiencing this issue

#28 Updated by Maria Di Girolamo about 3 years ago

Hi Giota,
the VRE is Dorne.
I used "Accept Selected".
In any case, I'll repeat the test.
Thanks Giota.

#29 Updated by Maria Di Girolamo about 3 years ago

The issue about the request to accept is not solved for me.
I repeated the test as mister Blue and mister Orange.
Below the steps:
1)mister blue leaves the Dorne VRE
2) mister blue send a request to access to the Dorne VRE
3) mister pink accepts the request by mister blue
4) mister blue is not member of the Dorne VRE although mister pink accepted the request

Please, find in attached (MisterBlue.tar.gz) the files about the steps executed (called from xxx_stepOne to xxx_step6).

Please, let me wrong If I wrong something.

Thank you Maria.

#30 Updated by Panagiota Koltsida about 3 years ago

I'm sorry I cannot understand because I go to the two available "Dorne" VREs and I can find mister.blue as a member. The strange thing is that you are not the acceptance manager neither is mister.pink.
The mister.blue user seems to be a member since a long time ago :), in fact since October.

@massimiliano.assante@isti.cnr.it could the leave group of a user not updating the register info?

#31 Updated by Massimiliano Assante about 3 years ago

Panagiota Koltsida wrote:

I'm sorry I cannot understand because I go to the two available "Dorne" VREs and I can find mister.blue as a member. The strange thing is that you are not the acceptance manager neither is mister.pink.
The mister.blue user seems to be a member since a long time ago :), in fact since October.

@massimiliano.assante@isti.cnr.it could the leave group of a user not updating the register info?

i think it can, but we should test this

However we need to run the test again DUE TO BUG https://support.d4science.org/issues/6115

#32 Updated by Massimiliano Assante about 3 years ago

  • Status changed from Test Issue to Deployed on Preprod

the preprod portal has been patched with the fix for bug #6115, please run the tests again

#33 Updated by Maria Di Girolamo about 3 years ago

  • Status changed from Deployed on Preprod to Test Issue

Test failed for the step#13 as reported in the TestPlan: Workspace > VRE Folders > gCube > Portlet Testing Plans > Releases > org.gcube.4.2.0 > portlets-admin > user-management-portlets.3-2-0 (https://goo.gl/cOitz8).

Please, let me know if I wrong something.

#34 Updated by Vassilis Floros about 3 years ago

Maria Di Girolamo wrote:

Test failed for the step#13 as reported in the TestPlan: Workspace > VRE Folders > gCube > Portlet Testing Plans > Releases > org.gcube.4.2.0 > portlets-admin > user-management-portlets.3-2-0 (https://goo.gl/cOitz8).

Please, let me know if I wrong something.

Hmm, maybe it's the test description, it might not be clear enough.
When you create a group in a VRE, this group is associated to that specific VRE. So, the displayed groups are the groups that belong to that specific VRE.
If you assign a user to a group in a VRE, the group name will appear in the user details for this VRE only.

The purpose of this test is to examine if adding the portlet to different VREs will affect users' details.
So, let's say you asscociate a user of VRE1 with groups A,B,C and then the same user registers to VRE2 where you have groups D,E,F.
If you add him to groups D,E,F in VRE2 and then go back to VRE2 will he be still be member of groups A,B,C in VRE1?
That's what is being examined here.

#35 Updated by Maria Di Girolamo about 3 years ago

  • Priority changed from Immediate to Normal
  • Status changed from Test Issue to Deployed on Preprod

Hi Giota,
thanks for you rclarification .
I repeated the test: portlet seems work as expected.

#36 Updated by Maria Di Girolamo about 3 years ago

  • Status changed from Deployed on Preprod to Tested on Preprod

#37 Updated by Massimiliano Assante about 3 years ago

  • Status changed from Tested on Preprod to Released

Also available in: Atom PDF