evgeni
August 27, 2021, 7:56am
#2
Exec[foreman-rake-db:migrate]/returns: uninitialized constant MigratePortOverridesToInt::Puppetclass
Exec[foreman-rake-db:migrate]/returns: /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_hooks-0.3.17/lib/foreman_hooks/as_depende
ncies_hook.rb:4:in `load_missing_constant'
Exec[foreman-rake-db:migrate]/returns: /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_openscap-4.3.3/db/migrate/20200117135424_
migrate_port_overrides_to_int.rb:13:in `transform_lookup_values'
Exec[foreman-rake-db:migrate]/returns: /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_openscap-4.3.3/db/migrate/20200117135424_
migrate_port_overrides_to_int.rb:3:in `up'
…
Which looks like Refactor #33137: Changes to align wiht foreman_puppet - OpenSCAP - Foreman
But there is no released foreman_openscap
yet with that change
cc @lzap @Ondrej_Prazak
lzap
September 1, 2021, 9:32am
#3
It was @ezr-ondrej who created the patch and I don’t understand - there is defined? ForemanPuppet
in that method. The class appears to be defined in the foreman_puppet plugin.
Is it possible that during the test ForemanPuppet gets defined without puppet plugin installed?
evgeni
September 1, 2021, 9:35am
#4
You’re late to the party, we already got a fixed foreman_openscap
out
theforeman:rpm/3.0
← xprazak2:scap-3050
opened 08:28AM - 27 Aug 21 UTC
<!--
If your package needs to be released within one or more release streams, a… nd/or distributions, please open PRs to each of those branches respectively. The easiest way to do this is to make the initial commit for the mainline branch (e.g. rpm/develop or deb/develop) and then cherry pick the commit hash onto each subsequent branch.
Supported Versions:
* Nightly
* 2.0
* 1.24
* 1.23
RPM Example:
git checkout -b rpm/develop-foreman-tasks-1.0.1 rpm/develop
# Make changes to update package
git commit -a -m 'Release foreman-tasks-1.0.1'
COMMIT=`git rev-parse HEAD`
git checkout -b rpm/1.20-foreman-tasks-1.0.1-1.20 rpm/1.20
git cherry-pick -x $COMMIT
DEB Example:
git checkout -b deb/develop-foreman-tasks-1.0.1 deb/develop
# Make changes to update package
git commit -a -m 'Release foreman-tasks-1.0.1'
COMMIT=`git rev-parse HEAD`
git checkout -b deb/1.20-foreman-tasks-1.0.1-1.20 deb/1.20
git cherry-pick -x $COMMIT
See Foreman's [plugin maintainer documentation](https://projects.theforeman.org/projects/foreman/wiki/How_to_Create_a_Plugin#Release-strategies) for more information.
-->
and the later pipeline passed
https://ci.theforeman.org/job/foreman-plugins-3.0-rpm-test-pipeline/3/
Granted, I could have updated it here, sorry
1 Like
system
Closed
September 8, 2021, 9:35am
#5
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.