Yesterday I debugged an installation of a pulp-server F19 node in EC2.
Of course, I hit a Selinux issue[1] which could have been solved by a
simple 'yum update -y' of the affected package. The thing is everyone
would have to do that.
Given the fact ami instances are ephemeral/disposable
Hey guys,
I'm hitting this issue[1] all the time with a userdata script [2].
Based on the error code, sh complains about non-existing command. My
suspicion is some filesystem service isn't running in the time
userdata scripts are evaluated by systemd/cloud-init. I'm unable to
locate the issue,
On Fri, Sep 20, 2013 at 03:45:58PM +0200, milanisko k wrote:
I'm hitting this issue[1] all the time with a userdata script [2].
Based on the error code, sh complains about non-existing command. My
suspicion is some filesystem service isn't running in the time
userdata scripts are evaluated by
On Fri, Sep 20, 2013 at 10:45:35AM +0200, milanisko k wrote:
Let's preserve the planet for our children by more frequent ami respins!
Yeah, I'd like to do this too. We need to get to the point where image
creation is automated and basic smoketests automatically run. Your help
is welcome on this!
done: https://bugzilla.redhat.com/show_bug.cgi?id=1010335
--
milan
2013/9/20 Matthew Miller mat...@fedoraproject.org:
On Fri, Sep 20, 2013 at 03:45:58PM +0200, milanisko k wrote:
I'm hitting this issue[1] all the time with a userdata script [2].
Based on the error code, sh complains about
