-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
supermarket onsite giving errors when downloading #1449
Comments
Hi there! What version of Supermarket are you currently running? And what was the maximum version you were running before rolling back? |
I've been running the supermarket-omnibus-cookbook for a while and it has upgraded packages for us over the last year:
it started this morning, I'm guessing when 2.8.29 hit? We did finally get things working again about 5 minutes ago. The database schema was missing fields. the columns in cookbook_versions table were missing We are functional now on 2.8.25-1 and will hold off here for the night. |
There indeed was a large bug with 2.8.29, which involved a migration. Apologies for the issues! We will be doing a post-mortum very soon! |
@nellshamrell Believe this is the same issue we are having. We built a Private Supermarket using supermarket-omnibus-cookbook and have the ['supermarket_omnibus']['package_version'] set to latest. This morning we had a Berkshelf failure on the client side and the Supermarket cookbook has been failing since around 19:00 hours last night. We re-started the Supermarket services which fixed the Berkshelf issue but we still have an issue with the Supermarket cookbook. The supermarket-omnibus cookbook we are using is version is 1.4.1 and unfortunately cannot downgrade the version of supermarket
Should we manually downgrade the version of Supermarket? |
@chrisgit to get you back and working, I do suggest manually downgrading your installation of Supermarket. Adding an issue to the Supermarket omnibus cookbook to allow downgrading. You many need to add these fields back to the cookbook_versions table after the downgrade is complete foodcritic_failure, foodcritic_feedback, collaborator_feedback, and collaborator_failure. Again, we apologize for this issue, and are working to remediate it right now. |
@nellshamrell Thank you for your help. Apologies but I'm not sure how to add foodcritic_failure, foodcritic_feedback, collaborator_feedback, and collaborator_failure to the cookbook_versions table. |
Let me find out the best way to do so and I will follow up with you shortly :) @TD-4242 - what method did you use? |
@chrisgit - one additional question - are you using an local DB on your Supermarket server or using a separate DB like Amazon RDS? |
Hello @nellshamrell . All help and advice is gratefully received. Our Private Supermarket is using a local DB. |
@chrisgit I am currently building an environment to test a solution and will update you hourly until it is complete. |
Thank you, I'm out tonight and at Chef Summit London tomorrow but a solution is probably helpful to others who also upgraded their Supermarket installations. |
Ah! I see that it is getting late in London, so I won't make a lot of noise by updating you hourly, but will continue to update periodically throughout the day. |
log into the postgres database as supermarket
|
Is there a proposed solution for fixing this problem currently? Should I login to the supermarket postgres database and run the commands posted by @TD-4242. |
@specialkevin @chrisgit Yes, please use the login to the supermarket postgres database and run the commands as mentioned by @TD-4242. That will get you working and unblocked for now. I am currently working on a new version which will fix this error and it will be released within the next few days. |
I confirm, that altering tables solve this issue temporary. Waiting for next release. |
@nellshamrell Thank you, we will attempt roll back today |
A fix has been built and is available as v2.8.30 in our current channel. It's been pretty thoroughly vetted and is running happily on our Staging instance. We're holding off releasing it to stable until next week because Friday Releases are Unfun™. I would recommend trying 2.8.30 before the effort of going through a roll back. 2.8.30 does not contain destructive changes, only some guards in the generation of the JSON output for the API endpoint that broke in 2.8.29. |
@here we have released 2.8.30, which includes a fix for this issue https://github.com/chef/supermarket/releases/tag/2.8.30 |
getting the following error on the supermarket server
Getting this from the client side trying to download our internal java wrapper cookbook
tried rolling back to 2.8.25 and getting the same messages.
The text was updated successfully, but these errors were encountered: