[StarCluster] Disable Selinux not sticking

[Stephen Smith]

I'm using CentOS7 on a custom AMI.  I did find and change the other 
location for selinux configuration - thank you.

Interestingly, I haven't been able to launch the cluster because 
StarCluster is now saying the keypair I have always used, does not reside 
in the correct region.  Which is not the case, but I went ahead and 
created a new keypair several different ways, manually and through the EC2

console, both had the same issue. 

Thinking this was a configuration file issue with StarCluster, I 
regenerated a template configuration file and now when I go and try to 
create a cluster, with any of my new or previously working keypairs, 
Starcluster says there is a fingerprint error.  The local fingerprint is 
correct, but StarCluster shows that the keypair fingerprint is incorrect 
and shows it as the same keypair fingerprint value for all of my keypairs.

 Which seems odd. 

Knowing my level of Linux knowledge, it could be something simple that I 
have misconfigured.  Any thoughts?

Thanks,
Stephen




From:   "MacMullan, Hugh" <hughmac at wharton.upenn.edu>
To:     Stephen Smith <stephen.smith at electrolux.com>, 
"starcluster at mit.edu" <starcluster at mit.edu>
Date:   02/26/2015 02:01 PM
Subject:        RE: [StarCluster] Disable Selinux not sticking



I don't think StarCluster plays with SELINUX at all. Is this a custom AMI 
of your own? Disabling selinux depends on the OS a bit I think? What OS?
 
I've found two places to do this in CentOS 7:
 
/etc/selinux/config
/etc/sysconfig/selinux
 
Not sure which overrides the other, but making sure they're both ' 
SELINUX=disabled' seems to do the trick.
 
-Hugh
 
From: starcluster-bounces at mit.edu [mailto:starcluster-bounces at mit.edu] On 
Behalf Of Stephen Smith
Sent: Thursday, February 26, 2015 1:56 PM
To: starcluster at mit.edu
Subject: [StarCluster] Disable Selinux not sticking
 
Hello, 

On my base AMI for StarCluster, I have set selinux=disabled, but when I 
launch a multi node cluster, the master/node images have selinux set to 
enabled by default.  Is this something that is being modified by 
StarCluster and if it is, how do I disable this as it seems to be over 
riding the base AMI image? 

Thanks in advance, 
Stephen 


=========================
=========================
===================== 
This e-mail and any attachments may contain information which is 
confidential, privileged, proprietary or otherwise protected by law. The 
information is solely intended for the named addressee (or a person 
responsible for delivering it to the addressee). If you are not the 
intended recipient of this message, you are not authorized to read, print,

retain, copy or disseminate this message or any part of it. If you have 
received this e-mail in error, please notify the sender immediately by 
return e-mail and delete it from your computer. 
=----==-====-=======-============-====================-
==================== 
  ­­ 

=======================================================================
This e-mail and any attachments may contain information which is
confidential, privileged, proprietary or otherwise protected by law.
The information is solely intended for the named addressee (or a person
responsible for delivering it to the addressee).  If you are not the
intended recipient of this message, you are not authorized to read,
print, retain, copy or disseminate this message or any part of it.
If you have received this e-mail in error, please notify the sender
immediately by return e-mail and delete it from your computer.
=----==-====-=======-============-====================-==================== 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/starcluster/attachments/20150227/f34a5543/attachment.htm