Merge lp:~julian-edwards/maas/cluster-name-override-bug-1380805 into lp:~maas-committers/maas/trunk
Proposed by
Julian Edwards
Status: | Rejected |
---|---|
Rejected by: | Julian Edwards |
Proposed branch: | lp:~julian-edwards/maas/cluster-name-override-bug-1380805 |
Merge into: | lp:~maas-committers/maas/trunk |
Diff against target: |
36 lines (+15/-0) 2 files modified
src/maasserver/forms.py (+4/-0) src/maasserver/tests/test_forms_nodegroup.py (+11/-0) |
To merge this branch: | bzr merge lp:~julian-edwards/maas/cluster-name-override-bug-1380805 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Gavin Panella (community) | Abstain | ||
Raphaël Badin (community) | Abstain | ||
Review via email: mp+238226@code.launchpad.net |
Commit message
Don't default cluster_name in NodeGroupDefineForm if it's already set. This is possibly the cause of clusters getting unilaterally renamed as part of the new cluster registration protocol for RPC when upgrading to 1.7.
Description of the change
The fix depends on the "instance" being present in the form; I'm testing this now in the real world to see if that's the case, but it will take an hour or more to install a fresh 1.5 and then upgrade to a test 1.7 package.
To post a comment you must log in.
Unmerged revisions
- 3248. By Julian Edwards
-
add back defaulting behaviour if the name doesn't exist yet
- 3247. By Julian Edwards
-
Don't default cluster_name as it can override the existing name
- 3246. By Julian Edwards
-
Failing test
Oh well I just tested this, and after upgrade the cluster name was empty! So this is clearly the wrong approach, but I am a little stumped. I'll wait for rvb to get here as I am still missing info on how rpc-based cluster registration works nowadays.