]> git.apps.os.sepia.ceph.com Git - ceph-build.git/commit
reconfigure apt during every "pbuilder update" 667/head
authorKen Dreyer <kdreyer@redhat.com>
Thu, 23 Mar 2017 22:17:30 +0000 (16:17 -0600)
committerKen Dreyer <kdreyer@redhat.com>
Thu, 23 Mar 2017 22:17:30 +0000 (16:17 -0600)
commit83ea1276600729d361bf641cfdfd841fb34853c3
treef3b4b3713f9807303d66644d02a9581172070c18
parent52a8bc496b23ae91bfa8d24da7d4264e88767ccb
reconfigure apt during every "pbuilder update"

The nfs-ganesha pbuilder setup code configures the pbuilder caches to
point at repos from shaman. Since all Jenkins jobs uses the same
pbuilder cache tarballs, this means that these shaman repositories will
still be enabled in the next jobs that run on a slave.

1) nfs-ganesha job runs on a slave
2) nfs-ganesha job configures pbuilder cache to use shaman repo
3) nfs-ganesha job finishes
4) ceph-build job runs on same slave slave
5) ceph-build job uses same pbuilder cache with shaman repo configured

In addition to polluting the pbuilder environment, this can also lead to
pbuilder failures when shaman/chacra garbage-collects old repositories,
because Apt wants to download repo metadata from old ceph repos that
are no longer available.

Force every job that runs "pbuilder update" to also run with
"--override-config" in order to wipe out any apt repositories that may
have been configured in the cache.
ceph-build/build/setup_pbuilder
ceph-dev-build/build/setup_pbuilder
ceph-dev-new-build/build/setup_pbuilder
diamond-build/build/setup_pbuilder
scripts/build_utils.sh