Ok, so how I "solved" it: Followed the upgrade procedure to the letter, but before running cloudstack-sysvmadm to upgrade my sytemvms I have replaced the QCOW2 file in the secondary storage with a modified template in which I copied /opt/cloud/bin/createIpAlias.sh to /opt/cloud/bin/createipAlias.sh (and made it immutable, just to make sure it doesn't go anywhere) ...
After that I ran "nohup cloudstack-sysvmadm -d IPaddress -u cloud -p password -a > sysvm.log 2>&1 &" Ugly, but it works. Thanks for helping me understand where the problem is exactly.. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Daan Hoogland" <daan.hoogl...@gmail.com> > To: "dev" <dev@cloudstack.apache.org> > Sent: Wednesday, 22 October, 2014 14:43:45 > Subject: Re: 431 to 441, VR upgrade fails with VR config: execution failed: > "/opt/cloud/bin/createipAlias.sh" > Jayapal, this was fixed but not in 4.4. why? and why does Lucian not > hit it in 4.3 that contains the same error? > > On Wed, Oct 22, 2014 at 2:22 PM, Nux! <n...@li.nux.ro> wrote: >> Ok, you lost me. So what do I need to modify to correct this? >> >> Would customising the sysvm template and symlinking >> /opt/cloud/bin/createIpAlias.sh to /opt/cloud/bin/createipAlias.sh solve the >> issue? >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! >> www.nux.ro >> >> ----- Original Message ----- >>> From: "Jayapal Reddy Uradi" <jayapalreddy.ur...@citrix.com> >>> To: "<dev@cloudstack.apache.org>" <dev@cloudstack.apache.org> >>> Sent: Wednesday, 22 October, 2014 13:18:05 >>> Subject: Re: 431 to 441, VR upgrade fails with VR config: execution failed: >>> "/opt/cloud/bin/createipAlias.sh" >> >>> Hi Nux, >>> >>> The problem is not from the template. >>> The file in the systemvm.iso has correct file name. >>> VR config feature is referred it as incorrect. >>> >>> Thanks, >>> Jayapal >>> On 22-Oct-2014, at 5:18 PM, Nux! <n...@li.nux.ro> wrote: >>> >>>> Daan, >>>> >>>> It may be old, but I don't see the problem with the 4.3.0 sysvm tmpl (that >>>> I am >>>> still using, even with 4.3.1). >>>> >>>> -- >>>> Sent from the Delta quadrant using Borg technology! >>>> >>>> Nux! >>>> www.nux.ro >>>> >>>> ----- Original Message ----- >>>>> From: "Daan Hoogland" <daan.hoogl...@gmail.com> >>>>> To: "dev" <dev@cloudstack.apache.org> >>>>> Sent: Wednesday, 22 October, 2014 11:40:09 >>>>> Subject: Re: 431 to 441, VR upgrade fails with VR config: execution >>>>> failed: >>>>> "/opt/cloud/bin/createipAlias.sh" >>>> >>>>> Just checked, >>>>> >>>>> It is fixed in 4.5 but wasn't backported into 4.4. It is old code and >>>>> the problem is in 4.3 as well. >>>>> >>>>> On Wed, Oct 22, 2014 at 9:39 AM, Nux! <n...@li.nux.ro> wrote: >>>>>> Jayapal, >>>>>> >>>>>> Thanks, but why are we releasing a faulty systemvm template? Can't we >>>>>> upload a >>>>>> new one without the typo? >>>>>> >>>>>> Lucian >>>>>> >>>>>> -- >>>>>> Sent from the Delta quadrant using Borg technology! >>>>>> >>>>>> Nux! >>>>>> www.nux.ro >>>>>> >>>>>> ----- Original Message ----- >>>>>>> From: "Jayapal Reddy Uradi" <jayapalreddy.ur...@citrix.com> >>>>>>> To: "<dev@cloudstack.apache.org>" <dev@cloudstack.apache.org> >>>>>>> Sent: Wednesday, 22 October, 2014 05:52:14 >>>>>>> Subject: Re: 431 to 441, VR upgrade fails with VR config: execution >>>>>>> failed: >>>>>>> "/opt/cloud/bin/createipAlias.sh" >>>>>> >>>>>>> Hi Nux, >>>>>>> >>>>>>> There is spelling mistake 'i' instead of 'I' in the file name >>>>>>> 'createipAlias.sh' >>>>>>> >>>>>>> Work around is in VR change createIpAlias.sh -> createipAlias.sh >>>>>>> Observe the MS log once the VR entered into Running state stop the MS >>>>>>> so that VR >>>>>>> won't be destroyed. >>>>>>> Now go to VR and change the file name. >>>>>>> >>>>>>> This issue got fixed in 4.5 CLOUDSTACK-7246 >>>>>>> >>>>>>> Thanks, >>>>>>> Jayapal >>>>>>> On 22-Oct-2014, at 6:03 AM, Nux! <n...@li.nux.ro> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I almost upgraded from 4.3.1 to 4.4.1, everything went smoothly except >>>>>>>> the VR >>>>>>>> upgrade (the other sysvms are fine). It will not upgrade, even if I >>>>>>>> delete it >>>>>>>> and create another, same story: >>>>>>>> >>>>>>>> On the agent I see: >>>>>>>> >>>>>>>> 2014-10-22 01:17:17,857 DEBUG [kvm.resource.LibvirtComputingResource] >>>>>>>> (agentRequest-Handler-5:null) Executing: >>>>>>>> /usr/share/cloudstack-common/scripts/network/domr/router_proxy.sh >>>>>>>> vr_cfg.sh >>>>>>>> 169.254.1.228 -c >>>>>>>> /var/cache/cloud/VR-5109f323-dc37-4af2-b75d-41dd65acbf93.cfg >>>>>>>> 2014-10-22 01:17:17,934 DEBUG [kvm.resource.LibvirtComputingResource] >>>>>>>> (agentRequest-Handler-5:null) Exit value is 1 >>>>>>>> 2014-10-22 01:17:17,934 DEBUG [kvm.resource.LibvirtComputingResource] >>>>>>>> (agentRequest-Handler-5:null) VR config: execution failed: >>>>>>>> "/opt/cloud/bin/createipAlias.sh >>>>>>>> 289:10.13.208.78:255.255.255.248-224:10.187.71.194:255.255.255.192-", >>>>>>>> check >>>>>>>> /var/log/cloud.log in VR for details >>>>>>>> >>>>>>>> But the VR is being destroyed and I cannot investigate the >>>>>>>> /var/log/cloud.log >>>>>>>> ... >>>>>>>> >>>>>>>> >>>>>>>> On the management log: >>>>>>>> >>>>>>>> Unable to start instance due to Unable to start >>>>>>>> VM[DomainRouter|r-443-VM] due to >>>>>>>> error in finalizeStart, not retrying >>>>>>>> more here http://pastebin.com/raw.php?i=fY7v8Sak >>>>>>>> >>>>>>>> -- >>>>>>>> Sent from the Delta quadrant using Borg technology! >>>>>>>> >>>>>>>> Nux! >>>>>>>> http://secure-web.cisco.com/1QTvqoF2kC8J2AVldxqw_eHOGu2lEYYQPIXQRv2AfAxFtBJkyYcGU9BExyL8RBhIRG7P2ubiMb3y4pE3uGE1bqL5YsDZRudJJY4-06h0_ISiM0scnTIC5qgQLx3NI9chTB64l33iEIMZFcsu49mvxV7PadSYmEtNCre8_xzMds-I/http%3A%2F%2Fwww.nux.ro >>>>> >>>>> >>>>> >>>>> -- >>> >> Daan > > > > -- > Daan
