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

Upgrade from Pravega version<0.7 to Pravega Version>=0.7 with external access enabled is failing #358

Closed
Prabhaker24 opened this issue Apr 7, 2020 · 2 comments
Assignees

Comments

@Prabhaker24
Copy link
Contributor

Description

Because of the changes for fixing of #312 we have modified the name of the segment store for versions above 0.7 but have not changed the service name and the script that runs as part of the creation of segment store needs the new service name.

Importance

Must have

Location

upgrade.go

Suggestions for an improvement

In the upgrade.go while deleting the segment store pod for version <0.7 remove the service as well

@jkhalack
Copy link

jkhalack commented Apr 7, 2020

Please, take into account that upgrade from 0.7.0 pravega that was deployed with 0.4.x releases of pravega-operator is failing too (the previous versions of pravega-operator used uniform naming for all versions of pravega).

@Prabhaker24
Copy link
Contributor Author

this is fixed this pr #368

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants