Fixes #37099 - Update repo fixture URL to Pulp hosted for tests #423
ruby.yml
on: pull_request
Rubocop
/
Rubocop
1m 6s
Matrix: Ruby / existing-database
Matrix: Ruby / test
Ruby
/
Existing database suite
0s
Ruby
/
Test suite
0s
Annotations
40 errors
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/yum_sync_test.rb#L18
Failure: test_sync_with_acs
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az735-446/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/yum_sync/sync_with_acs.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 67 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/yum_sync_test.rb:12:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/yum_sync_test.rb#L18
Failure: test_index_erratum_href
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az735-446/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/yum_sync/index_erratum_href.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 32 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/yum_sync_test.rb:12:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/yum_sync_test.rb#L18
Failure: test_optimize_false
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az735-446/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/yum_sync/optimize_false.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 51 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/yum_sync_test.rb:12:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/yum_sync_test.rb#L18
Failure: test_incompatible_mirror_repo_error
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az735-446/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/yum_sync/incompatible_mirror_repo_error.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 24 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/yum_sync_test.rb:12:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/yum_sync_test.rb#L18
Failure: test_sync_mirror_false
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az735-446/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/yum_sync/sync_mirror_false.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 26 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/yum_sync_test.rb:12:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/yum_sync_test.rb#L18
Failure: test_reindex_outdated_erratum
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az735-446/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/yum_sync/reindex_outdated_erratum.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 44 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/yum_sync_test.rb:12:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/yum_sync_test.rb#L18
Failure: test_sync
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az735-446/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/yum_sync/sync.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 26 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/yum_sync_test.rb:12:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/alternate_content_source_refresh_test.rb#L56
Failure: test_yum_refresh_simplified
RuntimeError: Neutered Exception ForemanTasks::TaskError: Task f9ad67ab-0f46-4d42-8fd3-b804c2f6cd76: VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az735-446/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/alternate_content_source_refresh/yum_refresh_simplified.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 36 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
; VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az735-446/pulp/api/v3/acs/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/alternate_content_source_refresh/yum_refresh_simplified.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 36 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.co
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/export_test.rb#L18
Failure: test_export
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az735-446/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/katello/content_view_version/export/export.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 36 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/support/pulp3_support.rb:81:in `create_and_sync'
katello/test/actions/pulp3/orchestration/export_test.rb:13:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/export_test.rb#L18
Failure: test_destroy_exporter
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az735-446/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/katello/content_view_version/export/destroy_exporter.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 33 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/support/pulp3_support.rb:81:in `create_and_sync'
katello/test/actions/pulp3/orchestration/export_test.rb:13:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/repository/repair_test.rb#L18
Failure: test_repair_task_succeeds
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az665-575/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/repository/repair/repair_task_succeeds.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 16 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/repository/repair_test.rb:12:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_with_duplicate_content
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az665-575/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_with_duplicate_content.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 70 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_with_whitelist_name_filter
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az665-575/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_with_whitelist_name_filter.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 57 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_all_no_filter_rules_without_dependency_solving
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az665-575/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_all_no_filter_rules_without_dependency_solving.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 57 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_with_whitelist_min_version_filter
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az665-575/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_with_whitelist_min_version_filter.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 57 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_nonmatching_package_exclusion_filter_copies_everything
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az665-575/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_nonmatching_package_exclusion_filter_copies_everything.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 57 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_with_whitelist_max_version_filter
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az665-575/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_with_whitelist_max_version_filter.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 57 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_with_errata_exclusion_filter
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az665-575/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_with_errata_exclusion_filter.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 57 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_with_errata_inclusion_filter
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az665-575/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_with_errata_inclusion_filter.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 57 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 2.7 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_with_whitelist_name_original_packages_filter
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az665-575/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_with_whitelist_name_original_packages_filter.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 57 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/alternate_content_source_refresh_test.rb#L56
Failure: test_yum_refresh_simplified
RuntimeError: Neutered Exception ForemanTasks::TaskError: Task 265abab4-4e56-4f91-a898-b3904435c2e9: VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az1490-491/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/alternate_content_source_refresh/yum_refresh_simplified.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 36 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
; VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az1490-491/pulp/api/v3/acs/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/alternate_content_source_refresh/yum_refresh_simplified.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 36 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_nonmatching_package_exclusion_filter_copies_everything
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az1490-491/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_nonmatching_package_exclusion_filter_copies_everything.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 57 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_with_whitelist_max_version_filter
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az1490-491/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_with_whitelist_max_version_filter.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 57 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_all_no_filter_rules
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az1490-491/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_all_no_filter_rules.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 57 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_with_errata_exclusion_filter
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az1490-491/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_with_errata_exclusion_filter.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 57 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_with_whitelist_name_filter
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az1490-491/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_with_whitelist_name_filter.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 57 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_copy_duplicated_errata
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az1490-491/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/copy_duplicated_errata.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 179 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_nonmatching_package_includion_filter_copies_no_content
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az1490-491/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_nonmatching_package_includion_filter_copies_no_content.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 52 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_with_duplicate_content
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az1490-491/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_with_duplicate_content.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 70 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 14 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb#L18
Failure: test_yum_copy_with_whitelist_min_version_filter
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az1490-491/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/copy_all_unit_yum_repository/yum_copy_with_whitelist_min_version_filter.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 57 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/copy_all_units_test.rb:110:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 18 on PostgreSQL 13:
katello/test/lib/tasks/pulpcore/repository_vcr_test.rb#L18
Failure: test_correct_repositories_fixes_deleted_library_repo
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az736-207/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/katello/pulp3/repository_task/correct_repositories_fixes_deleted_library_repo.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 20 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/lib/tasks/pulpcore/repository_vcr_test.rb:31:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb#L18
Failure: test_yum_copy_all_no_filter_rules
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az736-207/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/multi_copy_all_unit_yum_repository/yum_copy_all_no_filter_rules.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 56 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb:18:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb#L18
Failure: test_yum_copy_with_duplicate_content
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az736-207/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/multi_copy_all_unit_yum_repository/yum_copy_with_duplicate_content.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 75 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb:18:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb#L18
Failure: test_yum_copy_with_errata_inclusion_filter
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az736-207/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/multi_copy_all_unit_yum_repository/yum_copy_with_errata_inclusion_filter.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 59 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb:18:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb#L18
Failure: test_yum_copy_with_all_duplicate_content_with_dep_solving
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az736-207/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/multi_copy_all_unit_yum_repository/yum_copy_with_all_duplicate_content_with_dep_solving.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 75 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb:18:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb#L18
Failure: test_yum_copy_with_whitelist_name_filter
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az736-207/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/multi_copy_all_unit_yum_repository/yum_copy_with_whitelist_name_filter.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 59 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb:18:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb#L18
Failure: test_yum_copy_nonmatching_package_exclusion_filter_copies_everything
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az736-207/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/multi_copy_all_unit_yum_repository/yum_copy_nonmatching_package_exclusion_filter_copies_everything.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 60 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb:18:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb#L18
Failure: test_yum_copy_with_whitelist_min_version_filter
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az736-207/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/multi_copy_all_unit_yum_repository/yum_copy_with_whitelist_min_version_filter.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 59 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb:18:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb#L18
Failure: test_yum_copy_all_no_filter_rules_with_dependency_solving
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az736-207/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/multi_copy_all_unit_yum_repository/yum_copy_all_no_filter_rules_with_dependency_solving.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 56 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb:18:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Ruby / test:katello - Foreman develop with Ruby 3.0 and Node 18 on PostgreSQL 13:
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb#L18
Failure: test_yum_copy_all_no_filter_rules_without_dependency_solving
RuntimeError: Neutered Exception VCR::Errors::UnhandledHTTPRequestError:
================================================================================
An HTTP request has been made that VCR does not know how to handle:
POST https://fv-az736-207/pulp/api/v3/remotes/rpm/rpm/
VCR is currently using the following cassette:
- /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/multi_copy_all_unit_yum_repository/yum_copy_all_no_filter_rules_without_dependency_solving.yml
- :record => :none
- :match_requests_on => [:method, :path, :params, :body_json]
Under the current configuration VCR can not find a suitable HTTP interaction
to replay and is prevented from recording new requests. There are a few ways
you can deal with this:
* If you're surprised VCR is raising this error
and want insight about how VCR attempted to handle the request,
you can use the debug_logger configuration option to log more details [1].
* You can use the :new_episodes record mode to allow VCR to
record this new request to the existing cassette [2].
* If you want VCR to ignore this request (and others like it), you can
set an `ignore_request` callback [3].
* The current record mode (:none) does not allow requests to be recorded. You
can temporarily change the record mode to :once, delete the cassette file
and re-run your tests to allow the cassette to be recorded with this request [4].
* The cassette contains 56 HTTP interactions that have not been
played back. If your request is non-deterministic, you may need to
change your :match_requests_on cassette option to be more lenient
or use a custom request matcher to allow it to match [5].
[1] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/debug-logging
[2] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/new-episodes
[3] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/configuration/ignore-request
[4] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/record-modes/none
[5] https://www.relishapp.com/vcr/vcr/v/6-2-0/docs/request-matching
================================================================================
katello/app/services/katello/pulp3/service_common.rb:15:in `block in create_remote'
katello/app/services/katello/pulp3/service_common.rb:58:in `reformat_api_exception'
katello/app/services/katello/pulp3/service_common.rb:11:in `create_remote'
katello/app/services/katello/pulp3/repository.rb:72:in `create_remote'
katello/app/lib/actions/pulp3/repository/create_remote.rb:6:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:12:in `block in plan'
katello/app/lib/actions/pulp3/orchestration/repository/create.rb:7:in `plan'
katello/app/lib/actions/middleware/backend_services_check.rb:23:in `plan'
katello/app/lib/actions/middleware/remote_action.rb:9:in `plan'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:20:in `trigger'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:26:in `block in trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:46:in `block in rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:45:in `rails_safe_trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:24:in `trigger_task'
foreman-tasks (9.1.1) lib/foreman_tasks.rb:55:in `sync_task'
katello/test/support/pulp3_support.rb:75:in `create_repo'
katello/test/actions/pulp3/orchestration/multi_copy_all_units_test.rb:18:in `setup'
katello/test/support/vcr.rb:24:in `block in run'
katello/test/support/vcr.rb:23:in `run'
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
Gemfile-ruby-27-node-14-pg-13-foreman-develop-dbseed.lock
Expired
|
5.47 KB |
|
Gemfile-ruby-27-node-14-pg-13-foreman-develop-pluginassetsprecompilekatelloRAILSENVproductionDATABASEURLnulldbnohost.lock
Expired
|
5.47 KB |
|
Gemfile-ruby-27-node-14-pg-13-foreman-develop-testkatello.lock
Expired
|
5.47 KB |
|
Gemfile-ruby-27-node-18-pg-13-foreman-develop-dbseed.lock
Expired
|
5.47 KB |
|
Gemfile-ruby-27-node-18-pg-13-foreman-develop-pluginassetsprecompilekatelloRAILSENVproductionDATABASEURLnulldbnohost.lock
Expired
|
5.47 KB |
|
Gemfile-ruby-27-node-18-pg-13-foreman-develop-testkatello.lock
Expired
|
5.47 KB |
|
Gemfile-ruby-30-node-14-pg-13-foreman-develop-dbseed.lock
Expired
|
5.49 KB |
|
Gemfile-ruby-30-node-14-pg-13-foreman-develop-pluginassetsprecompilekatelloRAILSENVproductionDATABASEURLnulldbnohost.lock
Expired
|
5.49 KB |
|
Gemfile-ruby-30-node-14-pg-13-foreman-develop-testkatello.lock
Expired
|
5.49 KB |
|
Gemfile-ruby-30-node-18-pg-13-foreman-develop-dbseed.lock
Expired
|
5.49 KB |
|
Gemfile-ruby-30-node-18-pg-13-foreman-develop-pluginassetsprecompilekatelloRAILSENVproductionDATABASEURLnulldbnohost.lock
Expired
|
5.49 KB |
|
Gemfile-ruby-30-node-18-pg-13-foreman-develop-testkatello.lock
Expired
|
5.49 KB |
|
Gemfile-theforeman-actions-rubocop-ruby-2.7.lock
Expired
|
2.63 KB |
|
logs-ruby-27-node-14-pg-13-foreman-develop-testkatello
Expired
|
3.4 MB |
|
logs-ruby-27-node-18-pg-13-foreman-develop-testkatello
Expired
|
3.41 MB |
|
logs-ruby-30-node-14-pg-13-foreman-develop-testkatello
Expired
|
3.42 MB |
|
logs-ruby-30-node-18-pg-13-foreman-develop-testkatello
Expired
|
3.4 MB |
|
package-lock-ruby-27-node-14-pg-13-foreman-develop-pluginassetsprecompilekatelloRAILSENVproductionDATABASEURLnulldbnohost.json
Expired
|
307 KB |
|
package-lock-ruby-27-node-14-pg-13-foreman-develop-testkatello.json
Expired
|
307 KB |
|
package-lock-ruby-27-node-18-pg-13-foreman-develop-pluginassetsprecompilekatelloRAILSENVproductionDATABASEURLnulldbnohost.json
Expired
|
324 KB |
|
package-lock-ruby-27-node-18-pg-13-foreman-develop-testkatello.json
Expired
|
324 KB |
|
package-lock-ruby-30-node-14-pg-13-foreman-develop-pluginassetsprecompilekatelloRAILSENVproductionDATABASEURLnulldbnohost.json
Expired
|
307 KB |
|
package-lock-ruby-30-node-14-pg-13-foreman-develop-testkatello.json
Expired
|
307 KB |
|
package-lock-ruby-30-node-18-pg-13-foreman-develop-pluginassetsprecompilekatelloRAILSENVproductionDATABASEURLnulldbnohost.json
Expired
|
324 KB |
|
package-lock-ruby-30-node-18-pg-13-foreman-develop-testkatello.json
Expired
|
324 KB |
|