You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by "btzq (via GitHub)" <gi...@apache.org> on 2025/05/31 12:19:18 UTC
[D] VR suddenly was created with DHCP Service Failing. Can we Implement an auto-recovery? [cloudstack]
GitHub user btzq created a discussion: VR suddenly was created with DHCP Service Failing. Can we Implement an auto-recovery?
### problem
One of our users created a VPC and was complaining about how they were not able to get a private IP.
When we checked, turns out dhcp service was down. This surprised us because usually the VR is created without issues, and suddenly this happens.
Attached screenshot below:
Questions:
- Why is it that suddenly a service fails when a new VR is created, when we usually dont have issues with VR creation all this while?
- When VR detects a service is down, can it also restart that specific service in the VR without having to reboot or cleanup the VR? This would be more automatic and less downtime/issues.
### versions
Cloudstack Version: 4.19.1.1
Storage: Linstor DRBD
Architecture: Disaggregated
Hypervisor: Ubuntu
### The steps to reproduce the bug
Cant give a step. Just happens randomly when a new VPC is created.
### What to do about it?
When VR detects a service is down, auto estart that specific service in the VR without having to reboot or cleanup the VR? This would be more automatic and less downtime/issues.
GitHub link: https://github.com/apache/cloudstack/discussions/10938
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] VR suddenly was created with DHCP Service Failing. Can we Implement an auto-recovery? [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
GitHub user DaanHoogland added a comment to the discussion: VR suddenly was created with DHCP Service Failing. Can we Implement an auto-recovery?
@btzq A monitorring service could catch that event and issue a restart with cleanup command. I don’t think you need this implemented in cloudstack, do you?
GitHub link: https://github.com/apache/cloudstack/discussions/10938#discussioncomment-13640111
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] VR suddenly was created with DHCP Service Failing. Can we Implement an auto-recovery? [cloudstack]
Posted by "btzq (via GitHub)" <gi...@apache.org>.
GitHub user btzq closed a discussion: VR suddenly was created with DHCP Service Failing. Can we Implement an auto-recovery?
### problem
One of our users created a VPC and was complaining about how they were not able to get a private IP.
When we checked, turns out dhcp service was down. This surprised us because usually the VR is created without issues, and suddenly this happens.
Attached screenshot below:
Questions:
- Why is it that suddenly a service fails when a new VR is created, when we usually dont have issues with VR creation all this while?
- When VR detects a service is down, can it also restart that specific service in the VR without having to reboot or cleanup the VR? This would be more automatic and less downtime/issues.
### versions
Cloudstack Version: 4.19.1.1
Storage: Linstor DRBD
Architecture: Disaggregated
Hypervisor: Ubuntu
### The steps to reproduce the bug
Cant give a step. Just happens randomly when a new VPC is created.
### What to do about it?
When VR detects a service is down, auto estart that specific service in the VR without having to reboot or cleanup the VR? This would be more automatic and less downtime/issues.
GitHub link: https://github.com/apache/cloudstack/discussions/10938
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org