Re: [openstack-dev] [puppet] compatibility of puppet upstream modules
Thanks Matt’s, I was able to get system to vanilla state again ….
And also isolated initial problem,
my first puppet deployment failed on following error:
Debug: Executing '/usr/bin/openstack image list --quiet --format csv --long'
Debug: Executing '/usr/bin/openstack image create --format shell cirros
--public --container-format=bare --disk-format=qcow2
--copy-from=http://download.cirros-cloud
.net/0.3.4/cirros-0.3.4-x86_64-disk.img'
Error: Execution of '/usr/bin/openstack image create --format shell cirros
--public --container-format=bare --disk-format=qcow2
--copy-from=http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img'
returned 1: 400 Bad Request: The HTTP URL is invalid. (HTTP 400)
Error: /Stage[main]/Main/Glance_image[cirros]/ensure: change from absent to
present failed: Execution of '/usr/bin/openstack image create --format shell
cirros --public --container-format=bare --disk-format=qcow2
--copy-from=http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img'
returned 1: 400 Bad Request: The HTTP URL is invalid. (HTTP 400)
which is caused by “glance not able to download image when behind proxy” (even
when properly configured in .bashrc – http_proxy, https_proxy, no_proxy)
at least what I found about this so far is that in other deployment tools it’s
handled by some additional config to skip that part:
like RDO
https://bugzilla.redhat.com/show_bug.cgi?id=1147716
or store images locally before “image create” is called like from devstack:
2016-02-01 09:45:59.709 | + for image_url in '${IMAGE_URLS//,/ }'
2016-02-01 09:45:59.709 | + upload_image
http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-uec.tar.gz
…
2016-02-01 09:45:59.894 | + '[' -n
/home2/openstack/devstack/files/images/cirros-0.3.4-x86_64-uec/cirros-0.3.4-x86_64-vmlinuz
']'
2016-02-01 09:45:59.894 | ++ openstack --os-cloud=devstack-admin image create
cirros-0.3.4-x86_64-uec-kernel --public --container-format aki --disk-format aki
Is there any known way how to get puppet deployments working on systems behind
proxy ?
Thanks a lot,
Michal
From: Matt Fischer [mailto:m...@mattfischer.com]
Sent: Thursday, February 04, 2016 7:12 PM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [puppet] compatibility of puppet upstream modules
If you can't isolate the exact thing you need to get cleaned up here it can be
difficult to unwind. You'll either need to read the code to see what's
triggering the db setup (which is probably the package installs) or start on a
clean box. I'd recommend the latter.
On Thu, Feb 4, 2016 at 10:35 AM, Ptacek, MichalX
<michalx.pta...@intel.com<mailto:michalx.pta...@intel.com>> wrote:
Hi Emilien,
It seems that keystone database is not populated, because of something, which
happened on previous runs (e.g. some packages installation),
Following rows are visible just in log from first attempt
Debug: Executing '/usr/bin/mysql -e CREATE USER 'keystone'@'127.0.0.1'
IDENTIFIED BY PASSWORD '*936E8F7AB2E21B47F6C9A7E5D9FE14DBA2255E5A''
Debug: Executing '/usr/bin/mysql -e GRANT USAGE ON *.* TO
'keystone'@'127.0.0.1' WITH MAX_USER_CONNECTIONS 0 MAX_CONNECTIONS_PER_HOUR 0
MAX_QUERIES_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0'
….
….
I tried to clean databases & uninstall packages installed during deployment,
but maybe I miss something as it simply doesn’t work ☺
Is there any procedure, how can I restore system to “vanilla state” before
puppet modules installation ?
It looks to me that when deployment failed, it’s very difficult to “unstack” it
Thanks in advance,
Michal
From: Ptacek, MichalX
Sent: Thursday, February 04, 2016 11:14 AM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: RE: [openstack-dev] [puppet] compatibility of puppet upstream modules
-Original Message-
From: Emilien Macchi [mailto:emil...@redhat.com]
Sent: Thursday, February 04, 2016 10:06 AM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [puppet] compatibility of puppet upstream modules
On 02/03/2016 04:03 PM, Ptacek, MichalX wrote:
> Hi all,
>
>
>
> I have one general question,
>
> currently I am deploying liberty openstack as described in
> https://wiki.openstack.org/wiki/Puppet/Deploy
>
> Unfortunately puppet modules specified in
> puppet-openstack-integration/Puppetfile are not compatible
Did you take the file from stable/liberty branch?
https://github.com/openstack/puppet-openstack-integration/tree/stable/liberty
[Michal Ptacek] I am deploying scenario003 with stable/liberty
>
> and some are also missing as visible from following output of “puppet
> module list”
>
Re: [openstack-dev] [puppet] compatibility of puppet upstream modules
I'm not sure tbh, we don't have to deal with a proxy, but why not just
comment this part out for now?
Please file a bug on this against puppet-glance if there is a config option
we could add.
On Feb 5, 2016 4:59 AM, "Ptacek, MichalX" <michalx.pta...@intel.com> wrote:
> Thanks Matt’s, I was able to get system to vanilla state again ….
>
> And also isolated initial problem,
>
> my first puppet deployment failed on following error:
>
>
>
> Debug: Executing '/usr/bin/openstack image list --quiet --format csv
> --long'
>
> Debug: Executing '/usr/bin/openstack image create --format shell cirros
> --public --container-format=bare --disk-format=qcow2 --copy-from=
> http://download.cirros-cloud
>
> .net/0.3.4/cirros-0.3.4-x86_64-disk.img'
>
> Error: Execution of '/usr/bin/openstack image create --format shell cirros
> --public --container-format=bare --disk-format=qcow2 --copy-from=
> http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img'
> returned 1: 400 Bad Request: The HTTP URL is invalid. (HTTP 400)
>
> Error: /Stage[main]/Main/Glance_image[cirros]/ensure: change from absent
> to present failed: Execution of '/usr/bin/openstack image create --format
> shell cirros --public --container-format=bare --disk-format=qcow2
> --copy-from=
> http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img'
> returned 1: 400 Bad Request: The HTTP URL is invalid. (HTTP 400)
>
>
>
> *which is caused by “glance not able to download image when behind proxy”
> (even when properly configured in .bashrc – http_proxy, https_proxy,
> no_proxy)*
>
> at least what I found about this so far is that in other deployment tools
> it’s handled by some additional config to skip that part:
>
> like RDO
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1147716
>
> or store images locally before “image create” is called like from devstack:
>
>
>
> 2016-02-01 09:45:59.709 | + for image_url in '${IMAGE_URLS//,/ }'
>
> 2016-02-01 09:45:59.709 | + upload_image
> http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-uec.tar.gz
>
> …
>
> 2016-02-01 09:45:59.894 | + '[' -n
> /home2/openstack/devstack/files/images/cirros-0.3.4-x86_64-uec/cirros-0.3.4-x86_64-vmlinuz
> ']'
>
> 2016-02-01 09:45:59.894 | ++ openstack --os-cloud=devstack-admin image
> create cirros-0.3.4-x86_64-uec-kernel --public --container-format aki
> --disk-format aki
>
>
>
> Is there any known way how to get puppet deployments working on systems
> behind proxy ?
>
>
>
> Thanks a lot,
>
> Michal
>
>
>
>
>
>
>
> *From:* Matt Fischer [mailto:m...@mattfischer.com]
> *Sent:* Thursday, February 04, 2016 7:12 PM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [puppet] compatibility of puppet upstream
> modules
>
>
>
> If you can't isolate the exact thing you need to get cleaned up here it
> can be difficult to unwind. You'll either need to read the code to see
> what's triggering the db setup (which is probably the package installs) or
> start on a clean box. I'd recommend the latter.
>
>
>
> On Thu, Feb 4, 2016 at 10:35 AM, Ptacek, MichalX <michalx.pta...@intel.com>
> wrote:
>
> Hi Emilien,
>
>
>
> It seems that keystone database is not populated, because of something,
> which happened on previous runs (e.g. some packages installation),
>
>
>
> Following rows are visible just in log from first attempt
>
> Debug: Executing '/usr/bin/mysql -e CREATE USER 'keystone'@'127.0.0.1'
> IDENTIFIED BY PASSWORD '*936E8F7AB2E21B47F6C9A7E5D9FE14DBA2255E5A''
>
> Debug: Executing '/usr/bin/mysql -e GRANT USAGE ON *.* TO
> 'keystone'@'127.0.0.1'
> WITH MAX_USER_CONNECTIONS 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_QUERIES_PER_HOUR
> 0 MAX_UPDATES_PER_HOUR 0'
>
> ….
>
> ….
>
> I tried to clean databases & uninstall packages installed during
> deployment, but maybe I miss something as it simply doesn’t work J
>
>
>
> Is there any procedure, how can I restore system to “vanilla state” before
> puppet modules installation ?
>
> It looks to me that when deployment failed, it’s very difficult to
> “unstack” it
>
>
>
> Thanks in advance,
>
> Michal
>
>
>
> *From:* Ptacek, MichalX
> *Sent:* Thursday, February 04, 2016 11:14 AM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* RE: [openstack-dev] [puppet] compatibility of puppet upstream
> modules
>
>
>
>
>
>
>
> -Original Message-
> From: Emilien Macchi [mailto:emil...@redhat.com &
Re: [openstack-dev] [puppet] compatibility of puppet upstream modules
-Original Message- From: Emilien Macchi [mailto:emil...@redhat.com] Sent: Thursday, February 04, 2016 10:06 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [puppet] compatibility of puppet upstream modules On 02/03/2016 04:03 PM, Ptacek, MichalX wrote: > Hi all, > > > > I have one general question, > > currently I am deploying liberty openstack as described in > https://wiki.openstack.org/wiki/Puppet/Deploy > > Unfortunately puppet modules specified in > puppet-openstack-integration/Puppetfile are not compatible Did you take the file from stable/liberty branch? https://github.com/openstack/puppet-openstack-integration/tree/stable/liberty [Michal Ptacek] I am deploying scenario003 with stable/liberty > > and some are also missing as visible from following output of “puppet > module list” > > > > Warning: Setting templatedir is deprecated. See > http://links.puppetlabs.com/env-settings-deprecations > >(at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in > `issue_deprecation_warning') > > Warning: Module 'openstack-openstacklib' (v7.0.0) fails to meet some > dependencies: > > 'openstack-barbican' (v0.0.1) requires 'openstack-openstacklib' > (>=6.0.0 <7.0.0) > > 'openstack-zaqar' (v0.0.1) requires 'openstack-openstacklib' > (>=6.0.0 > <7.0.0) > > Warning: Module 'puppetlabs-postgresql' (v4.4.2) fails to meet some > dependencies: > > 'openstack-openstacklib' (v7.0.0) requires 'puppetlabs-postgresql' > (>=3.3.0 <4.0.0) > > Warning: Missing dependency 'deric-storm': > > 'openstack-monasca' (v1.0.0) requires 'deric-storm' (>=0.0.1 <1.0.0) > > Warning: Missing dependency 'deric-zookeeper': > > 'openstack-monasca' (v1.0.0) requires 'deric-zookeeper' (>=0.0.1 > <1.0.0) > > Warning: Missing dependency 'dprince-qpid': > > 'openstack-cinder' (v7.0.0) requires 'dprince-qpid' (>=1.0.0 <2.0.0) > > 'openstack-manila' (v7.0.0) requires 'dprince-qpid' (>=1.0.0 <2.0.0) > > 'openstack-nova' (v7.0.0) requires 'dprince-qpid' (>=1.0.0 <2.0.0) > > Warning: Missing dependency 'jdowning-influxdb': > > 'openstack-monasca' (v1.0.0) requires 'jdowning-influxdb' (>=0.3.0 > <1.0.0) > > Warning: Missing dependency 'opentable-kafka': > > 'openstack-monasca' (v1.0.0) requires 'opentable-kafka' (>=1.0.0 > <2.0.0) > > Warning: Missing dependency 'puppetlabs-stdlib': > > 'antonlindstrom-powerdns' (v0.0.5) requires 'puppetlabs-stdlib' (>= > 0.0.0) > > Warning: Missing dependency 'puppetlabs-corosync': > > 'openstack-openstack_extras' (v7.0.0) requires 'puppetlabs-corosync' > (>=0.1.0 <1.0.0) > > /etc/puppet/modules > > ├──antonlindstrom-powerdns (v0.0.5) > > ├──duritong-sysctl (v0.0.11) > > ├──nanliu-staging (v1.0.4) > > ├──openstack-barbican (v0.0.1) > > ├──openstack-ceilometer (v7.0.0) > > ├──openstack-cinder (v7.0.0) > > ├──openstack-designate (v7.0.0) > > ├──openstack-glance (v7.0.0) > > ├──openstack-gnocchi (v7.0.0) > > ├──openstack-heat (v7.0.0) > > ├──openstack-horizon (v7.0.0) > > ├──openstack-ironic (v7.0.0) > > ├──openstack-keystone (v7.0.0) > > ├──openstack-manila (v7.0.0) > > ├──openstack-mistral (v0.0.1) > > ├──openstack-monasca (v1.0.0) > > ├──openstack-murano (v7.0.0) > > ├──openstack-neutron (v7.0.0) > > ├──openstack-nova (v7.0.0) > > ├──openstack-openstack_extras (v7.0.0) > > ├──openstack-openstacklib (v7.0.0) invalid > > ├──openstack-sahara (v7.0.0) > > ├──openstack-swift (v7.0.0) > > ├──openstack-tempest (v7.0.0) > > ├──openstack-trove (v7.0.0) > > ├──openstack-tuskar (v7.0.0) > > ├──openstack-vswitch (v3.0.0) > > ├──openstack-zaqar (v0.0.1) > > ├──openstack_integration (???) > > ├──puppet-aodh (v7.0.0) > > ├──puppet-corosync (v0.8.0) > > ├──puppetlabs-apache (v1.4.1) > > ├──puppetlabs-apt (v2.1.1) > > ├──puppetlabs-concat (v1.2.5) > > ├──puppetlabs-firewall (v1.6.0) > > ├──puppetlabs-inifile (v1.4.3) > > ├──puppetlabs-mongodb (v0.11.0) > > ├──puppetlabs-mysql (v3.6.2) > > ├──puppetlabs-postgresql (v4.4.2) invalid > > ├──puppetlabs-rabbitmq (v5.2.3) > > ├──puppetlabs-rsync (v0.4.0) > > ├──puppetlabs-stdlib (v4.6.0) > > ├──puppetlabs-vcsrepo (v1.3.2) > > ├──puppetlabs-xinetd (v1.5.0) > > ├──qpid (???) > > ├──saz-memcached (v2.8.1) > >
Re: [openstack-dev] [puppet] compatibility of puppet upstream modules
On 02/03/2016 04:03 PM, Ptacek, MichalX wrote: > Hi all, > > > > I have one general question, > > currently I am deploying liberty openstack as described in > https://wiki.openstack.org/wiki/Puppet/Deploy > > Unfortunately puppet modules specified in > puppet-openstack-integration/Puppetfile are not compatible Did you take the file from stable/liberty branch? https://github.com/openstack/puppet-openstack-integration/tree/stable/liberty > > and some are also missing as visible from following output of “puppet > module list” > > > > Warning: Setting templatedir is deprecated. See > http://links.puppetlabs.com/env-settings-deprecations > >(at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in > `issue_deprecation_warning') > > Warning: Module 'openstack-openstacklib' (v7.0.0) fails to meet some > dependencies: > > 'openstack-barbican' (v0.0.1) requires 'openstack-openstacklib' > (>=6.0.0 <7.0.0) > > 'openstack-zaqar' (v0.0.1) requires 'openstack-openstacklib' (>=6.0.0 > <7.0.0) > > Warning: Module 'puppetlabs-postgresql' (v4.4.2) fails to meet some > dependencies: > > 'openstack-openstacklib' (v7.0.0) requires 'puppetlabs-postgresql' > (>=3.3.0 <4.0.0) > > Warning: Missing dependency 'deric-storm': > > 'openstack-monasca' (v1.0.0) requires 'deric-storm' (>=0.0.1 <1.0.0) > > Warning: Missing dependency 'deric-zookeeper': > > 'openstack-monasca' (v1.0.0) requires 'deric-zookeeper' (>=0.0.1 <1.0.0) > > Warning: Missing dependency 'dprince-qpid': > > 'openstack-cinder' (v7.0.0) requires 'dprince-qpid' (>=1.0.0 <2.0.0) > > 'openstack-manila' (v7.0.0) requires 'dprince-qpid' (>=1.0.0 <2.0.0) > > 'openstack-nova' (v7.0.0) requires 'dprince-qpid' (>=1.0.0 <2.0.0) > > Warning: Missing dependency 'jdowning-influxdb': > > 'openstack-monasca' (v1.0.0) requires 'jdowning-influxdb' (>=0.3.0 <1.0.0) > > Warning: Missing dependency 'opentable-kafka': > > 'openstack-monasca' (v1.0.0) requires 'opentable-kafka' (>=1.0.0 <2.0.0) > > Warning: Missing dependency 'puppetlabs-stdlib': > > 'antonlindstrom-powerdns' (v0.0.5) requires 'puppetlabs-stdlib' (>= 0.0.0) > > Warning: Missing dependency 'puppetlabs-corosync': > > 'openstack-openstack_extras' (v7.0.0) requires 'puppetlabs-corosync' > (>=0.1.0 <1.0.0) > > /etc/puppet/modules > > ├──antonlindstrom-powerdns (v0.0.5) > > ├──duritong-sysctl (v0.0.11) > > ├──nanliu-staging (v1.0.4) > > ├──openstack-barbican (v0.0.1) > > ├──openstack-ceilometer (v7.0.0) > > ├──openstack-cinder (v7.0.0) > > ├──openstack-designate (v7.0.0) > > ├──openstack-glance (v7.0.0) > > ├──openstack-gnocchi (v7.0.0) > > ├──openstack-heat (v7.0.0) > > ├──openstack-horizon (v7.0.0) > > ├──openstack-ironic (v7.0.0) > > ├──openstack-keystone (v7.0.0) > > ├──openstack-manila (v7.0.0) > > ├──openstack-mistral (v0.0.1) > > ├──openstack-monasca (v1.0.0) > > ├──openstack-murano (v7.0.0) > > ├──openstack-neutron (v7.0.0) > > ├──openstack-nova (v7.0.0) > > ├──openstack-openstack_extras (v7.0.0) > > ├──openstack-openstacklib (v7.0.0) invalid > > ├──openstack-sahara (v7.0.0) > > ├──openstack-swift (v7.0.0) > > ├──openstack-tempest (v7.0.0) > > ├──openstack-trove (v7.0.0) > > ├──openstack-tuskar (v7.0.0) > > ├──openstack-vswitch (v3.0.0) > > ├──openstack-zaqar (v0.0.1) > > ├──openstack_integration (???) > > ├──puppet-aodh (v7.0.0) > > ├──puppet-corosync (v0.8.0) > > ├──puppetlabs-apache (v1.4.1) > > ├──puppetlabs-apt (v2.1.1) > > ├──puppetlabs-concat (v1.2.5) > > ├──puppetlabs-firewall (v1.6.0) > > ├──puppetlabs-inifile (v1.4.3) > > ├──puppetlabs-mongodb (v0.11.0) > > ├──puppetlabs-mysql (v3.6.2) > > ├──puppetlabs-postgresql (v4.4.2) invalid > > ├──puppetlabs-rabbitmq (v5.2.3) > > ├──puppetlabs-rsync (v0.4.0) > > ├──puppetlabs-stdlib (v4.6.0) > > ├──puppetlabs-vcsrepo (v1.3.2) > > ├──puppetlabs-xinetd (v1.5.0) > > ├──qpid (???) > > ├──saz-memcached (v2.8.1) > > ├──stankevich-python (v1.8.0) > > └── theforeman-dns (v3.0.0) > > > > > > Most of the warning can be probably ignored, e.g I assume that latest > barbican & zaqar are compatible with liberty (7.0) version of > openstack-openstacklib > > 'openstack-barbican' (v0.0.1) requires 'openstack-openstacklib' > (>=6.0.0 <7.0.0) > > 'openstack-zaqar' (v0.0.1) requires 'openstack-openstacklib' (>=6.0.0 > <7.0.0) > > > > Am I right or I need to get rid of all of these compatibility warnings > before proceeding further ? > If you look at our CI jobs, we also have some warnings: http://logs.openstack.org/36/275836/1/gate/gate-puppet-openstack-integration-scenario001-tempest-dsvm-centos7/15a5ead/console.html#_2016-02-03_21_56_40_945 > > I tried both, but during subsequent deployments I reached some > intermediate issue with number of parallel mysql connections > > > > 2016-02-03 00:01:03.326 90406 DEBUG oslo_db.api [-] Loading backend > 'sqlalchemy' from 'nova.db.sqlalchemy.api' _load_backend >
Re: [openstack-dev] [puppet] compatibility of puppet upstream modules
Hi Emilien, It seems that keystone database is not populated, because of something, which happened on previous runs (e.g. some packages installation), Following rows are visible just in log from first attempt Debug: Executing '/usr/bin/mysql -e CREATE USER 'keystone'@'127.0.0.1' IDENTIFIED BY PASSWORD '*936E8F7AB2E21B47F6C9A7E5D9FE14DBA2255E5A'' Debug: Executing '/usr/bin/mysql -e GRANT USAGE ON *.* TO 'keystone'@'127.0.0.1' WITH MAX_USER_CONNECTIONS 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_QUERIES_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0' …. …. I tried to clean databases & uninstall packages installed during deployment, but maybe I miss something as it simply doesn’t work ☺ Is there any procedure, how can I restore system to “vanilla state” before puppet modules installation ? It looks to me that when deployment failed, it’s very difficult to “unstack” it Thanks in advance, Michal From: Ptacek, MichalX Sent: Thursday, February 04, 2016 11:14 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: RE: [openstack-dev] [puppet] compatibility of puppet upstream modules -Original Message- From: Emilien Macchi [mailto:emil...@redhat.com] Sent: Thursday, February 04, 2016 10:06 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [puppet] compatibility of puppet upstream modules On 02/03/2016 04:03 PM, Ptacek, MichalX wrote: > Hi all, > > > > I have one general question, > > currently I am deploying liberty openstack as described in > https://wiki.openstack.org/wiki/Puppet/Deploy > > Unfortunately puppet modules specified in > puppet-openstack-integration/Puppetfile are not compatible Did you take the file from stable/liberty branch? https://github.com/openstack/puppet-openstack-integration/tree/stable/liberty [Michal Ptacek] I am deploying scenario003 with stable/liberty > > and some are also missing as visible from following output of “puppet > module list” > > > > Warning: Setting templatedir is deprecated. See > http://links.puppetlabs.com/env-settings-deprecations > >(at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in > `issue_deprecation_warning') > > Warning: Module 'openstack-openstacklib' (v7.0.0) fails to meet some > dependencies: > > 'openstack-barbican' (v0.0.1) requires 'openstack-openstacklib' > (>=6.0.0 <7.0.0) > > 'openstack-zaqar' (v0.0.1) requires 'openstack-openstacklib' > (>=6.0.0 > <7.0.0) > > Warning: Module 'puppetlabs-postgresql' (v4.4.2) fails to meet some > dependencies: > > 'openstack-openstacklib' (v7.0.0) requires 'puppetlabs-postgresql' > (>=3.3.0 <4.0.0) > > Warning: Missing dependency 'deric-storm': > > 'openstack-monasca' (v1.0.0) requires 'deric-storm' (>=0.0.1 <1.0.0) > > Warning: Missing dependency 'deric-zookeeper': > > 'openstack-monasca' (v1.0.0) requires 'deric-zookeeper' (>=0.0.1 > <1.0.0) > > Warning: Missing dependency 'dprince-qpid': > > 'openstack-cinder' (v7.0.0) requires 'dprince-qpid' (>=1.0.0 <2.0.0) > > 'openstack-manila' (v7.0.0) requires 'dprince-qpid' (>=1.0.0 <2.0.0) > > 'openstack-nova' (v7.0.0) requires 'dprince-qpid' (>=1.0.0 <2.0.0) > > Warning: Missing dependency 'jdowning-influxdb': > > 'openstack-monasca' (v1.0.0) requires 'jdowning-influxdb' (>=0.3.0 > <1.0.0) > > Warning: Missing dependency 'opentable-kafka': > > 'openstack-monasca' (v1.0.0) requires 'opentable-kafka' (>=1.0.0 > <2.0.0) > > Warning: Missing dependency 'puppetlabs-stdlib': > > 'antonlindstrom-powerdns' (v0.0.5) requires 'puppetlabs-stdlib' (>= > 0.0.0) > > Warning: Missing dependency 'puppetlabs-corosync': > > 'openstack-openstack_extras' (v7.0.0) requires 'puppetlabs-corosync' > (>=0.1.0 <1.0.0) > > /etc/puppet/modules > > ├──antonlindstrom-powerdns (v0.0.5) > > ├──duritong-sysctl (v0.0.11) > > ├──nanliu-staging (v1.0.4) > > ├──openstack-barbican (v0.0.1) > > ├──openstack-ceilometer (v7.0.0) > > ├──openstack-cinder (v7.0.0) > > ├──openstack-designate (v7.0.0) > > ├──openstack-glance (v7.0.0) > > ├──openstack-gnocchi (v7.0.0) > > ├──openstack-heat (v7.0.0) > > ├──openstack-horizon (v7.0.0) > > ├──openstack-ironic (v7.0.0) > > ├──openstack-keystone (v7.0.0) > > ├──openstack-manila (v7.0.0) > > ├──openstack-mistral (v0.0.1) > > ├──openstack-monasca (v1.0.0) > > ├──openstack-murano (v7.0.0) > > ├──openstack-neutron (v7
Re: [openstack-dev] [puppet] compatibility of puppet upstream modules
If you can't isolate the exact thing you need to get cleaned up here it can be difficult to unwind. You'll either need to read the code to see what's triggering the db setup (which is probably the package installs) or start on a clean box. I'd recommend the latter. On Thu, Feb 4, 2016 at 10:35 AM, Ptacek, MichalX <michalx.pta...@intel.com> wrote: > Hi Emilien, > > > > It seems that keystone database is not populated, because of something, > which happened on previous runs (e.g. some packages installation), > > > > Following rows are visible just in log from first attempt > > Debug: Executing '/usr/bin/mysql -e CREATE USER 'keystone'@'127.0.0.1' > IDENTIFIED BY PASSWORD '*936E8F7AB2E21B47F6C9A7E5D9FE14DBA2255E5A'' > > Debug: Executing '/usr/bin/mysql -e GRANT USAGE ON *.* TO > 'keystone'@'127.0.0.1' > WITH MAX_USER_CONNECTIONS 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_QUERIES_PER_HOUR > 0 MAX_UPDATES_PER_HOUR 0' > > …. > > …. > > I tried to clean databases & uninstall packages installed during > deployment, but maybe I miss something as it simply doesn’t work J > > > > Is there any procedure, how can I restore system to “vanilla state” before > puppet modules installation ? > > It looks to me that when deployment failed, it’s very difficult to > “unstack” it > > > > Thanks in advance, > > Michal > > > > *From:* Ptacek, MichalX > *Sent:* Thursday, February 04, 2016 11:14 AM > *To:* OpenStack Development Mailing List (not for usage questions) < > openstack-dev@lists.openstack.org> > *Subject:* RE: [openstack-dev] [puppet] compatibility of puppet upstream > modules > > > > > > > > -Original Message- > From: Emilien Macchi [mailto:emil...@redhat.com <emil...@redhat.com>] > Sent: Thursday, February 04, 2016 10:06 AM > To: OpenStack Development Mailing List (not for usage questions) < > openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [puppet] compatibility of puppet upstream > modules > > > > > > > > On 02/03/2016 04:03 PM, Ptacek, MichalX wrote: > > > Hi all, > > > > > > > > > > > > I have one general question, > > > > > > currently I am deploying liberty openstack as described in > > > https://wiki.openstack.org/wiki/Puppet/Deploy > > > > > > Unfortunately puppet modules specified in > > > puppet-openstack-integration/Puppetfile are not compatible > > > > Did you take the file from stable/liberty branch? > > > https://github.com/openstack/puppet-openstack-integration/tree/stable/liberty > > > > *[Michal Ptacek]* I am deploying scenario003 with stable/liberty > > > > > > and some are also missing as visible from following output of “puppet > > > module list” > > > > > > > > > > > > Warning: Setting templatedir is deprecated. See > > > http://links.puppetlabs.com/env-settings-deprecations > > > > > >(at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in > > > `issue_deprecation_warning') > > > > > > Warning: Module 'openstack-openstacklib' (v7.0.0) fails to meet some > > > dependencies: > > > > > > 'openstack-barbican' (v0.0.1) requires 'openstack-openstacklib' > > > (>=6.0.0 <7.0.0) > > > > > > 'openstack-zaqar' (v0.0.1) requires 'openstack-openstacklib' > > > (>=6.0.0 > > > <7.0.0) > > > > > > Warning: Module 'puppetlabs-postgresql' (v4.4.2) fails to meet some > > > dependencies: > > > > > > 'openstack-openstacklib' (v7.0.0) requires 'puppetlabs-postgresql' > > > (>=3.3.0 <4.0.0) > > > > > > Warning: Missing dependency 'deric-storm': > > > > > > 'openstack-monasca' (v1.0.0) requires 'deric-storm' (>=0.0.1 <1.0.0) > > > > > > Warning: Missing dependency 'deric-zookeeper': > > > > > > 'openstack-monasca' (v1.0.0) requires 'deric-zookeeper' (>=0.0.1 > > > <1.0.0) > > > > > > Warning: Missing dependency 'dprince-qpid': > > > > > > 'openstack-cinder' (v7.0.0) requires 'dprince-qpid' (>=1.0.0 <2.0.0) > > > > > > 'openstack-manila' (v7.0.0) requires 'dprince-qpid' (>=1.0.0 <2.0.0) > > > > > > 'openstack-nova' (v7.0.0) requires 'dprince-qpid' (>=1.0.0 <2.0.0) > > > > > > Warning: Missing dependency 'jdowning-influxdb': > > > > > > 'openstack-monasca' (v1.0.0) requires 'jdowning-influxdb' (>=0.3.0 > > > <1.0.0) > >
