A developer noticed that the push to batched/stable buttons are appearing before 7 days are reached. It turns out that httpd hasn't been restarted on bodhi03 since 2017-10-24 (I didn't check 04), which means it hasn't picked up the changes made to the release policy[0] for when f27 went post-beta. This means that all F27 updates are only being required to be in testing for 3 days. Can I get an FBR to run this on bodhi03 and bodhi04?
$ sudo systemctl restart httpd
[0] https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/roles/bodhi...
On 11/14/2017 09:36 PM, Randy Barlow wrote:
A developer noticed that the push to batched/stable buttons are appearing before 7 days are reached. It turns out that httpd hasn't been restarted on bodhi03 since 2017-10-24 (I didn't check 04), which means it hasn't picked up the changes made to the release policy[0] for when f27 went post-beta. This means that all F27 updates are only being required to be in testing for 3 days. Can I get an FBR to run this on bodhi03 and bodhi04?
$ sudo systemctl restart httpd
We are out of freeze now, go for it!
kevin
On 11/15/2017 12:00 PM, Kevin Fenzi wrote:
We are out of freeze now, go for it!
So let it be written, so let it be done.
After restarting httpd the issue still seemed to be present. It was then that I realized that the playbook had never been run to send the changes to production.ini out to the frontend servers. I applied the changes by hand (since the playbook can't be run while the mash is running). The issue is resolved now.
infrastructure@lists.fedoraproject.org