Skip to content
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

hostname module failing in Scientific Linux 6.5 #8339

Closed
earlruby opened this issue Jul 29, 2014 · 4 comments
Closed

hostname module failing in Scientific Linux 6.5 #8339

earlruby opened this issue Jul 29, 2014 · 4 comments
Labels
bug This issue/PR relates to a bug.

Comments

@earlruby
Copy link

Issue Type:

Bug Report

Ansible Version:

ansible 1.7 (devel b64a5ff) last updated 2014/07/29 09:49:48 (GMT -700)

Environment:

Running from: OS/X 10.9.4
Managing: Scientific Linux 6.5

Summary:

A recent update to the hostname module is causing it to fail for Scientific Linux 6.5 with the error:

msg: Command failed rc=127, out=, err=/bin/sh: hostnamectl: command not found

Scientific Linux 6.5 does not use hostnamectl to set the hostname.

Steps To Reproduce:

I used this command to set the host name on Scientific Linux 6.5. It was working until recently.

  • name: Set the host name
    hostname: name={{ fqdn }}
Expected Results:

I expect the host name to be set on a Scientific Linux 6.5 host.

Actual Results:

The error:

msg: Command failed rc=127, out=, err=/bin/sh: hostnamectl: command not found

@dirtyharrycallahan
Copy link
Contributor

What version of ansible?

@earlruby
Copy link
Author

ansible 1.7 (devel b64a5ff) last updated 2014/07/29 09:49:48 (GMT -700)

@jimi-c jimi-c added P3 labels Jul 29, 2014
mpdehaan added a commit that referenced this issue Aug 4, 2014
Fixes issue #8339 where Scientific Linux incorrectly tries to use Fedora...
@mscherer
Copy link
Contributor

Can this bug be closed, since it seems fixed ?

@mpdehaan
Copy link
Contributor

Hi!

Thanks very much for your interest in Ansible. It sincerely means a lot to us.

On September 26, 2014, due to enormous levels of contribution to the project Ansible decided to reorganize module repos, making it easier
for developers to work on the project and for us to more easily manage new contributions and tickets.

We split modules from the main project off into two repos, http://github.com/ansible/ansible-modules-core and http://github.com/ansible/ansible-modules-extras

If you would still like this ticket attended to, we will need your help in having it reopened in one of the two new repos, and instructions are provided below.

We apologize that we are not able to make this transition happen seamlessly, though this is a one-time change and your help is greatly appreciated --
this will greatly improve velocity going forward.

Both sets of modules will ship with Ansible, though they'll receive slightly different ticket handling.

To locate where a module lives between 'core' and 'extras'

Additionally, should you need more help with this, you can ask questions on:

Thank you very much!

@ansibot ansibot added bug This issue/PR relates to a bug. and removed bug_report labels Mar 6, 2018
@ansible ansible locked and limited conversation to collaborators Apr 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug This issue/PR relates to a bug.
Projects
None yet
Development

No branches or pull requests

6 participants