On Sun, Nov 5, 2017 at 8:17 PM, Abhishek L <abhishek.lekshmanan@xxxxxxxxx> wrote: > On Sat, Nov 4, 2017 at 8:51 AM, Nathan Cutler <ncutler@xxxxxxx> wrote: >>> all or nothing. if we want to backport the fix of >>> http://tracker.ceph.com/issues/21762, we will have to backport the >>> "debian: fix package relationships after" fixes. so i think pull/18589 >>> is self-contained. and no additional step is needed. >>> >>> and per http://tracker.ceph.com/issues/21762, we need to have it in >>> luminous. but i have no strong opinion on including it in 12.2.2 or >>> post 12.2.2. Vikhyat and Nathan, what do you think? >> >> >> Yes, I tried to make 18589 self-contained by pulling in Kefu's and >> Abhishek's follow-on fixes. I think it would be nice to have it in 12.2.2. > > Rebuilt the integration branch with the newer PR and it still fails > with the same reason > http://pulpito.ceph.com/abhi-2017-11-05_11:53:02-ceph-disk-wip-abhi-testing-2017-11-05-0933-distro-basic-vps/ > for eg. > > Kefu, are there any more commits we need to solve the dependency issue? well, yes and no. we need to "dch" the changelog, to bump up the version number to 12.2.2 to address this issue. but i thought this was a step of our release process: see https://github.com/ceph/ceph-build/blob/2cb4f4069c7a0fac1abecd76e6014272f22cf139/ansible/roles/ceph-release/tasks/release/stable.yml#L3. that's why i believed that PR#18589 was self-contained. anyway, we can "fix" this issue in two ways: 1. "dch" the changelog in a commit only for testing, and it will not be merged into luminous. run that the upgrade suites using dch'ed version, and wait until the jenkins builder to tag and dch automatically for the official release of 12.2.2 2. just drop the PR#18589. so and include it in post 12.2.2. so the problem will be resolved w/o any efforts by then. -- Regards Kefu Chai -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
