Closed yanxinyuan closed 8 years ago
+1 This will also lead to failures in all air-gapped and vpc environments w/o access to internet or doing some odd routing gymnastics.
Finally, after i changing the routing policy of my machine by adding packagecloud.io(50.97.198.58) to our router, this issue has been avoided.
Cookbook version
runit (3.0.0)
Chef-client version
Chef: 12.13.37
Platform Details
Centos 6
Scenario:
After i upload the push-jobs cookbook to my server, and when i use chef-client command to configure the node, it occurs below error. As i know it's a network issue, but this is a network policy of my company, I can access the packagecloud.io by web, but not with ping, do you have any way to avoid this error ?
Recipe: yum-epel::default * yum_repository[epel] action create * template[/etc/yum.repos.d/epel.repo] action create (up to date) * execute[yum clean metadata epel] action nothing (skipped due to action :nothing) * execute[yum-makecache-epel] action nothing (skipped due to action :nothing) * ruby_block[yum-cache-reload-epel] action nothing (skipped due to action :nothing) (up to date) Recipe: runit::default * packagecloud_repo[imeyer/runit] action add
Steps to Reproduce:
Expected Result:
install push-jobs successfully.
Actual Result:
failed with the whole error. [root@delta opt]# chef-client Starting Chef Client, version 12.13.37 resolving cookbooks for run list: ["push-jobs"] Synchronizing Cookbooks:
Recipe: push-jobs::config
push_jobs_service_runit[push-jobs] action start[2016-09-27T18:54:51+08:00] WARN: Cloning resource attributes for runit_service[chef-push-jobs-client] from prior resource (CHEF-3694) Previous runit_service[chef-push-jobs-client]: /var/chef/cache/cookbooks/push-jobs/resources/service_runit.rb:87:in
create_init' Current runit_service[chef-push-jobs-client]: /var/chef/cache/cookbooks/push-jobs/resources/service_runit.rb:28:in
block in class_from_file' at /var/chef/cache/cookbooks/push-jobs/resources/service_runit.rb:28:in `block in class_from_file'Recipe: runit::default
Recipe: yum-epel::default * yum_repository[epel] action create * template[/etc/yum.repos.d/epel.repo] action create (up to date) * execute[yum clean metadata epel] action nothing (skipped due to action :nothing) * execute[yum-makecache-epel] action nothing (skipped due to action :nothing) * ruby_block[yum-cache-reload-epel] action nothing (skipped due to action :nothing) (up to date) Recipe: runit::default * packagecloud_repo[imeyer/runit] action add
Running handlers: [2016-09-27T18:54:54+08:00] ERROR: Running exception handlers Running handlers complete [2016-09-27T18:54:54+08:00] ERROR: Exception handlers complete Chef Client failed. 0 resources updated in 09 seconds [2016-09-27T18:54:55+08:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out [2016-09-27T18:54:55+08:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report [2016-09-27T18:54:55+08:00] ERROR: push_jobs_service_runit[push-jobs](push-jobs::service line 29) had an error: Errno::ENETUNREACH: packagecloud_repo[imeyer/runit](runit::default line 36) had an error: Errno::ENETUNREACH: Network is unreachable - connect(2) for "packagecloud.io" port 443 [2016-09-27T18:54:55+08:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)