Skip to content

add support for Amazon Linux as an operating system#15

Closed
brettporter wants to merge 1 commit intopuppetlabs:masterfrom
maestrodev:amazon-linux
Closed

add support for Amazon Linux as an operating system#15
brettporter wants to merge 1 commit intopuppetlabs:masterfrom
maestrodev:amazon-linux

Conversation

@brettporter
Copy link
Copy Markdown
Contributor

The Amazon Linux AMI on EC2 reports OS as "Amazon" to facter - it is CentOS based.

@cprice404
Copy link
Copy Markdown

I fired up a CentOS 6.2 AMI and ran facter -- I get these values:

operatingsystem => CentOS
operatingsystemrelease => 6.2
osfamily => RedHat

Also, after merging pull request #14, we've switched over to using osfamily for this, so hopefully that will fix it for you even on the AMI that was reporting that value for 'operatingsystem'.

If this is still causing a problem for you, can you please re-open and let us know a few more details about the version of facter and the AMI?

Thanks!

@cprice404 cprice404 closed this Oct 19, 2012
@brettporter
Copy link
Copy Markdown
Contributor Author

It doesn't look like that image is covered by the change:

$ facter | grep "^o"
operatingsystem => Amazon
operatingsystemrelease => 3.2.30-49.59.amzn1.x86_64
osfamily => Linux

I don't recall where I encountered this the first time, but I got the above by starting the Amazon Linux AMI today (ami-1624987f), not the RedHat/CentOS AMIs. I should have said it is yum-based, rather than CentOS-based. I'm not sure where it is derived from, but the redhat package style will work on it.

@cprice404
Copy link
Copy Markdown

Interesting, that is wacky that they would do that. I almost wonder if we should file a ticket against facter relating to this.

In any case, if the pull req that I merged is not covering your use case then we should re-open a variant of your original one. If you have a specific public AMI id that we could use to experiment with, that would be helpful.

Please feel free to reopen the pull or open a new one if you get a chance to rebase your fix against the recent change!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants