-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ubuntu 16.04 issues #379
Comments
RabbitMQ |
Hello, We work on Oracle Linux in our environment, and as logic this cookbook supports rhel, fedora. Can you please add 'oracle' as platform as well? ohai|grep platform"platform": "oracle", thanks |
@kulbirsaini30 there is no reason why the basic support shouldn't be there. Can you open another issue for Oracle support and any issues you may have seen? I need to have more than only one person asking for this also, to have another base OS in the support matrix will add another layer of complexity. |
Hi there, i just upgraded Chef to 12.12.0-1 ( amd64 ) from 12.11.1-1 and my log files flood with is there a way to "fix" that manually or is it something that is just broken for me ? |
This is not a support forum.
Take a take at the message, it provides a hint:
HOME environment variable (or HOMEDRIVE and HOMEPATH) must be set and
point to a directory
…On Tue, Feb 7, 2017 at 8:56 PM, akaias ***@***.***> wrote:
Hi there,
i just upgraded Chef to 12.12.0-1 ( amd64 ) from 12.11.1-1
and my log files flood with
opscode-expander.txt
<https://github.com/rabbitmq/chef-cookbook/files/758544/opscode-expander.txt>
is there a way to "fix" that manually or is it something that is just
broken for me ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#379 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAEQuKZC8A0RkVq-Sq0ufvsU7xC8-k_ks5raLBKgaJpZM4IwEzd>
.
--
MK
Staff Software Engineer, Pivotal/RabbitMQ
|
This issue is to track any specific 16.04 issues that are found with this cookbook and 16.04
The text was updated successfully, but these errors were encountered: