Merge lp:~stub/charms/precise/postgresql/test-upgrade-charm into lp:charms/postgresql
Proposed by
Stuart Bishop
Status: | Merged |
---|---|
Merge reported by: | Marco Ceppi |
Merged at revision: | not available |
Proposed branch: | lp:~stub/charms/precise/postgresql/test-upgrade-charm |
Merge into: | lp:charms/postgresql |
Prerequisite: | lp:~stub/charms/precise/postgresql/wal-e |
Diff against target: |
77 lines (+28/-2) 2 files modified
hooks/hooks.py (+4/-0) test.py (+24/-2) |
To merge this branch: | bzr merge lp:~stub/charms/precise/postgresql/test-upgrade-charm |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Review Queue (community) | automated testing | Needs Fixing | |
charmers | Pending | ||
Review via email: mp+229914@code.launchpad.net |
Description of the change
I've been trying to track down a weird state I've seen. This test failed to find it, since it passes, but it is a useful test to keep. It simply confirms that 'juju upgrade-charm' keeps the existing database intact. It doesn't test upgrades from old versions of the charm, which will be mojo jobs.
To post a comment you must log in.
merged in https:/ /code.launchpad .net/~stub/ charms/ precise/ postgresql/ integration/ +merge/ 233666