What you are missing is the fact that Devstack was not created for rebooting. It was written for testing OpenStack code in small clouds that can be set up quickly, then removed. It is not completely started up when you reboot the server.

In my experience (which doesn't include ODL), after a restart the network bridge has no IP address and is DOWN, and the loop devices for Cinder and Swift are not set up. You would have to correct that first, then restart Swift and Cinder. However I don't know if there are other complications due to ODL.

FYI the script I use to complete a restart of Devstack.

echo reviving network
sudo ip a add 172.24.4.1/24 dev br-ex
sudo ip l set dev br-ex up

echo setting up physical volumes for Cinder
sudo losetup -f --show /opt/stack/data/stack-volumes-default-backing-file
sudo losetup -f --show /opt/stack/data/stack-volumes-lvmdriver-1-backing-file

echo mounting Swift FS and restarting Swift
sudo mount -t xfs -o loop,noatime,nodiratime,nobarrier,logbufs=8 /opt/stack/data/swift/drives/images/swift.img /opt/stack/data/swift/drives/sdb1
sudo systemctl restart devstack@s-*
sudo systemctl status devstack@s-* --no-pager

echo restarting Cinder
sudo systemctl restart devstack@c-*

Your IP address, interface name and path names may vary.