[ceph-users] Re: 16.2.7 pacific QE validation status, RC1 available for testing

[Josh Durgin]

On 12/6/21 12:49, Yuri Weinstein wrote:

We merged 3 PRs on top of the RC1 tip:

https://github.com/ceph/ceph/pull/44164
https://github.com/ceph/ceph/pull/44154
https://github.com/ceph/ceph/pull/44201

Assuming that Neha or other leads see any point to retest any suites,
this is ready for publishing.

Pending Josh's final approval.


Looks like we're good to go, thanks everyone!

Josh



David FYI

Thx
YuriW

On Fri, Dec 3, 2021 at 4:19 AM David Orman  wrote:


We've been testing RC1 since release on our 504 OSD/21 host, with split db/wal 
test cluster, and have experienced no issues on upgrade or operation so far.

On Mon, Nov 29, 2021 at 11:23 AM Yuri Weinstein  wrote:


Details of this release are summarized here:

https://tracker.ceph.com/issues/53324
Release Notes - https://github.com/ceph/ceph/pull/44131

Seeking approvals for:

rados - Neha
rgw - Casey
rbd - Ilya, Deepika
krbd  Ilya, Deepika
fs - Venky, Patrick
upgrade/nautilus-x - Neha, Josh
upgrade/pacific-p2p - Neha, Josh


We are also publishing a release candidate this time for users to try
for testing only.

