-
Notifications
You must be signed in to change notification settings - Fork 502
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
Fix/caas relation datebag inconsistency #10270
Merged
jujubot
merged 12 commits into
juju:2.6
from
ycliuhw:fix/caas-relation-datebag-inconsistency
Jun 7, 2019
Merged
Fix/caas relation datebag inconsistency #10270
jujubot
merged 12 commits into
juju:2.6
from
ycliuhw:fix/caas-relation-datebag-inconsistency
Jun 7, 2019
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…de if units should be removed or not, also remove dying or dead unit if it has already been removed from the cloud
…to CloudService for ensuring desiredScale immutable until it is applied to to the cluster;
…eProtected in CloudService
ycliuhw
force-pushed
the
fix/caas-relation-datebag-inconsistency
branch
2 times, most recently
from
June 7, 2019 06:22
a3e2b68
to
11cd353
Compare
wallyworld
approved these changes
Jun 7, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Main issue to fix is that it will break older operators (need to allow nil generation)
apiserver/facades/controller/caasunitprovisioner/provisioner.go
Outdated
Show resolved
Hide resolved
apiserver/facades/controller/caasunitprovisioner/provisioner.go
Outdated
Show resolved
Hide resolved
apiserver/facades/controller/caasunitprovisioner/provisioner.go
Outdated
Show resolved
Hide resolved
apiserver/facades/controller/caasunitprovisioner/provisioner_test.go
Outdated
Show resolved
Hide resolved
ycliuhw
force-pushed
the
fix/caas-relation-datebag-inconsistency
branch
2 times, most recently
from
June 7, 2019 09:11
7306dc6
to
8c83a17
Compare
ycliuhw
force-pushed
the
fix/caas-relation-datebag-inconsistency
branch
from
June 7, 2019 10:41
8c83a17
to
94cdabf
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of change
Fix: statefulset pod units are been removed then cause relation data bag lost;
QA steps
$ kubectl delete pod/mariadb-k8s-0 -n $NS
monitor juju status to confirm, the unit number is not changed;
add/remove units;
Documentation changes
None
Bug reference
https://bugs.launchpad.net/juju/+bug/1830745