Hi Marco and Fabian,
thanks for your advise.
You are right in term of /etc/hosts - this has to be filled out
correctly. But you still can get your IP via DHCP. This is necessary in
our environment.
I know successfully installed PVE with Foreman and Puppet. Thanks to You
and all others!
On 01/09/2017 07:04 PM, Vadim Bulst wrote:
> Hi Jeff,
>
> i totally agree! I also tried to deploy PVE via Puppet:
>
> class urzpvesrv (
>
> ) inherits urzpvesrv::params {
>
> package { 'systemd-sysv':
> ensure => 'installed',
> provider => 'apt',
> }
> package {
Hi Jeff,
i totally agree! I also tried to deploy PVE via Puppet:
class urzpvesrv (
) inherits urzpvesrv::params {
package { 'systemd-sysv':
ensure => 'installed',
provider => 'apt',
}
package { 'ksm-control-daemon':
ensure => 'installed',
provider => 'apt',
}
Mandi! Vadim Bulst
In chel di` si favelave...
> Setting up pve-cluster (4.0-48) ...
> Job for pve-cluster.service failed. See 'systemctl status
> pve-cluster.service' and 'journalctl -xn' for details.
> invoke-rc.d: initscript pve-cluster, action "start" failed.
> dpkg: error processing package
Vadim,
Not that this helps solve your current issue, but a best practice in
foreman/puppet, is to have the unattended install just do a
bare-bones debian install.. and then puppet handles the actual
installation of the proxmox software. I personally would recommend
doing this as two distinctly
I changed the installation term. All packages seemed to be installed but
some configured. What can i do to this solved?
root@scvirt02:/home/urzadmin# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to
Well I have to apologize. Yeah this is true. I'll change it and give it
another try.
Cheers,
Vadim
Am 09.01.2017 um 13:30 schrieb Fabian Grünbichler:
On Mon, Jan 09, 2017 at 01:26:03PM +0100, Fabian Grünbichler wrote:
see comment inline
On Mon, Jan 09, 2017 at 12:03:02PM +0100, Vadim
On Mon, Jan 09, 2017 at 01:26:03PM +0100, Fabian Grünbichler wrote:
> see comment inline
>
> On Mon, Jan 09, 2017 at 12:03:02PM +0100, Vadim Bulst wrote:
> > Sorry my fault. It was the Debian Jessie howto and not Wheezy. Attached are
> > some logs. Let me know if you need some more.
> >
> > As
see comment inline
On Mon, Jan 09, 2017 at 12:03:02PM +0100, Vadim Bulst wrote:
> Sorry my fault. It was the Debian Jessie howto and not Wheezy. Attached are
> some logs. Let me know if you need some more.
>
> As you may see in syslog i'm calling a finish.sh script which should install
> the PVE
I was sending this mail with attached log - they got cut off. Here the
important lines of /var/log/installer/syslog:
Jan 8 19:24:26 finish-install: info: Running
/usr/lib/finish-install.d/07brltty
Jan 8 19:24:26 finish-install: info: Running
/usr/lib/finish-install.d/07preseed
Jan 8
Sorry my fault. It was the Debian Jessie howto and not Wheezy. Attached
are some logs. Let me know if you need some more.
As you may see in syslog i'm calling a finish.sh script which should
install the PVE and afterwards the Puppet-agent. The Puppet-agent gets
installed.
"
# Install
On Sun, Jan 08, 2017 at 09:48:00PM +0100, Vadim Bulst wrote:
> Dear all,
>
> I'm trying to automate the PVE server installation with Foreman and Puppet
> based on Debian stable. Well - i don't have any luck of installing the
> packages. I use
>
> "apt-get --force-yes -y install proxmox-ve ssh
Dear all,
I'm trying to automate the PVE server installation with Foreman and
Puppet based on Debian stable. Well - i don't have any luck of
installing the packages. I use
"apt-get --force-yes -y install proxmox-ve ssh postfix
ksm-control-daemon open-iscsi systemd-sysv"
seen on
13 matches
Mail list logo
