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

Remove require: user: servo #874

Closed
wants to merge 1 commit into from
Closed

Conversation

@Manishearth
Copy link
Member

Manishearth commented Aug 9, 2018

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)

r? @aneeshusa

cc @jdm


This change is Reviewable

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)
@aneeshusa
Copy link
Member

aneeshusa commented Aug 15, 2018

When is it the case/what command are you using to get that error message? Trying to set ownership to servo/servo won't work very well without a servo user, and the current buildbot master Salt code sets everything up to run under the servo user, so I'd rather make sure the user bits are included when needed and/or point to a better command.

@Manishearth
Copy link
Member Author

Manishearth commented Aug 15, 2018

Any highstate on servo-master.

require:
  user: servo

does not require there to be a user named servo, it requires there to be a state named servo with a user.present in it.

We depend on a servo user existing all over the place without doing this.

We could add a servo state somewhere if necessary.

@aneeshusa
Copy link
Member

aneeshusa commented Aug 25, 2018

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 common (example) and b) ideally the relevant states depend on the state that sets up the user (example).

@Manishearth
Copy link
Member Author

Manishearth commented Aug 26, 2018

Ah, that explains why it's somewhat intermittent, it depends on the order.

Opened #883 to fix this.

@Manishearth Manishearth deleted the Manishearth:user-present branch Aug 26, 2018
bors-servo added a commit that referenced this pull request Aug 26, 2018
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 -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.