All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Yuri Weinstein <yuri.weinstein@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: failed erasure code pool creation after client upgrade
Date: Sat, 25 Oct 2014 10:29:07 -0700	[thread overview]
Message-ID: <544BDDE3.5060506@dachary.org> (raw)
In-Reply-To: <CAJBxG-tw0qdSBF_fA7LOuFc-vg8Rq1AQsrqU0ic5Wux1Ozpbew@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1953 bytes --]

[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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

       reply	other threads:[~2014-10-25 18:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJBxG-tw0qdSBF_fA7LOuFc-vg8Rq1AQsrqU0ic5Wux1Ozpbew@mail.gmail.com>
2014-10-25 17:29 ` Loic Dachary [this message]
     [not found]   ` <CAJBxG-uLYfpoJoTGCFCT5+2n3uE2ucjtKSnnQTnK2gwdvKhukA@mail.gmail.com>
2014-10-25 17:36     ` failed erasure code pool creation after client upgrade Loic Dachary
     [not found]   ` <CAFd2DpTEMSJAykdicJPXND4_W6mgUM-gR8jXc3qubS1GzLwqQA@mail.gmail.com>
     [not found]     ` <CAJBxG-tyt9D4yFisb3J-vJeTq0_T5BjkWk5Kfi-X3gsZ97i2uw@mail.gmail.com>
2014-10-26 15:47       ` 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=544BDDE3.5060506@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=yuri.weinstein@inktank.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.