[PVE-User] unattended PVE server installation
Vadim Bulst
vadim.bulst at bbz.uni-leipzig.de
Mon Jan 9 19:04:48 CET 2017
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',
}
package { 'open-iscsi':
ensure => 'installed',
provider => 'apt',
}
package { 'proxmox-ve':
ensure => 'installed',
provider => 'apt',
install_options => ['--force-yes','-y'],
require =>
Package['open-iscsi','ksm-control-daemon','systemd-sysv'],
notify => Reboot['rebootafterpveinst'],
}
reboot { 'rebootafterpveinst':
apply => 'finished',
}
}
But no luck eighter!
Proxmox-ve is a virtual package. Shell I try to install them one by one?
I think there is to much interactive configuration going on in these
packages.
Is somebody deploying PVE unattended? What do you use? How things go?
Cheers,
Vadim
Am 09.01.2017 um 15:55 schrieb Jeff Palmer:
> 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 seperate things.
>
> Use your normal unattended install stuff for debian using
> forman/puppet, and assign the host into whatever proxmox group you've
> configured in forman. on the next puppet run, your normal proxmox role
> would handle the installation/configuration of the PVE software.
>
>
>
>
> On Mon, Jan 9, 2017 at 9:03 AM, Vadim Bulst
> <vadim.bulst at bbz.uni-leipzig.de> wrote:
>> I changed the installation term. All packages seemed to be installed but
>> some configured. What can i do to this solved?
>>
>> root at 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 remove and 0 not upgraded.
>> 9 not fully installed or removed.
>> After this operation, 0 B of additional disk space will be used.
>> 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 pve-cluster (--configure):
>> subprocess installed post-installation script returned error exit status 1
>> dpkg: dependency problems prevent configuration of libpve-access-control:
>> libpve-access-control depends on pve-cluster; however:
>> Package pve-cluster is not configured yet.
>>
>> dpkg: error processing package libpve-access-control (--configure):
>> dependency problems - leaving unconfigured
>> dpkg: dependency problems prevent configuration of librados2-perl:
>> librados2-perl depends on libpve-access-control; however:
>> Package libpve-access-control is not configured yet.
>>
>> dpkg: error processing package librados2-perl (--configure):
>> dependency problems - leaving unconfigured
>> dpkg: dependency problems prevent configuration of pve-firewall:
>> pve-firewall depends on pve-cluster; however:
>> Package pve-cluster is not configured yet.
>> pve-firewall depends on libpve-access-control; however:
>> Package libpve-access-control is not configured yet.
>>
>> dpkg: error processing package pve-firewall (--configure):
>> dependency problems - leaving unconfigured
>> dpkg: dependency problems prevent configuration of pve-ha-manager:
>> pve-ha-manager depends on pve-cluster (>= 3.0-17); however:
>> Package pve-cluster is not configured yet.
>>
>> dpkg: error processing package pve-ha-manager (--configure):
>> dependency problems - leaving unconfigured
>> dpkg: dependency problems prevent configuration of qemu-server:
>> qemu-server depends on libpve-access-control; however:
>> Package libpve-access-control is not configured yet.
>> qemu-server depends on pve-cluster; however:
>> Package pve-cluster is not configured yet.
>> qemu-server depends on pve-firewall; however:
>> Package pve-firewall is not configured yet.
>> qemu-server depends on pve-ha-manager; however:
>> Package pve-ha-manager is not configured yet.
>>
>> dpkg: error processing package qemu-server (--configure):
>> dependency problems - leaving unconfigured
>> dpkg: dependency problems prevent configuration of pve-container:
>> pve-container depends on pve-cluster (>= 4.0-8); however:
>> Package pve-cluster is not configured yet.
>> pve-container depends on pve-ha-manager; however:
>> Package pve-ha-manager is not configured yet.
>>
>> dpkg: error processing package pve-container (--configure):
>> dependency problems - leaving unconfigured
>> dpkg: dependency problems prevent configuration of pve-manager:
>> pve-manager depends on qemu-server (>= 1.1-1); however:
>> Package qemu-server is not configured yet.
>> pve-manager depends on pve-cluster (>= 1.0-29); however:
>> Package pve-cluster is not configured yet.
>> pve-manager depends on libpve-access-control (>= 3.0-2); however:
>> Package libpve-access-control is not configured yet.
>> pve-manager depends on librados2-perl; however:
>> Package librados2-perl is not configured yet.
>> pve-manager depends on pve-firewall; however:
>> Package pve-firewall is not configured yet.
>> pve-manager depends on pve-ha-manager; however:
>> Package pve-ha-manager is not configured yet.
>> pve-manager depends on pve-container; however:
>> Package pve-container is not configured yet.
>>
>> dpkg: error processing package pve-manager (--configure):
>> dependency problems - leaving unconfigured
>> dpkg: dependency problems prevent configuration of proxmox-ve:
>> proxmox-ve depends on pve-manager; however:
>> Package pve-manager is not configured yet.
>> proxmox-ve depends on qemu-server; however:
>> Package qemu-server is not configured yet.
>>
>> dpkg: error processing package proxmox-ve (--configure):
>> dependency problems - leaving unconfigured
>> Errors were encountered while processing:
>> pve-cluster
>> libpve-access-control
>> librados2-perl
>> pve-firewall
>> pve-ha-manager
>> qemu-server
>> pve-container
>> pve-manager
>> proxmox-ve
>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>
>> 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 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 and afterwards the Puppet-agent. The Puppet-agent gets
>>>>> installed.
>>>>>
>>>>> "
>>>>>
>>>>> # Install packages for Proxmox PVE
>>>>> /usr/bin/apt-get -y -f remove os-prober
>>>>> sleep 2
>>>>> /usr/bin/apt-get update
>>>>> /usr/bin/apt-get -f -y install
>>>>> /usr/bin/apt-get dist-upgrade
>>>>> /usr/bin/apt-get -y --force-yes proxmox-ve ssh ksm-control-daemon
>>>>> open-iscsi
>>>>> systemd-sysv
>>>> as the log in your other e-mail indicates, this is not a valid apt-get
>>>> call.. you are missing an "install" there, it should be
>>>>
>>>> /usr/sbin/apt-get -y --force-yes proxmox-ve ssh ksm-control-daemon
>>>> open-iscsi
>>>>
>>> as Thomas just pointed out to me, I of course also forgot the "install" ;)
>>>
>>> should be:
>>>
>>> /usr/sbin/apt-get install -y --force-yes proxmox-ve ssh ksm-control-daemon
>>> open-iscsi
>>>
>>> _______________________________________________
>>> pve-user mailing list
>>> pve-user at pve.proxmox.com
>>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user at pve.proxmox.com
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
More information about the pve-user
mailing list