Fix: Set correct user for service and cli

[ngetahun]

Description

RMT server service uses non-root user which causes access permissions issues. This PR fixes this issue.

Fixes bsc#1215176

Change Type

Please select the correct option.

• [x] Bug Fix (a non-breaking change which fixes an issue)
• [ ] New Feature (a non-breaking change which adds new functionality)
• [ ] Documentation Update (a change which only updates documentation)

Checklist

Please check off each item if the requirement is met.

• [x] I have verified that my code follows RMT's coding standards with rubocop.
• [x] I have reviewed my own code and believe that it's ready for an external review.
• [x] I have provided comments for any hard-to-understand code.
• [ ] I have documented the MANUAL.md file with any changes to the user experience.
• [x] RMT's test coverage remains at 100%.
• [x] If my changes are non-trivial, I have added a changelog entry to notify users at package/obs/rmt-server.changes.

Other Notes

Please use this space to provide notes or thoughts to the team, such as tips on how to review/demo your changes.

How to test

Pre-requisite: Setup a vm with nginx and ssl for client script setup. Also, please mirror the client system product on your test rmt.

1. Pull the rmt-client-setup on your client system:

curl <ip>/tools/rmt/client/setup

2. Register your client:

./rmt-client-setup https://<ip>

This should work without any issue,

[ngetahun]

Fix: RMT server install creates secrets.yml.key with root owner

[ngetahun]

@jsegitz Please review the new changes. I have incorporated your suggestions.

[jsegitz]

I think it's fine now

[suse-tests-pass]

Well Done! Your tests are still passing. https://ci.suse.de/job/scc-RMT-integration-tests/346622/console If the given link has expired,you can force a Prophet rerun by just deleting this comment. (Merged d4d748562ea13b0c5e8cb236633fd0ad088f9cc9 into f8da43c2e93aaa039461449d7c4b90128c33405b)