From: "Chen, Qi" <Qi.Chen@windriver.com>
To: "bruce.ashfield@gmail.com" <bruce.ashfield@gmail.com>
Cc: Christopher Clark <christopher.w.clark@gmail.com>,
Tim Orling <ticotimo@gmail.com>,
meta-virtualization <meta-virtualization@lists.yoctoproject.org>
Subject: RE: [meta-virtualization] ceph upgrade
Date: Thu, 14 Mar 2024 08:11:26 +0000 [thread overview]
Message-ID: <CO6PR11MB5602ABA096682FDDDD073876ED292@CO6PR11MB5602.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CADkTA4Pt0+KfK-93T-umk=xKs-9y+N7aCAs54TAF=dAGrkJSug@mail.gmail.com>
Hi Bruce,
I've sent out V2, which handles these QA issues, as well as some simple runtime issues.
Regards,
Qi
-----Original Message-----
From: meta-virtualization@lists.yoctoproject.org <meta-virtualization@lists.yoctoproject.org> On Behalf Of Bruce Ashfield via lists.yoctoproject.org
Sent: Wednesday, March 13, 2024 8:58 PM
To: Chen, Qi <Qi.Chen@windriver.com>
Cc: Christopher Clark <christopher.w.clark@gmail.com>; Tim Orling <ticotimo@gmail.com>; meta-virtualization <meta-virtualization@lists.yoctoproject.org>
Subject: Re: [meta-virtualization] ceph upgrade
I'll have a closer look at the patch this morning. Cmake is still not obvious to me, so I'm going to try and reverse engineer how you came up with the patches!
Christopher: I'm still interested if there's anything that can be removed from the vendored dependencies that you were looking into.
Bruce
On Wed, Mar 13, 2024 at 7:10 AM ChenQi <Qi.Chen@windriver.com> wrote:
>
> I found the install and packaging issues easy to fix. So I spend a
> little more time.
> The patch has been sent out.
>
> There are still some package_qa issues as shown below:
>
> WARNING: ceph-18.2.0-r0 do_package_qa: QA Issue: File
> /usr/bin/cephfs-top in package ceph contains reference to TMPDIR File
> /usr/sbin/cephadm in package ceph contains reference to TMPDIR
> [buildpaths]
> ERROR: ceph-18.2.0-r0 do_package_qa: QA Issue: ceph:
> /usr/bin/cephfs-top maximum shebang size exceeded, the maximum size is 128.
> ceph: /usr/sbin/cephadm maximum shebang size exceeded, the maximum
> size is 128. [shebang-size]
> ERROR: ceph-18.2.0-r0 do_package_qa: QA Issue: /usr/bin/cephfs-top
> contained in package ceph requires
> /ala-lpggp72/qichen/Yocto/builds/build-poky/tmp/work/core2-64-poky-lin
> ux/ceph/18.2.0/recipe-sysroot-native/usr/bin/python3-native/python3,
> but no providers found in RDEPENDS:ceph? [file-rdeps]
> WARNING: ceph-18.2.0-r0 do_package_qa: QA Issue: File
> /usr/lib/python3.12/site-packages/cephfs.cpython-312-x86_64-linux-gnu.
> so in package ceph-python contains reference to TMPDIR File
> /usr/lib/python3.12/site-packages/rbd.cpython-312-x86_64-linux-gnu.so
> in package ceph-python contains reference to TMPDIR File
> /usr/lib/python3.12/site-packages/rados.cpython-312-x86_64-linux-gnu.s
> o in package ceph-python contains reference to TMPDIR File
> /usr/lib/python3.12/site-packages/rgw.cpython-312-x86_64-linux-gnu.so
> in package ceph-python contains reference to TMPDIR File
> /usr/lib/python3.12/site-packages/ceph_volume-1.0.0-py3.12.egg-info/de
> pendency_links.txt in package ceph-python contains reference to TMPDIR
> [buildpaths]
> ERROR: ceph-18.2.0-r0 do_package_qa: QA Issue: -dev package ceph-dev
> contains non-symlink .so '/usr/lib/libcephsqlite.so' [dev-elf]
> WARNING: ceph-18.2.0-r0 do_package_qa: QA Issue: File
> /usr/lib/python3.12/site-packages/.debug/cephfs.cpython-312-x86_64-lin
> ux-gnu.so in package ceph-dbg contains reference to TMPDIR File
> /usr/lib/python3.12/site-packages/.debug/rbd.cpython-312-x86_64-linux-
> gnu.so in package ceph-dbg contains reference to TMPDIR File
> /usr/lib/python3.12/site-packages/.debug/rados.cpython-312-x86_64-linu
> x-gnu.so in package ceph-dbg contains reference to TMPDIR File
> /usr/lib/python3.12/site-packages/.debug/rgw.cpython-312-x86_64-linux-
> gnu.so in package ceph-dbg contains reference to TMPDIR [buildpaths]
> ERROR: ceph-18.2.0-r0 do_package_qa: Fatal QA errors were found,
> failing task.
> ERROR: Logfile of failure stored in:
> /ala-lpggp72/qichen/Yocto/builds/build-poky/tmp/work/core2-64-poky-lin
> ux/ceph/18.2.0/temp/log.do_package_qa.3746018
> ERROR: Task
> (/ala-lpggp72/qichen/Yocto/poky/meta-virtualization/recipes-extended/c
> eph/ceph_18.2.0.bb:do_package_qa)
> failed with exit code '1'
>
> Regards,
> Qi
>
>
> On 3/13/24 18:51, Chen Qi via lists.yoctoproject.org wrote:
> > Hi Bruce,
> >
> > I looked into this ceph issue this afternoon. Now I can make
> > do_compile pass.
> > There's still some do_install issue, but I really need to head home now.
> > I'll send out my patch soon.
> >
> > Regards,
> > Qi
> >
> >
> > On 3/13/24 02:43, Bruce Ashfield via lists.yoctoproject.org wrote:
> >> On Tue, Mar 12, 2024 at 1:58 PM Christopher Clark
> >> <christopher.w.clark@gmail.com> wrote:
> >>> On Mon, Mar 11, 2024 at 6:56 PM Bruce Ashfield
> >>> <bruce.ashfield@gmail.com> wrote:
> >>>> On Mon, Mar 11, 2024 at 8:41 PM Tim Orling <ticotimo@gmail.com> wrote:
> >>>>> On Mon, Mar 11, 2024 at 2:11 PM Bruce Ashfield
> >>>>> <bruce.ashfield@gmail.com> wrote:
> >>>>>> Hi all,
> >>>>>>
> >>>>>> I'm still looking for help with this.
> >>>>>>
> >>>>>> It's all fine and well that folks have packages that they are
> >>>>>> interested in more than others, but it needs to be more than
> >>>>>> maintainers that step up and fix the niche packages.
> >>>>>>
> >>>>>> I'm still holding the meta-virt master-next -> master push
> >>>>>> until Ceph is upgraded and working.
> >>>>>>
> >>>>>> I know absolutely nothing about CMake, so I'm flailing around
> >>>>>> in the build of Ceph and have gotten no further since I last
> >>>>>> asked for help.
> >>>>> Well I did try, but I am no CMake expert nor ceph expert either.
> >>>>> I got stalled on it detecting “thrift” in one of the vendored
> >>>>> libraries.
> >>>> I ended up with that as well (just a few minutes ago), I tried
> >>>> setting some Thrift variables, but it refuses to detect those as well.
> >>>>
> >>>> The errors seem to rotate .. and it isn't even obvious if some
> >>>> are really fatal, or not.
> >>>>
> >>>> Perhaps it just isn't something that cross builds anymore, and
> >>>> I'll just blacklist it with the broken recipe.
> >>>>
> >>>> I'll have one more try with it tomorrow before giving up.
> >>> Hi Bruce, Tim,
> >>>
> >>> I had a look at this yesterday, and I (possibly?) made some
> >>> progress with it but wanted to ask before getting too far with an approach:
> >>> would it be OK to pull out at least some of those vendored
> >>> components into some new separate recipes, so that rebuilding that
> >>> compile stage when it needs it is faster?
> >>>
> >> I'm fine with stripping it down to the bare minimum to be buildable.
> >>
> >> I'd rather have a building (but small) recipe, and then we can see
> >> if there's demand for more components.
> >>
> >> I was also poking at this today, and I'm still seeing dramatically
> >> different results when I call compile multiple times .. all the way
> >> back to cmake complaining it can't find the python3 interpreter,
> >> which was a problem I thought I had solved!
> >>
> >> Feel free to grab me on the #meta-virt channel if you have any
> >> interactive questions.
> >>
> >> Bruce
> >>
> >>> Christopher
> >>>
> >>>
> >>>> Bruce
> >>>>
> >>>>> We can only take so much abuse from upstream ;)
> >>>>>
> >>>>>
> >>>>>> Bruce
> >>>>>>
> >>>>>> On Tue, Mar 5, 2024 at 9:22 PM Bruce Ashfield via
> >>>>>> lists.yoctoproject.org
> >>>>>> <bruce.ashfield=gmail.com@lists.yoctoproject.org> wrote:
> >>>>>>> Hi all,
> >>>>>>>
> >>>>>>> If anyone has experience with Cmake, I could use a hand
> >>>>>>> completing the ceph upgrade that is marked as WIP in
> >>>>>>> master-next.
> >>>>>>>
> >>>>>>> It took me a few hours today, but I managed to get past
> >>>>>>> python3 detection issues, but now I'm running into a compiler
> >>>>>>> test failure during the build.
> >>>>>>>
> >>>>>>> To me, it looks like our sysroot isn't being passed, which
> >>>>>>> could be related to the toolchain.cmake not being used (since
> >>>>>>> the compiler test is being launched by a sub component).
> >>>>>>>
> >>>>>>> I'm inclined to be stubborn about this, and keep working on
> >>>>>>> getting the package bumped, as it has missed a few upgrades
> >>>>>>> and is in need of some love.
> >>>>>>>
> >>>>>>> Bruce
> >>>>>>>
> >>>>>>> --
> >>>>>>> - Thou shalt not follow the NULL pointer, for chaos and
> >>>>>>> madness await thee at its end
> >>>>>>> - "Use the force Harry" - Gandalf, Star Trek II
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> - Thou shalt not follow the NULL pointer, for chaos and madness
> >>>>>> await thee at its end
> >>>>>> - "Use the force Harry" - Gandalf, Star Trek II
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>>> --
> >>>> - Thou shalt not follow the NULL pointer, for chaos and madness
> >>>> await thee at its end
> >>>> - "Use the force Harry" - Gandalf, Star Trek II
> >>>>
> >>>>
> >>>>
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
> >
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
next prev parent reply other threads:[~2024-03-14 8:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17BA0B9342C35A1E.21429@lists.yoctoproject.org>
2024-03-11 21:11 ` [meta-virtualization] ceph upgrade Bruce Ashfield
2024-03-12 0:40 ` Tim Orling
2024-03-12 1:55 ` Bruce Ashfield
2024-03-12 17:58 ` Christopher Clark
2024-03-12 18:43 ` Bruce Ashfield
2024-03-13 10:51 ` ChenQi
[not found] ` <17BC4D73EFF2649F.27213@lists.yoctoproject.org>
2024-03-13 11:09 ` ChenQi
2024-03-13 12:58 ` Bruce Ashfield
2024-03-14 8:11 ` Chen, Qi [this message]
2024-03-06 2:22 Bruce Ashfield
2024-03-06 6:38 ` [meta-virtualization] " Khem Raj
2024-03-06 14:24 ` Bruce Ashfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CO6PR11MB5602ABA096682FDDDD073876ED292@CO6PR11MB5602.namprd11.prod.outlook.com \
--to=qi.chen@windriver.com \
--cc=bruce.ashfield@gmail.com \
--cc=christopher.w.clark@gmail.com \
--cc=meta-virtualization@lists.yoctoproject.org \
--cc=ticotimo@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).