Publication jobs should not start if authorized_keys is missing
Bug #513722 reported by
Thierry Carrez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| eucalyptus (Ubuntu) |
Fix Released
|
Medium
|
Thierry Carrez | ||
| Lucid |
Fix Released
|
Medium
|
Thierry Carrez | ||
Bug Description
Splitted from bug 504326
On package installs, authorized_keys must be manually set on components.
There is no point in starting publication jobs if the the component is not ready to be autoregistered.
Two options:
- Fail the publication job is authorized_keys is missing (requires the user to manually start the publication job after keys are setup)
- Poll for authorized_keys presence in the upstart script (slightly heavier on resource usage)
| Changed in eucalyptus (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
Revision history for this message
| Mathias Gug (mathiaz) wrote Re: [Bug 513722] [NEW] Publication jobs should not start if authorized_keys is missing | #1 |
Revision history for this message
| Thierry Carrez (ttx) wrote | #2 |
| Changed in eucalyptus (Ubuntu Lucid): | |
| milestone: | none → lucid-alpha-3 |
| Changed in eucalyptus (Ubuntu Lucid): | |
| assignee: | nobody → Thierry Carrez (ttx) |
| status: | Triaged → In Progress |
| Changed in eucalyptus (Ubuntu Lucid): | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in eucalyptus (Ubuntu Lucid): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
On Thu, Jan 28, 2010 at 11:26:16AM -0000, Thierry Carrez wrote:
> Public bug reported:
>
> On package installs, authorized_keys must be manually set on components.
> There is no point in starting publication jobs if the the component is not ready to be autoregistered.
>
> Two options:
> - Fail the publication job is authorized_keys is missing (requires the user to manually start the publication job after keys are setup)
> - Poll for authorized_keys presence in the upstart script (slightly heavier on resource usage)
>
Another option:
* fire off an upstart event when the authorized_keys file is installed on the
system (inotify?). The eucalytpus-nc job would also have to check for the
authorized_keys file and fire off the same upstart event to handle an
environment where authorized_keys has already been installed.
--
Mathias Gug
Ubuntu Developer http://