No this is a production cluster that I have not had a chance to upgrade yet.
We had an is with the OS on a node so I am just trying to reinstall ceph and hope that the osd data is still in tact. Once I get things stable again I was planning on upgrading…but the upgrade is a bit intensive by the looks of it so I need to set aside a decent amount of time. Thanks all! Shain > On Mar 15, 2017, at 12:38 PM, Vasu Kulkarni <vakul...@redhat.com> wrote: > > Just curious, why you still want to deploy new hammer instead of stable > jewel? Is this a test environment? the last .10 release was basically for bug > fixes for 0.94.9. > > > > On Wed, Mar 15, 2017 at 9:16 AM, Shinobu Kinjo <ski...@redhat.com > <mailto:ski...@redhat.com>> wrote: > FYI: > https://plus.google.com/+Cephstorage/posts/HuCaTi7Egg3 > <https://plus.google.com/+Cephstorage/posts/HuCaTi7Egg3> > > On Thu, Mar 16, 2017 at 1:05 AM, Shain Miley <smi...@npr.org > <mailto:smi...@npr.org>> wrote: > > Hello, > > I am trying to deploy ceph to a new server using ceph-deply which I have > > done in the past many times without issue. > > > > Right now I am seeing a timeout trying to connect to git.ceph.com > > <http://git.ceph.com/>: > > > > > > [hqosd6][INFO ] Running command: env DEBIAN_FRONTEND=noninteractive apt-get > > -q install --assume-yes ca-certificates > > [hqosd6][DEBUG ] Reading package lists... > > [hqosd6][DEBUG ] Building dependency tree... > > [hqosd6][DEBUG ] Reading state information... > > [hqosd6][DEBUG ] ca-certificates is already the newest version. > > [hqosd6][DEBUG ] 0 upgraded, 0 newly installed, 0 to remove and 3 not > > upgraded. > > [hqosd6][INFO ] Running command: wget -O release.asc > > https://ceph.com/git/?p=ceph.git;a=blob_plain;f=keys/release.asc > > <https://ceph.com/git/?p=ceph.git;a=blob_plain;f=keys/release.asc> > > [hqosd6][WARNIN] --2017-03-15 11:49:16-- > > https://ceph.com/git/?p=ceph.git;a=blob_plain;f=keys/release.asc > > <https://ceph.com/git/?p=ceph.git;a=blob_plain;f=keys/release.asc> > > [hqosd6][WARNIN] Resolving ceph.com <http://ceph.com/> (ceph.com > > <http://ceph.com/>)... 158.69.68.141 > > [hqosd6][WARNIN] Connecting to ceph.com <http://ceph.com/> (ceph.com > > <http://ceph.com/>)|158.69.68.141|:443... > > connected. > > [hqosd6][WARNIN] HTTP request sent, awaiting response... 301 Moved > > Permanently > > [hqosd6][WARNIN] Location: > > https://git.ceph.com/?p=ceph.git;a=blob_plain;f=keys/release.asc > > <https://git.ceph.com/?p=ceph.git;a=blob_plain;f=keys/release.asc> > > [following] > > [hqosd6][WARNIN] --2017-03-15 11:49:17-- > > https://git.ceph.com/?p=ceph.git;a=blob_plain;f=keys/release.asc > > <https://git.ceph.com/?p=ceph.git;a=blob_plain;f=keys/release.asc> > > [hqosd6][WARNIN] Resolving git.ceph.com <http://git.ceph.com/> > > (git.ceph.com <http://git.ceph.com/>)... 8.43.84.132 > > [hqosd6][WARNIN] Connecting to git.ceph.com <http://git.ceph.com/> > > (git.ceph.com <http://git.ceph.com/>)|8.43.84.132|:443... failed: > > Connection timed out. > > [hqosd6][WARNIN] Retrying. > > [hqosd6][WARNIN] > > [hqosd6][WARNIN] --2017-03-15 11:51:25-- (try: 2) > > https://git.ceph.com/?p=ceph.git;a=blob_plain;f=keys/release.asc > > <https://git.ceph.com/?p=ceph.git;a=blob_plain;f=keys/release.asc> > > [hqosd6][WARNIN] Connecting to git.ceph.com <http://git.ceph.com/> > > (git.ceph.com <http://git.ceph.com/>)|8.43.84.132|:443... failed: > > Connection timed out. > > [hqosd6][WARNIN] Retrying. > > [hqosd6][WARNIN] > > [hqosd6][WARNIN] --2017-03-15 11:53:34-- (try: 3) > > https://git.ceph.com/?p=ceph.git;a=blob_plain;f=keys/release.asc > > <https://git.ceph.com/?p=ceph.git;a=blob_plain;f=keys/release.asc> > > [hqosd6][WARNIN] Connecting to git.ceph.com <http://git.ceph.com/> > > (git.ceph.com <http://git.ceph.com/>)|8.43.84.132|:443... failed: > > Connection timed out. > > [hqosd6][WARNIN] Retrying. > > > > > > I am wondering if this is a known issue. > > > > Just an fyi...I am using an older version of ceph-deply (1.5.36) because in > > the past upgrading to a newer version I was not able to install hammer on > > the cluster…so the workaround was to use a slightly older version. > > > > Thanks in advance for any help you may be able to provide. > > > > Shain > > > > > > _______________________________________________ > > ceph-users mailing list > > ceph-users@lists.ceph.com <mailto:ceph-users@lists.ceph.com> > > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > > <http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com> > > > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com <mailto:ceph-users@lists.ceph.com> > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > <http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com> >
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com