[Ovirt-devel] [PATCH ovirt-node] run storage config script under different selinux context

Alan Pevec apevec at gmail.com
Thu Nov 20 21:27:06 UTC 2008

On Thu, Nov 20, 2008 at 10:08 PM, Darryl Pierce <dpierce at redhat.com> wrote:

> Alan Pevec wrote:
> > On Thu, Nov 20, 2008 at 9:24 PM, Darryl Pierce <dpierce at redhat.com
> > <mailto:dpierce at redhat.com>> wrote:
> >
> >     In running this script plus the other for node-image I'm not able to
> get
> >     the firstboot system working.
> >
> >     During boot the firstboot script itself never runs.
> >
> > Is standalone boot entry selected?
> > cat /proc/cmdline
> No, it wasn't booted from the standalone grub entry. I instead let it
> boot normally and fail to detech a server suite instead.
> Restarting and explicitly selecting the standalone option brought up the
> firstboot menu.
> >     When I log in as root and run the firstboot script itself, using both
> >     "service ovirt-firstboot start" and "/etc/init.d/ovirt-firstboot
> start",
> >     I see no output and am dumped directly back to the command prompt.
> >
> >
> > that's how it should behave in managed i.e. non-standalone mode
> The node was booted without a server suite even started, so should have
> come up in standalone mode.

Yeah, it was defined like that in initial discussions but when implementing
I was not able to make this reliable. What if e.g. DHCP or DNS is just
temporarily unavailable? Managed vs Standalone mode must be explicit admin
decision, not at the mercy of the current network status.
Standalone boot entry will be made default on Node ISO and ovirt-flash/-pxe
scripts will get an option to change default boot parameters (patches
pending) so that admin can choose managed vs standalone.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20081120/62fdc388/attachment.htm>

More information about the ovirt-devel mailing list