1302373 - Upgrade hg version to 3.9.1 on Linux build and test machines

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Comment 1

[Alin Selagea [:aselagea]]

Attachment: bug1302373_ubuntu_update_hg.patch

Tested on both tst-linux32-spot and tst-linux64-spot instances, it managed to deploy the new hg version without issues.

Comment 2

[Alin Selagea [:aselagea]]

Attachment: bug1302373_centos_update_hg.patch

I also tested this patch on a dev-linux64-spot instance, unfortunately it failed to upgrade the hg version due to some failed dependencies.

Error: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install mozilla-python27-mercurial-3.9.1-1.el6' returned 1: Error: Nothing to do
Wrapped exception:
Execution of '/usr/bin/yum -d 0 -e 0 -y install mozilla-python27-mercurial-3.9.1-1.el6' returned 1: Error: Nothing to do
Error: /Stage[main]/Packages::Mozilla::Py27_mercurial/Package[mozilla-python27-mercurial]/ensure: change from 3.7.3-1.el6 to 3.9.1-1.el6 failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install mozilla-python27-mercurial-3.9.1-1.el6' returned 1: Error: Nothing to do

Comment 3

[Justin Wood (:Callek)]

(In reply to Alin Selagea [:aselagea][:buildduty] from comment #2)
> Created attachment 8791214 [details] [diff] [review]
> bug1302373_centos_update_hg.patch
> 
> I also tested this patch on a dev-linux64-spot instance, unfortunately it
> failed to upgrade the hg version due to some failed dependencies.
> 
> Error: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install
> mozilla-python27-mercurial-3.9.1-1.el6' returned 1: Error: Nothing to do
> Wrapped exception:
> Execution of '/usr/bin/yum -d 0 -e 0 -y install
> mozilla-python27-mercurial-3.9.1-1.el6' returned 1: Error: Nothing to do
> Error:
> /Stage[main]/Packages::Mozilla::Py27_mercurial/Package[mozilla-python27-
> mercurial]/ensure: change from 3.7.3-1.el6 to 3.9.1-1.el6 failed: Could not
> update: Execution of '/usr/bin/yum -d 0 -e 0 -y install
> mozilla-python27-mercurial-3.9.1-1.el6' returned 1: Error: Nothing to do

ooo huh, no idea why :'(

Comment 4

[Alin Selagea [:aselagea]]

I've been debugging this for some time (even recreated the rpms) but had little luck, so I'd need some help here. Here's a snippet of the error when running puppet agent in verbose mode:

Debug: /Stage[main]/Puppet::Atboot/File[/etc/puppet/puppetmasters.txt]: The container Class[Puppet::Atboot] will propagate my refresh event
Debug: Executing '/sbin/service ntpd status'
Debug: Executing '/sbin/chkconfig ntpd'
Debug: Executing '/sbin/service yum-updatesd status'
Debug: Executing '/sbin/chkconfig yum-updatesd'
Debug: Executing '/sbin/service rsyslog status'
Debug: Executing '/sbin/chkconfig rsyslog'
Debug: Executing '/usr/bin/yum -d 0 -e 0 -y list mozilla-python27-mercurial'
Debug: Package[mozilla-python27-mercurial](provider=yum): Ensuring => 3.9.1-1.el6
Debug: Executing '/bin/rpm -q mozilla-python27-mercurial --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'
Debug: Executing '/usr/bin/yum -d 0 -e 0 -y install mozilla-python27-mercurial-3.9.1-1.el6'
Error: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install mozilla-python27-mercurial-3.9.1-1.el6' returned 1: Error: Nothing to do
Wrapped exception:
Execution of '/usr/bin/yum -d 0 -e 0 -y install mozilla-python27-mercurial-3.9.1-1.el6' returned 1: Error: Nothing to do
Error: /Stage[main]/Packages::Mozilla::Py27_mercurial/Package[mozilla-python27-mercurial]/ensure: change from 3.7.3-1.el6 to 3.9.1-1.el6 failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install mozilla-python27-mercurial-3.9.1-1.el6' returned 1: Error: Nothing to do


The machine I'm using for testing is "dev-linux64-ec2-aselagea". 
@Jake: when you have some time, could you please take a look?

Comment 5

[Amy Rich [:arr] [:arich]]

The cert expires on the 28th. We were going to try switching it on the 21st, but it's unlikely that gives us enough time to do an hg upgrade on windows testers. Instead, we're going to switch the cert on the 26th. If hg is not upgraded by that time, we will need to take a downtime to upgrade the hg configuration to change the hash for the pinned certs.

Comment 6

[Amy Rich [:arr] [:arich]]

It looks like you skipped the step where you update the repodata once you add new packages:

https://wiki.mozilla.org/ReleaseEngineering/PuppetAgain/Packages#CentOS:_Building_Custom_Packages

I did that and waited for the mirrors to sync up, then ran the following on dev-linux64-ec2-aselagea.dev.releng.use1.mozilla.com

puppet agent --test -v --no-splay --server releng-puppet2.srv.releng.scl3.mozilla.com --environment=aselagea

That finished without error.

Comment 7

[Alin Selagea [:aselagea]]

Thanks! It works fine now.

Comment 8

[Alin Selagea [:aselagea]]

http://hg.mozilla.org/build/puppet/rev/87f94cfdaad4
http://hg.mozilla.org/build/puppet/rev/a70fd70192e0

Comment 9

[Amy Rich [:arr] [:arich]]

Alin also had to patch the mock version of hg.