yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #77962
[Bug 1824444] [NEW] Instance is in active status though instance created with multiple network do not have multiple proper ports
Public bug reported:
when instance with multiple networks is created, instance is in active
status even thoung it does not have proper ports matching with multiple
networks while rescheduling for some reason.
root@dg-rp1-controller-01:> nova boot --nic <net-id=[vlb-bgp-net], net-id=[g_pz1_net], net-id=[vlb-mgmt-net]> ....
root@dg-rp1-controller-01:> nova show dc8762c2-e11b-4a38-bb6a-a4db908e9867
....
|
| OS-EXT-SRV-ATTR:host | dg-rp1-compute-06
|
| g_pz1_net network | 192.168.200.22
|
| status | ACTIVE
|
| vlb-bgp-net network | 10.214.1.19, 10.214.1.25 |
+--------------------------------------+-------------------------------
It happens when rescheduling sometimes. I think it shoud be done in
error status but active status.
Expected result:
root@dg-rp1-controller-01:~:> nova show 2bf34bc7-bf78-46db-9199-4072db111256
...
|
| OS-EXT-SRV-ATTR:host | dg-rp1-compute-06
|
| g_pz1_net network | 192.168.200.12
|
| status | ACTIVE
|
| vlb-bgp-net network | 10.214.1.33
|
| vlb-mgmt-net network | 10.208.0.36
|
+--------------------------------------+--------------------------------
** Affects: nova
Importance: Undecided
Status: New
** Description changed:
when instance with multiple networks is created, instance is in active
status even thoung it does not have proper ports matching with multiple
networks while rescheduling for some reason.
root@dg-rp1-controller-01:> nova boot --nic <net-id=[vlb-bgp-net], net-id=[g_pz1_net], net-id=[vlb-mgmt-net]> ....
root@dg-rp1-controller-01:> nova show dc8762c2-e11b-4a38-bb6a-a4db908e9867
....
|
- | OS-EXT-SRV-ATTR:host | dg-rp1-compute-06
+ | OS-EXT-SRV-ATTR:host | dg-rp1-compute-06
|
- | g_pz1_net network | 192.168.200.22
+ | g_pz1_net network | 192.168.200.22
|
- | status | ACTIVE
+ | status | ACTIVE
|
| vlb-bgp-net network | 10.214.1.19, 10.214.1.25 |
- +--------------------------------------+-----------------------------------------
+ +--------------------------------------+-------------------------------
It happens when rescheduling sometimes. I think it shoud be done with
error status but active status.
Expected result:
root@dg-rp1-controller-01:~:> nova show 2bf34bc7-bf78-46db-9199-4072db111256
...
|
| OS-EXT-SRV-ATTR:host | dg-rp1-compute-06 |
- | g_pz1_net network | 192.168.200.12
+ | g_pz1_net network | 192.168.200.12
|
- | status | ACTIVE
+ | status | ACTIVE
|
| vlb-bgp-net network | 10.214.1.33 |
| vlb-mgmt-net network | 10.208.0.36 |
- +--------------------------------------+-----------------------------------------
+ +--------------------------------------+--------------------------------
** Description changed:
when instance with multiple networks is created, instance is in active
status even thoung it does not have proper ports matching with multiple
networks while rescheduling for some reason.
root@dg-rp1-controller-01:> nova boot --nic <net-id=[vlb-bgp-net], net-id=[g_pz1_net], net-id=[vlb-mgmt-net]> ....
root@dg-rp1-controller-01:> nova show dc8762c2-e11b-4a38-bb6a-a4db908e9867
....
|
| OS-EXT-SRV-ATTR:host | dg-rp1-compute-06
|
| g_pz1_net network | 192.168.200.22
|
| status | ACTIVE
|
| vlb-bgp-net network | 10.214.1.19, 10.214.1.25 |
+--------------------------------------+-------------------------------
It happens when rescheduling sometimes. I think it shoud be done with
error status but active status.
Expected result:
root@dg-rp1-controller-01:~:> nova show 2bf34bc7-bf78-46db-9199-4072db111256
...
|
- | OS-EXT-SRV-ATTR:host | dg-rp1-compute-06 |
+ | OS-EXT-SRV-ATTR:host | dg-rp1-compute-06
+ |
| g_pz1_net network | 192.168.200.12
|
| status | ACTIVE
|
| vlb-bgp-net network | 10.214.1.33 |
| vlb-mgmt-net network | 10.208.0.36 |
+--------------------------------------+--------------------------------
** Description changed:
when instance with multiple networks is created, instance is in active
status even thoung it does not have proper ports matching with multiple
networks while rescheduling for some reason.
root@dg-rp1-controller-01:> nova boot --nic <net-id=[vlb-bgp-net], net-id=[g_pz1_net], net-id=[vlb-mgmt-net]> ....
root@dg-rp1-controller-01:> nova show dc8762c2-e11b-4a38-bb6a-a4db908e9867
....
|
| OS-EXT-SRV-ATTR:host | dg-rp1-compute-06
|
| g_pz1_net network | 192.168.200.22
|
| status | ACTIVE
|
| vlb-bgp-net network | 10.214.1.19, 10.214.1.25 |
+--------------------------------------+-------------------------------
It happens when rescheduling sometimes. I think it shoud be done with
error status but active status.
Expected result:
root@dg-rp1-controller-01:~:> nova show 2bf34bc7-bf78-46db-9199-4072db111256
...
|
- | OS-EXT-SRV-ATTR:host | dg-rp1-compute-06
+ | OS-EXT-SRV-ATTR:host | dg-rp1-compute-06
|
| g_pz1_net network | 192.168.200.12
|
| status | ACTIVE
|
- | vlb-bgp-net network | 10.214.1.33 |
- | vlb-mgmt-net network | 10.208.0.36 |
+ | vlb-bgp-net network | 10.214.1.33
+ |
+ | vlb-mgmt-net network | 10.208.0.36
+ |
+--------------------------------------+--------------------------------
** Description changed:
when instance with multiple networks is created, instance is in active
status even thoung it does not have proper ports matching with multiple
networks while rescheduling for some reason.
root@dg-rp1-controller-01:> nova boot --nic <net-id=[vlb-bgp-net], net-id=[g_pz1_net], net-id=[vlb-mgmt-net]> ....
root@dg-rp1-controller-01:> nova show dc8762c2-e11b-4a38-bb6a-a4db908e9867
....
|
| OS-EXT-SRV-ATTR:host | dg-rp1-compute-06
|
| g_pz1_net network | 192.168.200.22
|
| status | ACTIVE
|
| vlb-bgp-net network | 10.214.1.19, 10.214.1.25 |
+--------------------------------------+-------------------------------
- It happens when rescheduling sometimes. I think it shoud be done with
+ It happens when rescheduling sometimes. I think it shoud be done in
error status but active status.
Expected result:
root@dg-rp1-controller-01:~:> nova show 2bf34bc7-bf78-46db-9199-4072db111256
...
|
| OS-EXT-SRV-ATTR:host | dg-rp1-compute-06
|
| g_pz1_net network | 192.168.200.12
|
| status | ACTIVE
|
- | vlb-bgp-net network | 10.214.1.33
+ | vlb-bgp-net network | 10.214.1.33
|
| vlb-mgmt-net network | 10.208.0.36
|
+--------------------------------------+--------------------------------
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1824444
Title:
Instance is in active status though instance created with multiple
network do not have multiple proper ports
Status in OpenStack Compute (nova):
New
Bug description:
when instance with multiple networks is created, instance is in active
status even thoung it does not have proper ports matching with
multiple networks while rescheduling for some reason.
root@dg-rp1-controller-01:> nova boot --nic <net-id=[vlb-bgp-net], net-id=[g_pz1_net], net-id=[vlb-mgmt-net]> ....
root@dg-rp1-controller-01:> nova show dc8762c2-e11b-4a38-bb6a-a4db908e9867
....
|
| OS-EXT-SRV-ATTR:host | dg-rp1-compute-06
|
| g_pz1_net network | 192.168.200.22
|
| status | ACTIVE
|
| vlb-bgp-net network | 10.214.1.19, 10.214.1.25 |
+--------------------------------------+-------------------------------
It happens when rescheduling sometimes. I think it shoud be done in
error status but active status.
Expected result:
root@dg-rp1-controller-01:~:> nova show 2bf34bc7-bf78-46db-9199-4072db111256
...
|
| OS-EXT-SRV-ATTR:host | dg-rp1-compute-06
|
| g_pz1_net network | 192.168.200.12
|
| status | ACTIVE
|
| vlb-bgp-net network | 10.214.1.33
|
| vlb-mgmt-net network | 10.208.0.36
|
+--------------------------------------+--------------------------------
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1824444/+subscriptions
Follow ups