Katello Smart Proxy Upgrade issues - 1.15.6 (3.5) to 1.21.3 (3.11)

Problem:
Question: Can we upgrade Katello Smart Proxy directly from 1.15.6 to 1.21.3? Or do we need to upgrade sequentially??
I’m getting an issue where MongoDB is failing to start. Giving an error 100. It doesnt give much info other than that.
I can see that the DB didnt migrate to the new location, its still in /var/lib/mongodb. I can see the only file in the DB dir is /var/opt/rh/rh-mongodb34/lib/mongodb/mongod.lock. Deleting that makes no difference. Moving the DB files to the new location doesnt help. Maybe i’m doing this wrong?

Foreman and Proxy versions:
Foreman: 1.21.3 (3.11)
Proxy: 1.15.6 (3.5)

Other relevant data:

systemctl status  rh-mongodb34-mongod -l
â rh-mongodb34-mongod.service - High-performance, schema-free document-oriented database
   Loaded: loaded (/usr/lib/systemd/system/rh-mongodb34-mongod.service; disabled; vendor preset: disab                                                                                                         led)
   Active: failed (Result: exit-code) since Thu 2019-08-15 15:46:27 HKT; 2s ago
  Process: 13512 ExecStart=/opt/rh/rh-mongodb34/root/usr/libexec/mongodb-scl-helper enable $RH_MONGODB34_SCLS_ENABLED -- /opt/rh/rh-mongodb34/root/usr/bin/mongod $OPTIONS run (code=exited, status=100)

Aug 15 15:46:27 fqdn.xxxx.com systemd[1]: Starting High-performance, schema-free document-oriented database...
Aug 15 15:46:27 fqdn.xxxx.com mongodb-scl-helper[13512]: about to fork child process, waiting until server is ready for connections.
Aug 15 15:46:27 fqdn.xxxx.com mongodb-scl-helper[13512]: forked process: 13517
Aug 15 15:46:27 fqdn.xxxx.com mongodb-scl-helper[13512]: ERROR: child process failed, exited with error number 100
Aug 15 15:46:27 fqdn.xxxx.com systemd[1]: rh-mongodb34-mongod.service: control process exited, code=exited status=100
Aug 15 15:46:27 fqdn.xxxx.com systemd[1]: Failed to start High-performance, schema-free document-oriented database.
Aug 15 15:46:27 fqdn.xxxx.com systemd[1]: Unit rh-mongodb34-mongod.service entered failed state.
Aug 15 15:46:27 fqdn.xxxx.com systemd[1]: rh-mongodb34-mongod.service failed.

Hi magarvo,

It looks like having upgraded from 1.56.6 directly to 1.21.3 caused a MongoDB migration to be skipped. When upgrading the Smart Proxy, be sure to run the installer for each incremental version: Foreman :: Plugin Manuals

Since the upgrade put your server in a non-working state, it might be easier to reinstall the smart proxy and then re-sync your content.

1 Like

It appears thats what the issue was. I restored from snapshot and ran the upgrade sequentially, and everything went well.

1 Like