From: "Willem Jan Withagen (EcoRacks)" <wjw@ecoracks.nl>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Problems whilst running ceph-disk/run-tox.sh
Date: Tue, 16 Feb 2016 15:41:01 +0100 [thread overview]
Message-ID: <56C334FD.1010601@ecoracks.nl> (raw)
Hi,
Apart from the trouble this testscript is giving on general....
I'd like to shre two observations:
In TestCephDisk.test_list_dmcrypt_data
========
for seq in xrange(TMP_MAX):
name = names.next()
file = _os.path.join(dir, prefix + name + suffix)
try:
> _os.mkdir(file, 0700)
E OSError: [Errno 13] Permission denied:
'/var/lib/ceph/tmp/mnt.j5qCU5'
=========
Which was due to the previous run (as root) , so directories were owned
by root.
And once I fixed that one, by chown-ing stuff:
=========
E assert [{'partitions...: '/dev/Xda'}] ==
[{'partitions'...: '/dev/Xda'}]
E At index 0 diff: {'partitions': [{'mount': None,
'type': 'data', 'is_partition': True, 'state': 'unprepared', 'fs_type':
None, 'uuid': '56244cf5-83ef-4984-888a-2d8b8e0e04b2', 'dmcrypt':
{'holders': ['dm-0'], 'type': 'plain'}, 'ptype':
'4fbd7e29-9d25-41b8-afd0-5ec00ceff05d', 'path': '/dev/Xda1'}], 'path':
'/dev/Xda'} != {'partitions': [{'type': 'data', 'state': 'active',
'dmcrypt': {'holders': ['dm-0'], 'type': 'plain'}, 'mount': '/', 'uuid':
'56244cf5-83ef-4984-888a-2d8b8e0e04b2', 'is_partition': True, 'fs_type':
'xfs', 'ceph_fsid': None, 'whoami': None, 'ptype':
'4fbd7e29-9d25-41b8-afd0-5ec00ceff05d', 'path': '/dev/Xda1'}], 'path':
'/dev/Xda'}
E Full diff:
E - [{'partitions': [{'dmcrypt': {'holders': ['dm-0'],
'type': 'plain'},
E + [{'partitions': [{'ceph_fsid': None,
E + 'dmcrypt': {'holders': ['dm-0'],
'type': 'plain'},
E - 'fs_type': None,
E ? ^^^^
E + 'fs_type': 'xfs',
E ? ^^^^^
E 'is_partition': True,
E - 'mount': None,
E ? ^^^^
E + 'mount': '/',
E ? ^^^
E 'path': '/dev/Xda1',
E 'ptype': '4fbd7e29-9d25-41b8-afd0-5ec00ceff05d',
E - 'state': 'unprepared',
E ? ^^^^ -----
E + 'state': 'active',
E ? ^^^^^
E 'type': 'data',
E - 'uuid':
'56244cf5-83ef-4984-888a-2d8b8e0e04b2'}],
E
? --
E + 'uuid':
'56244cf5-83ef-4984-888a-2d8b8e0e04b2',
E + 'whoami': None}],
E 'path': '/dev/Xda'}]
tests/test_main.py:347: AssertionError
----------------------------- Captured stderr call
-----------------------------
DEBUG:ceph_disk.main:main_list: /dev/Xda1 ptype =
4fbd7e29-9d25-41b8-afd0-5ec00ceff05d uuid =
56244cf5-83ef-4984-888a-2d8b8e0e04b2
INFO:ceph_disk.main:Running command: /usr/sbin/blkid -s TYPE /dev/dm-0
DEBUG:ceph_disk.main:Mounting /dev/dm-0 on /var/lib/ceph/tmp/mnt.jzy74c
with options
INFO:ceph_disk.main:Running command: /usr/bin/mount -t xfs -o --
/dev/dm-0 /var/lib/ceph/tmp/mnt.jzy74c
mount: only root can use "--options" option
DEBUG:ceph_disk.main:main_list: {'Xda': ['Xda1']}, uuid_map =
{'56244cf5-83ef-4984-888a-2d8b8e0e04b2': '/dev/Xda1'}, space_map = {}
INFO:ceph_disk.main:list_dev(dev = /dev/Xda1, ptype =
4fbd7e29-9d25-41b8-afd0-5ec00ceff05d)
INFO:ceph_disk.main:Running command: /usr/sbin/blkid -s TYPE /dev/dm-0
=========
Thusfar I've grown used to the fact that script can be run as non-root.
Not sure if that was just coincidence, or by design.
And if by design, it would be nice to separate root and non-root scripts...
--WjW
next reply other threads:[~2016-02-16 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 14:41 Willem Jan Withagen (EcoRacks) [this message]
2016-02-16 15:25 ` Problems whilst running ceph-disk/run-tox.sh Loic Dachary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56C334FD.1010601@ecoracks.nl \
--to=wjw@ecoracks.nl \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox