Apparently our unix users are not created on the kinto stage instances. Could you please add them for the stage instances so that we can debug the migration problem? Can you give access to the following users? - tarek - alexis - mleplatre - rhubscher Here are some examples or puppet-config that were adding them to previous projects: - https://github.com/mozilla-services/puppet-config/blob/master/users/yaml/users/app/readinglist.stage.yaml - https://github.com/mozilla-services/puppet-config/blob/master/users/yaml/users/app/loop_server.stage.yaml - https://github.com/mozilla-services/puppet-config/blob/master/users/yaml/users/app/syncto.stage.yaml - https://github.com/mozilla-services/puppet-config/blob/master/msisdn/yaml/app/msisdn_gateway.stage.yaml Many thanks.
Assignee: nobody → dmaher
Depends on: 1095374
Hello, Unfortunately the user "mleplatre" doesn't exist anywhere in the Puppet repo, so adding him isn't as easy as the other users; I'll go ahead and prepare a PR with the other users just to get that started, and then move on to mleplatre afterwards.
Status: NEW → ASSIGNED
(In reply to Daniel Maher [:phrawzty] from comment #2) > https://github.com/mozilla-services/puppet-config/pull/1866 PR merged. I'm looking into how to best propagate these changes, however.
Thanks @phrawzty. I think you should be good by just spawning a new stack.
(In reply to Rémy Hubscher (:natim) from comment #4) > Thanks @phrawzty. I think you should be good by just spawning a new stack. That's true in the general case, which is to say, the target Kinto machines; however, the bastion server doesn't yet have mleplatre, so it will need to be treated separately (we don't re-roll those nodes unless we have to).
The Stage bastion has been updated, which is all that's required (or desirable) for now anyway. Closing ticket.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.