The branch name is pacific-16.2.7_RC1
(https://shaman.ceph.com/builds/ceph/pacific-16.2.7_RC1/fdc003bc12f1b2443c4596eeacb32cf62e806970/)

***Don’t use this RC on production clusters!***

The idea of doing Release Candidates (RC) for point releases before
doing final point releases was discussed in the first-ever Ceph User +
Dev Monthly Meeting. Everybody thought that it was a good idea, to
help identify bugs that do not get caught in integration testing.

The goal is to give users time to test and give feedback on RC
releases while our upstream long-running cluster also runs the same RC
release during that time (period of one week). We will kick this
process off with 16.2.7 and the pacific-16.2.7_RC1 release is now
available for users to test.

Please respond to this email to provide any feedback on issues found
in this release.

Thx
YuriW

___
Dev mailing list -- d...@ceph.io
To unsubscribe send an email to dev-le...@ceph.io


___
Dev mailing list -- d...@ceph.io
To unsubscribe send an email to dev-le...@ceph.io



___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: 16.2.7 pacific QE validation status, RC1 available for testing

[David Orman]

We've been testing RC1 since release on our 504 OSD/21 host, with split
db/wal test cluster, and have experienced no issues on upgrade or operation
so far.

On Mon, Nov 29, 2021 at 11:23 AM Yuri Weinstein  wrote:

> Details of this release are summarized here:
>
> https://tracker.ceph.com/issues/53324
> Release Notes - https://github.com/ceph/ceph/pull/44131
>
> Seeking approvals for:
>
> rados - Neha
> rgw - Casey
> rbd - Ilya, Deepika
> krbd  Ilya, Deepika
> fs - Venky, Patrick
> upgrade/nautilus-x - Neha, Josh
> upgrade/pacific-p2p - Neha, Josh
>
> 
> We are also publishing a release candidate this time for users to try
> for testing only.
>
> The branch name is pacific-16.2.7_RC1
> (
> https://shaman.ceph.com/builds/ceph/pacific-16.2.7_RC1/fdc003bc12f1b2443c4596eeacb32cf62e806970/
> )
>
> ***Don’t use this RC on production clusters!***
>
> The idea of doing Release Candidates (RC) for point releases before
> doing final point releases was discussed in the first-ever Ceph User +
> Dev Monthly Meeting. Everybody thought that it was a good idea, to
> help identify bugs that do not get caught in integration testing.
>
> The goal is to give users time to test and give feedback on RC
> releases while our upstream long-running cluster also runs the same RC
> release during that time (period of one week). We will kick this
> process off with 16.2.7 and the pacific-16.2.7_RC1 release is now
> available for users to test.
>
> Please respond to this email to provide any feedback on issues found
> in this release.
>
> Thx
> YuriW
>
> ___
> Dev mailing list -- d...@ceph.io
> To unsubscribe send an email to dev-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: 16.2.7 pacific QE validation status, RC1 available for testing

[Ernesto Puerta]

Neha: sure, done!

Yuri: dashboard approved.

Kind Regards,
Ernesto


On Thu, Dec 2, 2021 at 9:38 PM Neha Ojha  wrote:

> On Mon, Nov 29, 2021 at 9:23 AM Yuri Weinstein 
> wrote:
> >
> > Details of this release are summarized here:
> >
> > https://tracker.ceph.com/issues/53324
> > Release Notes - https://github.com/ceph/ceph/pull/44131
> >
> > Seeking approvals for:
> >
> > rados - Neha
>
> Approved, known issues:
> - rados/perf failures, should fixed by
> https://github.com/ceph/ceph/pull/44154
> - https://tracker.ceph.com/issues/50274 - in testing
> - https://tracker.ceph.com/issues/53123 - Ernesto can I get a +1 from
> you on this?
>
>
> > rgw - Casey
> > rbd - Ilya, Deepika
> > krbd  Ilya, Deepika
> > fs - Venky, Patrick
> > upgrade/nautilus-x - Neha, Josh
>
> Approved
>
> > upgrade/pacific-p2p - Neha, Josh
>
> Approved, known issues:
> - https://tracker.ceph.com/issues/52590#note-3
> - https://tracker.ceph.com/issues/51652
>
> Thanks,
> Neha
>
>
> >
> > 
> > We are also publishing a release candidate this time for users to try
> > for testing only.
> >
> > The branch name is pacific-16.2.7_RC1
> > (
> https://shaman.ceph.com/builds/ceph/pacific-16.2.7_RC1/fdc003bc12f1b2443c4596eeacb32cf62e806970/
> )
> >
> > ***Don’t use this RC on production clusters!***
> >
> > The idea of doing Release Candidates (RC) for point releases before
> > doing final point releases was discussed in the first-ever Ceph User +
> > Dev Monthly Meeting. Everybody thought that it was a good idea, to
> > help identify bugs that do not get caught in integration testing.
> >
> > The goal is to give users time to test and give feedback on RC
> > releases while our upstream long-running cluster also runs the same RC
> > release during that time (period of one week). We will kick this
> > process off with 16.2.7 and the pacific-16.2.7_RC1 release is now
> > available for users to test.
> >
> > Please respond to this email to provide any feedback on issues found
> > in this release.
> >
> > Thx
> > YuriW
> >
> > ___
> > Dev mailing list -- d...@ceph.io
> > To unsubscribe send an email to dev-le...@ceph.io
>
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: 16.2.7 pacific QE validation status, RC1 available for testing

[Neha Ojha]

On Mon, Nov 29, 2021 at 9:23 AM Yuri Weinstein  wrote:
>
> Details of this release are summarized here:
>
> https://tracker.ceph.com/issues/53324
> Release Notes - https://github.com/ceph/ceph/pull/44131
>
> Seeking approvals for:
>
> rados - Neha

Approved, known issues:
- rados/perf failures, should fixed by https://github.com/ceph/ceph/pull/44154
- https://tracker.ceph.com/issues/50274 - in testing
- https://tracker.ceph.com/issues/53123 - Ernesto can I get a +1 from
you on this?


> rgw - Casey
> rbd - Ilya, Deepika
> krbd  Ilya, Deepika
> fs - Venky, Patrick
> upgrade/nautilus-x - Neha, Josh

Approved

> upgrade/pacific-p2p - Neha, Josh

Approved, known issues:
- https://tracker.ceph.com/issues/52590#note-3
- https://tracker.ceph.com/issues/51652

Thanks,
Neha


>
> 
> We are also publishing a release candidate this time for users to try
> for testing only.
>
> The branch name is pacific-16.2.7_RC1
> (https://shaman.ceph.com/builds/ceph/pacific-16.2.7_RC1/fdc003bc12f1b2443c4596eeacb32cf62e806970/)
>
> ***Don’t use this RC on production clusters!***
>
> The idea of doing Release Candidates (RC) for point releases before
> doing final point releases was discussed in the first-ever Ceph User +
> Dev Monthly Meeting. Everybody thought that it was a good idea, to
> help identify bugs that do not get caught in integration testing.
>
> The goal is to give users time to test and give feedback on RC
> releases while our upstream long-running cluster also runs the same RC
> release during that time (period of one week). We will kick this
> process off with 16.2.7 and the pacific-16.2.7_RC1 release is now
> available for users to test.
>
> Please respond to this email to provide any feedback on issues found
> in this release.
>
> Thx
> YuriW
>
> ___
> Dev mailing list -- d...@ceph.io
> To unsubscribe send an email to dev-le...@ceph.io

___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: 16.2.7 pacific QE validation status, RC1 available for testing

[Casey Bodley]

On Thu, Dec 2, 2021 at 1:15 PM Yuri Weinstein  wrote:
>
> Update:
>
> Neha is finalizing reviewing rados and upgrades (I restarted some tests FYI)
> Still need rgw approval - Casey, Matt?

rgw approved

>
> Thx
> YuriW
>
> On Thu, Dec 2, 2021 at 6:08 AM Sebastian Wagner  wrote:
> >
> >
> > Am 29.11.21 um 18:23 schrieb Yuri Weinstein:
> > > Details of this release are summarized here:
> > >
> > > https://tracker.ceph.com/issues/53324
> > > Release Notes - https://github.com/ceph/ceph/pull/44131
> > >
> > > Seeking approvals for:
> > >
> > > rados - Neha
> > rados/cephadm looks good. Except for https://tracker.ceph.com/issues/53365
> > > rgw - Casey
> > > rbd - Ilya, Deepika
> > > krbd  Ilya, Deepika
> > > fs - Venky, Patrick
> > > upgrade/nautilus-x - Neha, Josh
> > > upgrade/pacific-p2p - Neha, Josh
> > >
> > > 
> > > We are also publishing a release candidate this time for users to try
> > > for testing only.
> > >
> > > The branch name is pacific-16.2.7_RC1
> > > (https://shaman.ceph.com/builds/ceph/pacific-16.2.7_RC1/fdc003bc12f1b2443c4596eeacb32cf62e806970/)
> > >
> > > ***Don’t use this RC on production clusters!***
> > >
> > > The idea of doing Release Candidates (RC) for point releases before
> > > doing final point releases was discussed in the first-ever Ceph User +
> > > Dev Monthly Meeting. Everybody thought that it was a good idea, to
> > > help identify bugs that do not get caught in integration testing.
> > >
> > > The goal is to give users time to test and give feedback on RC
> > > releases while our upstream long-running cluster also runs the same RC
> > > release during that time (period of one week). We will kick this
> > > process off with 16.2.7 and the pacific-16.2.7_RC1 release is now
> > > available for users to test.
> > >
> > > Please respond to this email to provide any feedback on issues found
> > > in this release.
> > >
> > > Thx
> > > YuriW
> > >
> > > ___
> > > Dev mailing list -- d...@ceph.io
> > > To unsubscribe send an email to dev-le...@ceph.io
>
> ___
> Dev mailing list -- d...@ceph.io
> To unsubscribe send an email to dev-le...@ceph.io

___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: 16.2.7 pacific QE validation status, RC1 available for testing

[Sebastian Wagner]

Am 29.11.21 um 18:23 schrieb Yuri Weinstein:
> Details of this release are summarized here:
>
> https://tracker.ceph.com/issues/53324
> Release Notes - https://github.com/ceph/ceph/pull/44131
>
> Seeking approvals for:
>
> rados - Neha
rados/cephadm looks good. Except for https://tracker.ceph.com/issues/53365
> rgw - Casey
> rbd - Ilya, Deepika
> krbd  Ilya, Deepika
> fs - Venky, Patrick
> upgrade/nautilus-x - Neha, Josh
> upgrade/pacific-p2p - Neha, Josh
>
> 
> We are also publishing a release candidate this time for users to try
> for testing only.
>
> The branch name is pacific-16.2.7_RC1
> (https://shaman.ceph.com/builds/ceph/pacific-16.2.7_RC1/fdc003bc12f1b2443c4596eeacb32cf62e806970/)
>
> ***Don’t use this RC on production clusters!***
>
> The idea of doing Release Candidates (RC) for point releases before
> doing final point releases was discussed in the first-ever Ceph User +
> Dev Monthly Meeting. Everybody thought that it was a good idea, to
> help identify bugs that do not get caught in integration testing.
>
> The goal is to give users time to test and give feedback on RC
> releases while our upstream long-running cluster also runs the same RC
> release during that time (period of one week). We will kick this
> process off with 16.2.7 and the pacific-16.2.7_RC1 release is now
> available for users to test.
>
> Please respond to this email to provide any feedback on issues found
> in this release.
>
> Thx
> YuriW
>
> ___
> Dev mailing list -- d...@ceph.io
> To unsubscribe send an email to dev-le...@ceph.io
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: 16.2.7 pacific QE validation status, RC1 available for testing

[Neha Ojha]

Hi Luis,

On Wed, Dec 1, 2021 at 8:19 AM Luis Domingues  wrote:
>
> We upgraded a test cluster (3 controllers + 6 osds nodes with HDD and SSDs 
> for rocksdb) from last Nautilus to this 16.2.7 RC1.
>
> Upgrade went well without issues. We repaired the OSDs and no one crashed.

That's good to know! Thanks for testing 16.2.7 RC1.

>
> But we are still hitting this bug:
> https://tracker.ceph.com/issues/50657
>
> Do you think this can still be backported to 16.2.7 before it get released?

Sure, we now have a PR out for it https://github.com/ceph/ceph/pull/44164.

Thanks,
Neha

>
> Luis Domingues
> Proton AG
> ___
> Dev mailing list -- d...@ceph.io
> To unsubscribe send an email to dev-le...@ceph.io
>

___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: 16.2.7 pacific QE validation status, RC1 available for testing

[Venky Shankar]

On Mon, Nov 29, 2021 at 10:53 PM Yuri Weinstein  wrote:

> fs - Venky, Patrick

fs approved - failures are known and have trackers.



-- 
Cheers,
Venky

___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: 16.2.7 pacific QE validation status, RC1 available for testing

[Mykola Golub]

On Tue, Nov 30, 2021 at 01:57:14PM +0530, Deepika Upadhyay wrote:
> krbd, rbd lgtm!
> 
>- krbd:
> 
> 
> 
> 
> 
> 
> 
>- rbd
> 
> 
> 
> 
> 
> 
> @Mykola adding existing issues found on these runs, can you take another
> look and approve?

I don't have much experience with krbd tests but the failures indeed
look like known issues, not related to pacific update.

rbd - LGTM.

Thanks.

-- 
Mykola Golub
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io