Hi! Fine! Maybe you know what a new user should do? Which does not yet have a local copy of the repository, and is now trying to install the latest version? ----- Original Message ----- > On 17.09.2019 06:54, Ashley Merrick wrote: >> Have just noticed their is packages available for 14.2.4.. >> >> I know with the whole 14.2.3 release and the notes not going out to a >> good day or so later.. but this is not long after the 14.2.3 release..? >> >> Was this release even meant to have come out? Makes it difficult for >> people installing a new node if they can't reply on the current "stable" >> packages that apt/yum will give them. > > > Never install packages until there is an announcement. > > IIRC developers have asked if anyone have experience with running repos > that could assist in improving the rollout of releases since this have > been a recurring issue. > > > If you need to do installs all the time, and can not postpone until the > repo settle. Consider rsyncing the repo after a release, and use that > for installs. > > kind regards > Ronny > > _______________________________________________ > ceph-users mailing list -- ceph-users(a)ceph.io > To unsubscribe send an email to ceph-users-leave(a)ceph.io

Hi! No. I looking information on https://ceph.io/ why I should not install version 14.2.4, although it is in the repository and how it differs from 14.2.3 ----- Original Message ----- > Depends on the OS you are using. > Version pinning is the search keyword you are looking for > > Hi! > > Fine! Maybe you know what a new user should do? Which does not yet have a local > copy of the repository, and is now trying to install the latest version? > > ----- Original Message ----- >> From: "Ronny Aasen" <ronny+ceph-users(a)aasen.cx> >> To: ceph-users(a)ceph.io >> Sent: Tuesday, 17 September, 2019 09:46:03 >> Subject: [ceph-users] Re: 14.2.4 Packages Avaliable > >> On 17.09.2019 06:54, Ashley Merrick wrote: >>> Have just noticed their is packages available for 14.2.4.. >>> >>> I know with the whole 14.2.3 release and the notes not going out to a >>> good day or so later.. but this is not long after the 14.2.3 release..? >>> >>> Was this release even meant to have come out? Makes it difficult for >>> people installing a new node if they can't reply on the current "stable" >>> packages that apt/yum will give them. >> >> >> Never install packages until there is an announcement. >> >> IIRC developers have asked if anyone have experience with running repos >> that could assist in improving the rollout of releases since this have >> been a recurring issue. >> >> >> If you need to do installs all the time, and can not postpone until the >> repo settle. Consider rsyncing the repo after a release, and use that >> for installs. >> >> kind regards >> Ronny >> >> _______________________________________________ >> ceph-users mailing list -- ceph-users(a)ceph.io >> To unsubscribe send an email to ceph-users-leave(a)ceph.io > _______________________________________________ > ceph-users mailing list -- ceph-users(a)ceph.io > To unsubscribe send an email to ceph-users-leave(a)ceph.io > _______________________________________________ > ceph-users mailing list -- ceph-users(a)ceph.io > To unsubscribe send an email to ceph-users-leave(a)ceph.io

Hello, That does not make sense. If a package is available on the repo and can be installed or update directly with apt or yum, it has to be the final release package, any other statement must be flagged as RC or beta. Why don't you add RC flags on this package if it's not ready to publish? I plan to install a new cluster with ceph-ansible, I don't have to take care of the release number as soon as it's the latest package available on the official stable repo. Even on a short period, an « almost ready but not completely full tested » packages can really have an impact on production servers, especially if not announce previously. Best regards, -- Yoann Moulin EPFL IC-IT

Hello, My reaction was not on this specific release but with this sentence : « Never install packages until there is an announcement. » And also with this one : « If you need to do installs all the time, and can not postpone until the repo settle. Consider rsyncing the repo after a release, and use that for installs. » This sound crazy to me. Best regards, -- Yoann Moulin EPFL IC-IT

Hi, Yesterday I completed the 14.2.4 release by jumping a few procedures that should've been followed, mainly communicating with the release manager and the team involved in sending out the release announcement. There was a sense of urgency since the 14.2.3 release introduced issues with the ceph-volume tool which breaks deployment tools that capture stderr/stdout (see https://tracker.ceph.com/issues/41660) The release process started on Friday (!) and finished late yesterday. I'm following up with the release manager to get the proper notes out, like I mentioned he was unaware of the ongoing release (my fault). Let me know if you have any questions (or complaints!) while we try to get this sorted out. -Alfredo On Tue, Sep 17, 2019 at 7:49 AM Janne Johansson <icepic.dz(a)gmail.com> wrote: