All right, again, this is related to upgrade to katell 2.4

Support
1

here is the log that I got during the upgrade,

it failed at one of the step and then quit, I don't know how many steps it
needs to go further, but from our foreman management gui, it seems ok.

from katello-installer log, I have this part that shows the exact error
info as follows:

[ INFO 2016-04-15 19:04:17 main] Upgrade Step: update_repository_metadata
(this may take a while) …
[ERROR 2016-04-15 19:08:19 main] rake aborted!
Required lock is already taken by other running tasks.
Please inspect their state, fix their errors and resume them.

Required lock: read
Conflicts with tasks:

··· - https://foreman.anim.odw.com.cn/foreman_tasks/tasks/3185a74a-dbe5-4ebe-a74b-31f648c2c88e

Tasks: TOP => katello:upgrades:2.2:update_metadata_expire
(See full trace by running task with --trace)
Updating Expire Metadata for Custom Content

[ERROR 2016-04-15 19:08:19 main] Upgrade step update_repository_metadata
failed. Check logs for more information.
[DEBUG 2016-04-15 19:08:19 main] Exit with status code: 1 (signal was 1)
[ERROR 2016-04-15 19:08:19 main] Repeating errors encountered during run:
[ERROR 2016-04-15 19:08:19 main] nil

2

I am in the middle of this upgrade, I don't know if this error impact a lot
or not, but it make me feel a little unsafe as we have around 500 nodes
managed by katello/foreman. can someone give me a hand please.

Thanks

··· On Friday, April 15, 2016 at 7:15:10 PM UTC+8, sinux shen wrote: > > here is the log that I got during the upgrade, > > it failed at one of the step and then quit, I don't know how many steps it > needs to go further, but from our foreman management gui, it seems ok. > > from katello-installer log, I have this part that shows the exact error > info as follows: > > [ INFO 2016-04-15 19:04:17 main] Upgrade Step: update_repository_metadata > (this may take a while) ... > [ERROR 2016-04-15 19:08:19 main] rake aborted! > Required lock is already taken by other running tasks. > Please inspect their state, fix their errors and resume them. > > Required lock: read > Conflicts with tasks: > - > https://foreman.anim.odw.com.cn/foreman_tasks/tasks/3185a74a-dbe5-4ebe-a74b-31f648c2c88e > > Tasks: TOP => katello:upgrades:2.2:update_metadata_expire > (See full trace by running task with --trace) > Updating Expire Metadata for Custom Content > > [ERROR 2016-04-15 19:08:19 main] Upgrade step update_repository_metadata > failed. Check logs for more information. > [DEBUG 2016-04-15 19:08:19 main] Exit with status code: 1 (signal was 1) > [ERROR 2016-04-15 19:08:19 main] Repeating errors encountered during run: > [ERROR 2016-04-15 19:08:19 main] nil > >
3

Sinux,

Can you see what state the task mentioned (id =
185a74a-dbe5-4ebe-a74b-31f648c2c88e
) is in, and any related errors to it? It looks like a task is trying to
run and is conflicting with a task that has not completed.

John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch

··· On Fri, Apr 15, 2016 at 7:16 AM, sinux shen wrote:

I am in the middle of this upgrade, I don’t know if this error impact a
lot or not, but it make me feel a little unsafe as we have around 500 nodes
managed by katello/foreman. can someone give me a hand please.

Thanks

On Friday, April 15, 2016 at 7:15:10 PM UTC+8, sinux shen wrote:

here is the log that I got during the upgrade,

it failed at one of the step and then quit, I don’t know how many steps
it needs to go further, but from our foreman management gui, it seems ok.

from katello-installer log, I have this part that shows the exact error
info as follows:

[ INFO 2016-04-15 19:04:17 main] Upgrade Step: update_repository_metadata
(this may take a while) …
[ERROR 2016-04-15 19:08:19 main] rake aborted!
Required lock is already taken by other running tasks.
Please inspect their state, fix their errors and resume them.

Required lock: read
Conflicts with tasks:

https://foreman.anim.odw.com.cn/foreman_tasks/tasks/3185a74a-dbe5-4ebe-a74b-31f648c2c88e

Tasks: TOP => katello:upgrades:2.2:update_metadata_expire
(See full trace by running task with --trace)
Updating Expire Metadata for Custom Content

[ERROR 2016-04-15 19:08:19 main] Upgrade step update_repository_metadata
failed. Check logs for more information.
[DEBUG 2016-04-15 19:08:19 main] Exit with status code: 1 (signal was 1)
[ERROR 2016-04-15 19:08:19 main] Repeating errors encountered during run:
[ERROR 2016-04-15 19:08:19 main] nil

–
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-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

4

