pserv doesn't listen to interfaces that come up after pserv get started

Bug #1274570 reported by Adam Collard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Triaged
High
Unassigned

Bug Description

We had to use a workaround of writing a maas-pserv.override containing http://paste.ubuntu.com/6844470/

This is because the bridge interface came up after maas-pserv was started and didn't listen on the new interface.

Raphaël Badin (rvb)
summary: - pserv should do dynamic rebinding so it listens on interfaces
+ pserv doesn't listen to interfaces that come up after pserv get started
Changed in maas:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Julian Edwards (julian-edwards) wrote :

This might be a dupe of an existing bug.

Changed in maas:
milestone: none → 14.04
tags: added: provisioning
Revision history for this message
James Page (james-page) wrote :

Maybe use an upstart configuration that restarts pserv whenever a restart event occurs - reload would be better

Revision history for this message
Gavin Panella (allenap) wrote :

pserv should thus handle HUP or some other signal.

Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 1274570] Re: pserv doesn't listen to interfaces that come up after pserv get started

On Monday 03 Feb 2014 08:12:32 you wrote:
> pserv should thus handle HUP or some other signal.

Can pserv detect new interfaces itself I wonder...

Revision history for this message
Gavin Panella (allenap) wrote :

> Can pserv detect new interfaces itself I wonder...

It could, by periodically checking. However, this is something that Upstart does natively, and notices as soon as it happens. An Upstart job to detect a change in NICs and reload the pserv job (which sends a HUP) would be simple and very effective I think.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

On Tuesday 04 Feb 2014 05:02:53 you wrote:
> > Can pserv detect new interfaces itself I wonder...
>
> It could, by periodically checking. However, this is something that
> Upstart does natively, and notices as soon as it happens. An Upstart job
> to detect a change in NICs and reload the pserv job (which sends a HUP)
> would be simple and very effective I think.

That's true, but I was trying to avoid more dependency on packaging for the
correct operation of MAAS itself.

Revision history for this message
Gavin Panella (allenap) wrote :

> That's true, but I was trying to avoid more dependency on packaging for the
> correct operation of MAAS itself.

Fair point.

I think we can build a better product overall by absorbing more of the packaging assets into upstream MAAS. It would blur the division between upstream and Ubuntu, but things like detecting changes to NICs is fairly platform-specific, and MAAS upstream is meant for Ubuntu anyway.

Put another way, we, as upstream maintainers, should take more responsibility for the end-user's experience by reducing the delta between upstream MAAS and installed MAAS.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

On Tuesday 04 Feb 2014 07:07:44 you wrote:
> Put another way, we, as upstream maintainers, should take more
> responsibility for the end-user's experience by reducing the delta
> between upstream MAAS and installed MAAS.

Totally +1

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.