Ask Your Question

14saki's profile - activity

2015-03-30 13:32:34 -0500 received badge  Popular Question (source)
2015-03-30 13:32:34 -0500 received badge  Famous Question (source)
2015-03-30 13:32:34 -0500 received badge  Notable Question (source)
2014-12-23 03:39:05 -0500 received badge  Student (source)
2014-12-22 06:23:55 -0500 asked a question How to setting retry and retry_interval of cinder.

I was not found it in cinder.conf. When Create Volume fails due to the capacity shortage, retrying is executed. Is it 3 at intervals of one second or it seems to be executed. Could you teach me the setting method?

2014-12-04 09:53:48 -0500 received badge  Famous Question (source)
2014-10-28 13:35:52 -0500 received badge  Notable Question (source)
2014-09-17 16:08:26 -0500 received badge  Popular Question (source)
2014-09-11 21:52:22 -0500 received badge  Notable Question (source)
2014-09-11 21:52:22 -0500 received badge  Famous Question (source)
2014-09-11 21:52:22 -0500 received badge  Popular Question (source)
2014-08-05 03:47:51 -0500 received badge  Famous Question (source)
2014-08-05 03:45:55 -0500 commented answer Please teach the method of fixing 'detached HEAD' state

Thank you for your reply. The matter in the state of Detached HEAD was solved. Thank you.

2014-08-01 12:07:10 -0500 received badge  Notable Question (source)
2014-08-01 12:07:10 -0500 received badge  Popular Question (source)
2014-08-01 03:32:26 -0500 asked a question Please teach the method of fixing 'detached HEAD' state

I want to abandon everything. And, I want to start again.

I deleted some commit registered in review. Having done the operation that did not have to be done noticed later. Committing that had been executed afterwards seems to have entered 'Detached HEAD' state. It is output to the log of pylint with "You are in 'detached HEAD' state.".

The local branch is not in the state of Detached-HEAD. I want to cancel the state of Detached-HEAD of the remote branch.

It is a state of detached HEAD when downloading it from review.openstack.org . $ git fetch https://user@review.openstack.org/ope... refs/changes/81/111881/1 && git checkout FETCH_HEAD

How should I do to return it normally?


2014-08-01 07:44:31.931 | + git fetch http://zm02.openstack.org/p/openstack/cinder refs/zuul/master/Ze495082d67c14b6eb71b8adf7828db16
2014-08-01 07:44:33.890 | From http://zm02.openstack.org/p/openstack/cinder
2014-08-01 07:44:33.927 |  * branch            refs/zuul/master/Ze495082d67c14b6eb71b8adf7828db16 -> FETCH_HEAD
2014-08-01 07:44:33.927 | + git checkout FETCH_HEAD
2014-08-01 07:44:33.928 | Note: checking out 'FETCH_HEAD'.
2014-08-01 07:44:33.928 | 
2014-08-01 07:44:33.928 | You are in 'detached HEAD' state. You can look around, make experimental
2014-08-01 07:44:33.928 | changes and commit them, and you can discard any commits you make in this
2014-08-01 07:44:33.928 | state without impacting any branches by performing another checkout.
2014-08-01 07:44:33.928 | 
2014-08-01 07:44:33.928 | If you want to create a new branch to retain commits you create, you may
2014-08-01 07:44:33.928 | do so (now or later) by using -b with the checkout command again. Example:
2014-08-01 07:44:33.928 | 
2014-08-01 07:44:33.929 |   git checkout -b new_branch_name
2014-08-01 07:44:33.929 | 
2014-08-01 07:44:33.929 | HEAD is now at 04851ba... Add Fujitsu ETERNUS DX support
2014-07-30 03:14:59 -0500 received badge  Enthusiast
2014-07-29 05:04:38 -0500 asked a question The device file of the detached volume is not deleted on compute node.

Environment - RDO HAVANA - iSCSI connection - DM-Multipath enable

[1].Two Volume is attached to the VM instance. /dev/sdb and /dev/sdc are found on Compute node.

# lsscsi
[0:2:0:0]    disk    LSI      MegaRAID SAS RMB 1.12  /dev/sda
[3:0:0:0]    cd/dvd  TEAC     DV-28S-V         J.0B  /dev/sr0
[15:0:0:0]   disk    FUJITSU  ETERNUS_DX400    0000  /dev/sdb
[15:0:0:1]   disk    FUJITSU  ETERNUS_DX400    0000  /dev/sdc

# multipath -ll
mpathc (3600000e00d100000001002af00770000) dm-4 FUJITSU,ETERNUS_DX400
size=2.0G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=10 status=active
  `- 15:0:0:1 sdc 8:32 active ready running
mpathb (3600000e00d100000001002af00760000) dm-3 FUJITSU,ETERNUS_DX400
size=1.0G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=10 status=active
  `- 15:0:0:0 sdb 8:16 active ready running
#

[2].detach /dev/sdc

[3]./dev/sdc is not deleted on Compute node /dev/sdc status is failed faulty. Why is not the device file(/dev/sdc) deleted?

# lsscsi
[0:2:0:0]    disk    LSI      MegaRAID SAS RMB 1.12  /dev/sda
[3:0:0:0]    cd/dvd  TEAC     DV-28S-V         J.0B  /dev/sr0
[15:0:0:0]   disk    FUJITSU  ETERNUS_DX400    0000  /dev/sdb
[15:0:0:1]   disk    FUJITSU  ETERNUS_DX400    0000  /dev/sdc

