Skip to content
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

Closed
jahkeup opened this issue Jul 5, 2018 · 10 comments
Closed

SUSE systemd unit missing appropriate stop, post-stop directives #182

jahkeup opened this issue Jul 5, 2018 · 10 comments

Comments

@jahkeup
Copy link
Member

jahkeup commented Jul 5, 2018

Summary

The SUSE systemd unit is missing the directives now present and accounted for in the AL2 systemd unit.

@fierlion
Copy link
Member

fierlion commented Jan 8, 2020

@fierlion
Copy link
Member

fierlion commented Jan 8, 2020

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 SUSE Linux Enterprise Server 12 SP4 (HVM), SSD Volume Type and SUSE Linux Enterprise Server 15 SP1 (HVM), SSD Volume Type in us-west-2) Hoping the service will just work. If not, we'll learn what else needs to happen.

@jahkeup
Copy link
Member Author

jahkeup commented Jan 9, 2020

@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 ecs-init at this point. From a quick glance, I do see that we're not calling the same subcommands that we're calling and using in AL2 (which was what this issue was opened to address). We should test/get-confirmations that the service works correctly and behaves similarly on OpenSUSE as it does in AL2.

@fierlion
Copy link
Member

fierlion commented Jan 9, 2020

Sorry. See updates to my comment above.

@jahkeup
Copy link
Member Author

jahkeup commented Jan 9, 2020

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?

@samuelkarp
Copy link
Contributor

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.

@fierlion
Copy link
Member

fierlion commented Jan 9, 2020

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?

that's right. I'll update here with my manual test results on SUSE.

@fierlion
Copy link
Member

fierlion commented Jan 10, 2020

#285
see the above for detail on my testing done

@rjschwei
Copy link
Contributor

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

@fierlion
Copy link
Member

Merged. I'll open a follow-up issue to work through the make rpm target and the suse spec file. make rpm is pinned to amazon-linux and the suse spec file hasn't been updated in a while and requires attention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants