But this comes back with ERROR: too many arguments
This is a clean foreman host just installed running 1.16. We are planning to upgrade it to 1.19 (or 1.20 if its done by the end of this process) to determine how the whole process works to eventually run it on our production host.
Currently, foreman-maintain does not have any upgrade scenarios for upstream versions of Foreman. That’s why it is giving empty result for upgrade command. “Upstream Foreman upgrade scenario” feature request is still a work in progress. You can track the PR here PR-230.
@mbacovsky, for backup/restore do you have any pointers? or I think it’s better to wait for this above PR to get merged into master so that users can experience the full flow cycle of backup-upgrade-restore.
@Mike, please check this link, one of the demo video which gives some internals of foreman-maintain.
No, but it is better to have supported Foreman version as it probably gone through some testing.
This sounds like a bug. Would you mind creating a new issue in our tracker with the description you have here and at least the backtrace from the log you have. This way we can make sure it is fixed for new Foreman releases and you can track the progress.
This error is caused by swapping the options and the final argument in the CLI. With correct order it should work:
Can you explain what you mean “upstream upgrade” ? I’m not entirely clear what it means.
My Apologies! Here, I wanted to refer as Foreman upgrade.
Using foreman-maintain upgrade command, user will able to upgrade their foreman instances. That is currently under work in progress.
Backup and Restore in Foreman Maintain works on the following:
Foreman Proxy with Content (>3.0)
Backup and Restore support for standalone Foreman is currently in development.
I’m not using Katello or Foreman Proxy with Content. Perhaps, that would be one possible explanation for that error.
p.s. Any idea how reliable the backups are for a standalone Foreman installation?
Its a bit counter-intuitive, but foreman-maintain backup and restore was written for Katello first. Katello is harder to backup than Foreman due to the multiple services and database it uses so it makes sense to have a tool manage it.
We definitely would like to support backing up Foreman and have it run without workarounds like the whitelisting of steps mentioned above so please do file any bugs if they have not been filed yet.
I do think there are rake tasks like foreman-rake db:dump to backup Foreman currently, you may find these helpful
Having the same, nil:NilClass error when it comes to backing up config. I saw there was some advice around using the white list option --whitelist="backup-config-files" to stop the config being backed up.
While testing the restore process, this also throws errors which point to using additional whitelist options. I can’t seem to get this working in a coherent way, so I’m not sure how reliable this would be as a work around.
Thanks for the suggestion, it did notice that fix from another forum post and gave it a go, but for some reason it didn’t work for me. Can’t quite remember the error it gave me.
I ended up downloading the foreman-maintain git repo, I tried a few tagged version but could only backup while on the master branch. This still doesn’t work with the restore function but at least backs up the config files. I’ll wait for the new version to come through yum and hopefully that will fix things for me.