What version are you running?
RB 2.0.11 and RBTools 0.6.3
What's the URL of the page containing the problem?
N/A
What steps will reproduce the problem?
1. Install Python 2.7.9 and RBTools 0.6.3
2. Set up RB to run on HTTPS listener
3. rbt post --server https://server:8081 --debug
What is the expected output? What do you see instead?
Expected (based on Python 2.7.8):
>>> RBTools 0.6.3
>>> Python 2.7.8 (default, Jul 4 2014, 11:28:55)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-50)]
>>> Running on Linux-2.6.32-358.6.2.el6.x86_64-x86_64-with-redhat-6.4-Santiago
>>> Home = /home/user
>>> Current directory = /vob/vob1
>>> Checking for a Subversion repository...
>>> Unable to execute "svn help": skipping SVN
>>> Checking for a Git repository...
>>> Unable to execute "git --help" or "git.cmd --help": skipping Git
>>> Checking for a Mercurial repository...
>>> Unable to execute "hg --help": skipping Mercurial
>>> Checking for a CVS repository...
>>> Checking for a Perforce repository...
>>> Unable to execute "p4 help": skipping Perforce
>>> Checking for a Plastic repository...
>>> Unable to execute "cm version": skipping Plastic
>>> Checking for a ClearCase repository...
>>> Running: cleartool pwv -short
>>> Running: diff --version
>>> Running: cleartool lsview -full -properties -cview
>>> Running: cleartool describe -short vob:.
>>> Running: cleartool pwv -root
>>> repository info: Path: /vob/vob1, Base path: /vob/vob1, Supports changesets: False
>>> Making HTTP GET request to https://server:8081/api/
>>> Running: cleartool lsvob -long /vob/vob1
>>> Repository's /vob/vob1 uuid is '60cd8109.c76411d4.b73f.00:10:83:fa:65:79'
...
Actual:
>>> RBTools 0.6.3
>>> Python 2.7.9 (default, Dec 29 2014, 12:30:20)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-54)]
>>> Running on Linux-2.6.32-358.6.2.el6.x86_64-x86_64-with-redhat-6.4-Santiago
>>> Home = /home/user
>>> Current directory = /vob/vob1
>>> Checking for a Subversion repository...
>>> Unable to execute "svn help": skipping SVN
>>> Checking for a Git repository...
>>> Unable to execute "git --help" or "git.cmd --help": skipping Git
>>> Checking for a Mercurial repository...
>>> Unable to execute "hg --help": skipping Mercurial
>>> Checking for a CVS repository...
>>> Checking for a Perforce repository...
>>> Unable to execute "p4 help": skipping Perforce
>>> Checking for a Plastic repository...
>>> Unable to execute "cm version": skipping Plastic
>>> Checking for a ClearCase repository...
>>> Running: cleartool pwv -short
>>> Running: diff --version
>>> Running: cleartool lsview -full -properties -cview
>>> Running: cleartool describe -short vob:.
>>> Running: cleartool pwv -root
>>> repository info: Path: /vob/vob1, Base path: /vob/vob1, Supports changesets: False
>>> Making HTTP GET request to https://server:8081/api/
Traceback (most recent call last):
File "/proj/subcm/tools/linux/python-2.7.9/bin/rbt", line 9, in <module>
load_entry_point('RBTools==0.6.3', 'console_scripts', 'rbt')()
File "/proj/subcm/tools/linux/python-2.7.9/lib/python2.7/site-packages/RBTools-0.6.3-py2.7.egg/rbtools/commands/main.py", line 134, in main
command.run_from_argv([RB_MAIN, command_name] + args)
File "/proj/subcm/tools/linux/python-2.7.9/lib/python2.7/site-packages/RBTools-0.6.3-py2.7.egg/rbtools/commands/__init__.py", line 416, in run_from_argv
exit_code = self.main(*args) or 0
File "/proj/subcm/tools/linux/python-2.7.9/lib/python2.7/site-packages/RBTools-0.6.3-py2.7.egg/rbtools/commands/post.py", line 710, in main
api_client, api_root = self.get_api(server_url)
File "/proj/subcm/tools/linux/python-2.7.9/lib/python2.7/site-packages/RBTools-0.6.3-py2.7.egg/rbtools/commands/__init__.py", line 561, in get_api
"server at %s" % server_url)
rbtools.commands.CommandError: Could not reach the Review Board server at https://server:8081
What operating system are you using? What browser?
RedHat Enterprise Linux 6.4 x86_64
Please provide any additional information below.
I have verified that both RBTools 0.6.2 and 0.6.3 work on Python 2.7.8 and they both don't work with Python 2.7.9. I guess this may have something to do with the ssl module changes in 2.7.9.
It could also matter that this server uses a certificate which is issued by internal corporate CA, which may not be added to standard trusted certificates.