show why mirrors are disabled
Bug #139275 reported by
Martin Pool
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
https:/
says "next mirror: disabled."
I presume this is because we don't run mirroring jobs in the edge environment. It would be nice to actually say so, both for the particular case of edge and for other reasons like past failures. The first case is particularly important when you consider that people can be transparently redirected to edge when they think they're looking at the real system, and then be concerned that mirroring is turned off.
If mirroring is always off for edge maybe just trivially inserting some text into this page to say so would be enough.
Revision history for this message
| Tim Penhey (thumper) wrote | #1 |
| Changed in launchpad-foundations: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| affects: | launchpad-foundations → launchpad-registry |
| tags: | added: mirror |
To post a comment you must log in.
The mirrors are not disabled.
What you are seeing is a discrepancy between how some internals are working now, and how they will work once the 1.1.9 roll out occurs.
Under normal circumstances there will be an error message showing for failing and disabled mirrors.