Back in the early fall we attempted a major upgrade of Ruby on Rails, the application framework that we use to build TroopTrack. We are currently on version 4.2, but the latest stable version is now 5.0. That upgrade didn’t go well and we had to back it out. We decided to wait until the super busy season (August - early November) was over before we tried it again.
This morning we are trying it again. We’ve spent a lot of time fixing the problems we saw back in September, and I hope it will go much better this time.
That said… this is a big deal and there is a big possibility we will see some problems throughout the day. We will resolve them as quickly as possible, so please bear with us today.
Can I recommend using a site offline / under maintenance page when things are being upgraded and unavailable? I was getting a page isn’t working error message which is not user friendly. Luckily I had the support forums open in another tab and was able to find this message.
We think that’s a good idea for when we are totally down. The upgrade we are going through is past the “totally down” part - we’re trying to fix problems that only occur under load right now.
Sorry to hear it didn’t go well this time. I don’t know what challenges resulted in a rollback, but If I could do something to help plan or test I’m willing to help. I don’t have rails experience, but I’ve done a bit of QA and related work.
Just a suggestion for next time - will you post somewhere in advance that there might be a disruption to TT service on a specific day? Maybe you did, and I just didn’t see it? Or maybe certain roles/ permissions were informed, and I am not one of them.
(It was unfortunate timing for TT not to be up - our shopper was planning to place our first order with AHG using TT that day, and was unable to log in to do so. She had to fall back on her Excel spreadsheets to place the order in time.)
Some better change management communication and timing would be nice. Announce to the community ahead of time when you plan to try an upgrade so that we can plan around it. Also, maybe these things can be done at the least busy times? Analyze traffic patterns and attempt during lowest usage times.
I’m seeing some weirdness (perhaps in relation to the Ruby upgrade) on my patrol pages. Anyone that has a profile pic has this message instead.
-Joshua
This might be related, When I edit a page on my Pack Web Site and try to add a picture I get the error
"We’re sorry, but something went wrong. We’ve been notified about this issue and we’ll take a look at it shortly."
Share > Home > Manage this page > Edit > Image Button > Browse Server
you man.
