CLOUDSTACK-10178: Hotfixes to make 4.10 work#2320
Conversation
Load br_netfilter in security_group management script.
exists in the system and should be loaded.
| Documentation=http://www.cloudstack.org/ | ||
| Requires=libvirtd.service | ||
| After=libvirtd.service | ||
| Requires=libvirt-bin.service |
There was a problem hiding this comment.
@bwsw remove these, during packaging for debian/ubuntu the services file is fixed using sed. The libvirtd name for centos 6,7 and most other distros is libvirtd, while it's libvirt-bin for debian and derivatives.
There was a problem hiding this comment.
I went ahead and fixed this to enable packaging+testing on this PR.
There was a problem hiding this comment.
Great to hear, I'm not able to code until the next week.
| else: | ||
| execute('iptables -I ' + vmchain + ' -p icmp --icmp-type ' + range + ' ' + direction + ' ' + ip + ' -j ' + action) | ||
| except: | ||
| pass |
There was a problem hiding this comment.
Should we log a warning or error be logged when an exception is hit?
There was a problem hiding this comment.
@rhtyd I believe the code should be improved before inclusion to master, but I believe it should be done in management server side, because agent is too far from API to do it correctly. But warning is probably a good thing. I don't remember why excluded, but probably because 'execute' includes debug.
There was a problem hiding this comment.
Basically, these try except for icmpv6, because (-1, -1) doesn't handled right for icmpv6.
|
@blueorangutan package |
…ases Also, removed @Local annotation that is not needed
Depending on the timezone you're running CS (before GMT timezones) you could experience that some jobs are marked as failed since the parent job got a null result despite its child job having successfully done the job. The child job got deleted by the CleanupTask ahead of time, due to a missing datetime conversion to GMT timezone. Jobs are failing with this message: Job failed with un-handled exception The fix intends to correct any datetime used in the code that should be using the GMT timezone instead of the local one since all DB datetime should be stored at GMT. Conflicts: server/src/com/cloud/test/DatabaseConfig.java
Depending on the timezone you're running CS (before GMT timezones) you could experience that some jobs are marked as failed since the parent job got a null result despite its child job having successfully done the job. The child job got deleted by the CleanupTask ahead of time, due to a missing datetime conversion to GMT timezone. Jobs are failing with this message: Job failed with un-handled exception The fix intends to correct any datetime used in the code that should be using the GMT timezone instead of the local one since all DB datetime should be stored at GMT. Conflicts: server/src/com/cloud/test/DatabaseConfig.java
|
Thanks for the PR @bwsw. Can you please create a JIRA ticket for this PR and append the ticket id with PR name?
Additionally, the description Such documentation helps us keeping track of issues and PRs; thus, we can detect what is already being handled. For instance, PR #2355 (avoid sending a null IPv6 address to Security Group Python script) tackles a problem already handled by this PR. |
|
@GabrielBrascher updated. Please, take a look. |
|
Thanks, @bwsw. |
|
@blueorangutan package |
|
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1409 |
|
@blueorangutan test |
|
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-1824)
|
|
@bwsw I see most of these commits are already in master, do you want to squash your commits and if there are no new changes/commits for master we can merge using |
|
@wido @GabrielBrascher (and others) are you lgtm on this? My only issue with the change is that it's suppressing exceptions with an |
|
Any update on this, ping? |
|
@rhtyd @wido @GabrielBrascher |
|
Sure thanks @bwsw |
This PR implements several fixes which are vital for CS 4.10 to work: