← Back to team overview

touch-packages team mailing list archive

[Bug 1511049] [NEW] add-apt-repository intermittently fails on krillin

 

Public bug reported:

Running 'sudo add-apt-repository --yes ppa:ci-train-ppa-service/stable-phone-overlay' on krillin devices (witth vivid devel-proposed images) sometimes fails to add the ppa and fails with the following error:
 
Cannot add PPA: 'ppa:~ci-train-ppa-service/ubuntu/stable-phone-overlay'.
The team named '~ci-train-ppa-service' has no PPA named 'ubuntu/stable-phone-overlay'
Please choose from the following available PPAs:
 * 'landing-000':  Landing PPA 000
 * 'landing-000':  Landing PPA 000 (RTM)
 * 'landing-001':  Landing PPA 001 (RTM)
 * 'landing-001':  Landing PPA 001
 * 'landing-002':  Landing PPA 002
 * 'landing-002':  Landing PPA 002 (RTM)
 * 'landing-003':  Landing PPA 003
 * 'landing-003':  Landing PPA 003 (RTM)
 * 'landing-004':  Landing PPA 004 (RTM)
 * 'landing-004':  Landing PPA 004
 * 'landing-005':  Landing PPA 005
 * 'landing-005':  Landing PPA 005 (RTM)
 * 'landing-006':  Landing PPA 006 (RTM)
 * 'landing-006':  Landing PPA 006
 * 'landing-007':  Landing PPA 007
 * 'landing-007':  Landing PPA 007 (RTM)
 * 'landing-008':  Landing PPA 008 (RTM)
 * 'landing-008':  Landing PPA 008
 * 'landing-009':  Landing PPA 009 (RTM)
 * 'landing-009':  Landing PPA 009
 * 'landing-010':  Landing PPA 010 (RTM)
 * 'landing-010':  Landing PPA 010
 * 'landing-011':  Landing PPA 011
 * 'landing-011':  Landing PPA 011 (RTM)
 * 'landing-012':  Landing PPA 012 (RTM)
 * 'landing-012':  Landing PPA 012
 * 'landing-013':  Landing PPA 013 (RTM)
 * 'landing-013':  Landing PPA 013
 * 'landing-014':  Landing PPA 014 (RTM)
 * 'landing-014':  Landing PPA 014
 * 'landing-015':  Landing PPA 015
 * 'landing-015':  Landing PPA 015 (RTM)
 * 'landing-016':  Landing PPA 016 (RTM)
 * 'landing-016':  Landing PPA 016
 * 'landing-017':  Landing PPA 017
 * 'landing-017':  Landing PPA 017 (RTM)
 * 'landing-018':  Landing PPA 018 (RTM)
 * 'landing-018':  Landing PPA 018
 * 'landing-019':  Landing PPA 019 (RTM)
 * 'landing-019':  Landing PPA 019
 * 'landing-020':  Landing PPA 020
 * 'landing-020':  Landing PPA 020 (RTM)
 * 'landing-021':  Landing PPA 021 (RTM)
 * 'landing-021':  Landing PPA 021
 * 'landing-022':  Landing PPA 022 (RTM)
 * 'landing-022':  Landing PPA 022
 * 'landing-023':  Landing PPA 023 (RTM)
 * 'landing-023':  Landing PPA 023
 * 'landing-024':  Landing PPA 024
 * 'landing-024':  Landing PPA 024 (RTM)
 * 'landing-025':  Landing PPA 025
 * 'landing-025':  Landing PPA 025 (RTM)
 * 'landing-026':  Landing PPA 026
 * 'landing-026':  Landing PPA 026 (RTM)
 * 'landing-027':  Landing PPA 027
 * 'landing-027':  Landing PPA 027 (RTM)
 * 'landing-028':  Landing PPA 028 (RTM)
 * 'landing-028':  Landing PPA 028
 * 'landing-029':  Landing PPA 029
 * 'landing-029':  Landing PPA 029 (RTM)
 * 'landing-030':  Landing PPA 030 (RTM)
 * 'landing-030':  Landing PPA 030
 * 'landing-031':  Landing PPA 031
 * 'landing-031':  Landing PPA 031 (RTM)
 * 'landing-032':  Landing PPA 032
 * 'landing-032':  Landing PPA 032 (RTM)
 * 'landing-033':  Landing PPA 033
 * 'landing-033':  Landing PPA 033 (RTM)
 * 'landing-034':  Landing PPA 034 (RTM)
 * 'landing-034':  Landing PPA 034
 * 'landing-035':  Landing PPA 035
 * 'landing-035':  Landing PPA 035 (RTM)
 * 'landing-036':  Landing PPA 036
 * 'landing-036':  Landing PPA 036 (RTM)
 * 'landing-037':  Landing PPA 037 (RTM)