# multipath -ll
Jul 29 18:23:11 | sdc: alua not supported
mpathc (3600000e00d100000001002af00770000) dm-4 FUJITSU,ETERNUS_DX400
size=2.0G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=0 status=active
  `- 15:0:0:1 sdc 8:32 failed faulty running
mpathb (3600000e00d100000001002af00760000) dm-3 FUJITSU,ETERNUS_DX400
size=1.0G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=10 status=active
  `- 15:0:0:0 sdb 8:16 active ready  running
#
2014-07-29 01:47:21 -0500 asked a question How does Cinder select node when Copy Image to Volume?

Might Volume be attached to controller node?

Should I install Open-iscsi also in the controller node?

2014-07-28 21:11:18 -0500 commented question In the iscsi multipath configuration, Attach Volume does not work.

When the environment was restructured, the problem was solved.

2014-07-28 02:48:12 -0500 asked a question In the iscsi multipath configuration, Attach Volume does not work.

Attaching volume to the VM instance succeeds at the iSCSI single path.

Attaching volume to compute node succeed.

$ sudo iscsiadm -m session tcp: [1] 10.21.134.14:3260,10 iqn.2000-09.com.fujitsu:storage-system.eternus-dxl:000444EC00 tcp: [2] 192.168.0.86:3260,9 iqn.2000-09.com.fujitsu:storage-system.eternus-dxl:000444EC00 $ sudo multipath -ll mpath2 (3600000e00d110000001104ec00220000) dm-2 FUJITSU,ETERNUS_DXL size=3.0G features='0' hwhandler='0' wp=rw -+- policy='round-robin 0' prio=130 status=active |- 31:0:0:0 sdb 8:16 active ready running - 30:0:0:0 sdc 8:32 active ready running 3500000e115cdd800 dm-0 FUJITSU,MBE2147RC size=137G features='0' hwhandler='0' wp=rw -+- policy='round-robin 0' prio=1 status=active - 2:0:0:0 sda 8:0 active ready running $

However, it fails in attaching to the VM instance.

Please help.


nova-compute log

2014-07-28 16:10:54.807 DEBUG nova.openstack.common.lockutils [req-3750136b-4970-46d6-8360-83caeb79eb4e admin demo] Got semaphore "b21e95e9-13e3-488c-accf-fd0df5b2ec5a" from (pid=17804) lock /opt/stack/nova/nova/openstack/common/lockutils.py:168 2014-07-28 16:10:54.807 DEBUG nova.openstack.common.lockutils [req-3750136b-4970-46d6-8360-83caeb79eb4e admin demo] Got semaphore / lock "do_reserve" from (pid=17804) inner /opt/stack/nova/nova/openstack/common/lockutils.py:248 2014-07-28 16:10:54.820 DEBUG nova.compute.utils [req-3750136b-4970-46d6-8360-83caeb79eb4e admin demo] Using /dev/vd instead of None from (pid=17804) get_next_device_name /opt/stack/nova/nova/compute/utils.py:163 2014-07-28 16:10:54.851 DEBUG nova.openstack.common.lockutils [req-3750136b-4970-46d6-8360-83caeb79eb4e admin demo] Semaphore / lock released "do_reserve" from (pid=17804) inner /opt/stack/nova/nova/openstack/common/lockutils.py:252 2014-07-28 16:10:55.062 AUDIT nova.compute.manager [req-3750136b-4970-46d6-8360-83caeb79eb4e admin demo] [instance: b21e95e9-13e3-488c-accf-fd0df5b2ec5a] Attaching volume 391fb914-8a55-4384-a747-588641db3b15 to /dev/vdc 2014-07-28 16:10:55.063 DEBUG nova.volume.cinder [req-3750136b-4970-46d6-8360-83caeb79eb4e admin demo] Cinderclient connection created using URL: http://10.21.134.69:8776/v1/f36c99844... from (pid=17804) cinderclient /opt/stack/nova/nova/volume/cinder.py:97 2014-07-28 16:10:55.244 DEBUG nova.openstack.common.processutils [req-3750136b-4970-46d6-8360-83caeb79eb4e admin demo] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf cat /etc/iscsi/initiatorname.iscsi from (pid=17804) execute /opt/stack/nova/nova/openstack/common/processutils.py:155 2014-07-28 16:10:55.306 DEBUG nova.openstack.common.processutils [req-3750136b-4970-46d6-8360-83caeb79eb4e admin demo] Result was 0 from (pid=17804) execute /opt/stack/nova/nova/openstack/common/processutils.py:188 2014-07-28 16:10:55.307 DEBUG nova.openstack.common.processutils [req-3750136b-4970-46d6-8360-83caeb79eb4e admin demo] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf systool -c fc_host -v from (pid=17804) execute /opt/stack/nova/nova/openstack/common/processutils.py:155 2014-07-28 16:10:55.369 DEBUG nova.openstack.common.processutils [req-3750136b-4970-46d6-8360-83caeb79eb4e admin demo] Result was 0 from (pid=17804) execute /opt/stack/nova/nova/openstack/common/processutils.py:188 2014-07-28 16:10:55.370 DEBUG nova.openstack.common.processutils [req-3750136b-4970-46d6-8360-83caeb79eb4e admin demo] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf systool -c fc_host -v from (pid=17804) execute /opt/stack/nova/nova/openstack/common/processutils.py:155 2014-07-28 16:10:55.436 DEBUG nova.openstack.common.processutils ...

(more)
2014-07-25 01:33:53 -0500 received badge  Necromancer (source)
2014-07-25 01:33:53 -0500 received badge  Teacher (source)
2014-07-25 00:12:44 -0500 edited answer Logs full of "Arguments dropped when creating context ...": why?

I think that the following information is helpful for you. https://bugs.launchpad.net/cinder/+bug/1329156

2014-07-25 00:12:44 -0500 received badge  Editor (source)
2013-11-07 01:06:31 -0500 received badge  Supporter (source)