Closed tserong closed 3 years ago
@dasrohr - for your review also
@kshtsk Any idea why storage-ci/deepsea-make-rpm
is failing?
I've had a quick skim through the console output from the previous successful run on this PR (https://storage-ci.suse.de/job/deepsea-teuthology-rpm-builder/1340/consoleFull) and the failed run (https://storage-ci.suse.de/job/deepsea-teuthology-rpm-builder/1342/console), and ISTM we have some sort of chicken-and-egg problem.
See this?
Step 12/15 : RUN pwd && ls -la && cd DeepSea && sudo zypper --non-interactive --gpg-auto-import-keys refresh && sudo zypper --non-interactive install --no-recommends $(rpmspec --requires -q deepsea.spec.in 2>/dev/null)
That'll try to install all the requires listed in deepsea.spec.in, but, at that time, Version is DEVVERSION and Release is 0. With the previous version of this commit, deepsea-cli specified Requires: deepsea
, so the above went and installed deepsea from filesystems:ceph:nautilus (which we arguably don't want before the build anyway). With the latest version of this commit, this means we've got Requires: deepsea = DEVVERSION=0
, which can't be satisfied. There's a later step in the successful run where the correct version is sedded in (Step 13/15 : RUN cd DeepSea && make rpm
), but even if that were to happen earlier, it still wouldn't help, because this new version of deepsea doesn't exist yet!
I suspect this is fixable if we change Step 12 to $(rpmspec --requires -q deepsea.spec.in 2>/dev/null | grep -v deepsea)
which will strip deepsea itself from the list of requirements pre-build.
@tserong Nice catch, but I don't remember why do we need this --requires
if we want --buildrequires
, @smithfarm ?
Review this https://github.com/SUSE/sesci/pull/49
@kshtsk It's possible that it will work if you replace --requires
with --buildrequires
. Just give it a try?
Proof that this change is fixing the issue: https://storage-ci.suse.de/job/deepsea-teuthology-rpm-builder/1343/console
retest this please
retest this please
@kshtsk Thanks!
@susebot run teuthology
Commit f606511d340d1d59742edbd0ca72fceed28f3c9e is OK for suite deepsea:tier2. Check tests results in the Jenkins job: https://storage-ci.suse.de/job/pr-deepsea/493/
This means removing deepsea will also automatically remove deepsea-cli (see https://github.com/SUSE/doc-ses/issues/816 for related discussion).
Signed-off-by: Tim Serong tserong@suse.com