Skip to content
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

facing issue in git checkout while upgrading to 24.1.1 to 24.1.2 #2802

Closed
balaG4046 opened this issue Feb 19, 2024 · 17 comments
Closed

facing issue in git checkout while upgrading to 24.1.1 to 24.1.2 #2802

balaG4046 opened this issue Feb 19, 2024 · 17 comments
Labels

Comments

@balaG4046
Copy link

Self-Hosted Version

24.1.1

CPU Architecture

x86_64

Docker Version

20.10.25

Docker Compose Version

2.16.0

Steps to Reproduce

while upgrading to 24.1.1 to 24.1.2 we are facing issue

error: Your local changes to the following files would be overwritten by checkout:
cron/Dockerfile

even for 24.2.0 also same issue - kindly help us to resolve the issue. @hubertdeng123 @chad

Expected Result

it should upgrade to 24.1.2

Actual Result

Screenshot 2024-02-19 123712

Event ID

No response

@balaG4046
Copy link
Author

@chadwhitacre @hubertdeng123 - Kindly help me with your suggestion here

@DarkByteZero
Copy link

This is a normal Git error that you are experiencing. You made custom changes to this file, and git asks if you want to overwrite these. If the changes you have made to the Dockerfile are not relevant, you can do the following.
git reset --hard

@balaG4046
Copy link
Author

Hi
issue is fixed now for the commit issue, and we are facing new issue while updating from 24.1.1 to 24.1.2 - please refer the error screenshot,

whether the fix will we release in upcoming versions, however 24.2.0 also we are facing the same issue, Kindly need your suggestion to proceed

image

Thanks!

@aldy505
Copy link
Collaborator

aldy505 commented Feb 21, 2024

Hi @balaG4046 I can't really deduct what your issue is from that clipped log. Can you show us the complete log? There should be a sentry_install_log... file on your directory. It's best to put it on a Pastebin or similar.

@balaG4046
Copy link
Author

Hi @aldy505
i have attached the logs - kindly check and help us to fix the issue
sentry_install_log-2024-02-19_14-08-34.txt
sentry_install_log-2024-02-20_06-58-48.txt

Thanks!

@aldy505
Copy link
Collaborator

aldy505 commented Feb 21, 2024

Oh, it's just the Sentry container got a connection lost issue during connecting to the Postgres container. It's probably because a bad hardware on your end. Since the second log file looks like everything is okay, I suppose you are running a normal working Sentry right now?

If you don't have normal working Sentry running, try to check your server disk speed.

@balaG4046
Copy link
Author

balaG4046 commented Feb 21, 2024

Hi @aldy505

Thanks for looking in to our issue,

We are using RDS Postgres 13.10, in our Sentry. We have replaced the below variables which was provided in sentry.conf.py

SENTRY_DB_NAME
SENTRY_DB_USER
SENTRY_DB_PASSWORD
SENTRY_POSTGRES_PORT
SENTRY_POSTGRES_HOST

Looks like in our log, it is trying to access default postgress container,

Below Hardware specification for our Sentry Dev Environment (AWS Cloud)

Instance type - m6a.4xlarge,
OS version - amazon Linux 2,
EBS Volume type - gp2,
IOPS - 300,
EBS volume size - 100GB.

Sentry is deployed via docker compose method.

Kindly suggest us, what need to be done, if we are using external postgress like RDS in our case.

Thanks!

@azaslavsky
Copy link
Contributor

This is being discussed in another issue at the moment: #2804

Worth noting that Sentry is currently on postgres 14. This probably isn't the cause of this specific issue, but may be a problem down the line in other subtle ways.

@praseeb
Copy link

praseeb commented Feb 23, 2024

@aldy505 @BYK @azaslavsky

Will there be any upcoming fix for this issue? the same issue facing while upgrading to 24.2.0 as well from 24.1.1
We are stuck in 24.1.1 version now. Any suggestions.

@balaG4046

@hubertdeng123
Copy link
Member

I've put up this PR to help with self-hosted installs using external DBs. However, you can get around this by performing the sql commands manually yourself.

#2827

@praseeb
Copy link

praseeb commented Mar 13, 2024

@hubertdeng123 @aldy505 @BYK @azaslavsky

Any new release for this fix coming soon?

@aldy505
Copy link
Collaborator

aldy505 commented Mar 13, 2024

Any new release for this fix coming soon?

@praseeb I'm kind of lost here, what kind of issue are you experiencing right now?

@praseeb
Copy link

praseeb commented Mar 13, 2024

@aldy505 Looking for this ticket solution #2804

Looks like its closed now. Basically, with non-default Postgresql set-up-and-migrate-database.sh is getting failed.
we were looking for that solution.
Could you please suggest what need to be done.

@hubertdeng123
Copy link
Member

The fix to support non-default postgres db setups should be released soon. Thanks for your patience

#2827

@getsantry
Copy link

getsantry bot commented Apr 5, 2024

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@getsantry getsantry bot added the Stale label Apr 5, 2024
@chadwhitacre
Copy link
Member

#2827 is merged. Are we good here?

@hubertdeng123
Copy link
Member

Should be, and we've cut a release with the changes.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
Archived in project
Archived in project
Development

No branches or pull requests

7 participants