Plugin lifecycle order should be correct
Bug #1648326 reported by
janonymous
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kuryr-libnetwork |
Confirmed
|
Low
|
janonymous | ||
Bug Description
According to Docker Plugin Documentation:
Reference:
https:/
Plugins should be started before Docker, and stopped after Docker.
But in Devstack i think kuryr server starts after docker and is stopped before docker stop.
| Changed in kuryr-libnetwork: | |
| assignee: | nobody → janonymous (janonymous) |
Revision history for this message
| Antoni Segura Puimedon (celebdor) wrote | #1 |
| Changed in kuryr-libnetwork: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
To post a comment you must log in.
IIRC this works because the plugins are lazy loaded. As long as there is the plugin descriptor, the call to register is not done until the first usage, that is why it works.