Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upRemove require: user: servo #874
Conversation
This only works if we have a `servo: user.present` state somewhere; but
we don't, so we get the following error:
```
Comment: The following requisites were not found:
require:
user: servo
```
We assume the user exists elsewhere anyway, though perhaps we could add
the user.present in case (but when i tried i wasn't able to make that
work)
|
When is it the case/what command are you using to get that error message? Trying to set ownership to |
|
Any highstate on servo-master.
does not require there to be a user named We depend on a servo user existing all over the place without doing this. We could add a servo state somewhere if necessary. |
|
I took a look and the issue is that none of the sls files that the master is using which depend on the servo user are pulling in the common.sls file. The better fix here is to make progress on #496 and make sure the states using the servo user - either for ownership or its home directory - a) have an include for |
|
Ah, that explains why it's somewhat intermittent, it depends on the order. Opened #883 to fix this. |
Add include: common to everything needing user: servo Fixes intermittent "The following requisites were not found: `user: servo`" in buildbot states See #874 (comment) r? @jdm <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/saltfs/883) <!-- Reviewable:end -->
Manishearth commentedAug 9, 2018
•
edited by larsbergstrom
This only works if we have a
servo: user.presentstate somewhere; butwe don't, so we get the following error:
We assume the user exists elsewhere anyway, though perhaps we could add
the user.present in case (but when i tried i wasn't able to make that
work)
r? @aneeshusa
cc @jdm
This change is