Ceph » CephFS

We have to do this change whenever we branch out a release (branch) with the main branch tracking the next release - I wonder if the N-{1,2} branch names can be automatically picked up.

i remember discussing this with adam king when he wrote https://github.com/ceph/ceph/pull/52881. it will be interesting on how to set up a variable that knows what the latest release is; this indeed needs to done otherwise we will face this at every release

Dhairya Parmar wrote:

i remember discussing this with adam king when he wrote https://github.com/ceph/ceph/pull/52881. it will be interesting on how to set up a variable that knows what the latest release is; this indeed needs to done otherwise we will face this at every release

Let's fix this manually for now and then work on auto fetching the releases.

Venky Shankar wrote:

Dhairya Parmar wrote:

i remember discussing this with adam king when he wrote https://github.com/ceph/ceph/pull/52881. it will be interesting on how to set up a variable that knows what the latest release is; this indeed needs to done otherwise we will face this at every release

Let's fix this manually for now and then work on auto fetching the releases.

I was researching on automating this but if you'd like this manually then sure, i'll do it. So, the oldest one would be pacific and the latest being reef.

Dhairya Parmar wrote:

Venky Shankar wrote:

Dhairya Parmar wrote:

i remember discussing this with adam king when he wrote https://github.com/ceph/ceph/pull/52881. it will be interesting on how to set up a variable that knows what the latest release is; this indeed needs to done otherwise we will face this at every release

Let's fix this manually for now and then work on auto fetching the releases.

I was researching on automating this but if you'd like this manually then sure, i'll do it. So, the oldest one would be pacific and the latest being reef.

In the interest of time, yes, manually. We can then see how to automagically fetch the releases.

I found this on adam's PR desciption https://github.com/ceph/ceph/pull/53105:

Since reef is released, we should ideally be
testing upgrades from reef -> main now

This cannot be merged until main reports a version 19.y.z instead of the current 18.0.0. Otherwise trying to do an upgrade from reef to main hits an error like Upgrade: Paused due to UPGRADE_BAD_TARGET_VERSION: Upgrade: cannot upgrade/downgrade to 18.0.0-5596-gdb1309a8. This cannot be resolved with a workaround in the upgrade code in main, as it's the upgrade code in the reef image that is actually hitting the failure.

Pacific is EOL in a few days. So either we ignore the EOL and keep using pacific-quincy or the I fear we are limited to using just the quincy

Dhairya Parmar wrote:

I found this on adam's PR desciption https://github.com/ceph/ceph/pull/53105:

[...]

Pacific is EOL in a few days. So either we ignore the EOL and keep using pacific-quincy or the I fear we are limited to using just the quincy

fs:upgrade includes tests to start upgrading from octopus/nautilus. This change is for yamls that upgrade to current main (squid) and that should be from Q/R releases.