This may be a leftover vestige of bug 1065589, or a dup of
460925 - it depends on whether the upstart job is being started
in the container - which seems unlikely as other upstart messages
do end up in the container - or on the host, due to a udev misfire.
The latter seems more likely.
The message says:
ifdown: interface veth9HRJRD not configured
Is there something we can do about this in ifupdown? Why should it
bother to spit this out?
This may be a leftover vestige of bug 1065589, or a dup of
460925 - it depends on whether the upstart job is being started
in the container - which seems unlikely as other upstart messages
do end up in the container - or on the host, due to a udev misfire.
The latter seems more likely.
The message says:
ifdown: interface veth9HRJRD not configured
Is there something we can do about this in ifupdown? Why should it
bother to spit this out?
importance: low
status: confirmed