Hi Daniel,

The reason of this problem is a recent change in ubuntu repositories, systemd 
package was moved from proposed repository to updates 
https://lists.ubuntu.com/archives/trusty-changes/2016-December/023368.html
It leads to situation when this package is installed and puppet detects init 
system as being systemd and is trying to use systemctl to start services. It is 
now not only problem of fuel: 
https://groups.google.com/forum/#!msg/ansible-devel/dCEYP4Ojs2Q/uICWPJp4CgAJ

There is already fix merged to stable/mitaka branch: 
https://review.openstack.org/#/c/409112/ which adds systemd-shim package which 
prevent install systemd. There are two options now to deploy successfully with 
colorado 3.0 ISO:

1) Use local mirrors included on ISO as described here: 
http://artifacts.opnfv.org/fuel/colorado/3.0/docs/installationprocedure/index.html#optional-set-local-mirror-repos
2) Before deployment user can add  systemd-shim package to initial list of 
packages on Environment>Settings>General page.

Michal
> On 11 Dec 2016, at 15:04, Daniel Smith <daniel.sm...@ericsson.com> wrote:
> 
> Hello.
>  
> Reporting that the latest release of FUEL Colorado 3.0 does not work. 
>  
> Symptoms include:
> -        Someone has added an “atop” command in a OSNAILFACTER plugin that is 
> being executed at the end of installation – this Bad “error’code causes the 
> installation to fail and deployment to cease
> -        There are additional “tools” directories that don’t exist in the 
> upstream version of FUEL ( built from source), so it seem that we have done 
> some “post build modifications”.
>  
> Looking at the CI Pipeline, there is an issue there, since the build are 
> passing, but the deployment (even though they says they are) in fact on the 
> baremetal system do not pass.
>  
>  
> For those of you experiencing FUEL failed installations, I would suggest 
> going back to 2.0 release, it works better.
>  
> Daniel
>  
> _______________________________________________
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

_______________________________________________
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to