when I upgrade katello from 2.4 to 3.0, I found it stuck at
"update_puppet_repository_distributors (this may take a while)"
Upgrade Step: import_puppet_modules (this may take a while) …
Upgrade Step: import_subscriptions (this may take a while) …
Upgrade Step: elasticsearch_message…
Elasticsearch has been removed as a dependency. The database files can be
removed manually with #rm -rf /var/lib/elasticsearch. Some packages are no
longer needed and can be removed: #rpm -e ruby193-rubygem-tire
tfm-rubygem-tire elasticsearch sigar-java sigar snappy-java lucene4-contrib
lucene4
Upgrade Step: add_export_distributor (this may take a while) …
Upgrade Step: remove_docker_v1_content (this may take a while) …
Upgrade Step: update_puppet_repository_distributors (this may take a while)
…
the whole system still works though, but I don't know if any impact it will
has, is there any way that we can manually run to trouble shoot or proceed.?
How long was it running that step? Was there system activity during it? Do
you have a lot of puppet repos? Any errors in the logs?
···
On Jul 8, 2016 12:28 AM, "sinux shen" wrote:
Hey guys,
when I upgrade katello from 2.4 to 3.0, I found it stuck at
"update_puppet_repository_distributors (this may take a while)"
Upgrade Step: import_puppet_modules (this may take a while) …
Upgrade Step: import_subscriptions (this may take a while) …
Upgrade Step: elasticsearch_message…
Elasticsearch has been removed as a dependency. The database files can be
removed manually with #rm -rf /var/lib/elasticsearch. Some packages are no
longer needed and can be removed: #rpm -e ruby193-rubygem-tire
tfm-rubygem-tire elasticsearch sigar-java sigar snappy-java lucene4-contrib
lucene4
Upgrade Step: add_export_distributor (this may take a while) …
Upgrade Step: remove_docker_v1_content (this may take a while) …
Upgrade Step: update_puppet_repository_distributors (this may take a
while) …
the whole system still works though, but I don’t know if any impact it
will has, is there any way that we can manually run to trouble shoot or
proceed.?
Our Katello Server is a VM running on RHEV, for the first time it stuck at
"update_puppet_repository_distributors", I did a roll back and upgrade it
again, it stuck at the same place, for the first time, it ran like 12 hrs,
and I just "ctrl+c" it, for the second time, It's been running for 10 hrs,
and I haven't kill it.
the system was running and as katello/foreman server has been upgraded,
(due to the log: Upgrade Step: Running installer…
Installing Done
[100%]
[…]
The full log is at /var/log/foreman-installer/katello.log)
it seems that katello/foreman is running correctly, I don't know if there
is any impact on it.
To answer your third question, I don't think I have any puppet repo been
used in our system, we do have a bunch of puppet classes that was imported,
but my understand was that they are not puppet repo, please correct me if I
am wrong.
I checked katello.log under /var/log/foreman-installer/katello.log
it stop at: [ INFO 2016-07-08 23:17:58 main] Upgrade Step:
update_puppet_repository_distributors (this may take a while) …
and I attached the log file, see if it helps for trouble shooting.
···
On Friday, July 8, 2016 at 6:48:14 PM UTC+8, Eric Helms wrote:
>
> How long was it running that step? Was there system activity during it? Do
> you have a lot of puppet repos? Any errors in the logs?
> On Jul 8, 2016 12:28 AM, "sinux shen" <sinux...@gmail.com > > wrote:
>
>> Hey guys,
>>
>> when I upgrade katello from 2.4 to 3.0, I found it stuck at
>> "update_puppet_repository_distributors (this may take a while)"
>> Upgrade Step: import_puppet_modules (this may take a while) ...
>> Upgrade Step: import_subscriptions (this may take a while) ...
>> Upgrade Step: elasticsearch_message...
>> Elasticsearch has been removed as a dependency. The database files can
>> be removed manually with #rm -rf /var/lib/elasticsearch. Some packages are
>> no longer needed and can be removed: #rpm -e ruby193-rubygem-tire
>> tfm-rubygem-tire elasticsearch sigar-java sigar snappy-java lucene4-contrib
>> lucene4
>> Upgrade Step: add_export_distributor (this may take a while) ...
>> Upgrade Step: remove_docker_v1_content (this may take a while) ...
>> Upgrade Step: update_puppet_repository_distributors (this may take a
>> while) ...
>>
>> the whole system still works though, but I don't know if any impact it
>> will has, is there any way that we can manually run to trouble shoot or
>> proceed.?
>>
>> Thanks
>> -Sinux
>>
>> --
>> 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.
>>
>
