ClearCase Connector requires project vob access
I ran into a problem when creating a new "ClearCase Synchronized Stream" - after filling out the wizard and clicking finish I got:
Unable to find the stream (mystream@\mypvob) selector specified. Please check it by trying the following command at the command prompt:
cleartool describe stream:mystream@\mypvob
The cleartool describe worked (in fact, I created the stream on this machine).
It turned out to be because the id I was running windows as did not have access to the project vob (we protect vobs using acls' on the vob storage dirs).
In our shop, ClearCase users don't need access to the pvob, just the component vobs. I'm wondering why RTC would? Is it trying to mount it?
Unable to find the stream (mystream@\mypvob) selector specified. Please check it by trying the following command at the command prompt:
cleartool describe stream:mystream@\mypvob
The cleartool describe worked (in fact, I created the stream on this machine).
It turned out to be because the id I was running windows as did not have access to the project vob (we protect vobs using acls' on the vob storage dirs).
In our shop, ClearCase users don't need access to the pvob, just the component vobs. I'm wondering why RTC would? Is it trying to mount it?
4 answers
The sync process needs to create a baseline in the ClearCase stream
being synchronized, so that it has a baseline to compare with the next
time a sync is requested. This requires write access to the pvob, since
baselines are stored in the pvob.
Cheers,
Geoff
eanderso wrote:
being synchronized, so that it has a baseline to compare with the next
time a sync is requested. This requires write access to the pvob, since
baselines are stored in the pvob.
Cheers,
Geoff
eanderso wrote:
I ran into a problem when creating a new "ClearCase Synchronized
Stream" - after filling out the wizard and clicking finish I
got:
Unable to find the stream (mystream@\mypvob) selector specified.
Please check it by trying the following command at the command
prompt:
cleartool describe stream:mystream@\mypvob
The cleartool describe worked (in fact, I created the stream on this
machine).
It turned out to be because the id I was running windows as did not
have access to the project vob (we protect vobs using acls' on the
vob storage dirs).
In our shop, ClearCase users don't need access to the pvob, just the
component vobs. I'm wondering why RTC would? Is it trying to mount
it?
None of our users have access to the pvob and the only thing they haven't been able to do is mount the pvob (which is not necessary). They make baselines and use the other features of UCM w/o problems.
I granted read access to the pvob and was able to get by this (it also allowed me to mount the pvob which is why I thought RTC was attempting a mount).
At a minimum, the original error message is misleading (can not find stream).
I granted read access to the pvob and was able to get by this (it also allowed me to mount the pvob which is why I thought RTC was attempting a mount).
At a minimum, the original error message is misleading (can not find stream).
I need to clarify access - they do have access to the pvob (via RPC), but they don't need access to the pvob storage directory via file sharing (which is how we secure our vobs). Using standard ClearCase tools, it is never necessary to mount the pvob. The connector shouldn't need to mount the pvob.
I opened workitem 64433 for this.
Cheers,
Geoff
eanderso wrote:
Cheers,
Geoff
eanderso wrote:
I need to clarify access - they do have access to the pvob (via RPC),
but they don't need access to the pvob storage directory via file
sharing (which is how we secure our vobs). Using standard ClearCase
tools, it is never necessary to mount the pvob. The connector
shouldn't need to mount the pvob.