-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SUSE systemd unit missing appropriate stop, post-stop directives #182
Comments
We've got the stop and post-stop here: https://github.com/aws/amazon-ecs-init/blob/master/packaging/amazon-linux-ami/ecs.service#L29-L30 I'll start by manually adding them to SUSE (the link above) then testing the service manually in an instance of the SUSE AMI (testing on |
@fierlion not sure what's meant with these links, I think there's still differences present here though I'm somewhat removed from on going work in |
Sorry. See updates to my comment above. |
Okay, I got it 👍 So the real outstanding task here is to actually go and test it before we commit that change (which I think was the reason why I deferred the effort to an issue long, long ago..), is that right? |
https://build.opensuse.org/package/show/openSUSE:Factory/amazon-ecs-init appears to be the place where the OpenSUSE build is produced. @rjschwei is the maintainer who had been helping us package ecs-init for that distro. |
that's right. I'll update here with my manual test results on SUSE. |
#285 |
https://build.opensuse.org/package/show/openSUSE:Factory/amazon-ecs-init is the derived package for release with openSUSE Tumbleweed which will eventually make it's way into openSUSE Leap and SLE. Development of the package happens here: https://build.opensuse.org/package/show/Cloud:Tools/amazon-ecs-init |
Merged. I'll open a follow-up issue to work through the |
Summary
The SUSE systemd unit is missing the directives now present and accounted for in the AL2 systemd unit.
The text was updated successfully, but these errors were encountered: