Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
From: wilderrodrigues <git@git.apache.org>
To: dev@cloudstack.apache.org
Reply-To: dev@cloudstack.apache.org
References: <git-pr-1050-cloudstack@git.apache.org>
In-Reply-To: <git-pr-1050-cloudstack@git.apache.org>
Subject: [GitHub] cloudstack pull request: CLOUDSTACK-9046 - Fix upgrade path
 from 4...
Content-Type: text/plain
Message-Id: <20151109143550.375BEE0243@git1-us-west.apache.org>
Date: Mon,  9 Nov 2015 14:35:50 +0000 (UTC)

Github user wilderrodrigues commented on the pull request:

    https://github.com/apache/cloudstack/pull/1050#issuecomment-155080182
  
    Ping @remibergsma @borisroman @DaanHoogland @wido 
    
    Tests were executed as described below:
    
    * Deploy 4.4.4
      - KVM Host
      - Management Server
      - 2 VMs running on Isolated Networks + 2Pub IPs + FW/PF
      - 2 VPCs  with 1 tier each + 1 VM per tier + ACL + PF
      - SSH into the 4 VMs to testify it was all fine with 4.4.4
    
    * Upgrade steps
      - Register SysteVM 4.5 and 4.6
        - Needed because we were upgrading from 4.4.4
      - Stop/Update the KVM agent
      - Stop/Update the Management Server
      - Check the Routers say "Requires Upgrade = YES"
      - SSH into SSVM/CPVM and check /etc/cloudstack-release file. It should say 4.4.1
      - Destroy SSVM/CPVM
      - Check again the /etc/cloudstack-release file. It should say 4.6.0
      - Reboot the Virtual Routers
      - Check the /etc/cloudstack-release. It should say 4.6.0
      - SSH into the VMs via the public IPs. It should be possible


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---