Thanks you.
Yes I did fix it for the first error.
For the permission I did follow the technote before and also others
setting. As I was using the apache user (added to the correct group) I have
to chmod everything, which I did. I finally found that I was missing one
chmod in one folder.
It's now working.
Creating review with base CC is working fine, now I'll check with UCM.
Thanks again.
On Monday, August 19, 2019 at 6:32:25 PM UTC+2, Laurent M. wrote:
>
> Good morning,
>
> I've setup RB with Git with no issue, but when trying with ClearCase, that
> did not went well.
> I understand the current integration is done by the community.
> Looking at old messages (both in forum, review and bugtracking) did not
> really help.
>
>
> I was wondering if there are any kind of best practice or setup
> instructions somewhere or made by current CC user ?
>
> I'm on CentOS, CC9.0.1.7, Apache, RB 3.0.15, RBT 1.0.2
>
> The first issue I got was during a rbt post where it keep failing with
> missing attribute.
>
> if parse_version(server.rb_version) >= parse_version('1.5.3'):
> File "/usr/lib/python2.7/site-packages/rbtools/api/resource.py", line
> 348, in __getattr__
> % (self.__class__.__name__, name))
> AttributeError: This RootResource does not have an attribute "rb_version".
>
>
> After some time, I found out that it cannot grab the uuid and by renaming
> the repository to the CC vobtag, it could process.
>
> Which is where I'm stuck now. I "know" the issue, it's with access
> permissions. But until now whatever I changed did not help.
>
> When trying to post from rbt
>
>
> >>> Error data: {u'stat': u'fail', u'err': {u'msg': u'There was an error
> fetching extended information for this repository.', u'code': 210}}
> Traceback (most recent call last):
> File "/usr/bin/rbt", line 11, in <module>
> sys.exit(main())
> File "/usr/lib/python2.7/site-packages/rbtools/commands/main.py", line
> 120, in main
> command.run_from_argv([RB_MAIN, command_name] + args)
> File "/usr/lib/python2.7/site-packages/rbtools/commands/__init__.py",
> line 725, in run_from_argv
> exit_code = self.main(*args) or 0
> File "/usr/lib/python2.7/site-packages/rbtools/commands/post.py", line
> 770, in main
> repository_info = repository_info.find_server_repository_info(api_root
> )
> File "/usr/lib/python2.7/site-packages/rbtools/clients/clearcase.py",
> line 1252, in find_server_repository_info
> raise SCMError('You do not have permission to access '
> rbtools.clients.errors.SCMError: You do not have permission to access this
> repository.
>
>
>
> When doing it from the web
>
>
> File
> "/usr/lib64/python2.7/site-packages/reviewboard/scmtools/clearcase.py",
> line 58, in __init__
> self.viewtype = self._get_view_type(self.repopath)
> File
> "/usr/lib64/python2.7/site-packages/reviewboard/scmtools/clearcase.py",
> line 156, in _get_view_type
> shell=_popen_shell)
> File "/usr/lib64/python2.7/subprocess.py", line 711, in __init__
> errread, errwrite)
> File "/usr/lib64/python2.7/subprocess.py", line 1327, in _execute_child
> raise child_exception
> OSError: [Errno 13] Permission denied: '/view/rbview/vobs/stdvob'
>
> From what I understand, it cannot access the view/vob to grab/extract the
> file content.
> The process is running under the apache/apache user
> I have added the apache group to the VOB group list and reprotected (using
> protect and protectvob (so 'others' also have access)
> Also made apache user as a member of the VOB group
> I tried with a view from one user, also with a view created by the apache
> user.
>
> So for people that actually run it, do you run it with the generic apache
> user or a more "CC" ones (like running an httpd instance as vob_owner) ?
> I'm kind of surpized that, even if there are only a few CC user, there is
> not a lot of info on the "how-to".
>
> Regards.
>
>
>
>
>
>
--
Supercharge your Review Board with Power Pack:
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons:
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
---
You received this message because you are subscribed to the Google Groups
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/reviewboard/a775d7d2-1b44-4009-a46c-f30849f180a9%40googlegroups.com.
