I did some searching/grepping and it looks like the azure plugin the culprit:
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_azure_rm-2.1.2/lib/foreman_azure_rm/engine.rb: Faraday::default_adapter=:excon
so anyone that has that plugin installed would likely hit this. Let me see if can make our code compatible with both excon and net_http.
1 Like
Should I remove it as it only for testing?
@techietubby if you’ve not created any azure compute resources, sure!
foreman-installer --no-enable-foreman-plugin-azure --no-enable-foreman-cli-azure
Preparing installation Done
Executing: foreman-rake upgrade:run
Upgrade Step 1/3: katello:correct_repositories. This may take a long while.
Processing Repository 1/1: Centos-7-repo (1)
Repository 1 Missing
Recreating 1
Failed upgrade task: katello:correct_repositories, see logs for more information.
Upgrade Step 2/3: katello:correct_puppet_environments. This may take a long while.
Upgrade Step 3/3: katello:clean_backend_objects. This may take a long while.
0 orphaned consumer id(s) found in candlepin.
Candlepin orphaned consumers:
0 orphaned consumer id(s) found in pulp.
Pulp orphaned consumers:
foreman-rake upgrade:run finished successfully!
Success!
Foreman is running at https://foreman.bluefinch.local
To install an additional Foreman proxy on separate machine continue by running:
foreman-proxy-certs-generate --foreman-proxy-fqdn “$FOREMAN_PROXY” --certs-tar “/root/$FOREMAN_PROXY-certs.tar”
Foreman Proxy is running at https://foreman.bluefinch.local:9090
The full log is at /var/log/foreman-installer/katello.log
I then tried to create a new REPO and I still get the Faraday error? I can reinstall without the azure stuff as this is a crash-and-burn machine with snapshots?
I’m not sure that running again with --no-enable-foreman-cli-azure actually uninstalls the plugins themselves, you might have to do that manually.
A fresh install might be best?
I opened an issue:
and a PR:
Katello:master
← jlsherrill:30746
opened 03:26PM - 31 Aug 20 UTC
faraday adapter, in case the azure plugin is installed
We will get that patch into 3.16.1, in the meantime anyone hitting this could try to apply the patch yourself, or install without the azure plugin
1 Like
Justin, you are a superstar!!
I reinstalled without Azure and it now wors:
yum -y localinstall https://yum.theforeman.org/releases/2.2/el7/x86_64/foreman-release-2.2.0-0.3.rc1.el7.noarch.rpm
yum -y localinstall https://fedorapeople.org/groups/katello/releases/yum/3.17/katello/el7/x86_64/katello-repos-latest.rpm
yum -y install foreman-installer
yum install python2-django tfm-rubygem-hammer_cli_foreman puppet-agent-oauth pulp-server pulp-katello -y --nogpg
yum install katello -y
foreman-installer --scenario katello --foreman-initial-admin-username admin --foreman-initial-admin-password ‘admin’ --enable-foreman-cli-openscap --enable-foreman-compute-libvirt --enable-foreman-plugin-ansible --enable-foreman-proxy-plugin-ansible --enable-foreman-cli-ansible --enable-foreman-plugin-bootdisk --enable-foreman-plugin-openscap --enable-foreman-plugin-remote-execution --enable-foreman-proxy-plugin-remote-execution-ssh --enable-foreman-proxy-plugin-openscap --enable-foreman-compute-ec2 --enable-foreman-plugin-remote-execution-cockpit --enable-foreman-cli-remote-execution --enable-foreman-plugin-bootdisk
yum install foreman-console -y
yum install -y openscap openscap-daemon openscap-scanner openscap puppet-foreman_scap_client-utils
foreman-rake foreman_openscap:bulk_upload:default