Review Board 5.0.2 - Unable to trust svn host when adding a repository or modifying an existing repository.

47 views
Skip to first unread message

Kerry Groeschel

unread,
Feb 17, 2023, 6:30:33 PM2/17/23
to Review Board Community
I have a Review Board instance 5.0.2 that was recently setup and is using a database migrated from 2.5.13.1.  Everything has been working okay but we recently needed to add a new repository.   When trying to save the new repository, I get the error "The SSL certificate for this repository was not verified and might not be safe."  It gives me the option to "I trust this host" or "Re-edit repository".  If I click "I trust this host".  It just redisplays the Add Repository page will all the fields back to default values with error messages that these fields are required.  If I fill everything back in again, I get back to the SSL certificate trust error and this cycle will just repeat.  If you try to just click Save on an existing repository being viewed, the SSL certificate error is also displayed.  I have python3-subvertpy installed and running on Ubuntu 22.04.1 LTS.  

From what I can find online and looking at our old server, it looks like RB should be putting certificates info under /var/www/rb/data/.subversion/auth/svn.simple.  But when I look on the new server, I only see /var/www/rb/data/.subversion and it is empty.  The .subversion folder is owned by www-data which also runs the apache server.  
Seems like a permissions issue but not sure of the issue.  Any thoughts?  


Christian Hammond

unread,
Feb 17, 2023, 7:22:59 PM2/17/23
to revie...@googlegroups.com
Hi Kerry,

This is a regression in 5.0 that we're working on fixing. It has to do with fields being disabled while that prompt is shown, but not being re-enabled correctly when submitting the form.

A fix will be coming in the next couple weeks as part of 5.0.3.

There's a (hacky) workaround you can use for now. When you get that trust confirmation, open the browser's JavaScript console (part of the browser's built-in developer tools) and type:

    $('input, select').prop('disabled', false);

Verify that the repository configuration fields (like Name) now appear editable, and then click the Trust button to submit.

Really sorry about that, and we'll have that fix soon.

Christian

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/reviewboard/cdd42ab3-a90d-4c9e-bb26-9803ed949570n%40googlegroups.com.


--
Christian Hammond
President/CEO of Beanbag
Makers of Review Board

Kerry Groeschel

unread,
Feb 22, 2023, 2:57:19 PM2/22/23
to Review Board Community
I attempted this work around and it did not resolve my issue.  I tried again to create a repository and get the "I trust this host" option. I entered the line suggested in the JavaScript console and the configuration fields do become editable.  But when I then click "I trust this hope" the page just starts spinning and never returns or times out.  At least it has been spinning more than 5 minutes so far.  Review Board is still running and I can access it from another browser window without issue.

Christian Hammond

unread,
Feb 22, 2023, 5:21:22 PM2/22/23
to revie...@googlegroups.com
Could you determine whether the repository fields, like "Name", were editable after you ran that command?

Were there any logs in the JavaScript console when you clicked the button?

We should have the proper fix released next week.

Christian

Kerry Groeschel

unread,
Mar 14, 2023, 9:40:44 AM3/14/23
to Review Board Community
I updated our RB server to 5.0.3 and now when I click 'I trust this host', the web page just starts spinning and never returns.  The rb debug log file just starts filling up with repeated errors multiple times a second.  I have to restart apache2 service to stop it.  I will note our .subversion folder is empty so it appears no credentials have been successfully stored.  The owner of the folder www-data which is also running apache2 and it has full rwx rights to this folder.  Here is a snippet from the rb log file.  

2023-03-14 13:07:55,554 - ERROR -  - reviewboard.scmtools.svn - SVN: Failed to get repository information for https://<svn-servername>/svn/markXX/branches/branch_1pt60_20220816: ("Unable to connect to a repository at URL 'https://<svn-servername>/svn/markXX/branches/branch_1pt60_20220816'", 170013)

2023-03-14 13:07:57,276 - DEBUG -  - djblets.cache.backend - Cache miss for key "<rb-servername>:/:dmarc-record-emerson.com"

2023-03-14 13:08:01,791 - ERROR -  - reviewboard.scmtools.svn - SVN: Failed to get repository information for https://<svn-servername>/svn/markXX/branches/branch_1pt60_20220816: ("Unable to connect to a repository at URL 'https://<svn-servername>/svn/markXX/branches/branch_1pt60_20220816'", 170013)

2023-03-14 13:08:02,246 - ERROR -  - reviewboard.scmtools.svn - SVN: Failed to get repository information for https://<svn-servername>/svn/markXX/branches/branch_1pt60_20220816: ("Unable to connect to a repository at URL 'https://<svn-servername>/svn/markXX/branches/branch_1pt60_20220816'", 170013)

2023-03-14 13:08:02,653 - ERROR -  - reviewboard.scmtools.svn - SVN: Failed to get repository information for https://<svn-servername>/svn/markXX/branches/branch_1pt60_20220816: ("Unable to connect to a repository at URL 'https://<svn-servername>/svn/markXX/branches/branch_1pt60_20220816'", 170013)

2023-03-14 13:08:03,059 - ERROR -  - reviewboard.scmtools.svn - SVN: Failed to get repository information for https://<svn-servername>/svn/markXX/branches/branch_1pt60_20220816: ("Unable to connect to a repository at URL 'https://<svn-servername>/svn/markXX/branches/branch_1pt60_20220816'", 170013)

2023-03-14 13:08:03,474 - ERROR -  - reviewboard.scmtools.svn - SVN: Failed to get repository information for https://<svn-servername>/svn/markXX/branches/branch_1pt60_20220816: ("Unable to connect to a repository at URL 'https://<svn-servername>/svn/markXX/branches/branch_1pt60_20220816'", 170013)

2023-03-14 13:08:03,885 - ERROR -  - reviewboard.scmtools.svn - SVN: Failed to get repository information for https://<svn-servername>/svn/markXX/branches/branch_1pt60_20220816: ("Unable to connect to a repository at URL 'https://<svn-servername>/svn/markXX/branches/branch_1pt60_20220816'", 170013)

Kerry Groeschel

unread,
Mar 14, 2023, 12:35:46 PM3/14/23
to Review Board Community
You can disregard my last issue with 5.0.3.  My problem was with using subvertpy instead of using pysvn.  Not sure what installation notes I was using but I saw the latest 5.0 notes recommended pysvn.  I uninstalled subvertpy and installed pysvn and issue is resolved.  Certificate for svn server is accepted and I can see credentials being saved in the .subversion folder.  That resolved my issue.  Follow the latest installation notes.  

David Trowbridge

unread,
Mar 14, 2023, 12:48:17 PM3/14/23
to revie...@googlegroups.com
Kerry,

Glad you got it working. We’re seriously considering dropping support for subvertpy, as it has grown increasingly buggy over the last few years. This sounds like another data point in favor of that.

David


Reply all
Reply to author
Forward
0 new messages