| Summary: | Bring up task should test user accounts | ||
|---|---|---|---|
| Product: | [Infrastructure] AutoBuilder | Reporter: | Armin Kuster <akuster> |
| Component: | autobuilder | Assignee: | Michael Halstead <mhalstead> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | akuster808, infras.ab.watcher, Infras.watcher, pidge, richard.purdie, ross.burton |
| Version: | unspecified | ||
| Target Milestone: | 3.3 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Armin Kuster
2019-09-19 19:53:33 UTC
Only Richard and Ross's accounts were configured to be automatically added to new workers. I've changed configuration so Armin's will be added as well. Is there a larger list of users who should be added to every new worker? (In reply to comment #1) > Only Richard and Ross's accounts were configured to be automatically added > to new workers. I've changed configuration so Armin's will be added as well. > Is there a larger list of users who should be added to every new worker? I was not suggesting I get added automatically, that is not my call. I was more for being consistent across all workers with what ever policy folks think is reasonable. Is there someway of flagging things as not being the same so appropriate action can take place. I don't care if the AB "bring up" was the correct place so some other worker setup scrips you might be using. that was the intent of this bug. How do can we make your life easier? sorry, Neither Richard or Ross being cc'.d I don't know of a good way to test accounts automatically. They are now being added. Would sending an e-mail to all account holders asking them to login to any new workers be an acceptable solution? I am fine that when this fails, IT is notified. |