Packaging: Issueshttps://projects.theforeman.org/https://projects.theforeman.org/favicon.ico?16970236342018-06-01T08:57:15ZForeman
Redmine Bug #23767 (Resolved): Update Katello spec enable SCL for Mongohttps://projects.theforeman.org/issues/237672018-06-01T08:57:15ZChris Robertschrobert@redhat.com
<p>/usr/sbin/foreman-debug: line 79: mongo: command not found</p>
<p>mongo does not work unless we run</p>
<p>scl enable rh-mongodb34 bash</p> Bug #22266 (Duplicate): Fresh installation of Foreman with Ansible plugin and proxy is broken aft...https://projects.theforeman.org/issues/222662018-01-15T10:03:13ZRomans Krjukovsr.krjukovs@dynatech.lv
<p>Hey,</p>
<p>Fresh installation of Foreman 1.16 with Ansible plugin and proxy on clean Ubuntu Xenial is broken after host restart.</p>
<p>Steps to reproduce:<br />- get clean OS (virtualbox in my case);<br />- enable Ansible ppa:<br /><pre>
sudo apt-get update
sudo apt-get install software-properties-common
sudo apt-add-repository ppa:ansible/ansible
</pre><br />- install foreman installer:<br /><pre>
sudo su -
apt-get -y install ca-certificates
wget https://apt.puppetlabs.com/puppet5-release-xenial.deb
dpkg -i puppet5-release-xenial.deb
echo "deb http://deb.theforeman.org/ xenial 1.16" > /etc/apt/sources.list.d/foreman.list
echo "deb http://deb.theforeman.org/ plugins 1.16" >> /etc/apt/sources.list.d/foreman.list
apt-get -y install ca-certificates
wget -q https://deb.theforeman.org/pubkey.gpg -O- | apt-key add -
apt-get update && apt-get -y install foreman-installer
</pre><br />- install foreman:<br /><pre>
foreman-installer --enable-foreman-plugin-ansible --enable-foreman-proxy-plugin-ansible -v
</pre><br />- installation is complete without errors:<br /><pre>
...
[DEBUG 2018-01-15T11:35:30 main] Finishing transaction 65695780
[DEBUG 2018-01-15T11:35:30 main] Received report to process from foremansible.lan
[ INFO 2018-01-15T11:35:33 main] Puppet has finished, bye!
[ INFO 2018-01-15T11:35:33 main] Executing hooks in group post
[DEBUG 2018-01-15T11:35:33 main] Hook /usr/share/foreman-installer/hooks/post/10-post_install_message.rb returned nil
[ INFO 2018-01-15T11:35:33 main] All hooks in group post finished
[DEBUG 2018-01-15T11:35:33 main] Exit with status code: 2 (signal was 2)
[DEBUG 2018-01-15T11:35:33 main] Cleaning /tmp/kafo_puppet20180115-9397-3rrchs.conf
[DEBUG 2018-01-15T11:35:33 main] Cleaning /tmp/kafo_hiera20180115-9397-b011lm
[DEBUG 2018-01-15T11:35:33 main] Cleaning /tmp/kafo_puppet20180115-9397-1aae9jd.conf
[DEBUG 2018-01-15T11:35:33 main] Cleaning /tmp/default_values.yaml
[ INFO 2018-01-15T11:35:33 main] Installer finished in 1356.3395379 seconds
</pre><br />- check Foreman is up & running via browser (is OK);<br />- restart host;<br />- check Foreman is up & running via browser (is NOK):<br /> got "We're sorry, but something went wrong." etc.;</p>
<p>Latest error in /var/log/apache2/error.lg:<br /><pre>
[ 2018-01-15 11:45:42.1745 1399/7ff5a005c700 age/Cor/App/Implementation.cpp:304 ]: Could not spawn process for application /usr/share/foreman: An error occured while starting the web application.
Error ID: 8fbdc3a8
Error details saved to: /tmp/passenger-error-PSIaZW.html
Message from application: PG::DuplicateColumn: ERROR: column "version" of relation "dynflow_schema_info" already exists
(Sequel::DatabaseError)
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/adapters/postgres.rb:145:in `async_exec'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/adapters/postgres.rb:145:in `block in execute_query'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/database/logging.rb:38:in `log_connection_yield'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/adapters/postgres.rb:145:in `execute_query'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/adapters/postgres.rb:133:in `block in execute'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/adapters/postgres.rb:109:in `check_disconnect_errors'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/adapters/postgres.rb:133:in `execute'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/adapters/postgres.rb:449:in `_execute'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/adapters/postgres.rb:273:in `block (2 levels) in execute'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/adapters/postgres.rb:471:in `check_database_errors'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/adapters/postgres.rb:273:in `block in execute'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/database/connecting.rb:264:in `block in synchronize'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/connection_pool/threaded.rb:91:in `hold'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/database/connecting.rb:264:in `synchronize'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/adapters/postgres.rb:273:in `execute'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/database/query.rb:50:in `execute_dui'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/database/query.rb:43:in `execute_ddl'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/database/schema_methods.rb:411:in `block in apply_alter_table'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/database/schema_methods.rb:411:in `each'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/database/schema_methods.rb:411:in `apply_alter_table'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/database/schema_methods.rb:424:in `apply_alter_table_generator'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/database/schema_methods.rb:70:in `alter_table'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/extensions/migration.rb:622:in `schema_dataset'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/extensions/migration.rb:450:in `initialize'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/extensions/migration.rb:517:in `initialize'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/extensions/migration.rb:398:in `new'
/usr/share/foreman/vendor/ruby/2.3.0/gems/sequel-5.2.0/lib/sequel/extensions/migration.rb:398:in `run'
/usr/share/foreman/vendor/ruby/2.3.0/gems/dynflow-0.8.33/lib/dynflow/persistence_adapters/sequel.rb:238:in `migrate_db'
/usr/share/foreman/vendor/ruby/2.3.0/gems/dynflow-0.8.33/lib/dynflow/persistence_adapters/sequel.rb:46:in `initialize'
/usr/share/foreman/vendor/ruby/2.3.0/gems/foreman-tasks-0.10.6/lib/foreman_tasks/dynflow/configuration.rb:39:in `new'
/usr/share/foreman/vendor/ruby/2.3.0/gems/foreman-tasks-0.10.6/lib/foreman_tasks/dynflow/configuration.rb:39:in `initialize_persistence'
/usr/share/foreman/vendor/ruby/2.3.0/gems/dynflow-0.8.33/lib/dynflow/rails/configuration.rb:107:in `block in world_config'
/usr/share/foreman/vendor/ruby/2.3.0/gems/dynflow-0.8.33/lib/dynflow/rails/configuration.rb:103:in `tap'
/usr/share/foreman/vendor/ruby/2.3.0/gems/dynflow-0.8.33/lib/dynflow/rails/configuration.rb:103:in `world_config'
/usr/share/foreman/vendor/ruby/2.3.0/gems/foreman-tasks-0.10.6/lib/foreman_tasks/dynflow/configuration.rb:8:in `world_config'
/usr/share/foreman/vendor/ruby/2.3.0/gems/dynflow-0.8.33/lib/dynflow/rails/configuration.rb:66:in `initialize_world'
/usr/share/foreman/vendor/ruby/2.3.0/gems/dynflow-0.8.33/lib/dynflow/rails.rb:100:in `init_world'
/usr/share/foreman/vendor/ruby/2.3.0/gems/dynflow-0.8.33/lib/dynflow/rails.rb:37:in `initialize!'
/usr/share/foreman/vendor/ruby/2.3.0/gems/foreman-tasks-0.10.6/lib/foreman_tasks/engine.rb:153:in `block (2 levels) in <class:Engine>'
/usr/lib/ruby/vendor_ruby/phusion_passenger/public_api.rb:42:in `block in call_event'
/usr/lib/ruby/vendor_ruby/phusion_passenger/public_api.rb:41:in `each'
/usr/lib/ruby/vendor_ruby/phusion_passenger/public_api.rb:41:in `call_event'
/usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:393:in `before_handling_requests'
/usr/share/passenger/helper-scripts/rack-preloader.rb:134:in `negotiate_spawn_command'
/usr/share/passenger/helper-scripts/rack-preloader.rb:158:in `<module:App>'
/usr/share/passenger/helper-scripts/rack-preloader.rb:30:in `<module:PhusionPassenger>'
/usr/share/passenger/helper-scripts/rack-preloader.rb:29:in `<main>'
[ 2018-01-15 11:45:42.1870 1399/7ff5a0bab700 age/Cor/Con/CheckoutSession.cpp:285 ]: [Client 1-7] Cannot checkout session because a spawning error occurred. The identifier of the error is 8fbdc3a8. Please see earlier logs for details about the error.
App 2552 stdout:
App 2552 stderr: The PGconn, PGresult, and PGError constants are deprecated, and will be
App 2552 stderr: removed as of version 1.0.
App 2552 stderr:
App 2552 stderr: You should use PG::Connection, PG::Result, and PG::Error instead, respectively.
App 2552 stderr:
App 2552 stderr: Called from /usr/share/foreman/vendor/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/dependencies.rb:274:in `block in require'
</pre></p>
<p>Please, advise.<br />Thank You!</p>
<p>Regards<br />/Romans</p> Bug #20050 (Closed): ruby-sequel-pg DEB pollutes Foreman ruby gem environmenthttps://projects.theforeman.org/issues/200502017-06-19T13:16:06ZWim Goddenprojects.theforeman.org-ag@wim.email.be
<p>I had a running foreman install, but needed to run the foreman-installer again to change some settings. Upon doing so, the installer failed on this :<br /> /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]: Failed to call refresh: '/usr/sbin/foreman-rake db:migrate' returned 1 instead of one of [0]<br /> /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]: '/usr/sbin/foreman-rake db:migrate' returned 1 instead of one of [0]</p>
<p>Apparently the issue is at :<br />Sequel::DatabaseError: PG::DuplicateColumn: ERROR: column "version" of relation "dynflow_schema_info" already exists</p>
<p>Any idea if this is a bug or something I did wrong ?</p>
<p>I tried dropping the database, then restarting, but that didn't change anything.</p> Bug #19481 (Rejected): replace foreman-installer/scenarios.d/katello.yaml and %{_sysconfdir}/fore...https://projects.theforeman.org/issues/194812017-05-09T06:46:51ZKlaas D
<p><a class="external" href="https://github.com/Katello/katello-packaging/blob/master/katello-installer/katello-installer-base.spec#L53">https://github.com/Katello/katello-packaging/blob/master/katello-installer/katello-installer-base.spec#L53</a> and <a class="external" href="https://github.com/Katello/katello-packaging/blob/master/katello-installer/katello-installer-base.spec#L55">https://github.com/Katello/katello-packaging/blob/master/katello-installer/katello-installer-base.spec#L55</a><br />From what I understand those two files should be replaced if there is a new version in rpm and not be handled like answer files.</p>
<p>I'll also fix -devel in <a class="external" href="https://github.com/Katello/katello-packaging/blob/master/katello-installer/katello-installer-base.spec#L80">https://github.com/Katello/katello-packaging/blob/master/katello-installer/katello-installer-base.spec#L80</a></p>
<p>Greetings<br />Klaas</p> Bug #18145 (Closed): [RFE] Add RHSM.log to katello-debughttps://projects.theforeman.org/issues/181452017-01-18T15:58:53ZChris Robertschrobert@redhat.com
<p>Sometimes a user will have the katello instance registered to itself and running virt-who can run into issues, we should include the rhsm.log to help debug subscription/candlepin/virt-who related issues.</p> Bug #18012 (Closed): katello-agent depends on gofer >= 2.5, should be 2.7.6https://projects.theforeman.org/issues/180122017-01-10T10:36:16ZChris Duryeecduryee@redhat.com
<p>If a user has a client system with an older version of katello-agent and performs a "yum update katello-agent", they'll get a newer agent but will still have an older gofer version.</p>
<p>There have been numerous fixes to gofer since 2.5, so it would be advantageous to require gofer 2.7.6 or newer.</p>
<p>impl note: I think this is just a matter of bumping the rev in the Requires field to be >= 2.7.6.</p> Bug #17621 (Closed): Misnamed rpm in katello-removehttps://projects.theforeman.org/issues/176212016-12-09T15:16:06ZChristine Fouantcfouant@redhat.com
<p>python-semantic_version was mislabeled as python-semantic-version.</p> Bug #17174 (Closed): katello-restore refuses to restore a backup created with katello-backup --sk...https://projects.theforeman.org/issues/171742016-11-01T15:45:17ZChristine Fouantcfouant@redhat.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1389814">https://bugzilla.redhat.com/show_bug.cgi?id=1389814</a></p>
<p>Description of problem:<br />katello-restore refuses to restore a backup created with katello-backup --skip-pulp-content</p>
<p>Version-Release number of selected component (if applicable):<br />Satellite 6.2.3<br />katello-common-3.0.0-14.el7sat.noarch</p>
<p>How reproducible:<br />always</p>
<p>Steps to Reproduce:<br />1. katello-backup --skip-pulp-content /var/satbackup/2016-10-28<br />2. satellite-installer --reset<br />3. katello-restore /var/satbackup/2016-10-28/</p>
Actual results:<br />20:03:34 [root@satellite ~]# katello-restore /var/satbackup/2016-10-28/
<ul>
<li>Given directory does not include pulp content <strong>**</strong></li>
<li>Please choose a backup that contains pulp content <strong>**</strong><br />Usage: katello-restore /path/to/dir [options]<br /> eg: $ katello-restore /tmp/katello-backup<br /> -y, --assumeyes Answer yes for all questions<br />20:03:54 [root@satellite ~]#</li>
</ul>
<p>Expected results:<br />ability to restore a backup created as per <a class="external" href="https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/server-administration-guide/chapter-6-backup-and-disaster-recovery">https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/server-administration-guide/chapter-6-backup-and-disaster-recovery</a><br />either via a --no-pulp-present or similar flag to katello-restore<br />or "katello-backup --skip-pulp-content" creating an empty pulp data file</p>
<p>Additional info:</p> Bug #17114 (Closed): foreman-debug to collect whole newest (log)files instead of tailing all (log...https://projects.theforeman.org/issues/171142016-10-26T14:32:53ZPavel Moravecpmoravec@redhat.com
<p>(cloned from <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: foreman-debug to collect whole newest (log)files instead of tailing all (log)files (Closed)" href="https://projects.theforeman.org/issues/16680">#16680</a> since I was unable to change project from Katello to Packaging)</p>
<p>Description of problem:<br />Currently foreman-debug truncates any (log)file it collects after 5000 lines, to shrink the size of created tarball. This causes the problem that collected logs have "gaps" in timeline, what means we lose track of events happened that time.</p>
<p>Assume I want to investigate some problem with relevant logs scattered in past 2 days, and these logs are kept in files A.log, A.1.log and A.2.log, each exceeding 5k lines. Then I get tails of the logfiles (plus tails of A.9999.log from very past) but dont know what happened at the beginning of say A.1.log.</p>
<p>So we don't collect <strong>some</strong> log records in close history while we collect some logs in very past history.</p>
<p>What about to rather collect all newest files, until some per-directory limit is reached?</p>
<p>Something like that is done in sosreport [1] where it works well.</p>
<p>[1] <a class="external" href="https://github.com/sosreport/sos/blob/master/sos/plugins/__init__.py#L508">https://github.com/sosreport/sos/blob/master/sos/plugins/__init__.py#L508</a></p>
<p>Version-Release number of selected component (if applicable):<br />foreman-debug-1.11.0.49-1.el7sat.noarch</p>
<p>How reproducible:<br />100%</p>
<p>Steps to Reproduce:<br />1. Generate logfiles (i.e. production.log*) each bigger than 5k lines<br />2. collect foreman-debug and unpack it<br />3. Check what logfiles are collected</p>
<p>Actual results:<br />Currently tails of all logfiles (even 2 years old, irrelevant for current problem investigation) are collected. But head of first log-rotated logfile is missing (causing we dont know what happened yesterday morning)</p>
<p>Expected results:<br />Collected logifles completely cover past few days without a gap; older logfiles not collected.</p>
<p>Additional info:<br />This issue tracks changes in katello-debug.sh required to be done after changing foreman-debug and it's methods.</p> Bug #17047 (Resolved): katello-clean-empty-puppet-environments cron.weekly job needs to hide erro...https://projects.theforeman.org/issues/170472016-10-20T09:58:03ZChris Robertschrobert@redhat.com
<p>Cloned from Bugzilla:</p>
<p>Description of problem:<br />The cron.weekly job put in place to clean empty puppet environments will now have situations where there are no KT_* environments to clean up. In this situation, the find command fails and an error is output. We should redirect the errors to null (hide them) or come up with a different command.</p>
<p>Version-Release number of selected component (if applicable):<br />Satellite 6.2.2.1</p>
<p>How reproducible:<br />100%</p>
<p>Steps to Reproduce:<br />1. Install Satellite 6.2<br />2. Have no publshed puppet environments. (KT_* folders are no longer created for content-views, so on if not modules are published)<br />3. Run /etc/cron.weekly/katello-clean-empty-puppet-environments</p>
<p>Actual results:<br />find: ‘/etc/puppet/environments/KT*’: No such file or directory</p>
<p>Expected results:<br />No errors from script output</p>
<p>Additional info:<br />Since the only purpose is to clean out unused puppet environments, we could simply add '> /dev/null 2>&1' to the end of the scripts `find` command.</p> Bug #15230 (Closed): katello-installer requires new katello-servicehttps://projects.theforeman.org/issues/152302016-05-30T11:36:39ZMarek Hulánmhulan@redhat.com
<p>Otherwise upgrading of older version fails</p>
<pre>
Upgrading...
Upgrade Step: stop_services...
Upgrade Step: start_databases...
Upgrade step start_databases failed. Check logs for more information.
</pre>
<p>since it uses <code>katello-service start --only mongod,postgresql</code>, older version does not have the support for <code>--only</code></p> Bug #14423 (Resolved): Package tfm-rubygem-hammer_cli_csv fails still requires gettext but should...https://projects.theforeman.org/issues/144232016-03-31T11:19:45Zalvin starralvin@netvel.net
<p>From a 3.0.0 related bug</p>
<p>The gettext dependency seems to be dropped upstream recently as can be seen on <a class="external" href="https://github.com/Katello/hammer-cli-csv/commit/6f221b512cd2cbdf58a590f08479c6580698ae39#diff-47a6305b01b3fb14a7db42be13725c81L23">https://github.com/Katello/hammer-cli-csv/commit/6f221b512cd2cbdf58a590f08479c6580698ae39#diff-47a6305b01b3fb14a7db42be13725c81L23</a><br />Therefore it should be good enough to update the tfm-rubygem-hammer_cli_csv package to version 1.0.2 to get this issue resolved</p>
<p>There is no version 1.0.2 rpm in the 2.4 repo.</p> Bug #14358 (Closed): Upgrade from Katello 2.3 to 3.0 failhttps://projects.theforeman.org/issues/143582016-03-26T23:26:11ZMario Gamboamario.gamboa@gmail.com
<p>Hi Team</p>
<p>I trying to make the upgrade from 2.3 to nightly without success this is the procedure i did</p>
<p>1.- Use the correct repos because in the instructions are pointing wrong<br />yum update -y <a class="external" href="https://fedorapeople.org/groups/katello/releases/yum/nightly/katello/el7/x86_64/katello-repos-latest.rpm">https://fedorapeople.org/groups/katello/releases/yum/nightly/katello/el7/x86_64/katello-repos-latest.rpm</a><br />yum update -y <a class="external" href="http://yum.theforeman.org/releases/1.11/el7/x86_64/foreman-release.rpm">http://yum.theforeman.org/releases/1.11/el7/x86_64/foreman-release.rpm</a></p>
<p>2.- This point is no included in the instruction and is going to give a lot of dependencies missing from ruby2.2 and ror<br />yum -y install foreman-release-scl</p>
<p>3.- yum update -y</p>
<p>This is what i got<br />--> Finished Dependency Resolution<br />Error: Package: ruby193-rubygem-strong_parameters-0.2.1-11.el7.noarch (@katello)<br />Requires: ruby193-ruby-wrapper<br />Removing: ruby193-ruby-wrapper-0.0.2-6.el7.noarch (@foreman)<br />ruby193-ruby-wrapper = 0.0.2-6.el7<br />Obsoleted By: tfm-runtime-2.0-2.el7.x86_64 (foreman)<br />Not found<br />Error: Package: ruby193-rubygem-tire-0.6.2-1.el7.noarch (@katello)<br />Requires: ruby193-rubygem(rest-client) >= 1.6<br />Removing: ruby193-rubygem-rest-client-1.6.7-2.el7.noarch (@foreman)<br />ruby193-rubygem(rest-client) = 1.6.7<br />Obsoleted By: tfm-rubygem-rest-client-1.6.7-4.el7.noarch (foreman)<br />Not found<br />Error: Package: ruby193-rubygem-less-2.5.1-2.el7.noarch (@foreman-plugins)<br />Requires: ruby193-rubygem(commonjs) >= 0.2.7<br />Removing: ruby193-rubygem-commonjs-0.2.7-1.el7.noarch (@foreman-plugins)<br />ruby193-rubygem(commonjs) = 0.2.7<br />Obsoleted By: tfm-rubygem-commonjs-0.2.7-3.el7.noarch (foreman-plugins)<br />Not found<br />Error: Package: ruby193-rubygem-hashr-0.0.22-5.el7.noarch (@katello)<br />Requires: ruby193-ruby-wrapper<br />Removing: ruby193-ruby-wrapper-0.0.2-6.el7.noarch (@foreman)<br />ruby193-ruby-wrapper = 0.0.2-6.el7<br />Obsoleted By: tfm-runtime-2.0-2.el7.x86_64 (foreman)<br />Not found<br />Error: Package: ruby193-rubygem-less-2.5.1-2.el7.noarch (@foreman-plugins)<br />Requires: ruby193-rubygem(commonjs) < 0.3<br />Removing: ruby193-rubygem-commonjs-0.2.7-1.el7.noarch (@foreman-plugins)<br />ruby193-rubygem(commonjs) = 0.2.7<br />Obsoleted By: tfm-rubygem-commonjs-0.2.7-3.el7.noarch (foreman-plugins)<br />Not found<br />Error: Package: ruby193-rubygem-tire-0.6.2-1.el7.noarch (@katello)<br />Requires: ruby193-rubygem(ansi)<br />Removing: ruby193-rubygem-ansi-1.4.3-3.el7.noarch (@katello)<br />ruby193-rubygem(ansi) = 1.4.3<br />Obsoleted By: tfm-rubygem-ansi-1.4.3-6.el7.noarch (foreman)<br />Not found</p>
<p>4.- if i make the same procedure but just before upgrade to 2.4 works ok the issue is the upgrade procedure from 2.3 to nightly (3.0) is no working as expected</p> Bug #14260 (Closed): Katello repos nigthly are wrong https://projects.theforeman.org/issues/142602016-03-18T05:30:22ZMario Gamboamario.gamboa@gmail.com
<p>The latest nightly coming with a typo in the repo links</p>
<p><a class="external" href="https://fedorapeople.org/groups/katello/releases/yum/nightly/pulp/.el7/$basearch/">https://fedorapeople.org/groups/katello/releases/yum/nightly/pulp/.el7/$basearch/</a></p>
<p>on the el7 is a dot before and making the repo no work</p> Bug #13676 (Closed): Create a sub package for ostreehttps://projects.theforeman.org/issues/136762016-02-11T11:31:44ZPartha Ajipaji@redhat.com
<p>We need to create a sub package for ostree.</p>
<p>That sub package needs to include<br />1) a dep on pulp-ostree-plugins<br />2) include lib/katello/repository_types/ostree.rb<br />3) Fix katello spec to exclude lib/katello/repository_types/ostree.rb</p>