cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kishan Kavala (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-5277) upgrade router template API is not upgrading stopped routers
Date Tue, 10 Dec 2013 12:33:08 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844232#comment-13844232
] 

Kishan Kavala commented on CLOUDSTACK-5277:
-------------------------------------------

We should not start VRs which were stopped by admin. Whenever the VR is started, it'll be
upgraded. 
cloudsys-adm script behavior was also same.

> upgrade router template API is not upgrading stopped routers
> ------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5277
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5277
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade, Virtual Router
>    Affects Versions: 4.3.0
>         Environment: upgraded from 3.0.7 to 4.3
>            Reporter: shweta agarwal
>            Assignee: Kishan Kavala
>            Priority: Critical
>             Fix For: 4.3.0
>
>
> Currently upgrade router API take care of only running routers so router that are stop
before calling upgrade router template is missed from upgrades.
> So rather than calling reboot router internally for upgrade router template its better
to call stop /start router api .
> this way it will take care of stopped routers as well .



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message