Greetings,
Is there any way to force Katello to unpack puppet modules to
/etc/puppet/environments from /var/lib/pulp/content/puppet_module/?
I've purged all of my pulp content, then manually removed pulp repos
(puppet and rpm) and /etc/puppet/environments/* and resynchronised whole
capsule content using hammer after all but it seems that I've missed one
step because now this capsule is missing puppet environments while all
puppet modules is present in /var/lib/pulp/content/puppet_module/:
ls -1 /var/lib/pulp/content/puppet_module/
[…]
puppet-subscription_manager-0.0.1.tar.gz
razorsedge-network-3.5.0.tar.gz
razorsedge-network-3.6.0.tar.gz
richardc-datacat-0.6.2.tar.gz
saz-rsyslog-3.5.1.tar.gz
saz-sudo-3.1.0.tar.gz
sgnl05-colorprompt-2.0.0.tar.gz
stbenjam-hash_resources-1.0.1.tar.gz
theforeman-puppet-4.1.0.tar.gz
theforeman-puppet-4.2.0.tar.gz
thias-sysctl-1.0.2.tar.gz
thomasvandoren-etckeeper-0.0.9.tar.gz
ls -1 /etc/puppet/environments/
example_env
production
pulp-admin puppet repo list
Warning: path should have mode 0700 because it may contain sensitive
information: /root/.pulp/
···
+----------------------------------------------------------------------+
Puppet Repositories
+----------------------------------------------------------------------+
Id: […]CM_CentOS_7_puppet_modules
Display Name: […]CM CentOS 7 puppet modules
Description: None
Content Unit Counts:
Puppet Module: 22
[…]
… no single one was missing in pulp-admin puppet repo list output.
I’ll appreciate any advice, thanks!
–
Kind regards,
Vladimir.
> Greetings,
>
> Is there any way to force Katello to unpack puppet modules to
> /etc/puppet/environments from /var/lib/pulp/content/puppet_module/?
>
> I've purged all of my pulp content, then manually removed pulp repos
> (puppet and rpm) and /etc/puppet/environments/* and resynchronised whole
> capsule content using hammer after all but it seems that I've missed one
> step because now this capsule is missing puppet environments while all
> puppet modules is present in /var/lib/pulp/content/puppet_module/:
Repositories wouldn't be published to /etc/puppet/environments, do you
have a content view, and published to a lifecycle environment? That's
what will show up in /etc/puppet/environments.
···
On Thu, Oct 15, 2015 at 06:17:36PM +0300, Vladimir Stackov wrote:
ls -1 /var/lib/pulp/content/puppet_module/
[…]
puppet-subscription_manager-0.0.1.tar.gz
razorsedge-network-3.5.0.tar.gz
razorsedge-network-3.6.0.tar.gz
richardc-datacat-0.6.2.tar.gz
saz-rsyslog-3.5.1.tar.gz
saz-sudo-3.1.0.tar.gz
sgnl05-colorprompt-2.0.0.tar.gz
stbenjam-hash_resources-1.0.1.tar.gz
theforeman-puppet-4.1.0.tar.gz
theforeman-puppet-4.2.0.tar.gz
thias-sysctl-1.0.2.tar.gz
thomasvandoren-etckeeper-0.0.9.tar.gz
ls -1 /etc/puppet/environments/
example_env
production
pulp-admin puppet repo list
Warning: path should have mode 0700 because it may contain sensitive
information: /root/.pulp/
±---------------------------------------------------------------------+
Puppet Repositories
±---------------------------------------------------------------------+
Id: […]CM_CentOS_7_puppet_modules
Display Name: […]CM CentOS 7 puppet modules
Description: None
Content Unit Counts:
Puppet Module: 22
[…]
… no single one was missing in pulp-admin puppet repo list output.
I’ll appreciate any advice, thanks!
–
Kind regards,
Vladimir.
–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
Yes, I have content views, they were published and correctly updated on
Foreman host and other capsules, but nothing happens with
/etc/puppet/environments on capsule I'm talking about.
P.S. In pulp terms CVs appears to be puppet/rpm repositories or I'm wrong?
···
2015-10-15 19:01 GMT+03:00 Stephen Benjamin :
On Thu, Oct 15, 2015 at 06:17:36PM +0300, Vladimir Stackov wrote:
Greetings,
Is there any way to force Katello to unpack puppet modules to
/etc/puppet/environments from /var/lib/pulp/content/puppet_module/?
I’ve purged all of my pulp content, then manually removed pulp repos
(puppet and rpm) and /etc/puppet/environments/* and resynchronised whole
capsule content using hammer after all but it seems that I’ve missed one
step because now this capsule is missing puppet environments while all
puppet modules is present in /var/lib/pulp/content/puppet_module/:
Repositories wouldn’t be published to /etc/puppet/environments, do you
have a content view, and published to a lifecycle environment? That’s
what will show up in /etc/puppet/environments.
ls -1 /var/lib/pulp/content/puppet_module/
[…]
puppet-subscription_manager-0.0.1.tar.gz
razorsedge-network-3.5.0.tar.gz
razorsedge-network-3.6.0.tar.gz
richardc-datacat-0.6.2.tar.gz
saz-rsyslog-3.5.1.tar.gz
saz-sudo-3.1.0.tar.gz
sgnl05-colorprompt-2.0.0.tar.gz
stbenjam-hash_resources-1.0.1.tar.gz
theforeman-puppet-4.1.0.tar.gz
theforeman-puppet-4.2.0.tar.gz
thias-sysctl-1.0.2.tar.gz
thomasvandoren-etckeeper-0.0.9.tar.gz
ls -1 /etc/puppet/environments/
example_env
production
pulp-admin puppet repo list
Warning: path should have mode 0700 because it may contain sensitive
information: /root/.pulp/
±---------------------------------------------------------------------+
Puppet Repositories
±---------------------------------------------------------------------+
Id: […]CM_CentOS_7_puppet_modules
Display Name: […]CM CentOS 7 puppet modules
Description: None
Content Unit Counts:
Puppet Module: 22
[…]
… no single one was missing in pulp-admin puppet repo list output.
I’ll appreciate any advice, thanks!
–
Kind regards,
Vladimir.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Kind regards,
Vladimir.
> Yes, I have content views, they were published and correctly updated on
> Foreman host and other capsules, but nothing happens with
> /etc/puppet/environments on capsule I'm talking about.
If its an external capsule, take a look at Infrastructure / Smart
Proxies and the paritcular proxy - does it have the lifecycle
environment assigned that the CV belongs to?
···
On Thu, Oct 15, 2015 at 07:49:09PM +0300, Vladimir Stackov wrote:
P.S. In pulp terms CVs appears to be puppet/rpm repositories or I’m wrong?
2015-10-15 19:01 GMT+03:00 Stephen Benjamin stephen@redhat.com:
On Thu, Oct 15, 2015 at 06:17:36PM +0300, Vladimir Stackov wrote:
Greetings,
Is there any way to force Katello to unpack puppet modules to
/etc/puppet/environments from /var/lib/pulp/content/puppet_module/?
I’ve purged all of my pulp content, then manually removed pulp repos
(puppet and rpm) and /etc/puppet/environments/* and resynchronised whole
capsule content using hammer after all but it seems that I’ve missed one
step because now this capsule is missing puppet environments while all
puppet modules is present in /var/lib/pulp/content/puppet_module/:
Repositories wouldn’t be published to /etc/puppet/environments, do you
have a content view, and published to a lifecycle environment? That’s
what will show up in /etc/puppet/environments.
ls -1 /var/lib/pulp/content/puppet_module/
[…]
puppet-subscription_manager-0.0.1.tar.gz
razorsedge-network-3.5.0.tar.gz
razorsedge-network-3.6.0.tar.gz
richardc-datacat-0.6.2.tar.gz
saz-rsyslog-3.5.1.tar.gz
saz-sudo-3.1.0.tar.gz
sgnl05-colorprompt-2.0.0.tar.gz
stbenjam-hash_resources-1.0.1.tar.gz
theforeman-puppet-4.1.0.tar.gz
theforeman-puppet-4.2.0.tar.gz
thias-sysctl-1.0.2.tar.gz
thomasvandoren-etckeeper-0.0.9.tar.gz
ls -1 /etc/puppet/environments/
example_env
production
pulp-admin puppet repo list
Warning: path should have mode 0700 because it may contain sensitive
information: /root/.pulp/
±---------------------------------------------------------------------+
Puppet Repositories
±---------------------------------------------------------------------+
Id: […]CM_CentOS_7_puppet_modules
Display Name: […]CM CentOS 7 puppet modules
Description: None
Content Unit Counts:
Puppet Module: 22
[…]
… no single one was missing in pulp-admin puppet repo list output.
I’ll appreciate any advice, thanks!
–
Kind regards,
Vladimir.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Kind regards,
Vladimir.
–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
Yes, CV was assigned to Library and Library was assigned to this smart
proxy.
···
2015-10-15 20:13 GMT+03:00 Stephen Benjamin :
On Thu, Oct 15, 2015 at 07:49:09PM +0300, Vladimir Stackov wrote:
Yes, I have content views, they were published and correctly updated on
Foreman host and other capsules, but nothing happens with
/etc/puppet/environments on capsule I’m talking about.
If its an external capsule, take a look at Infrastructure / Smart
Proxies and the paritcular proxy - does it have the lifecycle
environment assigned that the CV belongs to?
P.S. In pulp terms CVs appears to be puppet/rpm repositories or I’m
wrong?
2015-10-15 19:01 GMT+03:00 Stephen Benjamin stephen@redhat.com:
On Thu, Oct 15, 2015 at 06:17:36PM +0300, Vladimir Stackov wrote:
Greetings,
Is there any way to force Katello to unpack puppet modules to
/etc/puppet/environments from /var/lib/pulp/content/puppet_module/?
I’ve purged all of my pulp content, then manually removed pulp repos
(puppet and rpm) and /etc/puppet/environments/* and resynchronised
whole
capsule content using hammer after all but it seems that I’ve missed
one
step because now this capsule is missing puppet environments while
all
puppet modules is present in /var/lib/pulp/content/puppet_module/:
Repositories wouldn’t be published to /etc/puppet/environments, do you
have a content view, and published to a lifecycle environment? That’s
what will show up in /etc/puppet/environments.
ls -1 /var/lib/pulp/content/puppet_module/
[…]
puppet-subscription_manager-0.0.1.tar.gz
razorsedge-network-3.5.0.tar.gz
razorsedge-network-3.6.0.tar.gz
richardc-datacat-0.6.2.tar.gz
saz-rsyslog-3.5.1.tar.gz
saz-sudo-3.1.0.tar.gz
sgnl05-colorprompt-2.0.0.tar.gz
stbenjam-hash_resources-1.0.1.tar.gz
theforeman-puppet-4.1.0.tar.gz
theforeman-puppet-4.2.0.tar.gz
thias-sysctl-1.0.2.tar.gz
thomasvandoren-etckeeper-0.0.9.tar.gz
ls -1 /etc/puppet/environments/
example_env
production
pulp-admin puppet repo list
Warning: path should have mode 0700 because it may contain sensitive
information: /root/.pulp/
±---------------------------------------------------------------------+
Puppet Repositories
±---------------------------------------------------------------------+
Id: […]CM_CentOS_7_puppet_modules
Display Name: […]CM CentOS 7 puppet modules
Description: None
Content Unit Counts:
Puppet Module: 22
[…]
… no single one was missing in pulp-admin puppet repo list output.
I’ll appreciate any advice, thanks!
–
Kind regards,
Vladimir.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
You received this message because you are subscribed to the Google
Groups
“Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Kind regards,
Vladimir.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Kind regards,
Vladimir.
No ideas? Maybe I need to check some pulp settings?
···
2015-10-15 20:45 GMT+03:00 Vladimir Stackov :
Yes, CV was assigned to Library and Library was assigned to this smart
proxy.
2015-10-15 20:13 GMT+03:00 Stephen Benjamin stephen@redhat.com:
On Thu, Oct 15, 2015 at 07:49:09PM +0300, Vladimir Stackov wrote:
Yes, I have content views, they were published and correctly updated on
Foreman host and other capsules, but nothing happens with
/etc/puppet/environments on capsule I’m talking about.
If its an external capsule, take a look at Infrastructure / Smart
Proxies and the paritcular proxy - does it have the lifecycle
environment assigned that the CV belongs to?
P.S. In pulp terms CVs appears to be puppet/rpm repositories or I’m
wrong?
2015-10-15 19:01 GMT+03:00 Stephen Benjamin stephen@redhat.com:
On Thu, Oct 15, 2015 at 06:17:36PM +0300, Vladimir Stackov wrote:
Greetings,
Is there any way to force Katello to unpack puppet modules to
/etc/puppet/environments from /var/lib/pulp/content/puppet_module/?
I’ve purged all of my pulp content, then manually removed pulp repos
(puppet and rpm) and /etc/puppet/environments/* and resynchronised
whole
capsule content using hammer after all but it seems that I’ve
missed one
step because now this capsule is missing puppet environments while
all
puppet modules is present in /var/lib/pulp/content/puppet_module/:
Repositories wouldn’t be published to /etc/puppet/environments, do you
have a content view, and published to a lifecycle environment? That’s
what will show up in /etc/puppet/environments.
ls -1 /var/lib/pulp/content/puppet_module/
[…]
puppet-subscription_manager-0.0.1.tar.gz
razorsedge-network-3.5.0.tar.gz
razorsedge-network-3.6.0.tar.gz
richardc-datacat-0.6.2.tar.gz
saz-rsyslog-3.5.1.tar.gz
saz-sudo-3.1.0.tar.gz
sgnl05-colorprompt-2.0.0.tar.gz
stbenjam-hash_resources-1.0.1.tar.gz
theforeman-puppet-4.1.0.tar.gz
theforeman-puppet-4.2.0.tar.gz
thias-sysctl-1.0.2.tar.gz
thomasvandoren-etckeeper-0.0.9.tar.gz
ls -1 /etc/puppet/environments/
example_env
production
pulp-admin puppet repo list
Warning: path should have mode 0700 because it may contain sensitive
information: /root/.pulp/
±---------------------------------------------------------------------+
Puppet Repositories
±---------------------------------------------------------------------+
Id: […]CM_CentOS_7_puppet_modules
Display Name: […]CM CentOS 7 puppet modules
Description: None
Content Unit Counts:
Puppet Module: 22
[…]
… no single one was missing in pulp-admin puppet repo list output.
I’ll appreciate any advice, thanks!
–
Kind regards,
Vladimir.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
You received this message because you are subscribed to the Google
Groups
“Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Kind regards,
Vladimir.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Kind regards,
Vladimir.
–
Kind regards,
Vladimir.
> No ideas? Maybe I need to check some pulp settings?
Maybe permissions on /etc/puppet/environments, or look at the sync tasks
on the Satellite as one of them is the Copy task for /etc/puppet, you
might see errors on the task.
Also you could re-run capsule-installer which should fix any
configuration that's out of place.
···
On Fri, Oct 16, 2015 at 09:47:19AM +0300, Vladimir Stackov wrote:
2015-10-15 20:45 GMT+03:00 Vladimir Stackov amigo.elite@gmail.com:
Yes, CV was assigned to Library and Library was assigned to this smart
proxy.
2015-10-15 20:13 GMT+03:00 Stephen Benjamin stephen@redhat.com:
On Thu, Oct 15, 2015 at 07:49:09PM +0300, Vladimir Stackov wrote:
Yes, I have content views, they were published and correctly updated on
Foreman host and other capsules, but nothing happens with
/etc/puppet/environments on capsule I’m talking about.
If its an external capsule, take a look at Infrastructure / Smart
Proxies and the paritcular proxy - does it have the lifecycle
environment assigned that the CV belongs to?
P.S. In pulp terms CVs appears to be puppet/rpm repositories or I’m
wrong?
2015-10-15 19:01 GMT+03:00 Stephen Benjamin stephen@redhat.com:
On Thu, Oct 15, 2015 at 06:17:36PM +0300, Vladimir Stackov wrote:
Greetings,
Is there any way to force Katello to unpack puppet modules to
/etc/puppet/environments from /var/lib/pulp/content/puppet_module/?
I’ve purged all of my pulp content, then manually removed pulp repos
(puppet and rpm) and /etc/puppet/environments/* and resynchronised
whole
capsule content using hammer after all but it seems that I’ve
missed one
step because now this capsule is missing puppet environments while
all
puppet modules is present in /var/lib/pulp/content/puppet_module/:
Repositories wouldn’t be published to /etc/puppet/environments, do you
have a content view, and published to a lifecycle environment? That’s
what will show up in /etc/puppet/environments.
ls -1 /var/lib/pulp/content/puppet_module/
[…]
puppet-subscription_manager-0.0.1.tar.gz
razorsedge-network-3.5.0.tar.gz
razorsedge-network-3.6.0.tar.gz
richardc-datacat-0.6.2.tar.gz
saz-rsyslog-3.5.1.tar.gz
saz-sudo-3.1.0.tar.gz
sgnl05-colorprompt-2.0.0.tar.gz
stbenjam-hash_resources-1.0.1.tar.gz
theforeman-puppet-4.1.0.tar.gz
theforeman-puppet-4.2.0.tar.gz
thias-sysctl-1.0.2.tar.gz
thomasvandoren-etckeeper-0.0.9.tar.gz
ls -1 /etc/puppet/environments/
example_env
production
pulp-admin puppet repo list
Warning: path should have mode 0700 because it may contain sensitive
information: /root/.pulp/
±---------------------------------------------------------------------+
Puppet Repositories
±---------------------------------------------------------------------+
Id: […]CM_CentOS_7_puppet_modules
Display Name: […]CM CentOS 7 puppet modules
Description: None
Content Unit Counts:
Puppet Module: 22
[…]
… no single one was missing in pulp-admin puppet repo list output.
I’ll appreciate any advice, thanks!
–
Kind regards,
Vladimir.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
You received this message because you are subscribed to the Google
Groups
“Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Kind regards,
Vladimir.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Kind regards,
Vladimir.
–
Kind regards,
Vladimir.
–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
So stupid mistake I've made…
Thanks, Stephen, this error was caused by wrong permissions on
/etc/puppet/environments because of puppet manual update on this capsule.
···
2015-10-16 14:29 GMT+03:00 Stephen Benjamin :
On Fri, Oct 16, 2015 at 09:47:19AM +0300, Vladimir Stackov wrote:
No ideas? Maybe I need to check some pulp settings?
Maybe permissions on /etc/puppet/environments, or look at the sync tasks
on the Satellite as one of them is the Copy task for /etc/puppet, you
might see errors on the task.
Also you could re-run capsule-installer which should fix any
configuration that’s out of place.
2015-10-15 20:45 GMT+03:00 Vladimir Stackov amigo.elite@gmail.com:
Yes, CV was assigned to Library and Library was assigned to this smart
proxy.
2015-10-15 20:13 GMT+03:00 Stephen Benjamin stephen@redhat.com:
On Thu, Oct 15, 2015 at 07:49:09PM +0300, Vladimir Stackov wrote:
Yes, I have content views, they were published and correctly
updated on
Foreman host and other capsules, but nothing happens with
/etc/puppet/environments on capsule I’m talking about.
If its an external capsule, take a look at Infrastructure / Smart
Proxies and the paritcular proxy - does it have the lifecycle
environment assigned that the CV belongs to?
P.S. In pulp terms CVs appears to be puppet/rpm repositories or I’m
wrong?
2015-10-15 19:01 GMT+03:00 Stephen Benjamin stephen@redhat.com:
On Thu, Oct 15, 2015 at 06:17:36PM +0300, Vladimir Stackov wrote:
Greetings,
Is there any way to force Katello to unpack puppet modules to
/etc/puppet/environments from
/var/lib/pulp/content/puppet_module/?
I’ve purged all of my pulp content, then manually removed pulp
repos
(puppet and rpm) and /etc/puppet/environments/* and
resynchronised
whole
capsule content using hammer after all but it seems that I’ve
missed one
step because now this capsule is missing puppet environments
while
all
puppet modules is present in
/var/lib/pulp/content/puppet_module/:
Repositories wouldn’t be published to /etc/puppet/environments,
do you
have a content view, and published to a lifecycle environment?
That’s
what will show up in /etc/puppet/environments.
ls -1 /var/lib/pulp/content/puppet_module/
[…]
puppet-subscription_manager-0.0.1.tar.gz
razorsedge-network-3.5.0.tar.gz
razorsedge-network-3.6.0.tar.gz
richardc-datacat-0.6.2.tar.gz
saz-rsyslog-3.5.1.tar.gz
saz-sudo-3.1.0.tar.gz
sgnl05-colorprompt-2.0.0.tar.gz
stbenjam-hash_resources-1.0.1.tar.gz
theforeman-puppet-4.1.0.tar.gz
theforeman-puppet-4.2.0.tar.gz
thias-sysctl-1.0.2.tar.gz
thomasvandoren-etckeeper-0.0.9.tar.gz
ls -1 /etc/puppet/environments/
example_env
production
pulp-admin puppet repo list
Warning: path should have mode 0700 because it may contain
sensitive
information: /root/.pulp/
±---------------------------------------------------------------------+
Puppet Repositories
±---------------------------------------------------------------------+
Id: […]CM_CentOS_7_puppet_modules
Display Name: […]CM CentOS 7 puppet modules
Description: None
Content Unit Counts:
Puppet Module: 22
[…]
… no single one was missing in pulp-admin puppet repo list
output.
I’ll appreciate any advice, thanks!
–
Kind regards,
Vladimir.
–
You received this message because you are subscribed to the
Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from
it,
send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to
foreman-users@googlegroups.com
.
Visit this group at
http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
You received this message because you are subscribed to the Google
Groups
“Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to
foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Kind regards,
Vladimir.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
You received this message because you are subscribed to the Google
Groups
“Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Kind regards,
Vladimir.
–
Kind regards,
Vladimir.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Kind regards,
Vladimir.
