[Bug 2100625] Re: [SRU] ceph 17.2.9

[Matthew Ruffell]

Hi Luciano,

I encountered the following build issue on armhf with -updates and
-proposed:

[ 46%] Building CXX object src/exporter/CMakeFiles/ceph-exporter.dir/DaemonMetricCollector.cc.o
cd /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/src/exporter && /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ASIO_DISABLE_THREAD_KEYWORD_EXTENSION -DBOOST_ASIO_USE_TS_EXECUTOR_AS_DEFAULT -DBOOST_ATOMIC_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_RANDOM_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK -DHAVE_CONFIG_H -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D__CEPH__ -D__STDC_FORMAT_MACROS -D__linux__ -I/<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/src/include -I/<<PKGBUILDDIR>>/src -isystem /<<PKGBUILDDIR>>/obj-arm-linux-gnueabihf/include -isystem /<<PKGBUILDDIR>>/src/xxHash -isystem /<<PKGBUILDDIR>>/src/rapidjson/include -isystem /<<PKGBUILDDIR>>/src/fmt/include -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -g1 -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -fPIE   -U_FORTIFY_SOURCE -Wall -fno-strict-aliasing -fsigned-char -Wtype-limits -Wignored-qualifiers -Wpointer-arith -Werror=format-security -Winit-self -Wno-unknown-pragmas -Wnon-virtual-dtor -Wno-ignored-qualifiers -ftemplate-depth-1024 -Wpessimizing-move -Wredundant-move -Wstrict-null-sentinel -Woverloaded-virtual -fno-new-ttp-matching -fstack-protector-strong -fdiagnostics-color=auto -std=c++17 -MD -MT src/exporter/CMakeFiles/ceph-exporter.dir/DaemonMetricCollector.cc.o -MF CMakeFiles/ceph-exporter.dir/DaemonMetricCollector.cc.o.d -o CMakeFiles/ceph-exporter.dir/DaemonMetricCollector.cc.o -c /<<PKGBUILDDIR>>/src/exporter/DaemonMetricCollector.cc
In file included from /<<PKGBUILDDIR>>/src/boost/boost/json/detail/ryu/impl/d2s.ipp:55,
                 from /<<PKGBUILDDIR>>/src/boost/boost/json/src.hpp:60,
                 from /<<PKGBUILDDIR>>/src/exporter/DaemonMetricCollector.cc:3:
/<<PKGBUILDDIR>>/src/boost/boost/json/detail/ryu/impl/../detail/d2s.hpp:35:10: fatal error: boost/json/detail/ryu/detail/d2s_intrinsics.hpp: No such file or directory
   35 | #include <boost/json/detail/ryu/detail/d2s_intrinsics.hpp>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

I did a search, and it appears that you missed this one in exporter-
fix.patch.

ceph-17.2.9/src/boost$ grep -Rin "boost/json/detail/ryu/"
boost/json/detail/ryu/detail/d2s.hpp:35:#include <boost/json/detail/ryu/detail/d2s_intrinsics.hpp>
libs/json/test/ryu/d2s_test.cpp:22:#include <boost/json/detail/ryu/ryu.hpp>
libs/json/test/ryu/d2s_intrinsics_test.cpp:22:#include <boost/json/detail/ryu/detail/d2s_intrinsics.hpp>
libs/json/test/ryu/d2s_table_test.cpp:33:#include <boost/json/detail/ryu/detail/d2s.hpp>
libs/json/test/ryu/d2s_table_test.cpp:34:#include <boost/json/detail/ryu/detail/d2s_full_table.hpp>

There also seems to be some testcases that you didn't do either.

I will try get this fixed up. Next time, please build with all arches
enabled.

As a side note, ceph takes a lot of resources during its autopkgtest
runs...

Thanks,
Matthew

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/2100625

Title:
  [SRU] ceph 17.2.9

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive yoga series:
  Triaged
Status in ceph package in Ubuntu:
  Invalid
Status in ceph source package in Focal:
  Invalid
Status in ceph source package in Jammy:
  In Progress

Bug description:
  [Impact]
  This release fixes several bugs. We would like to make sure all of our users have access to these improvements.

  The update contains the following package updates:

     * ceph 17.2.9
     * Race condition prevention when printing Inode in ll_sync_inode (by Ponnuvel Palaniyappan)

  [Test Case]
  The following SRU process was followed:

  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  OpenStack-Updates/

  In order to avoid regression of existing users, the OpenStack team
  will run their continuous integration test against the packages that
  are in -proposed. A successful run of all available tests will be
  required before the proposed packages can be let into -updates.

  The OpenStack team will be in charge of attaching the output summary
  of the executed tests. The OpenStack team members will not mark
  ‘verification-done’ until this has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the aforementioned tests will be attached to this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2100625/+subscriptions