From: Loic Dachary <loic@dachary.org>
To: Nathan Cutler <ncutler@suse.cz>,
Abhishek L <abhishek.lekshmanan@gmail.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: hammer/firefly backports upgrade suite
Date: Thu, 30 Jul 2015 10:03:31 +0200 [thread overview]
Message-ID: <55B9DA53.9050904@dachary.org> (raw)
In-Reply-To: <55B9D0D7.607@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
On 30/07/2015 09:23, Nathan Cutler wrote:
>> It turns out the mistake was to use upgrade/firefly-x and upgrade/hammer-x instead of upgrade/firelfy and upgrade/hammer. When -c hammer-backports or -c firefly-backports is given to teuthology-suite, it will upgrade to this version, from older versions of the same stable branch.
>>
>> I've updated:
>>
>> http://tracker.ceph.com/issues/11644#upgrade
>> http://tracker.ceph.com/issues/11990#upgrade
>>
>> whith the fix and they are running (using the OpenStack cluster though, there may be issues with the firefly upgrade suite but the hammer upgrade suite must run fine, it has run at http://ceph.aevoo.fr:8081/ enough times to suggest there are no OpenStack specific issues).
>
> Hi Loic:
>
> As you predicted, the firefly upgrade suite finished with quite a few failures. I looked at the first one and the log said:
>
> ERROR:teuthology.misc:. teuthology/test/integration/openrc.sh && openstack network show -f json unknown error ERROR: openstack No networks with a name or ID of 'unknown' found
>
> Nathan
These can be ignored. I'll fix that so it does not show in the future.
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2015-07-30 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 21:34 hammer/firefly backports upgrade suite Loic Dachary
2015-07-30 7:23 ` Nathan Cutler
2015-07-30 8:03 ` Loic Dachary [this message]
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=55B9DA53.9050904@dachary.org \
--to=loic@dachary.org \
--cc=abhishek.lekshmanan@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ncutler@suse.cz \
/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.