Uploaded image for project: 'CloudStack'
  1. CloudStack
  2. CLOUDSTACK-1151

vmware systemVm template upgrade is missing in 4.0 upgrade

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • 4.0.0
    • 4.0.2
    • Template
    • Security Level: Public (Anyone can view this level - this is the default.)
    • None
    • vmware esx 4.1/5.1

    Description

      I have upgraded from 3.0.2 to 4.0.0 and the management server started and updated the database just fine, however the rest of the upgrade procedure just does not work.
      I'm running the script: "nohup cloud-sysvmadm -d 192.168.1.5 -u cloud -p password -c -r > sysvm.log 2>&1 &" accordingly to my environment and see in its log it is trying to stop/start a router.
      It stops it, then recreates the same secondary datastore (vmware) and then starts the same router rather than deploying the new imported systemVM template and creating a new one.
      It neither touches the sec-storage VM nor the console-proxy VM so new management system, old systemVMs.

      No errors during running the script no errors in the log:
      Stopping and starting 1 running routing vm(s)...
      Done restarting router(s).

      Attachments

        Activity

          People

            Unassigned Unassigned
            tamasm Tamas Monos
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: