Hello, On Sat, 30 Aug 2014 20:24:00 -0400 J David wrote: > While adding some nodes to a ceph emperor cluster using ceph-deploy, > the new nodes somehow wound up with 0.80.1, which I think is a Firefly > release. > This was asked and solved in the "ceph-deploy with --release (--stable) for dumpling?" thread earlier this week. I wouldn't want to run mixed cluster for a prolonged time, so if you don't want to upgrade to firefly in general, pin it to emperor. Christian > The ceph version on existing nodes: > > $ ceph --version > ceph version 0.72.2 (a913ded2ff138aefb8cb84d347d72164099cfd60) > > The repository on the new nodes: > > $ cat /etc/apt/sources.list.d/ceph.list > deb http://ceph.com/debian-emperor/ trusty main > > The ceph version on new nodes: > > $ ceph --version > ceph version 0.80.1 (a38fe1169b6d2ac98b427334c12d7cf81f809b74) > > Inspecting the repository on ceph.com, it does look like it contains > 0.72.2 packages. > > How did we get 0.80.1 instead? Is this expected behavior? Will it > cause problems for us? > > Thanks for any advice! > _______________________________________________ > ceph-users mailing list > ceph-users at lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > -- Christian Balzer Network/Systems Engineer chibi at gol.com Global OnLine Japan/Fusion Communications http://www.gol.com/
 |