canmove, Confirmed users
2,850
edits
ReleaseEngineering/OPSI: Difference between revisions
no edit summary
No edit summary |
ChrisCooper (talk | contribs) No edit summary |
||
| Line 157: | Line 157: | ||
Your package should now show up in the OPSI Config Editor. Make sure to set staging slaves to install/update the package as well as production ones. | Your package should now show up in the OPSI Config Editor. Make sure to set staging slaves to install/update the package as well as production ones. | ||
== | == Troubleshooting == | ||
=== error: HTTP/1.1 401 Unauthorized === | === error: HTTP/1.1 401 Unauthorized === | ||
This error appears before logging in. I believe you can only stop "the installation" and be able to access the machine. | This error appears before logging in. I believe you can only stop "the installation" and be able to access the machine. | ||
| Line 166: | Line 166: | ||
[[File:OPSI_Pre-login_loader_error.png|300px|thumb|center|error: HTTP/1.1 401 Unauthorized]] | [[File:OPSI_Pre-login_loader_error.png|300px|thumb|center|error: HTTP/1.1 401 Unauthorized]] | ||
=== How to update the opt_pcbin drive mapping password === | |||
'''NOTE:''' this has never been tested. | |||
In {{bug|519989}}, we did some preliminary investigation into how we might go about updating the password used for mounting the OPSI shared package drive in case we happen to expose it: | |||
# Arrange for a long downtime. Depending about how comfortable you are about burning builds in progress, you'll likely need between 3-6 hours. | |||
# Shutdown, possibly gracefully, any affected buildbot masters. | |||
# Push out an OPSI product that changes the password but leaves the pcpatch user password as it is (for now) | |||
# Reboot the clients, and during their OPSI check-in the change is made. The change is made after the mount is authenticated, so they *should* be fine this time around. | |||
# After all the clients have the new package (as verified through the OPSI dashboard), change the pcpatch user password on the server. Future reboots will work with the new password. | |||
# Reboot the clients again to make sure they can connect. | |||
Further background can be found in {{bug|519989}}. | |||
== Documentation/Links == | == Documentation/Links == | ||