# install-suse-cloud & proxy

**URL:** <https://forums.suse.com/t/install-suse-cloud-proxy/27187>\
**Category:** SUSE OpenStack Cloud\
**Created:** [June 24, 2015, 6:33pm UTC](https://forums.suse.com/t/install-suse-cloud-proxy/27187 "2015-06-24T18:33:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![quentinsourice](https://avatars.discourse-cdn.com/v4/letter/q/e47774/32.png) [@quentinsourice](https://forums.suse.com/u/quentinsourice)\
**Post date:** [June 24, 2015, 6:33pm UTC](https://forums.suse.com/t/install-suse-cloud-proxy/27187/1 "2015-06-24T18:33:48Z")

</div>

Hi,

I’m deploying a Suse OpenStack Cloud 5 but facing a proxy problem.

If I activate my proxy settings, without forgetting to add my administration server’s ip & hostname in the “no proxy” part :  
 → The install-suse-cloud script seems to avoid the “no proxy” configuration in the chef “knife” part :

`Where should I put the config file? [/root/.chef/knife.rb]
Please enter the chef server URL: [http://suse01a.local:4000]
Please enter a clientname for the new client: [root]
Please enter the existing admin clientname: [chef-webui]
Please enter the location of the existing admin client's private key: [/etc/chef/webui.pem]
Please enter the validation clientname: [chef-validator]
Please enter the location of the validation key: [/etc/chef/validation.pem]
Please enter the path to a chef repository (or leave blank): Creating initial API user...
ERROR: Server returned error for http://suse01a.local:4000/clients, retrying 1/5 in 4s`

From this step, a wget [http://suse01a.local:4000/clients](http://suse01a.local:4000/clients) will return a good request

If I deactivate my proxy settings, the knife part is ok but as I’m running without my proxy, in this case zypper seems to fail somewhere…

`[2015-06-24T17:32:04+02:00] ERROR: Running exception handlers
[2015-06-24T17:32:04+02:00] FATAL: Saving node information to /var/chef/cache/failed-run-data.json
[2015-06-24T17:32:04+02:00] ERROR: Exception handlers complete
[2015-06-24T17:32:04+02:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2015-06-24T17:32:04+02:00] FATAL: Chef::Exceptions::Package: package[rsyslog] (logging::server line 17) had an error: Chef::Exceptions::Package: zypper failed - #<Process::Status: pid 4438 exit 4>!
`

Somebody ?

Thank you by advance,  
Quentin

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\
**Post date:** [June 29, 2015, 7:30am UTC](https://forums.suse.com/t/install-suse-cloud-proxy/27187/2 "2015-06-29T07:30:12Z")

</div>

quentinsourice,

It appears that in the past few days you have not received a response to your  
posting. That concerns us, and has triggered this automated reply.

Has your issue been resolved? If not, you might try one of the following options:

- Visit [http://www.suse.com/support](http://www.suse.com/support) and search the knowledgebase and/or check all  
the other support options available.
- You could also try posting your message again. Make sure it is posted in the  
correct newsgroup. ([http://forums.suse.com](http://forums.suse.com))

Be sure to read the forum FAQ about what to expect in the way of responses:  
[http://forums.suse.com/faq.php](http://forums.suse.com/faq.php)

If this is a reply to a duplicate posting, please ignore and accept our apologies  
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your SUSE Forums Team  
[http://forums.suse.com](http://forums.suse.com)

---

<div class="post-metadata">

**Author:** ![jniedergang](https://avatars.discourse-cdn.com/v4/letter/j/ebca7d/32.png) [@jniedergang](https://forums.suse.com/u/jniedergang)\
**Post date:** [June 29, 2015, 11:38am UTC](https://forums.suse.com/t/install-suse-cloud-proxy/27187/3 "2015-06-29T11:38:31Z")

</div>

Hello Quentin,

It looks like you have a problem with the access to repositories set on your admin node.  
How do you provision repositories to your SUSE Cloud admin installation? (SMT, SUSE Manager…?)  
What is displayed in /etc/crowbar/provisioner.json ?

Thank you

[QUOTE=quentinsourice;28527]Hi,

I’m deploying a Suse OpenStack Cloud 5 but facing a proxy problem.

If I activate my proxy settings, without forgetting to add my administration server’s ip & hostname in the “no proxy” part :  
 → The install-suse-cloud script seems to avoid the “no proxy” configuration in the chef “knife” part :

`Where should I put the config file? [/root/.chef/knife.rb]
Please enter the chef server URL: [http://suse01a.local:4000]
Please enter a clientname for the new client: [root]
Please enter the existing admin clientname: [chef-webui]
Please enter the location of the existing admin client's private key: [/etc/chef/webui.pem]
Please enter the validation clientname: [chef-validator]
Please enter the location of the validation key: [/etc/chef/validation.pem]
Please enter the path to a chef repository (or leave blank): Creating initial API user...
ERROR: Server returned error for http://suse01a.local:4000/clients, retrying 1/5 in 4s`

From this step, a wget [http://suse01a.local:4000/clients](http://suse01a.local:4000/clients) will return a good request

If I deactivate my proxy settings, the knife part is ok but as I’m running without my proxy, in this case zypper seems to fail somewhere…

`[2015-06-24T17:32:04+02:00] ERROR: Running exception handlers
[2015-06-24T17:32:04+02:00] FATAL: Saving node information to /var/chef/cache/failed-run-data.json
[2015-06-24T17:32:04+02:00] ERROR: Exception handlers complete
[2015-06-24T17:32:04+02:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2015-06-24T17:32:04+02:00] FATAL: Chef::Exceptions::Package: package[rsyslog] (logging::server line 17) had an error: Chef::Exceptions::Package: zypper failed - #<Process::Status: pid 4438 exit 4>!
`

Somebody ?

Thank you by advance,  
Quentin[/QUOTE]
