Bug 1085152

Summary: SubComponent doesn't show in search page
Product: [Community] Bugzilla Reporter: Wenjie Guo <wguo>
Component: WebServiceAssignee: Simon Green <sgreen>
Status: CLOSED CURRENTRELEASE QA Contact: Simon Green <sgreen>
Severity: high Docs Contact:
Priority: high    
Version: 4.4CC: ebaak, jmcdonal, rjoost
Target Milestone: 4.4Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.4.4019 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-07 00:58:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Script that creates and renames subcomponents none

Description Wenjie Guo 2014-04-08 02:01:51 UTC 
Description of problem:
When using the xmlrpc api to change the name of the subcomponent , the children subcomponents of this subcomponent will disappear .

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Invoking the xmlrpc to do operation "update" on the subcomponent A (which has two children subcomponents , A1 and A2), 
2. Then if i changed the name to "changeit" , updated successfully .
3. When i check the result , the A had been changed to "changeit" , but the subcomponents A1 and A2 doesn't exist any more.

Actual results:
Changing the name of parent subcomponents may have changed the relationship with the subcomponents .

Expected results:
Changing the name of parent subcomponents should not have any impact on the relationship with the subcomponents . 

Additional info:
Comment 1 Jason McDonald 2014-04-08 06:55:50 UTC 
I am unable to reproduce this bug using either the Web UI or the XMLRPC interface.

Please review the attached perl xmlrpc script in case I misunderstood the "Steps to Reproduce" above.  Note that you will need to modify the script to specify the URL of the Bugzilla instance you are testing on, and to specify a username and password for an account that has permissions to edit subcomponents in that Bugzilla instance.

The script creates a top-level subcomponent 'A' for the 'kernel' component of the 'Red Hat Enterprise Linux 6" product, then creates two child subcomponents of 'A' called 'A1' and 'A2'.  It renames the top-level subcomponent from 'A' to 'changeit' by passing SubComponent.update the subcomponent id, then renames it a second time from 'changeit' to 'changeitagain' by passing Subcomponent.update the product name, component name and subcomponent name.

After running the script against Bugzilla 4.4.2017 and viewing the subcomponent list, I see subcomponent "changeitagain" with two children 'A1' and 'A2'.

If you are still able to reproduce this bug, please attach a script that demonstrates the problem.
Comment 2 Jason McDonald 2014-04-08 06:56:43 UTC 
Created attachment 883914 [details]
Script that creates and renames subcomponents
Comment 3 Wenjie Guo 2014-04-08 07:38:39 UTC 
Hi Jason , 

   The issue exists on the search page:
   https://bz-stage.devel.redhat.com/query.cgi

   Where i test it with the query parameter : Product: Maitai

   Each time i exe the java client to update the name of subcomponent , i check the result on search page, to click the button '<== Click here to update components/versions/releases/milestones' to check the result .
Comment 4 Jason McDonald 2014-04-09 02:13:29 UTC 
I am now able to reproduce this bug as follows:

1. Choose a product and component and create a top-level subcomponent with two child subcomponents.
2. View the Advanced Search page, select the Product and click the "Refresh Components/Versions/Releases/Milestones" button.
3. Observe that all three subcomponents are shown in the "Sub Component" list box.
4. Using xmlrpc, rename the top-level subcomponent.
5. On the Advanced Search page, click the "Refresh Components/Versions/Releases/Milestones" button again.
6. Observe that only the top-level subcomponent is shown in the "Sub Component" list box.

The behaviour is the same regardless of which of the two possible ways to nominate a sub-component to be renamed is used in step 4 (the Subcomponent.update xmlrpc function can take either a subcomponent id or the product, component and subcomponent names).

Interestingly, If I perform the subcomponent renaming via the Web UI, the bug does not occur.
Comment 5 Simon Green 2014-04-14 01:28:44 UTC 
Found the problem to this. It all depending on the alphabetically ordering of the sub components (the parent had to come first alphabetically otherwise there was an error)

This error occurred without any making any changes with a sub component Tahi, and two children Rua and Toru (Māori for one, two and three respectively)

new_for_list bits me in the rear end again :(
Comment 6 Simon Green 2014-05-07 00:58:16 UTC 
This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.

  -- simon