Re: failed erasure code pool creation after client upgrade

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Yuri,

In the logs I see

2014-10-24T20:08:46.258 INFO:teuthology.task.install:Package version is 0.67.11-26-g6a90775-1precise

which would explain why it fails. If the cluster is running dumpling and an upgrade to a firefly client tries to create an erasure coded pool, that will fail with -95 as expected.

Cheers

On 25/10/2014 10:30, Yuri Weinstein wrote:
> Via crontab treuthology-suite cl
> 
> On Saturday, October 25, 2014, Loic Dachary <loic@xxxxxxxxxxx <mailto:loic@xxxxxxxxxxx>> wrote:
> 
>     [cc'ing ceph-devel for archive]
> 
>     Hi,
> 
>     I see a lot of errors with
> 
>     #define EOPNOTSUPP      95      /* Operation not supported on transport endpoint */
> 
>     2014-10-24T20:26:54.335 INFO:tasks.workunit.client.0.plana63.stdout:[ RUN      ] LibRadosAioEC.SimpleWrite
>     2014-10-24T20:26:56.737 INFO:tasks.workunit.client.0.plana63.stdout:test/librados/aio.cc:1634: Failure
>     2014-10-24T20:26:56.737 INFO:tasks.workunit.client.0.plana63.stdout:Value of: test_data.init()
>     2014-10-24T20:26:56.737 INFO:tasks.workunit.client.0.plana63.stdout:  Actual: "create_one_ec_pool(test-rados-api-plana63-14645-33) failed: error rados_mon_command erasure-code-profile set name:testprofile failed with error -95"
>     2014-10-24T20:26:56.738 INFO:tasks.workunit.client.0.plana63.stdout:Expected: ""
>     2014-10-24T20:26:56.738 INFO:tasks.workunit.client.0.plana63.stdout:[  FAILED  ] LibRadosAioEC.SimpleWrite (2403 ms)
>     2014-10-24T20:26:56.738 INFO:tasks.workunit.client.0.plana63.stdout:[ RUN      ] LibRadosAioEC.SimpleWritePP
>     2014-10-24T20:26:59.141 INFO:tasks.workunit.client.0.plana63.stdout:test/librados/aio.cc:1669: Failure
>     2014-10-24T20:26:59.142 INFO:tasks.workunit.client.0.plana63.stdout:Value of: test_data.init()
>     2014-10-24T20:26:59.142 INFO:tasks.workunit.client.0.plana63.stdout:  Actual: "create_one_ec_pool(test-rados-api-plana63-14645-
> 
>     which indeed suggests that the client is trying to create an erasure coded pool in a cluster that does not support it. But since it looks like it's upgrading from firefly to a later version, I don't understand why that would be a problem.
> 
>     How did that get scheduled ?
> 
>     Cheers
> 
>     On 25/10/2014 08:37, Yuri Weinstein wrote:
>     > Not sure what's going on with it, thx.
>     >
>     > It's unusual in a way that upgrades a client first.
>     >
>     > http://qa-proxy.ceph.com/teuthology/teuthology-2014-10-24_17:05:01-upgrade:firefly:singleton-firefly-distro-basic-multi/569532/teuthology.log
> 
>     --
>     Loïc Dachary, Artisan Logiciel Libre
> 

-- 
Loïc Dachary, Artisan Logiciel Libre

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux