libbe_py should export global_active boot environment property
After integration of #3845 new boot environment property was introduced - BE_ATTR_GLOBAL_ACTIVE. Now, to determine which BE would be active in zone after reboot we should check for active_boot && global_active. However, python libbe_py consumers don't know about it. This leads to situation when IPS can mistakenly consider active_boot and not global_active zone BE be the next active one. Both IPS and libbe_py should be fixed.
Updated by Electric Monk almost 7 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
commit a74909fd1b8a12f99797bbadb7a8af8bdca8596c Author: Alexander Pyhalov <firstname.lastname@example.org> Date: 2014-12-15T21:01:53.000Z 5435 libbe_py should export global_active boot environment property Reviewed by: Josef 'Jeff' Sipek <email@example.com> Reviewed by: Andy Stormont <firstname.lastname@example.org> Reviewed by: Igor Kozhukhov <email@example.com> Reviewed by: Alexander Eremin <firstname.lastname@example.org> Approved by: Dan McDonald <email@example.com>