===============================================
We ran this by the launchpad team and based on the analysis that cjwatson carried out, he had this to say:

'The bit where it only lists a subset of PPAs is a bug in add-apt-
repository. It's talking to the Launchpad API by hand to avoid needing
to introduce additional dependencies, but unfortunately it doesn't
implement the collection API properly: it needs to follow links to
subsequent batches until it's found everything. (Notice that it's shown
you 75 entries, which is exactly our current batch size on production.)
I'd suggest raising that with the Foundations team, who can come to us
if they need help fixing it.

I'm not completely sure why it couldn't add the PPA in the first place,
though, and I suspect the underlying error has been obscured by add-apt-
repository somewhere along the line. I compared with appserver logs for
the relevant timestamps (which are just about still available); there
are records of requests from a bit later in that hour, but add-apt-
repository's request didn't hit any appserver as far as I can tell. I
therefore suspect that it was denied by haproxy due to temporary high
load or some transient network problem, and indeed, add-apt-repository
ought to have some back-off-and-retry logic. Again, that's something the
Foundations team would be best-placed to fix.'

We could add that this issue is only visible for us on krillin devices
and that this is an intermittent issue with somewhat higher frequency.
The mako runs with the same command hasn't failed at all this way.

** Affects: software-properties (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1511049

Title:
  add-apt-repository intermittently fails on krillin

Status in software-properties package in Ubuntu:
  New

Bug description:
  Running 'sudo add-apt-repository --yes ppa:ci-train-ppa-service/stable-phone-overlay' on krillin devices (witth vivid devel-proposed images) sometimes fails to add the ppa and fails with the following error:
   
  Cannot add PPA: 'ppa:~ci-train-ppa-service/ubuntu/stable-phone-overlay'.
  The team named '~ci-train-ppa-service' has no PPA named 'ubuntu/stable-phone-overlay'
  Please choose from the following available PPAs:
   * 'landing-000':  Landing PPA 000
   * 'landing-000':  Landing PPA 000 (RTM)
   * 'landing-001':  Landing PPA 001 (RTM)
   * 'landing-001':  Landing PPA 001
   * 'landing-002':  Landing PPA 002
   * 'landing-002':  Landing PPA 002 (RTM)
   * 'landing-003':  Landing PPA 003
   * 'landing-003':  Landing PPA 003 (RTM)
   * 'landing-004':  Landing PPA 004 (RTM)
   * 'landing-004':  Landing PPA 004
   * 'landing-005':  Landing PPA 005
   * 'landing-005':  Landing PPA 005 (RTM)
   * 'landing-006':  Landing PPA 006 (RTM)
   * 'landing-006':  Landing PPA 006
   * 'landing-007':  Landing PPA 007
   * 'landing-007':  Landing PPA 007 (RTM)
   * 'landing-008':  Landing PPA 008 (RTM)
   * 'landing-008':  Landing PPA 008
   * 'landing-009':  Landing PPA 009 (RTM)
   * 'landing-009':  Landing PPA 009
   * 'landing-010':  Landing PPA 010 (RTM)
   * 'landing-010':  Landing PPA 010
   * 'landing-011':  Landing PPA 011
   * 'landing-011':  Landing PPA 011 (RTM)
   * 'landing-012':  Landing PPA 012 (RTM)
   * 'landing-012':  Landing PPA 012
   * 'landing-013':  Landing PPA 013 (RTM)
   * 'landing-013':  Landing PPA 013
   * 'landing-014':  Landing PPA 014 (RTM)
   * 'landing-014':  Landing PPA 014
   * 'landing-015':  Landing PPA 015
   * 'landing-015':  Landing PPA 015 (RTM)
   * 'landing-016':  Landing PPA 016 (RTM)
   * 'landing-016':  Landing PPA 016
   * 'landing-017':  Landing PPA 017
   * 'landing-017':  Landing PPA 017 (RTM)
   * 'landing-018':  Landing PPA 018 (RTM)
   * 'landing-018':  Landing PPA 018
   * 'landing-019':  Landing PPA 019 (RTM)
   * 'landing-019':  Landing PPA 019
   * 'landing-020':  Landing PPA 020
   * 'landing-020':  Landing PPA 020 (RTM)
   * 'landing-021':  Landing PPA 021 (RTM)
   * 'landing-021':  Landing PPA 021
   * 'landing-022':  Landing PPA 022 (RTM)
   * 'landing-022':  Landing PPA 022
   * 'landing-023':  Landing PPA 023 (RTM)
   * 'landing-023':  Landing PPA 023
   * 'landing-024':  Landing PPA 024
   * 'landing-024':  Landing PPA 024 (RTM)
   * 'landing-025':  Landing PPA 025
   * 'landing-025':  Landing PPA 025 (RTM)
   * 'landing-026':  Landing PPA 026
   * 'landing-026':  Landing PPA 026 (RTM)
   * 'landing-027':  Landing PPA 027
   * 'landing-027':  Landing PPA 027 (RTM)
   * 'landing-028':  Landing PPA 028 (RTM)
   * 'landing-028':  Landing PPA 028
   * 'landing-029':  Landing PPA 029
   * 'landing-029':  Landing PPA 029 (RTM)
   * 'landing-030':  Landing PPA 030 (RTM)
   * 'landing-030':  Landing PPA 030
   * 'landing-031':  Landing PPA 031
   * 'landing-031':  Landing PPA 031 (RTM)
   * 'landing-032':  Landing PPA 032
   * 'landing-032':  Landing PPA 032 (RTM)
   * 'landing-033':  Landing PPA 033
   * 'landing-033':  Landing PPA 033 (RTM)
   * 'landing-034':  Landing PPA 034 (RTM)
   * 'landing-034':  Landing PPA 034
   * 'landing-035':  Landing PPA 035
   * 'landing-035':  Landing PPA 035 (RTM)
   * 'landing-036':  Landing PPA 036
   * 'landing-036':  Landing PPA 036 (RTM)
   * 'landing-037':  Landing PPA 037 (RTM)
  ===============================================
  We ran this by the launchpad team and based on the analysis that cjwatson carried out, he had this to say:

  'The bit where it only lists a subset of PPAs is a bug in add-apt-
  repository. It's talking to the Launchpad API by hand to avoid needing
  to introduce additional dependencies, but unfortunately it doesn't
  implement the collection API properly: it needs to follow links to
  subsequent batches until it's found everything. (Notice that it's
  shown you 75 entries, which is exactly our current batch size on
  production.) I'd suggest raising that with the Foundations team, who
  can come to us if they need help fixing it.

  I'm not completely sure why it couldn't add the PPA in the first
  place, though, and I suspect the underlying error has been obscured by
  add-apt-repository somewhere along the line. I compared with appserver
  logs for the relevant timestamps (which are just about still
  available); there are records of requests from a bit later in that
  hour, but add-apt-repository's request didn't hit any appserver as far
  as I can tell. I therefore suspect that it was denied by haproxy due
  to temporary high load or some transient network problem, and indeed,
  add-apt-repository ought to have some back-off-and-retry logic. Again,
  that's something the Foundations team would be best-placed to fix.'

  We could add that this issue is only visible for us on krillin devices
  and that this is an intermittent issue with somewhat higher frequency.
  The mako runs with the same command hasn't failed at all this way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1511049/+subscriptions


Follow ups