I have install katello 3.12.3/foreman 1.22.1 with tfm-rubygem-foreman_scc_manager-1.6.2-1.fm1_22.el7.noarch and I can’t login to SUSE account. When I run “Test Connection” I get Connection test failed!
/var/log/foreman/production.log :
2019-09-09T21:25:52 [I|app|fb9dbc11] Started GET “/notification_recipients” for 10.122.1.223 at 2019-09-09 21:25:52 +0200
2019-09-09T21:25:52 [I|app|fb9dbc11] Processing by NotificationRecipientsController#index as JSON
2019-09-09T21:25:52 [I|app|fb9dbc11] Current user set to admin (admin)
2019-09-09T21:25:52 [I|app|fb9dbc11] Completed 200 OK in 9ms (Views: 0.2ms | ActiveRecord: 1.3ms)
2019-09-09T21:25:52 [I|app|4a2a46ce] Started PUT “/scc_accounts/test_connection?scc_account_id=3” for 10.122.1.223 at 2019-09-09 21:25:52 +0200
2019-09-09T21:25:52 [I|app|4a2a46ce] Processing by SccAccountsController#test_connection as JSON
2019-09-09T21:25:52 [I|app|4a2a46ce] Parameters: {“utf8”=>“✓”, “authenticity_token”=>“iecg82VFgADILK9SwjHVXqC1uLa8m0pKEVm7F0mrAK4crarybm15OgjbHA7t9wPOLjgQxlVmy3MWUfm5v9m13g==”, “scc_account”=>{“name”=>“snt”, “login”=>“XXXX”, “password”=>"[FILTERED]", “base_url”=>“https://scc.suse.com”, “interval”=>“never”, “sync_date”=>“2019-09-09T21:25:06”, “organization_id”=>“3”}, “fakepassword”=>"[FILTERED]", “scc_account_id”=>“3”}
2019-09-09T21:25:52 [I|app|4a2a46ce] Current user set to admin (admin)
2019-09-09T21:25:53 [I|app|4a2a46ce] Completed 404 Not Found in 975ms (Views: 0.2ms | ActiveRecord: 2.8ms)
Are there any other logs to check? It’s strange because I can connect to https://scc.suse.com without any problems.
Short answer: Yes.
The plugin creates products and repositories for you. You can use them in content views in much the same way as any other repository.
How can I then use Content Views if there is no activation keys for sles? How can I use this repo from Content Views in zypper repo? Where can I get url?
Can you please check if you can save the Account without testing it first and then try to sync it?
We had some problems in the past, where only the Test-button refused to connect via HTTP-Proxy.