I have upgrade katello server and the capsule to 2.4 and when I ran capsule
content synchronize --id 4
I got
> capsule content synchronize --id 4
[…]
[100%]
500 Internal Server Error

··· On Friday, April 15, 2016 at 8:19:59 PM UTC+8, John Mitsch wrote: > > Sinux, > > Can you see what state the task mentioned (id = > 185a74a-dbe5-4ebe-a74b-31f648c2c88e > ) is in, and any related errors to it? It looks like a task is trying to > run and is conflicting with a task that has not completed. > > John Mitsch > Red Hat Engineering > (860)-967-7285 > irc: jomitsch > > On Fri, Apr 15, 2016 at 7:16 AM, sinux shen > wrote: > >> I am in the middle of this upgrade, I don't know if this error impact a >> lot or not, but it make me feel a little unsafe as we have around 500 nodes >> managed by katello/foreman. can someone give me a hand please. >> >> Thanks >> >> >> On Friday, April 15, 2016 at 7:15:10 PM UTC+8, sinux shen wrote: >>> >>> here is the log that I got during the upgrade, >>> >>> it failed at one of the step and then quit, I don't know how many steps >>> it needs to go further, but from our foreman management gui, it seems ok. >>> >>> from katello-installer log, I have this part that shows the exact error >>> info as follows: >>> >>> [ INFO 2016-04-15 19:04:17 main] Upgrade Step: >>> update_repository_metadata (this may take a while) ... >>> [ERROR 2016-04-15 19:08:19 main] rake aborted! >>> Required lock is already taken by other running tasks. >>> Please inspect their state, fix their errors and resume them. >>> >>> Required lock: read >>> Conflicts with tasks: >>> - >>> https://foreman.anim.odw.com.cn/foreman_tasks/tasks/3185a74a-dbe5-4ebe-a74b-31f648c2c88e >>> >>> Tasks: TOP => katello:upgrades:2.2:update_metadata_expire >>> (See full trace by running task with --trace) >>> Updating Expire Metadata for Custom Content >>> >>> [ERROR 2016-04-15 19:08:19 main] Upgrade step update_repository_metadata >>> failed. Check logs for more information. >>> [DEBUG 2016-04-15 19:08:19 main] Exit with status code: 1 (signal was 1) >>> [ERROR 2016-04-15 19:08:19 main] Repeating errors encountered during run: >>> [ERROR 2016-04-15 19:08:19 main] nil >>> >>> -- >> 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. >> > >
5

Do you see errors in the production log on the server?

··· On Tue, May 3, 2016 at 12:47 AM, sinux shen wrote:

I have upgrade katello server and the capsule to 2.4 and when I ran
capsule content synchronize --id 4
I got

capsule content synchronize --id 4
[…]
[100%]
500 Internal Server Error

On Friday, April 15, 2016 at 8:19:59 PM UTC+8, John Mitsch wrote:

Sinux,

Can you see what state the task mentioned (id =
185a74a-dbe5-4ebe-a74b-31f648c2c88e
) is in, and any related errors to it? It looks like a task is trying to
run and is conflicting with a task that has not completed.

John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch

On Fri, Apr 15, 2016 at 7:16 AM, sinux shen sinux...@gmail.com wrote:

I am in the middle of this upgrade, I don’t know if this error impact a
lot or not, but it make me feel a little unsafe as we have around 500 nodes
managed by katello/foreman. can someone give me a hand please.

Thanks

On Friday, April 15, 2016 at 7:15:10 PM UTC+8, sinux shen wrote:

here is the log that I got during the upgrade,

it failed at one of the step and then quit, I don’t know how many steps
it needs to go further, but from our foreman management gui, it seems ok.

from katello-installer log, I have this part that shows the exact error
info as follows:

[ INFO 2016-04-15 19:04:17 main] Upgrade Step:
update_repository_metadata (this may take a while) …
[ERROR 2016-04-15 19:08:19 main] rake aborted!
Required lock is already taken by other running tasks.
Please inspect their state, fix their errors and resume them.

Required lock: read
Conflicts with tasks:

https://foreman.anim.odw.com.cn/foreman_tasks/tasks/3185a74a-dbe5-4ebe-a74b-31f648c2c88e

Tasks: TOP => katello:upgrades:2.2:update_metadata_expire
(See full trace by running task with --trace)
Updating Expire Metadata for Custom Content

[ERROR 2016-04-15 19:08:19 main] Upgrade step
update_repository_metadata failed. Check logs for more information.
[DEBUG 2016-04-15 19:08:19 main] Exit with status code: 1 (signal was 1)
[ERROR 2016-04-15 19:08:19 main] Repeating errors encountered during
run:
[ERROR 2016-04-15 19:08:19 main] nil

–
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.

–
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-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University