I was thinking of updating first to el9/centos9/rocky9 one node at a time, and after that do the ceph upgrade(s). I think this will give me the least intrusive upgrade path. However that requires the availability of Nautilus el9 rpms. I have been trying to build them via https://github.com/ceph/ceph and via rpmbuild ceph.spec. And without applying to many 'hacks', currently I seem to get around 30%-50%(?) of the code build[1] (albeit with quite some warnings[2]). This leads me to believe that it is most likely possible to build these for el9. Obviously I prefer to have someone with experience do this. Is it possible someone from the ceph development team can build these rpms for el9? Or are there serious issues that prevent this? [1] [build -- -- --prod --progress=false] > ceph-dashboard(a)0.0.0 build /home/ceph/src/pybind/mgr/dashboard/frontend [build -- -- --prod --progress=false] > export _locale=${LOCALE:-$npm_package_config_locale}; if [ ${_locale} = $npm_package_config_locale ]; then export _file=; else export _file=src/locale/messages.${_locale}.xlf; fi; ng build --outputPath=dist/${_locale} --i18nFile=${_file} --i18nLocale=${_locale} "--" "--prod" "--progress=false" [build -- -- --prod --progress=false] [ 51%] Building CXX object src/test/CMakeFiles/ceph_test_admin_socket_output.dir/test_admin_socket_output.cc.o [build -- -- --prod --progress=false] Unknown option: '--prod' [build -- -- --prod --progress=false] npm ERR! code ELIFECYCLE [build -- -- --prod --progress=false] npm ERR! errno 1 [build -- -- --prod --progress=false] npm ERR! ceph-dashboard(a)0.0.0 build: `export _locale=${LOCALE:-$npm_package_config_locale}; if [ ${_locale} = $npm_package_config_locale ]; then export _file=; else export _file=src/locale/messages.${_locale}.xlf; fi; ng build --outputPath=dist/${_locale} --i18nFile=${_file} --i18nLocale=${_locale} "--" "--prod" "--progress=false"` [build -- -- --prod --progress=false] npm ERR! Exit status 1 [build -- -- --prod --progress=false] npm ERR! [build -- -- --prod --progress=false] npm ERR! Failed at the ceph-dashboard(a)0.0.0 build script. [build -- -- --prod --progress=false] npm ERR! This is probably not a problem with npm. There is likely additional logging output above. [build -- -- --prod --progress=false] [build -- -- --prod --progress=false] npm ERR! A complete log of this run can be found in: [build -- -- --prod --progress=false] npm ERR! /root/.npm/_logs/2023-04-01T12_05_03_456Z-debug.log ERROR: "build -- -- --prod --progress=false" exited with 1. make[2]: *** [src/pybind/mgr/dashboard/CMakeFiles/mgr-dashboard-frontend-build.dir/build.make:736: ../src/pybind/mgr/dashboard/frontend/dist] Error 1 make[1]: *** [CMakeFiles/Makefile2:5884: src/pybind/mgr/dashboard/CMakeFiles/mgr-dashboard-frontend-build.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... [ 51%] Building CXX object src/test/CMakeFiles/ceph_test_admin_socket_output.dir/admin_socket_output.cc.o [ 51%] Building CXX object src/test/CMakeFiles/ceph_test_admin_socket_output.dir/admin_socket_output_tests.cc.o [ 51%] Linking CXX executable ../../bin/ceph_test_admin_socket_output [ 51%] Built target ceph_test_admin_socket_output make: *** [Makefile:146: all] Error 2 [2] [@]# cat /tmp/build.log | grep '^/home' | awk '{print $2" "$3" "$4" "$5}' | sort | uniq -c | sort -n 3 warning: ‘dummy’ may be 5 In instantiation of ‘void 27 In instantiation of ‘testing::PolymorphicMatcher<Impl>::PolymorphicMatcher(const 27 note: in expansion of 27 required from ‘testing::PolymorphicMatcher<Impl> testing::MakePolymorphicMatcher(const 67 required from ‘static void 79 In constructor ‘rocksdb::FdWithKeyRange::FdWithKeyRange(rocksdb::FileDescriptor, rocksdb::Slice, 82 In instantiation of ‘static 82 note: use non-reference type 82 warning: loop variable ‘e’ 96 required from ‘std::enable_if_t<(traits::supported && 153 In instantiation of ‘constexpr 239 note: because ‘rocksdb::FileDescriptor’ has 239 warning: implicitly-declared ‘constexpr rocksdb::FileDescriptor::FileDescriptor(const 270 required from here