Katello 3.0 (Saison) RC2 is now available for testing. This release is a
major version bump because it introduces some backwards incompatible
changes and the removal of all deprecations that existed through the 2.X
lifespan.
We appreciate the testing and bug reports thus far, we are working to make
this release as solid as possible and hence the long RC process. Currently
RC2 can only be tested on EL7. There was a patch needed to Foreman that we
did not request be put into 1.11.0 and will thus require us to wait till
1.11.1 (sometime next week according to the schedule) to build EL6.
RC2 addresses upgrade issues seen from 2.4 to 3.0 except for a few
migration issues that afflict certain data setups:
···
On Wednesday, April 13, 2016 at 10:54:19 AM UTC-7, Eric Helms wrote:
>
>
> Katello 3.0 (Saison) RC2 is now available for testing. This release is a
> major version bump because it introduces some backwards incompatible
> changes and the removal of all deprecations that existed through the 2.X
> lifespan.
>
> We appreciate the testing and bug reports thus far, we are working to make
> this release as solid as possible and hence the long RC process. Currently
> RC2 can only be tested on EL7. There was a patch needed to Foreman that we
> did not request be put into 1.11.0 and will thus require us to wait till
> 1.11.1 (sometime next week according to the schedule) to build EL6.
>
> * RC2 addresses upgrade issues seen from 2.4 to 3.0 except for a few
> migration issues that afflict certain data setups:
> - http://projects.theforeman.org/issues/14551
> - http://projects.theforeman.org/issues/14533
> * Upgrading from 2.3 to 3.0 needs some testing, scratch built RPMs of an
> open PR can be found here to test:
> - http://koji.katello.org/koji/taskinfo?taskID=448153
>
>
> For a detailed list and information of the changes in Katello 3.0 is in
> our release notes:
> http://www.katello.org/docs/3.0/release_notes/release_notes.html
>
>
>
> Installation
> ============
>
> For installation, please see the instructions at:
>
> Server: http://www.katello.org/docs/3.0/installation/index.html
>
> Capsule: http://www.katello.org/docs/3.0/installation/capsule.html
>
>
> Bug reporting
> =============
> If you come across a bug in your testing, please file it and note the
> version of Katello that you're using in the report and set the release
> to 3.0.0.
>
> http://projects.theforeman.org/projects/katello/issues/new
>
>
> --
> Eric D. Helms
> Red Hat Engineering
> Ph.D. Student - North Carolina State University
>
Same here, same issues after follow all the workaround
[ INFO 2016-04-16 13:00:20 verbose] Upgrade Step: migrate_foreman…
PG::Error: ERROR: update or delete on table "katello_systems" violates
foreign key constraint "system_activation_keys_
system_id_fk" on table "katello_system_activation_keys"
DETAIL: Key (id)=(79) is still referenced from table
"katello_system_activation_keys".
: DELETE FROM "katello_systems" WHERE "katello_systems"."id" = 78
Please file a Redmine issue for us as they may have been introduced during
RC2.
···
On Apr 16, 2016 7:47 AM, "Mario Gamboa" wrote:
Same here, same issues after follow all the workaround
[ INFO 2016-04-16 13:00:20 verbose] Upgrade Step: migrate_foreman…
PG::Error: ERROR: update or delete on table “katello_systems” violates
foreign key constraint “system_activation_keys_
system_id_fk” on table “katello_system_activation_keys"
DETAIL: Key (id)=(79) is still referenced from table
"katello_system_activation_keys”.
: DELETE FROM “katello_systems” WHERE “katello_systems”.“id” = 78
Erasing those pulp-nodes* packages should do the trick. They are no longer
required as we are now doing Capsule syncing via Pulp APIs instead of
through the Pulp node feature.
Eric
···
On Apr 15, 2016 9:40 AM, wrote:
I got a lot of dependencies errors for ruby22 packages…
I fixed it by running => yum upgrade foreman-release-scl
But now I´m not sure what would be the best way for:
Transaction check error:
file /usr/lib/python2.7/site-packages/semantic_version/init.py from
install of python-semantic_version-2.4.2-1.el7.noarch conflicts with file
from package python-semantic-version-2.2.0-3.el7.noarch
file /usr/lib/python2.7/site-packages/semantic_version/init.pyc from
install of python-semantic_version-2.4.2-1.el7.noarch conflicts with file
from package python-semantic-version-2.2.0-3.el7.noarch
file /usr/lib/python2.7/site-packages/semantic_version/init.pyo from
install of python-semantic_version-2.4.2-1.el7.noarch conflicts with file
from package python-semantic-version-2.2.0-3.el7.noarch
file /usr/lib/python2.7/site-packages/semantic_version/compat.py from
install of python-semantic_version-2.4.2-1.el7.noarch conflicts with file
from package python-semantic-version-2.2.0-3.el7.noarch
file /usr/lib/python2.7/site-packages/semantic_version/compat.pyc from
install of python-semantic_version-2.4.2-1.el7.noarch conflicts with file
from package python-semantic-version-2.2.0-3.el7.noarch
file /usr/lib/python2.7/site-packages/semantic_version/compat.pyo from
install of python-semantic_version-2.4.2-1.el7.noarch conflicts with file
from package python-semantic-version-2.2.0-3.el7.noarch
file /usr/lib/python2.7/site-packages/semantic_version/base.py from
install of python-semantic_version-2.4.2-1.el7.noarch conflicts with file
from package python-semantic-version-2.2.0-3.el7.noarch
file /usr/lib/python2.7/site-packages/semantic_version/base.pyc from
install of python-semantic_version-2.4.2-1.el7.noarch conflicts with file
from package python-semantic-version-2.2.0-3.el7.noarch
file /usr/lib/python2.7/site-packages/semantic_version/base.pyo from
install of python-semantic_version-2.4.2-1.el7.noarch conflicts with file
from package python-semantic-version-2.2.0-3.el7.noarch
file /usr/lib/python2.7/site-packages/semantic_version/django_fields.py
from install of python-semantic_version-2.4.2-1.el7.noarch conflicts with
file from package python-semantic-version-2.2.0-3.el7.noarch
file /usr/lib/python2.7/site-packages/semantic_version/django_fields.pyc
from install of python-semantic_version-2.4.2-1.el7.noarch conflicts with
file from package python-semantic-version-2.2.0-3.el7.noarch
file /usr/lib/python2.7/site-packages/semantic_version/django_fields.pyo
from install of python-semantic_version-2.4.2-1.el7.noarch conflicts with
file from package python-semantic-version-2.2.0-3.el7.noarchEnter code here
…
Workaround performed by erasing python-semantic-version-2.2.0-3.el7.noarch,
because
it will be re-installed as dependecy with python-semantic_version-2.4.2-
1.el7.noarch
Hi Eric, my Upgrade is failing, I will open a Ticket shortly, below some
short infos:
[ INFO 2016-04-15 17:19:58 verbose] Upgrade Step: migrate_foreman…
Katello::Errors::ConnectionRefusedException: A backend service [ Candlepin
] is unreachable
Errno::ECONNREFUSED: Connection refused - connect(2) for "localhost" port
8443
and after a Workaround for above issue:
[ INFO 2016-04-15 17:56:20 verbose] Upgrade Step: migrate_foreman…
PG::Error: ERROR: update or delete on table "katello_systems" violates
foreign key constraint "system_activation_keys_system_id_fk" on table
"katello_system_activation_keys"
DETAIL: Key (id)=(49) is still referenced from table
"katello_system_activation_keys".
: DELETE FROM "katello_systems" WHERE "katello_systems"."id" = 49
I apologize to reopen an old thread.
I'm migrating from a katello 2.4 to a katello 3.2 and I encounter the same
issue. I tried to migrate first to 3.0 but issue remain the same.
So How should I erase those pulp-nodes* ?
I tried with "yum remove pulp-nodes*", but dependancy will remove the
katello package…
I also tried to exclude pulp-nodes* from my "yum update" command but to no
avail…
Regards
Yannig Rousseau
···
On Friday, 15 April 2016 15:46:00 UTC+2, Eric Helms wrote:
>
> Erasing those pulp-nodes* packages should do the trick. They are no longer
> required as we are now doing Capsule syncing via Pulp APIs instead of
> through the Pulp node feature.
>
> Eric
> On Apr 15, 2016 9:40 AM, <ehar...@gmail.com > wrote:
>
>> I got a lot of dependencies errors for ruby22 packages...
>> I fixed it by running => yum upgrade foreman-release-scl
>>
>> But now I´m not sure what would be the best way for:
>>
>> Error: Package: pulp-nodes-common-2.6.4-1.el7.noarch (@katello-pulp)
>> Requires: python-pulp-bindings = 2.6.4
>> Removing: python-pulp-bindings-2.6.4-1.el7.noarch
>> (@katello-pulp)
>> python-pulp-bindings = 2.6.4-1.el7
>> Updated By: python-pulp-bindings-2.8.0-1.el7.noarch
>> (katello-pulp)
>> python-pulp-bindings = 2.8.0-1.el7
>> Error: Package: pulp-nodes-parent-2.6.4-1.el7.noarch (@katello-pulp)
>> Requires: pulp-server = 2.6.4
>> Removing: pulp-server-2.6.4-1.el7.noarch (@katello-pulp)
>> pulp-server = 2.6.4-1.el7
>> Updated By: pulp-server-2.8.0-1.el7.noarch (katello-pulp)
>> pulp-server = 2.8.0-1.el7
>> Error: Package: pulp-nodes-common-2.6.4-1.el7.noarch (@katello-pulp)
>> Requires: pulp-server = 2.6.4
>> Removing: pulp-server-2.6.4-1.el7.noarch (@katello-pulp)
>> pulp-server = 2.6.4-1.el7
>> Updated By: pulp-server-2.8.0-1.el7.noarch (katello-pulp)
>> pulp-server = 2.8.0-1.el7
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to foreman-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
