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

[postgresql] Permission's error installing chart 8.6.3 and warning #2171

Closed
mkanakis opened this issue Mar 31, 2020 · 5 comments
Closed

[postgresql] Permission's error installing chart 8.6.3 and warning #2171

mkanakis opened this issue Mar 31, 2020 · 5 comments
Labels
stale 15 days without activity

Comments

@mkanakis
Copy link

mkanakis commented Mar 31, 2020

I am coping this over from helm stable Charts.

Describe the bug
I have been using version 8.4.3 for a while now. Today I attempted to install 8.6.3 which led to a chmod permissions error.

After removing the chart and re-installing it with:

volumePermissions: enabled: "true"

It deployed successfully with an init Container as well but also gave the following warning:

postgresql 14:44:14.25 WARN ==> Data directory is set with a legacy value, adapting POSTGRESQL_DATA_DIR...
postgresql 14:44:14.25 WARN ==> POSTGRESQL_DATA_DIR set to "/var/lib/bitnami/postgresql/data"!!

I don't mind having an init container running, however I am worried to upgrade the rest of the containers due to this warning. Should I be worried upgrading from 8.4.3 to 8.6.3? Will this affect existing data somehow?

Version of Helm and Kubernetes:
Helm Version -> v2.14.3-rancher1
Kubernetes Version -> 1.17.4

Thanks.

Edit: fix styling

@mkanakis mkanakis added the bug label Mar 31, 2020
@Mauraza
Copy link
Contributor

Mauraza commented Apr 1, 2020

Hi @mkanakis.

only the path where PostgreSQL saves the data has been changed, anyway it is always advisable to make a copy of the data. Please check https://github.com/bitnami/charts/tree/master/bitnami/postgresql#persistence

@mkanakis
Copy link
Author

mkanakis commented Apr 1, 2020

Thanks for the quick reply @Mauraza,

Of course I will make a copy but I would prefer avoiding the hassle in the first place.
In any case, existing data in the old path will remain there, I guess.

About the chmod error, do you know what changed and I have to spawn an initContainer now?

Best,
Marios.

@Mauraza
Copy link
Contributor

Mauraza commented Apr 1, 2020

Could you copy the error of chmod? please I need to know when it's happened and which is the folder.

@stale
Copy link

stale bot commented Apr 16, 2020

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@stale stale bot added the stale 15 days without activity label Apr 16, 2020
@stale
Copy link

stale bot commented Apr 23, 2020

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@stale stale bot closed this as completed Apr 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale 15 days without activity
Projects
None yet
Development

No branches or pull requests

2 participants