Upgrade to 5.4: activity log vanishes

[GID]

I'm upgrading my docker-compose installation step by step from 4.17 to 5.8. Up to 5.3 all is fine. Upon moving to 5.4, I notice that the activity log (which I believe is retrieved from the DB) is no longer visible. I can't find something in the release notes that would indicate the reason.

Has this happened to anyone else? Any ideas?

Thanks!

[rac...@rundeck.com]

Hi Bob,

I notice that the activity log (which I believe is retrieved from the DB) is no longer visible.

I think you’re facing this. Can you test upgrading to 5.5? According to this, it’s fixed.

Anyway, the best strategy to upgrade from older versions is to import your projects following this (like this answer). I think is a time-saving option.

Regards!

​

[GID]

Thanks to your help I have resolved both issues I faced and reached 5.8 on the testing server. I have updated step by step, i.e. 10+ steps from 4.15. Each docker-compose took 22+ minutes so it was very time-consuming. 

Do I need to do the same on the production server, or can I jump directly to 5.8 ?  

By that I mean, update my dockerfile to point to 5.8 instead of 4.15, build the container and start my docker-compose.

I can also export jobs (and what else???) from 4.15 just in case I need to import them again into 5.8. 

Thanks again!

[rac...@rundeck.com]

Hi Bob,

> I can also export jobs (and what else???) from 4.15 just in case I need to import them again into 5.8.

Projects (with Jobs, Config, Readme/MOTD, ACLs, SCM config, webhooks ) and keys. You can check the reference here. 

Of course, make sure to add any custom/extra plugins in the new instance.

Test your migration in a non-prod environment first.

Regards!