Hi all,
I wish to update the bodhi-server package on bodhi01/02 servers with the latest package that I deployed to the releng machines weeks ago. All it'll take is this command:
sudo -i ansible-playbook --extra-vars="target='bodhi' package='bodhi-server'" $(pwd)/update_packages.yml
At the moment people that *only* have commit privs on the epel7 branch are unable to push updates. Upgrading bodhi to the version that is already in our infra repo should resolve this issue, and it'll be easy to downgrade if unexpected explosions occur.
Thanks,
luke
On Tue, Sep 23, 2014 at 12:56:59PM -0600, Luke Macken wrote:
Hi all,
I wish to update the bodhi-server package on bodhi01/02 servers with the latest package that I deployed to the releng machines weeks ago. All it'll take is this command:
sudo -i ansible-playbook --extra-vars="target='bodhi' package='bodhi-server'" $(pwd)/update_packages.yml
At the moment people that *only* have commit privs on the epel7 branch are unable to push updates. Upgrading bodhi to the version that is already in our infra repo should resolve this issue, and it'll be easy to downgrade if unexpected explosions occur.
I suspect it will require as well a: sudo -i ansible bodhi -m shell -a "service httpd restart"
But +1 for me anyhow.
Pierre
On Tue, 23 Sep 2014 12:56:59 -0600 Luke Macken lmacken@redhat.com wrote:
Hi all,
I wish to update the bodhi-server package on bodhi01/02 servers with the latest package that I deployed to the releng machines weeks ago. All it'll take is this command:
sudo -i ansible-playbook --extra-vars="target='bodhi' package='bodhi-server'" $(pwd)/update_packages.yml
At the moment people that *only* have commit privs on the epel7 branch are unable to push updates. Upgrading bodhi to the version that is already in our infra repo should resolve this issue, and it'll be easy to downgrade if unexpected explosions occur.
+1
we have already pushed out the post alpha chud, so I don't see any problems with doing this now.
kevin
infrastructure@lists.fedoraproject.org