Comment 4 for bug 1408193
Revision history for this message
| Armando Migliaccio (armando-migliaccio) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Are you trying some sort of 'fail-over' action? Changing the device id on a router port does not sound like the right thing to do, as you may need other events to occur in the system to move from one router to another. To me the fact that this was 'working' in Icehouse leads to me believe that it was failing silently rather than working as you say. Ultimately I think we should prevent such a port update from occurring.
Marking incomplete, as I would like to understand more about the use case being addressed.