| 2017-03-06 02:54:13 |
Rikimaru Honjo |
bug |
|
|
added bug |
| 2017-03-06 03:39:07 |
Rikimaru Honjo |
description |
os-brick's iscsi initiator unexpectedly reverts node.startup from "auto" to "manual". in some specific cases.
[Premises]
* os-brick's iscsi initiator changes node.startup from "manual" to "auto" when it makes iscsi connections.
* If "iscsiadm -m discovery -t sendtargets -p ..." command is executed, node.startup is reverted from "auto" to "manual".
* In current os-brick's implementation, it won't login iscsi session and change node.startup if sessions are already existed.
(That logic is implemented in os_brick.initiator.connectors.iscsi.ISCSIConnector._connect_to_iscsi_portal() )
[Reproduce steps]
1. User attaches a volume to a instance with iscsi.
2. As a result, iscsi sessions are made.
And, node.startup is changed from "manual" to "auto".
3. The host of the instance is rebooted by with some reason.
4. After operating system is launched, iscsi sessions are automatically recovered.
Because node.startup is "auto".
5. The instance has stopped because the host was rebooted.
User calls "Start Server" API.
6. Nova try to re-make iscsi sessions.
7. In starting server process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
As a result, node.startup is reverted from "auto" to "manual".
8. But os-brick doesn't change node.startup to "auto" after that because iscsi sessions are already existed.
9. node.startup is still "manual" when server start is completed.
[My opinion]
In my opinion, os-brick should change node.startup even if iscsi sessions are already existed.
[Question]
I have also another opinion( or question).
Is changing node.startup really necessary?
If it is unnecessary, we should remove the process of changing node.startup.
IMO, that simplifies implementations over the above idea. |
os-brick's iscsi initiator unexpectedly reverts node.startup from "auto" to "manual". in some specific cases.
[Premises]
* os-brick's iscsi initiator changes node.startup from "manual" to "auto" when it makes iscsi connections.
* If "iscsiadm -m discovery -t sendtargets -p ..." command is executed, node.startup is reverted from "auto" to "manual".
* In current os-brick's implementation, it won't login iscsi session and change node.startup if sessions are already existed.
(That logic is implemented in os_brick.initiator.connectors.iscsi.ISCSIConnector._connect_to_iscsi_portal() )
[Reproduce steps - 1]
1. User attaches a volume to a instance with iscsi.
2. iscsi sessions are made.
And, node.startup is changed from "manual" to "auto".
3. User attaches other volume to a instance with iscsi.
4. In attaching volume process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
5. As a result, node.startup of 1st attaching is reverted from "manual" to "auto".
[Reproduce steps - 2]
1. User attaches a volume to a instance with iscsi.
2. As a result, iscsi sessions are made.
And, node.startup is changed from "manual" to "auto".
3. The host of the instance is rebooted by with some reason.
4. After operating system is launched, iscsi sessions are automatically recovered.
Because node.startup is "auto".
5. The instance has stopped because the host was rebooted.
User calls "Start Server" API.
6. Nova try to re-make iscsi sessions.
7. In starting server process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
As a result, node.startup is reverted from "auto" to "manual".
8. But os-brick doesn't change node.startup to "auto" after that because iscsi sessions are already existed.
9. node.startup is still "manual" when server start is completed.
[My opinion]
Is changing node.startup from "manual" to "auto" really necessary?
If it is unnecessary, we should remove the process of changing node.startup.
IMO, that simplifies implementations. |
|
| 2017-03-06 03:40:27 |
Rikimaru Honjo |
description |
os-brick's iscsi initiator unexpectedly reverts node.startup from "auto" to "manual". in some specific cases.
[Premises]
* os-brick's iscsi initiator changes node.startup from "manual" to "auto" when it makes iscsi connections.
* If "iscsiadm -m discovery -t sendtargets -p ..." command is executed, node.startup is reverted from "auto" to "manual".
* In current os-brick's implementation, it won't login iscsi session and change node.startup if sessions are already existed.
(That logic is implemented in os_brick.initiator.connectors.iscsi.ISCSIConnector._connect_to_iscsi_portal() )
[Reproduce steps - 1]
1. User attaches a volume to a instance with iscsi.
2. iscsi sessions are made.
And, node.startup is changed from "manual" to "auto".
3. User attaches other volume to a instance with iscsi.
4. In attaching volume process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
5. As a result, node.startup of 1st attaching is reverted from "manual" to "auto".
[Reproduce steps - 2]
1. User attaches a volume to a instance with iscsi.
2. As a result, iscsi sessions are made.
And, node.startup is changed from "manual" to "auto".
3. The host of the instance is rebooted by with some reason.
4. After operating system is launched, iscsi sessions are automatically recovered.
Because node.startup is "auto".
5. The instance has stopped because the host was rebooted.
User calls "Start Server" API.
6. Nova try to re-make iscsi sessions.
7. In starting server process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
As a result, node.startup is reverted from "auto" to "manual".
8. But os-brick doesn't change node.startup to "auto" after that because iscsi sessions are already existed.
9. node.startup is still "manual" when server start is completed.
[My opinion]
Is changing node.startup from "manual" to "auto" really necessary?
If it is unnecessary, we should remove the process of changing node.startup.
IMO, that simplifies implementations. |
os-brick's iscsi initiator unexpectedly reverts node.startup from "auto" to "manual". in some specific cases.
[Premises]
* os-brick's iscsi initiator changes node.startup from "manual" to "auto" when it makes iscsi connections.
* If "iscsiadm -m discovery -t sendtargets -p ..." command is executed, node.startup is reverted from "auto" to "manual".
* In current os-brick's implementation, it won't login iscsi session and change node.startup if sessions are already existed.
(That logic is implemented in os_brick.initiator.connectors.iscsi.ISCSIConnector._connect_to_iscsi_portal() )
[Reproduce steps - 1]
1. User attaches a volume to a instance with iscsi.
2. iscsi sessions are made.
And, node.startup is changed from "manual" to "auto".
3. User attaches other volume to a instance with iscsi.
4. In attaching volume process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
5. As a result, node.startup of 1st attaching is reverted from "auto" to "manual".
[Reproduce steps - 2]
1. User attaches a volume to a instance with iscsi.
2. As a result, iscsi sessions are made.
And, node.startup is changed from "manual" to "auto".
3. The host of the instance is rebooted by with some reason.
4. After operating system is launched, iscsi sessions are automatically recovered.
Because node.startup is "auto".
5. The instance has stopped because the host was rebooted.
User calls "Start Server" API.
6. Nova try to re-make iscsi sessions.
7. In starting server process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
As a result, node.startup is reverted from "auto" to "manual".
8. But os-brick doesn't change node.startup to "auto" after that because iscsi sessions are already existed.
9. node.startup is still "manual" when server start is completed.
[My opinion]
Is changing node.startup from "manual" to "auto" really necessary?
If it is unnecessary, we should remove the process of changing node.startup.
IMO, that simplifies implementations. |
|
| 2017-03-06 04:04:32 |
Rikimaru Honjo |
summary |
os-brick's iscsi initiator unexpectedly reverts node.startup from "auto" to "manual". |
os-brick's iscsi initiator unexpectedly reverts node.startup from "automatic" to "manual". |
|
| 2017-03-06 04:05:32 |
Rikimaru Honjo |
description |
os-brick's iscsi initiator unexpectedly reverts node.startup from "auto" to "manual". in some specific cases.
[Premises]
* os-brick's iscsi initiator changes node.startup from "manual" to "auto" when it makes iscsi connections.
* If "iscsiadm -m discovery -t sendtargets -p ..." command is executed, node.startup is reverted from "auto" to "manual".
* In current os-brick's implementation, it won't login iscsi session and change node.startup if sessions are already existed.
(That logic is implemented in os_brick.initiator.connectors.iscsi.ISCSIConnector._connect_to_iscsi_portal() )
[Reproduce steps - 1]
1. User attaches a volume to a instance with iscsi.
2. iscsi sessions are made.
And, node.startup is changed from "manual" to "auto".
3. User attaches other volume to a instance with iscsi.
4. In attaching volume process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
5. As a result, node.startup of 1st attaching is reverted from "auto" to "manual".
[Reproduce steps - 2]
1. User attaches a volume to a instance with iscsi.
2. As a result, iscsi sessions are made.
And, node.startup is changed from "manual" to "auto".
3. The host of the instance is rebooted by with some reason.
4. After operating system is launched, iscsi sessions are automatically recovered.
Because node.startup is "auto".
5. The instance has stopped because the host was rebooted.
User calls "Start Server" API.
6. Nova try to re-make iscsi sessions.
7. In starting server process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
As a result, node.startup is reverted from "auto" to "manual".
8. But os-brick doesn't change node.startup to "auto" after that because iscsi sessions are already existed.
9. node.startup is still "manual" when server start is completed.
[My opinion]
Is changing node.startup from "manual" to "auto" really necessary?
If it is unnecessary, we should remove the process of changing node.startup.
IMO, that simplifies implementations. |
os-brick's iscsi initiator unexpectedly reverts node.startup from "automatic" to "manual". in some specific cases.
[Premises]
* os-brick's iscsi initiator changes node.startup from "manual" to "automatic" when it makes iscsi connections.
* If "iscsiadm -m discovery -t sendtargets -p ..." command is executed, node.startup is reverted from "automatic" to "manual".
* In current os-brick's implementation, it won't login iscsi session and change node.startup if sessions are already existed.
(That logic is implemented in os_brick.initiator.connectors.iscsi.ISCSIConnector._connect_to_iscsi_portal() )
[Reproduce steps - 1]
1. User attaches a volume to a instance with iscsi.
2. iscsi sessions are made.
And, node.startup is changed from "manual" to "automatic".
3. User attaches other volume to a instance with iscsi.
4. In attaching volume process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
5. As a result, node.startup of 1st attaching is reverted from "automatic" to "manual".
[Reproduce steps - 2]
1. User attaches a volume to a instance with iscsi.
2. As a result, iscsi sessions are made.
And, node.startup is changed from "manual" to "automatic".
3. The host of the instance is rebooted by with some reason.
4. After operating system is launched, iscsi sessions are automatically recovered.
Because node.startup is "automatic".
5. The instance has stopped because the host was rebooted.
User calls "Start Server" API.
6. Nova try to re-make iscsi sessions.
7. In starting server process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
As a result, node.startup is reverted from "automatic" to "manual".
8. But os-brick doesn't change node.startup to "automatic" after that because iscsi sessions are already existed.
9. node.startup is still "manual" when server start is completed.
[My opinion]
Is changing node.startup from "manual" to "automatic" really necessary?
If it is unnecessary, we should remove the process of changing node.startup.
IMO, that simplifies implementations. |
|
| 2017-03-16 08:53:09 |
Rikimaru Honjo |
description |
os-brick's iscsi initiator unexpectedly reverts node.startup from "automatic" to "manual". in some specific cases.
[Premises]
* os-brick's iscsi initiator changes node.startup from "manual" to "automatic" when it makes iscsi connections.
* If "iscsiadm -m discovery -t sendtargets -p ..." command is executed, node.startup is reverted from "automatic" to "manual".
* In current os-brick's implementation, it won't login iscsi session and change node.startup if sessions are already existed.
(That logic is implemented in os_brick.initiator.connectors.iscsi.ISCSIConnector._connect_to_iscsi_portal() )
[Reproduce steps - 1]
1. User attaches a volume to a instance with iscsi.
2. iscsi sessions are made.
And, node.startup is changed from "manual" to "automatic".
3. User attaches other volume to a instance with iscsi.
4. In attaching volume process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
5. As a result, node.startup of 1st attaching is reverted from "automatic" to "manual".
[Reproduce steps - 2]
1. User attaches a volume to a instance with iscsi.
2. As a result, iscsi sessions are made.
And, node.startup is changed from "manual" to "automatic".
3. The host of the instance is rebooted by with some reason.
4. After operating system is launched, iscsi sessions are automatically recovered.
Because node.startup is "automatic".
5. The instance has stopped because the host was rebooted.
User calls "Start Server" API.
6. Nova try to re-make iscsi sessions.
7. In starting server process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
As a result, node.startup is reverted from "automatic" to "manual".
8. But os-brick doesn't change node.startup to "automatic" after that because iscsi sessions are already existed.
9. node.startup is still "manual" when server start is completed.
[My opinion]
Is changing node.startup from "manual" to "automatic" really necessary?
If it is unnecessary, we should remove the process of changing node.startup.
IMO, that simplifies implementations. |
os-brick's iscsi initiator unexpectedly reverts node.startup from "automatic" to "manual". in some specific cases.
[Premises]
* Use multipath.
* os-brick's iscsi initiator changes node.startup from "manual" to "automatic" when it makes iscsi connections.
* If "iscsiadm -m discovery -t sendtargets -p ..." command is executed, node.startup is reverted from "automatic" to "manual".
* In current os-brick's implementation, it won't login iscsi session and change node.startup if sessions are already existed.
(That logic is implemented in os_brick.initiator.connectors.iscsi.ISCSIConnector._connect_to_iscsi_portal() )
[Reproduce steps - 1]
1. User attaches a volume to a instance with iscsi.
2. iscsi sessions are made.
And, node.startup is changed from "manual" to "automatic".
3. User attaches other volume to a instance with iscsi.
4. In attaching volume process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
5. As a result, node.startup of 1st attaching is reverted from "automatic" to "manual".
[Reproduce steps - 2]
1. User attaches a volume to a instance with iscsi.
2. As a result, iscsi sessions are made.
And, node.startup is changed from "manual" to "automatic".
3. The host of the instance is rebooted by with some reason.
4. After operating system is launched, iscsi sessions are automatically recovered.
Because node.startup is "automatic".
5. The instance has stopped because the host was rebooted.
User calls "Start Server" API.
6. Nova try to re-make iscsi sessions.
7. In starting server process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
As a result, node.startup is reverted from "automatic" to "manual".
8. But os-brick doesn't change node.startup to "automatic" after that because iscsi sessions are already existed.
9. node.startup is still "manual" when server start is completed.
[My opinion]
Is changing node.startup from "manual" to "automatic" really necessary?
If it is unnecessary, we should remove the process of changing node.startup.
IMO, that simplifies implementations. |
|
| 2017-03-16 08:55:39 |
Rikimaru Honjo |
description |
os-brick's iscsi initiator unexpectedly reverts node.startup from "automatic" to "manual". in some specific cases.
[Premises]
* Use multipath.
* os-brick's iscsi initiator changes node.startup from "manual" to "automatic" when it makes iscsi connections.
* If "iscsiadm -m discovery -t sendtargets -p ..." command is executed, node.startup is reverted from "automatic" to "manual".
* In current os-brick's implementation, it won't login iscsi session and change node.startup if sessions are already existed.
(That logic is implemented in os_brick.initiator.connectors.iscsi.ISCSIConnector._connect_to_iscsi_portal() )
[Reproduce steps - 1]
1. User attaches a volume to a instance with iscsi.
2. iscsi sessions are made.
And, node.startup is changed from "manual" to "automatic".
3. User attaches other volume to a instance with iscsi.
4. In attaching volume process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
5. As a result, node.startup of 1st attaching is reverted from "automatic" to "manual".
[Reproduce steps - 2]
1. User attaches a volume to a instance with iscsi.
2. As a result, iscsi sessions are made.
And, node.startup is changed from "manual" to "automatic".
3. The host of the instance is rebooted by with some reason.
4. After operating system is launched, iscsi sessions are automatically recovered.
Because node.startup is "automatic".
5. The instance has stopped because the host was rebooted.
User calls "Start Server" API.
6. Nova try to re-make iscsi sessions.
7. In starting server process, os-brick executes "iscsiadm -m discovery -t sendtargets ...".
As a result, node.startup is reverted from "automatic" to "manual".
8. But os-brick doesn't change node.startup to "automatic" after that because iscsi sessions are already existed.
9. node.startup is still "manual" when server start is completed.
[My opinion]
Is changing node.startup from "manual" to "automatic" really necessary?
If it is unnecessary, we should remove the process of changing node.startup.
IMO, that simplifies implementations. |
os-brick's iscsi initiator unexpectedly reverts node.startup from "automatic" to "manual". in some specific cases.
[Premises]
* Use multipath.
* os-brick's iscsi initiator changes node.startup from "manual" to "automatic" when it makes iscsi connections.
* If "iscsiadm -m discovery -t sendtargets -p ..." command is executed, node.startup is reverted from "automatic" to "manual".
* In current os-brick's implementation, it won't login iscsi session and change node.startup if sessions are already existed.
(That logic is implemented in os_brick.initiator.connectors.iscsi.ISCSIConnector._connect_to_iscsi_portal() )
[Reproduce steps - 1]
1. User attaches a volume to a instance with iscsi.
2. iscsi sessions are made.
And, node.startup is changed from "manual" to "automatic".
3. User attaches other volume to a instance with iscsi.
4. In attaching volume process, os-brick will execute "iscsiadm -m discovery -t sendtargets ..." if multipath is used.
5. As a result, node.startup of 1st attaching is reverted from "automatic" to "manual".
[Reproduce steps - 2]
1. User attaches a volume to a instance with iscsi.
2. As a result, iscsi sessions are made.
And, node.startup is changed from "manual" to "automatic".
3. The host of the instance is rebooted by with some reason.
4. After operating system is launched, iscsi sessions are automatically recovered.
Because node.startup is "automatic".
5. The instance has stopped because the host was rebooted.
User calls "Start Server" API.
6. Nova try to re-make iscsi sessions.
7. In starting server process, os-brick will execute "iscsiadm -m discovery -t sendtargets ..." if multipath is used.
As a result, node.startup is reverted from "automatic" to "manual".
8. But os-brick doesn't change node.startup to "automatic" after that because iscsi sessions are already existed.
9. node.startup is still "manual" when server start is completed.
[My opinion]
Is changing node.startup from "manual" to "automatic" really necessary?
If it is unnecessary, we should remove the process of changing node.startup.
IMO, that simplifies implementations. |
|
| 2017-03-16 09:58:08 |
Rikimaru Honjo |
os-brick: assignee |
|
Rikimaru Honjo (honjo-rikimaru-c6) |
|
| 2017-03-20 17:48:54 |
Walt Boring |
os-brick: status |
New |
Confirmed |
|
| 2017-03-20 17:49:00 |
Walt Boring |
os-brick: importance |
Undecided |
Medium |
|
| 2017-05-19 01:44:50 |
OpenStack Infra |
os-brick: status |
Confirmed |
In Progress |
|
| 2017-05-19 01:59:13 |
Rikimaru Honjo |
description |
os-brick's iscsi initiator unexpectedly reverts node.startup from "automatic" to "manual". in some specific cases.
[Premises]
* Use multipath.
* os-brick's iscsi initiator changes node.startup from "manual" to "automatic" when it makes iscsi connections.
* If "iscsiadm -m discovery -t sendtargets -p ..." command is executed, node.startup is reverted from "automatic" to "manual".
* In current os-brick's implementation, it won't login iscsi session and change node.startup if sessions are already existed.
(That logic is implemented in os_brick.initiator.connectors.iscsi.ISCSIConnector._connect_to_iscsi_portal() )
[Reproduce steps - 1]
1. User attaches a volume to a instance with iscsi.
2. iscsi sessions are made.
And, node.startup is changed from "manual" to "automatic".
3. User attaches other volume to a instance with iscsi.
4. In attaching volume process, os-brick will execute "iscsiadm -m discovery -t sendtargets ..." if multipath is used.
5. As a result, node.startup of 1st attaching is reverted from "automatic" to "manual".
[Reproduce steps - 2]
1. User attaches a volume to a instance with iscsi.
2. As a result, iscsi sessions are made.
And, node.startup is changed from "manual" to "automatic".
3. The host of the instance is rebooted by with some reason.
4. After operating system is launched, iscsi sessions are automatically recovered.
Because node.startup is "automatic".
5. The instance has stopped because the host was rebooted.
User calls "Start Server" API.
6. Nova try to re-make iscsi sessions.
7. In starting server process, os-brick will execute "iscsiadm -m discovery -t sendtargets ..." if multipath is used.
As a result, node.startup is reverted from "automatic" to "manual".
8. But os-brick doesn't change node.startup to "automatic" after that because iscsi sessions are already existed.
9. node.startup is still "manual" when server start is completed.
[My opinion]
Is changing node.startup from "manual" to "automatic" really necessary?
If it is unnecessary, we should remove the process of changing node.startup.
IMO, that simplifies implementations. |
os-brick's iscsi initiator unexpectedly reverts node.startup from "automatic" to "manual" in some specific cases if we use multipath.
As a result, automatic nodes and manual nodes are mixed on that host.
[Premises]
* Use multipath.
* os-brick's iscsi initiator changes node.startup from "manual" to "automatic" when it makes iscsi connections.
* If "iscsiadm -m discovery -t sendtargets -p ..." command is executed, node.startup is reverted from "automatic" to "manual".
* In current os-brick's implementation, it won't login iscsi session and change node.startup if sessions are already existed.
(That logic is implemented in os_brick.initiator.connectors.iscsi.ISCSIConnector._connect_to_iscsi_portal() )
[Reproduce steps - 1]
1. User attaches a volume to a instance with iscsi.
2. iscsi sessions are made.
And, node.startup is changed from "manual" to "automatic".
3. User attaches other volume to a instance with iscsi.
4. In attaching volume process, os-brick will execute "iscsiadm -m discovery -t sendtargets ..." if multipath is used.
5. As a result, node.startup of 1st attaching is reverted from "automatic" to "manual". And automatic nodes and manual nodes are mixed on that host.
[Reproduce steps - 2]
1. User attaches a volume to a instance with iscsi.
2. As a result, iscsi sessions are made.
And, node.startup is changed from "manual" to "automatic".
3. The host of the instance is rebooted by with some reason.
4. After operating system is launched, iscsi sessions are automatically recovered.
Because node.startup is "automatic".
5. The instance has stopped because the host was rebooted.
User calls "Start Server" API.
6. Nova try to re-make iscsi sessions.
7. In starting server process, os-brick will execute "iscsiadm -m discovery -t sendtargets ..." if multipath is used.
As a result, node.startup is reverted from "automatic" to "manual".
8. But os-brick doesn't change node.startup to "automatic" after that because iscsi sessions are already existed.
9. node.startup is still "manual" when server start is completed.
[My opinion]
Changing node.startup from "manual" to "automatic" is unnecessary.
Current os-brick users[1] create/re-create iSCSI sessions when they need it.
If someone needs node.startup=automatic, he should set default value as "automatic" in iscsi.conf.
[1]e.g. nova,cinder... |
|
| 2018-01-03 19:50:51 |
OpenStack Infra |
os-brick: status |
In Progress |
Fix Released |
|
| 2018-01-03 19:50:53 |
OpenStack Infra |
bug watch added |
|
https://github.com/open-iscsi/open-iscsi/issues/58 |
|
