Actions
Feature #27060
closedAdd configurable delay after before response is returned
Difficulty:
easy
Triaged:
Yes
Description
Some backend engines (e.g. Infoblox DHCP) takes 1-2 minutes to apply the changes which leads to boot errors of VMs orchestrated by Foreman. New setting "Launch VM Wait Time" should solve this easily.
Updated by The Foreman Bot almost 5 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/6846 added
Updated by Lukas Zapletal almost 5 years ago
- Project changed from Foreman to Infoblox
- Subject changed from Add configurable delay before a VM is launched to Add configurable delay after before response is returned
- Category changed from Compute resources to DHCP plugin
- Status changed from Ready For Testing to Assigned
Updated by Lukas Zapletal almost 5 years ago
- Pull request deleted (
https://github.com/theforeman/foreman/pull/6846)
Updated by Lukas Zapletal almost 5 years ago
- Pull request https://github.com/theforeman/smart_proxy_dhcp_infoblox/pull/45 added
Updated by Lukas Zapletal almost 5 years ago
- Status changed from Assigned to Resolved
Updated by The Foreman Bot almost 5 years ago
- Pull request https://github.com/theforeman/smart_proxy_dhcp_infoblox/pull/46 added
Updated by Lukas Zapletal over 4 years ago
- Pull request deleted (
https://github.com/theforeman/smart_proxy_dhcp_infoblox/pull/46)
Updated by The Foreman Bot over 4 years ago
- Pull request https://github.com/theforeman/smart_proxy_dhcp_infoblox/pull/46 added
Actions