[
https://issues.apache.org/jira/browse/CLOUDSTACK-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-153:
------------------------------------
Description:
Setup : Management server Platform: RHEL 6.3 64 bit , Hypervisor : Xen 6.0.2
1. Setup Advanced Zone
2. Add new account and Create Network 1 with out Redundant Router
3. Deploy instance with the above network.
4. Access DB and check domain_router.
Observation:
redundant_state of Virtual Router is set as UNKNOWN - It Should be no if its
not Redundant Router
Additional Details:
domain_router:
mysql> select id,is_redundant_router,redundant_state,role from domain_router
where id=21;
+----+---------------------+-----------------+----------------+
| id | is_redundant_router | redundant_state | role |
+----+---------------------+-----------------+----------------+
| 21 | 0 | UNKNOWN | VIRTUAL_ROUTER |
+----+---------------------+-----------------+----------------+
1 row in set (0.00 sec)
UNKNOWN status is to indicate , Management Server Failed to get the status of
Virtual Router.
When Router details are accessed from UI, it displayed correctly saying
"Redundant Router : No "
Expected Results :
It should be set as NO with domain_router table if its not a Redundant Router .
Note: This issue is observed in 3.0.5 and Pre 4.0
was:
Setup : Management server Platform: RHEL 6.3 64 bit , Hypervisor : Xen 6.0.2
1. Setup Advanced Zone
2. Add new account and Create Network 1 with out Redundant Router
3. Deploy instance with the above network.
4. Access DB and check domain_router.
Observation:
redundant_state of Virtual Router is set as UNKNOWN - It Should be no if its
not Redundant Router
Additional Details:
domain_router:
mysql> select id,is_redundant_router,redundant_state,role from domain_router
where id=21;
+----+---------------------+-----------------+----------------+
| id | is_redundant_router | redundant_state | role |
+----+---------------------+-----------------+----------------+
| 21 | 0 | UNKNOWN | VIRTUAL_ROUTER |
+----+---------------------+-----------------+----------------+
1 row in set (0.00 sec)
UNKNOWN status is to indicate , Management Server Failed to get the status of
Virtual Router.
When Router details are accessed from UI, it displayed correctly saying
"Redundant Router : No "
Expected Results :
It should be set as NO if its not a Redundant Router .
Note: This issue is observed in 3.0.5 and Pre 4.0
> redundant_state of Virtual Router is set as UNKNOWN - It Should be no if its
> not Redundant Router
> -------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-153
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-153
> Project: CloudStack
> Issue Type: Bug
> Components: Management Server
> Affects Versions: pre-4.0.0
> Reporter: Sailaja Mada
> Priority: Minor
>
> Setup : Management server Platform: RHEL 6.3 64 bit , Hypervisor : Xen 6.0.2
> 1. Setup Advanced Zone
> 2. Add new account and Create Network 1 with out Redundant Router
> 3. Deploy instance with the above network.
> 4. Access DB and check domain_router.
> Observation:
> redundant_state of Virtual Router is set as UNKNOWN - It Should be no if its
> not Redundant Router
> Additional Details:
> domain_router:
> mysql> select id,is_redundant_router,redundant_state,role from domain_router
> where id=21;
> +----+---------------------+-----------------+----------------+
> | id | is_redundant_router | redundant_state | role |
> +----+---------------------+-----------------+----------------+
> | 21 | 0 | UNKNOWN | VIRTUAL_ROUTER |
> +----+---------------------+-----------------+----------------+
> 1 row in set (0.00 sec)
> UNKNOWN status is to indicate , Management Server Failed to get the status
> of Virtual Router.
> When Router details are accessed from UI, it displayed correctly saying
> "Redundant Router : No "
> Expected Results :
> It should be set as NO with domain_router table if its not a Redundant Router
> .
> Note: This issue is observed in 3.0.5 and Pre 4.0
--
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
