Label Promotion problem

kasti · Post by **kasti** » Thu Mar 03, 2005 3:16 am

Hi there,

We have got a problem with label promotion. Its not very serious for us right now but I decided to submit it anyway.

Here is the setup:

Vault Structure looks as follows:

--Project
------comp1
------comp2
------comp3

"Project" was labelled at a certain stage. Now I wanted to promote a file of comp3. The strange thing is comp3 does not even appear in the label promotion dialog, only comp1 and comp2. If I go to the "show labels" dialog however, I can see the inherited label on comp3.

Back to the "label promotion dialog" I decided now to add comp3 to the label of "Project". Comp3 is listed in the "Add to Label" dialog. Adding it however will generate a Database error. Server log says:

----3/3/2005 9:50:57 AM --SSL Disabled Violation of PRIMARY KEY constraint 'pk_tblfsobjectlabelviews'. Cannot insert duplicate key in object 'tblfsobjectlabelviews'.
The statement has been terminated.
----3/3/2005 9:50:57 AM --SSL Disabled PromoteLabelItems returned: FailDBInsert

This makes sense since comp3 is already part of the label. Only somehow the label promotion dialog seems to get it wrong.

As I said, not serious for us, if you guys need more info, let me know.

Bye,
Herbert.

Post by **jclausius** » Thu Mar 03, 2005 8:18 am

Can you view the label logged in as the Admin user? Is comp3 there?

I'd like to rule out the possibility of a permissions based issue.

kasti · Post by **kasti** » Thu Mar 03, 2005 9:27 am

Hi Jeff,

Right as usual. I think I narrowed it down a bit but am not 100% sure if this is the problem. What we do is:

1. Our users have only Group rights
2. This user is part of 2 Groups, a "Developer" and a "component developer" group
3. As Developer, the users have no rights to comp3
4. As Component Developer, the user has read/write access to comp3

This setup works ok for normal checkin/out but not for label promotion.

If I remove the "Developer" group, I suddenly see comp3 in the label promotion dialog.

I hope this covers the problem, I had no chance yet to reproduce it in another DB to make sure.

Bye,
Herbert.

Post by **jclausius** » Thu Mar 03, 2005 9:38 am

Herbert:

It does look as if the Dev rights are over-riding the Component rights. I'll log an investigation item this look into this problem.

Thanks for the report.

Post by **jclausius** » Wed Mar 30, 2005 11:57 am

Herbert:

I'm going back over some old listings for Vault 3.1. Can I solicit some more information from you? ( I cannot create this problem ).

Here's what I have done:

$/
$/Proj/
$/Proj/1/
$/Proj/2/
$/Proj/3/

I've created User X. User X has NO default permissions.

I have also created Group Dev. Group Dev has RCA on $/Proj/1/ and $/Proj/2/. Group Dev also has NO rights on $/Proj/3/

There is another group, Group Comp. Group Comp has RCA on $/Proj/, NO rights on $/Proj/1/ and NO Rights for $/Proj/2/. Finally, Gruop Comp has RCA on $/Proj/3/

User X is a member of both Group Dev and Group Comp.

If I look at User X's security rights, they have the following:
Default rights - all unchecked
RCA on $/Proj/ Inherited from Comp
RCA on $/Proj/3/ Inherited from Comp
RCA on $/Proj/2/ Inherited from Dev
RCA on $/Proj/1/ Inherited from Dev

I next have User X create a Label on $/Proj/. If I view the label, all three sub-directories are present. I can even modify the label through promotion.

Is there something different in my setup, that I cannot re-create this behavior?