Im building a Ubuntu Live ISO with all Openstack services installed and configured for a single node setup(all services installed on same node). To build this ISO I'm creating a chroot env. by unwrapping Live Ubuntu ISO. While doing Openstack installation with puppet, puppet is unable to start services in the chroot env.
我正在构建一个Ubuntu Live ISO，其中所有Openstack服务都已安装并配置为单节点设置（所有服务都安装在同一节点上）。为了构建这个ISO，我正在创建一个chroot env。通过展开Live Ubuntu ISO。使用puppet进行Openstack安装时，puppet无法在chroot环境中启动服务。
Eg:
/etc/init.d/mysql status #gives this O/P
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service mysql status
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the status(8) utility, e.g. status mysql
service mysql status
shows no output.
Any pointers will be appreciated :)
任何指针将不胜感激:)
1 个解决方案
#1
0
I have found that puppet is indeed awkward in chroot jails because the gathering of facter facts does not work appropriately (or something in that vein).
我发现傀儡在chroot*里确实很尴尬，因为收集事实并不恰当（或者说是那种情况）。
To the problem at hand, though - you way want to make your service resources use an appropriate provider is Puppet doesn't select the right one, e.g.
但是，对于手头的问题 - 你想让你的服务资源使用合适的提供者是Puppet没有选择正确的提供者，例如
service { "mysql": provider => upstart }
or even
甚至
Service { provider => upstart } # resource default at global scope
See the list of service providers. Note how Puppet is supposed to select the appropriate one on its own, so this may indeed be a problem with the chroot and how it skews facter's deliberations.
请参阅服务提供商列表。注意Puppet应该如何自己选择合适的一个，所以这可能确实是chroot的问题以及它如何扭曲了facter的审议。
#1
0
I have found that puppet is indeed awkward in chroot jails because the gathering of facter facts does not work appropriately (or something in that vein).
我发现傀儡在chroot*里确实很尴尬，因为收集事实并不恰当（或者说是那种情况）。
To the problem at hand, though - you way want to make your service resources use an appropriate provider is Puppet doesn't select the right one, e.g.
但是，对于手头的问题 - 你想让你的服务资源使用合适的提供者是Puppet没有选择正确的提供者，例如
service { "mysql": provider => upstart }
or even
甚至
Service { provider => upstart } # resource default at global scope
See the list of service providers. Note how Puppet is supposed to select the appropriate one on its own, so this may indeed be a problem with the chroot and how it skews facter's deliberations.
请参阅服务提供商列表。注意Puppet应该如何自己选择合适的一个，所以这可能确实是chroot的问题以及它如何扭曲了facter的审议。