Hi, I meet the same issue a month ago. It is because that Ubuntu release 16.04.04 LTS in March 2018, while it is only 16.04.02 LTS when Danube released. There are some of the packages updated from the Ubuntu OS. They are not compatible with Fuel installers' packages.
There are other packages issues when you even resolved this one. The only possible way is to set up a local apt repo with the version 16.04.03 at most. BR, Julien Damon <[email protected]>于2018年4月9日周一 上午11:41写道： > > > OPNFV – Danube 3.0 Fuel install error. > > I am getting this error during the openstack install process. I have > installed OS using fuel many times before on previous Openstack releases, > and never ran into this. > > It says pacemaker can’t install without corosync, but corosync does appear > to be installed. Would anyone know why I’m seeing this error? > > > > Tried this with a single controller and a dual one, same result. Node is > simple KVM, standard OVS VLAN config, with cinder as storage. > > > > This is the command the install script seems to be failing at: > > > > root@node-10:~# /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold > -o APT::Get::AllowUnauthenticated=1 install pacemaker > > Reading package lists... > > Building dependency tree... > > Reading state information... > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > pacemaker : Depends: corosync (>= 2.3.0) but it is not going to be > installed > > E: Unable to correct problems, you have held broken packages. > > root@node-10:~# > > > > Coroysnc appears to be installed passed the required version. > > > > ||/ Name Version > Architecture Description > > > +++-=====================================-=======================-=======================-================================================================================ > > ii corosync 2.3.5-3ubuntu2.1 > amd64 cluster engine daemon and utilities > > root@node-10:~# > > > > > > Puppet log, which is basically the output of the failed command. > > 2018-04-06 14:42:07 > > ERR > > (/Stage[main]/Corosync/Package[pacemaker]/ensure) E: Unable to correct > problems, you have held broken packages. > > 2018-04-06 14:42:07 > > ERR > > (/Stage[main]/Corosync/Package[pacemaker]/ensure) pacemaker : Depends: > corosync (>= 2.3.0) but it is not going to be installed > > 2018-04-06 14:42:07 > > ERR > > (/Stage[main]/Corosync/Package[pacemaker]/ensure) The following packages > have unmet dependencies: > > 2018-04-06 14:42:07 > > ERR > > (/Stage[main]/Corosync/Package[pacemaker]/ensure) > > 2018-04-06 14:42:07 > > ERR > > (/Stage[main]/Corosync/Package[pacemaker]/ensure) The following > information may help to resolve the situation: > > 2018-04-06 14:42:07 > > ERR > > (/Stage[main]/Corosync/Package[pacemaker]/ensure) or been moved out of > Incoming. > > 2018-04-06 14:42:07 > > ERR > > (/Stage[main]/Corosync/Package[pacemaker]/ensure) distribution that some > required packages have not yet been created > > 2018-04-06 14:42:07 > > ERR > > (/Stage[main]/Corosync/Package[pacemaker]/ensure) requested an impossible > situation or if you are using the unstable > > 2018-04-06 14:42:07 > > ERR > > (/Stage[main]/Corosync/Package[pacemaker]/ensure) Some packages could not > be installed. This may mean that you have > > 2018-04-06 14:42:07 > > ERR > > (/Stage[main]/Corosync/Package[pacemaker]/ensure) Reading state > information... > > 2018-04-06 14:42:07 > > ERR > > (/Stage[main]/Corosync/Package[pacemaker]/ensure) Building dependency > tree... > > 2018-04-06 14:42:07 > > ERR > > (/Stage[main]/Corosync/Package[pacemaker]/ensure) change from purged to > present failed: Execution of '/usr/bin/apt-get -q -y -o > DPkg::Options::=--force-confold -o APT::Get::AllowUnauthenticated=1 install > pacemaker' returned 100: Reading package lists... > > > > > _______________________________________________ > opnfv-tech-discuss mailing list > [email protected] > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss >
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
