cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangeetha Hariharan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-4643) When the master host is put in maitenance mode , another host in the pool is set as master. This is with manage.xenserver.pool.master set to false.
Date Tue, 10 Sep 2013 23:35:54 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sangeetha Hariharan updated CLOUDSTACK-4643:
--------------------------------------------

    Attachment: management-server.log
    
> When the master host is put in maitenance mode , another host in the pool is set as master.
This is with manage.xenserver.pool.master set to false.
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4643
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4643
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.1
>         Environment: Build from 4.2-forward
>            Reporter: Sangeetha Hariharan
>            Priority: Critical
>             Fix For: 4.2.1
>
>         Attachments: management-server.log
>
>
> When the master host is put in maitenance mode , another host in the pool is set as master.
This is with manage.xenserver.pool.master set to false.
> Steps to reproduce the problem:
> Advanced zone set up with 2 Xenserver hosts (6.0.2) in cluster.
> I want to upgrade the Xenserver hosts to 6.2.
> Followed these steps:
> 1. Edit the file /etc/cloudstack/management/environment.properties and add the following
:
> manage.xenserver.pool.master=false
> 2. Restart management server.
> 3. Put the Master Host (H1) in maintenance mode.
> This results in the all the Vms in this host to migrate to another host (H2).
>  It also results in making the other host (H2) in the cluster as the Master of this pool.
> 4. Unmanage the cluster.
> 5. Try to upgrade the host (H1) that was put in maintenance mode.
> Upgrade complains saying that the master host of the pool should be upgraded before this
host can be upgraded.
> Step 3 which is putting Master Host (H1) to maintenance mode should not have resulted
in changing the master of the pool to another host.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message