Closed hellais closed 4 years ago
I am trying to update ooni-backend to the latest version we have recently released.
The building of the rpm is successful, though when I copy the rpm to another test slice and attempt to install it I get the following message:
[mlab_ooni@mlab1 ~]$ sudo rpm -Uvh mlab_ooni-1.2.0-rc1.i686.rpm
We trust you have received the usual lecture from the local System
Preparing... ########################################### [100%]
error: %pre(mlab_ooni-1.2.0-rc1.i686) scriptlet failed, exit status 255
error: install: %pre scriptlet failed (2), skipping mlab_ooni-1.2.0-rc1
[mlab_ooni@mlab1 ~]$ Disabling nightly yum update: [ OK ]
Stopping crond: [ OK ]
Shutting down system logger: [ OK ]
Stopping Slice initscript vinit.slice@mlab_ooni
[FAILED]
Session terminated, killing shell... ...killed.
Connection to mlab1.nuq0t.measurement-lab.org closed.
Looking at #71 it seems like this used to happen also with older versions of the RPM, however when I log back into the slice the version of the installed ooni-backend appears to be the older one and not the most recent one.
Any ideas as to what I am doing wrong?
cc @stephen-soltesz
@stephen-soltesz @nkinkade any updates on this?
@hellais hello, we're sorry for the delay. Unfortunately, my mail filters don't highlight all github messages equally, and I missed this one initially.
The OONI package is managed by M-Lab which means that when a machine reinstalls or a package update occurs, the slice filesystem is deleted and recreated. The package that's deployed is from http://mirror.measurementlab.net/production-centos6/slicebase-i386/i686/ The latest version there is probably the version you find after your slice is recreated.
If you're ready to upgrade your slice globally, then we can prepare a new OONI package and update the mirror server with a new package.
If you're just wanting to test it, you can rm -rf /etc/mlab
; then run rpm -Uhv ...
.
Does this address your question?
@stephen-soltesz yes, thanks this answers my question.
The backend is ready to be updated globally, though I would prefer first doing some testing on the test slices before proceeding to doing a global update.
Will let you know when we are ready to do that.
I believe this is obsolete.