[
https://issues.apache.org/jira/browse/CLOUDSTACK-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nux updated CLOUDSTACK-7781:
----------------------------
Description:
Hello,
During a VR upgrade from 4.3.1 the VM will not start because missing
"/opt/cloud/bin/createipAlias.sh", this is a typo as the file is present as
"/opt/cloud/bin/createIpAlias.sh".
This blocks the VR upgrade, but not the SSVM or the CPVM.
The work-around was to copy /opt/cloud/bin/createIpAlias.sh to
/opt/cloud/bin/createipAlias.sh in the SSVM template, before running the
cloudstack-systemvmadm upgrade procedure.
The problem is not always encountered, I do have a testing environment that was
not hit by the issue. Sod's law dictates this will manifest itself only in
production, critical deployments. :)
Imho the 4.4.1 sysvm template should be updated ASAP so other people won't hit
this issue.
For 4.5 this is fixed in https://issues.apache.org/jira/browse/CLOUDSTACK-7246
Made some noise about it on the mailing list, so for more details and logs go
to eg
http://www.mail-archive.com/dev@cloudstack.apache.org/msg36853.html
http://www.mail-archive.com/dev@cloudstack.apache.org/msg36871.html
was:
Hello,
During a VR upgrade from 4.3.1 the VM will not start because missing
"/opt/cloud/bin/createipAlias.sh", this is a typo as the file is present as
"/opt/cloud/bin/createIpAlias.sh".
This blocks the VR upgrade, but not the SSVM or the CPVM.
The work-around was to copy /opt/cloud/bin/createIpAlias.sh to
/opt/cloud/bin/createipAlias.sh in the SSVM template, before running the
cloudstack-systemvmadm upgrade procedure.
The problem is not always encountered, I do have a testing environment that was
not hit by the issue. Sod's law dictates this will manifest itself only in
production, critical deployments. :)
Imho the 4.4.1 sysvm template should be updated ASAP so other people won't hit
this issue.
Made some noise about it on the mailing list, so for more details and logs go
to eg
http://www.mail-archive.com/dev@cloudstack.apache.org/msg36853.html
http://www.mail-archive.com/dev@cloudstack.apache.org/msg36871.html
> Typo in calling /opt/cloud/bin/createipAlias.sh
> -----------------------------------------------
>
> Key: CLOUDSTACK-7781
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7781
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: SystemVM
> Affects Versions: 4.4.0, 4.4.1
> Environment: CentOS 6.5 mgmt & HVs
> Reporter: Nux
> Priority: Blocker
> Labels: systemvm
> Fix For: 4.5.0
>
>
> Hello,
> During a VR upgrade from 4.3.1 the VM will not start because missing
> "/opt/cloud/bin/createipAlias.sh", this is a typo as the file is present as
> "/opt/cloud/bin/createIpAlias.sh".
> This blocks the VR upgrade, but not the SSVM or the CPVM.
> The work-around was to copy /opt/cloud/bin/createIpAlias.sh to
> /opt/cloud/bin/createipAlias.sh in the SSVM template, before running the
> cloudstack-systemvmadm upgrade procedure.
> The problem is not always encountered, I do have a testing environment that
> was not hit by the issue. Sod's law dictates this will manifest itself only
> in production, critical deployments. :)
> Imho the 4.4.1 sysvm template should be updated ASAP so other people won't
> hit this issue.
> For 4.5 this is fixed in https://issues.apache.org/jira/browse/CLOUDSTACK-7246
> Made some noise about it on the mailing list, so for more details and logs go
> to eg
> http://www.mail-archive.com/dev@cloudstack.apache.org/msg36853.html
> http://www.mail-archive.com/dev@cloudstack.apache.org/msg36871.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
