| Clark[m] | I think the zuul restarts may have stalled on zm02. I can't take a look tonight, but will see if I have time tomorrow | 02:56 |
|---|---|---|
| frickler | clarkb: seems some conflict with apt update happening in the background. guess we could just restart the playbook? | 08:39 |
| frickler | not sure who is reading here, but how can I update the second and third email on https://www.openstack.org/profile/? those values don't seem to get copied from the openinfraid profile | 08:40 |
| fungi | frickler: you should be able to update them at https://openinfra.dev/a/profile and that's supposed to replicate to https://www.openstack.org/profile/ but if it's not working i can reach out to the webdev contractors who maintain that | 15:15 |
| clarkb | yup I just forwarded the question on to the people who maintain all that | 15:18 |
| clarkb | re zm02 it looks like there was a conflict between unattended upgrades and our playbook grabbing the apt lock on zm02 | 15:18 |
| clarkb | the playbook errored at that point and stopped running. I'll start a root screen on bridge and restart the playbook | 15:19 |
| opendevreview | Clark Boylan proposed opendev/system-config master: Append zuul reboot logs instead of truncating them https://review.opendev.org/c/opendev/system-config/+/855826 | 15:33 |
| clarkb | Note I modified the command to append in the screen so the current manual run is appending. That change just helps ensure we continue to append for manual intervention in the future | 15:34 |
| fungi | frickler: for the record, i confirmed that adding a new address to https://id.openinfra.dev/accounts/user/profile immediately also showed up in https://openinfra.dev/a/profile but has not (yet at least) appeared at the older https://www.openstack.org/profile/ interface | 15:37 |
| fungi | adding through https://openinfra.dev/a/profile also seems to immediately update https://id.openinfra.dev/accounts/user/profile so those seem to probably be sharing a common backend data set | 15:39 |
| clarkb | The current playbook will hopefully get through things quickly since it appears quiet on the zuul dashboard. I'll have to think about ways to handle the apt lock conflict. Maybe waiting up to 20 minutes or something for the apt lock to be released | 15:40 |
| fungi | frickler: i vaguely recall updating the published profile is blocked by a verification e-mail process, so it's possible the verification message wasn't sent, or got caught up in a spam filter | 16:17 |
| fungi | not sure when we'll hear from the webdev folks since it's a holiday weekend in the usa | 16:18 |
| fungi | sounds like second and third addresses don't to any verification e-mails, only setting or changing the first address field does that | 17:52 |
| clarkb | it occured to me that the graceful shutdown process relies on docker exec which I think relies on actually having a container running. I've manually run docker-compose up -d on zm02 to prevent the current playbook run from failing there due to no running container | 22:42 |
| clarkb | so two things to handle. Graceful shutdown when services are already down and apt tasks colliding with unattended-upgrades | 22:43 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!