Description of problem: I attempted to move a gear and it would not move. I verified the move failed and found this in the log file: I, [2012-11-20T11:26:42.151009 #21049] INFO -- : openshift.rb:360:in `cartridge_do_action' cartridge_do_ action validation = php-5.3 add-alias 'auto' 'lyurl' '7990b6d2ebf64b96a7f0250dbf058f81' '1' I, [2012-11-20T11:26:42.151988 #21049] INFO -- : openshift.rb:341:in `handle_cartridge_action' handle_ca rtridge_action executing /usr/bin/runcon -l s0-s0:c0.c1023 /usr/libexec/openshift/cartridges/php-5.3/info /hooks/add-alias 'auto' 'lyurl' '7990b6d2ebf64b96a7f0250dbf058f81' '1' 2>&1 I, [2012-11-20T11:26:42.308667 #21049] INFO -- : openshift.rb:330:in `complete_process_gracefully' ERROR : (2) ------ CLIENT_ERROR: FATAL ERROR: 1 Already exists. ------) It appears that there was an alias for this application named "1". I believe this should be the FQDN of the application. I listed out the server aliases on the box: [root ~]# ll /etc/httpd/conf.d/openshift/7990b* -rw-r--r--. 1 root root 699 Nov 20 11:39 /etc/httpd/conf.d/openshift/7990b6d2ebf64b96a7f0250dbf058f81_lyurl_auto.conf /etc/httpd/conf.d/openshift/7990b6d2ebf64b96a7f0250dbf058f81_lyurl_auto: total 36 -rw-r--r--. 1 root root 69 Nov 20 11:39 0000000000000_disabled.conf -rw-r--r--. 1 root root 125 Nov 20 11:39 00000_default.conf -rw-r--r--. 1 root root 14 Nov 20 11:40 server_alias-1.conf -rw-r--r--. 1 root root 29 Nov 20 11:39 server_alias-lanyu19950216.tk.conf -rw-r--r--. 1 root root 29 Nov 20 11:39 server_alias-lanyu19950316.tk.conf -rw-r--r--. 1 root root 22 Nov 20 11:40 server_alias-lan-yu.tk.conf -rw-r--r--. 1 root root 33 Nov 20 11:40 server_alias-www.lanyu19950316.tk.conf -rw-r--r--. 1 root root 26 Nov 20 11:40 server_alias-www.lan-yu.tk.conf -rw-r--r--. 1 root root 94 Nov 20 11:39 zzzzz_proxy.conf I believe these are causing the oo-admin-move to fail. Steps to Reproduce: 1. Create a gear. 2. Create a server alias like the above mentioned: server_alias-1.conf Its contents: ServerAlias 1 3. Attempt an oo-admin-move on this gear. Actual results: The gear fails to move. Expected results: The gear should not be able to create server-alias's that will not move onto other hosts. Additional info: Gear in question: 7990b6d2ebf64b96a7f0250dbf058f81
Moving the remainder of this work to futurefeature
This is only applicable to move cross district and we are considering removing that feature.
The remaining issue of duplicate and problem aliases was moved into US3232.