Hello Giles and community,
Wondering where documentation contributions should be sent?
For example if a missing spot is found in the current docs or just want
to write down a step-by-step guide for certain customization.
Usually I document any integrations, customizations or deployments for
my colleagues. I am new to ACD and don’t mind creating some docs during the
process of learning (and setting up our production later, fingers crossed!).
Best regards,
Jordan
-----Original Message-----
From: Giles Sirett [mailto:[email protected]]
Sent: Friday, October 5, 2018 6:00 PM
To: [email protected]
Subject: RE: 4.9 to 4.11 upgrade broken
" If so, why hasn’t anyone fixed the following document yet"
Because this is an open source community of volunteers (who would probably
appreciate you wording such points in a more constructive way)
Of course, your could always volunteer to do it yourself
Kind regards
Giles
[email protected]
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
-----Original Message-----
From: Yiping Zhang <[email protected]>
Sent: 04 October 2018 23:11
To: [email protected]
Subject: Re: 4.9 to 4.11 upgrade broken
Gosh, I just encountered exactly the same problem!
If I understand this thread correctly, the root cause is that the document
contains wrong url for systemvm template to download, it points to 4.11.0
version instead of 4.11.1 version of templates for all hypervisors!
If so, why hasn’t anyone fixed the following document yet:
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html
???
Yiping
On 8/21/18, 11:28 PM, "Asai" <[email protected]> wrote:
Before upgrading the router, can I restart the network and check "Make
redundant" so that VMs don’t becoming inaccessible during upgrade? Will this
work without upgrading first?
Asai
> On Aug 21, 2018, at 11:18 PM, Sergey Levitskiy <[email protected]>
wrote:
>
> You can either Restart the network with cleanup or simply destroy VR and
let it be created on the next VM deployment.
>
> On 8/21/18, 11:13 PM, "Asai" <[email protected]> wrote:
>
> Thanks, nearly back up and running. One question, what about the
Virtual Router upgrade? What do I do if the upgrade fails on the Virtual
Router? Looking for docs on this, but can’t find anything.
>
> Thanks for your assistance.
>
> Asai
>
>
>> On Aug 21, 2018, at 6:35 PM, Sergey Levitskiy <[email protected]>
wrote:
>>
>> Yes. this should bring you back.
>> However if you perform what you described in your previous reply +
rename template in CS DB to systemvm-kvm-4.11.1 from what it is now
systemvm-kvm-4.11 you should be able to bring all up as it is. Updating
template image is not enough.
>>
>> On 8/21/18, 4:04 PM, "Asai" <[email protected]> wrote:
>>
>> OK thanks a lot, Sergey,
>>
>> That helps. What’s the best method to roll back? Just use yum to
roll back to 4.9 and rebuild the DB from backup?
>>
>>
>>> On Aug 21, 2018, at 3:59 PM, Sergey Levitskiy <[email protected]>
wrote:
>>>
>>> The fastest and easiest way is to rollback both DB and management
server and start over. You need to have correct systemVM template registered
before you initiate an upgrade.
>>>
>>> Thanks,
>>> Sergey
>>>
>>>
>>> On 8/21/18, 2:30 PM, "Asai" <[email protected]> wrote:
>>>
>>> Is there anybody out there that can assist with this?
>>>
>>> Asai
>>>
>>>
>>>> On Aug 21, 2018, at 2:01 PM, Asai <[email protected]> wrote:
>>>>
>>>> Is there any more specific instruction about this?
>>>>
>>>> What is the best practice? Should I roll back first? Is there any
documentation about rolling back? Do I uninstall cloudstack management and
re-install 4.9?
>>>>
>>>> Or is it as simple as just overwriting the file? If so, what about
the template.properties file and the metadata in there like qcow2.size?
>>>>
>>>> filename=9cebb971-8605-3493-86f3-f5d1aef1715e.qcow2
>>>> id=225
>>>> qcow2.size=316310016
>>>> public=true
>>>> uniquename=225-2-826a2950-bb8e-34dd-9420-1eb24ea16b4a
>>>> qcow2.virtualsize=2516582400
>>>> virtualsize=2516582400
>>>> checksum=2d8d1e4eacc976814b97f02849481433
>>>> hvm=true
>>>> description=systemvm-kvm-4.11
>>>> qcow2=true
>>>> qcow2.filename=9cebb971-8605-3493-86f3-f5d1aef1715e.qcow2
>>>> size=316310016
>>>>
>>>>
>>>> Asai
>>>>
>>>>
>>>>> On Aug 21, 2018, at 1:56 PM, ilya musayev
<[email protected]> wrote:
>>>>>
>>>>> yes - please try the proper 4.11 systemvm templates.
>>>>>
>>>>>> On Aug 21, 2018, at 1:54 PM, Asai <[email protected]> wrote:
>>>>>>
>>>>>> Can I manually download the systemvm template from here?
http://download.cloudstack.org/systemvm/4.11/
<http://download.cloudstack.org/systemvm/4.11/>
>>>>>>
>>>>>> Then manually overwrite it in the filesystem and update it
accordingly in the database?
>>>>>>
>>>>>> Asai
>>>>>>
>>>>>>
>>>>>>> On Aug 21, 2018, at 1:40 PM, Asai <[email protected]>
wrote:
>>>>>>>
>>>>>>> 4.11.0
>>>>>>>
>>>>>>> As outlined in this
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html
<http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html>
>>>>>>>> On Aug 21, 2018, at 1:37 PM, ilya musayev
<[email protected]> wrote:
>>>>>>>>
>>>>>>>> which template did you use?
>>>>>>>>
>>>>>>>>> On Aug 21, 2018, at 1:36 PM, Asai <[email protected]>
wrote:
>>>>>>>>>
>>>>>>>>> Greetings,
>>>>>>>>>
>>>>>>>>> I just tried to upgrade from 4.9 to 4.11, but it looks like the
system VM template I downloaded according to the upgrade guide is the wrong
template. It’s 4.11, but I upgraded to 4.11.1 and I get this error message:
>>>>>>>>>
>>>>>>>>> Caused by: com.cloud.utils.exception.CloudRuntimeException:
4.11.1.0KVM SystemVm template not found. Cannot upgrade system Vms
>>>>>>>>> at
com.cloud.upgrade.dao.Upgrade41100to41110.updateSystemVmTemplates(Upgrade41100to41110.java:281)
>>>>>>>>> at
com.cloud.upgrade.dao.Upgrade41100to41110.performDataMigration(Upgrade41100to41110.java:68)
>>>>>>>>> at
com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:578)
>>>>>>>>> ... 53 more
>>>>>>>>> 2018-08-21 13:28:25,257 INFO [o.e.j.s.h.ContextHandler]
(main:null) (logid:) Started
o.e.j.s.h.MovedContextHandler@15bfd87{/,null,AVAILABLE}
>>>>>>>>> 2018-08-21 13:28:25,317 INFO [o.e.j.s.AbstractConnector]
(main:null) (logid:) Started
ServerConnector@4b1c1ea0{HTTP/1.1,[http/1.1]}{:::8080}
>>>>>>>>> 2018-08-21 13:28:25,318 INFO [o.e.j.s.Server] (main:null)
(logid:) Started @20725ms
>>>>>>>>>
>>>>>>>>> Can anyone assist with getting this corrected?
>>>>>>>>>
>>>>>>>>> Thank you,
>>>>>>>>> Asai
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
