Re: [foreman-users] Errata and Content View issue

[Lachlan Musicman]

On 9 December 2017 at 07:38, Arsène Gschwind 
wrote:

> Hi,
>
> I'm running Foreman 1.15.6 and Katello 3.4.
> I did apply an Errata to a host what did generate a new Content View
> version, so far s good. The new Content View includes the Errata but not
> the package for the this Errata.
>
>
> 
> As you may see on the picture in version 1.1 there is one more Errata but
> the amount of packages didn't change.
> When doing a yum check-update on host i don't see any new package.
>
> After generating a full new version version of the content view i will get
> those updates on the host.
> This sounds like a bug
>
> Thanks for any hint to help debug that issue.
>
>
I also saw this with these versions. If you look at the release notes for
Foreman 1.16 and Katello 3.5 there are a number of bugs related that will
hopefully fix this issue.

The upgrade is a relatively simple process - I'd recommend it.

Cheers
L.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] [foreman-announce] Katello 3.5.0 (a.k.a. Schwarzbier) is Here!

[Lachlan Musicman]

Thanks to all involved! Updates applied easier than ever before. Nice
little speed bump in spots.

Cheers
L.

--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

On 8 December 2017 at 07:01, Andrew Kofink  wrote:

> Katello 3.5.0 is now available; It works with the recently released
> Foreman 1.16.0. This release fixes 28 bugs since 3.5 RC2 - thanks to all
> who tested and reported issues!
>
> Installation instructions:
> https://theforeman.org/plugins/katello/3.5/installation/index.html
>
> Upgrade instructions:
> https://theforeman.org/plugins/katello/3.5/upgrade/index.html
>
> Release notes:
> https://theforeman.org/plugins/katello/3.5/release_notes/
> release_notes.html
>
> Complete 3.5 changelog:
> https://github.com/Katello/katello/blob/KATELLO-3.5/CHANGELOG.md
>
> Bug Reporting:
> If you find an issue, please file it and note the version of Katello you
> are using.
> http://projects.theforeman.org/projects/katello/issues/new
>
>
> Go have a schwarzbier today!
>
> --
> Andrew Kofink
> akof...@redhat.com
> IRC: akofink
> Software Engineer
> Red Hat Satellite
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Re: Foreman-Katello installation

[Lachlan Musicman]

On 24 November 2017 at 03:23, Ondrej Prazak  wrote:

> Hi,
> I just went over the installation steps at [1]. I executed on a clean
> CentOS 7:
>
> yum -y localinstall 
> http://fedorapeople.org/groups/katello/releases/yum/3.4/katello/el7/x86_64/katello-repos-latest.rpm
> yum -y localinstall 
> http://yum.theforeman.org/releases/1.15/el7/x86_64/foreman-release.rpm
> yum -y localinstall 
> https://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
> yum -y localinstall 
> http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
> yum -y install foreman-release-scl
> yum -y update
> yum -y install katello
>
>
Wow. This is the new quickstart. A thing of beauty. Brutal, but beautiful.

L.



--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] katello 3.3

[Lachlan Musicman]

On 18 October 2017 at 09:20, Edward Clay  wrote:

> I have some host that I attempted to apply applicable erratas to in a
> large group of host.  During that task some host failed and others
> completed.  I can't remember why they failed but I was able to manually
> update the systems once I fixed the issues with these host.  Now I have
> several paused "apply applicable erratas" task for these host and I can't
> get them to resume nor cancel.  I'm not sure how to clean this up since
> It's preventing me from updating to katello 3.4.
>
>
> errors in paused task:
>
> 404 Resource Not Found
>
> and
>
> host did not respond within 20 seconds.  The task has been canceled.  Is
> katello-agent installed and goferd running on the Host?
>
> the katello agent is installed on all managed host and the goferd agent is
> running.  I've even tried to restart the goferd agent without success.
>

I am not an expert on Katello by any stretch, but I have seen this before
and these are two methods I've used:
 - try running katello-tracer-upload from the affected hosts. If that
doesn't work,
 - rebooting the Foreman server does. You probably don't need to go that
far. Maybe just "systemctl restart foreman-tasks"

Cheers
L.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: How to remove a lifecycle environment from a content view?

[Lachlan Musicman]

On 5 October 2017 at 10:35, Lachlan Musicman <data...@gmail.com> wrote:

> If a Lifecycle Environment is inadvertently  promoted to the wrong Content
> View, what is the process for removing it from that content view?
>
>


To answer my own question - you use "remove" in the CV view, but don't
select "completely remove version". That is what was confusing me.

cheers
L.




--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] How to remove a lifecycle environment from a content view?

[Lachlan Musicman]

If a Lifecycle Environment is inadvertently  promoted to the wrong Content
View, what is the process for removing it from that content view?


cheers
L.
--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Re: [Katello] Successfully imported CentOS errata into Katello

[Lachlan Musicman]

Hmm. I'm about to leave work, but it works for us with no major changes.

We run Foreman 1.15.3 and Katello 3.4.5

L.

--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

On 6 September 2017 at 05:49, Jon Dison  wrote:

> Instructions look solid to me but when I run it I get
>
> NOTICE: Skipping errata CESA-2017:2563 (Moderate CentOS openssh Security
> Update) -- No packages found
> for every errata.  Any ideas?
>
> On Friday, June 19, 2015 at 3:14:44 AM UTC-4, Rodrigo Menezes wrote:
>>
>> Not sure if anyone is interested or not but I created this:
>> https://github.com/brdude/pulp_centos_errata_import
>>
>> It's poor code, but it's working for me. Only tested with 2.2 and very
>> little testing at that.
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: How to add Content View to Lifecycle Environment?

[Lachlan Musicman]

Ignore me - I've only just had my first sip of coffee. Of course CVs are
promoted to LFEs, not added.

My bad, cheers

L.

--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

On 6 September 2017 at 08:12, Lachlan Musicman <data...@gmail.com> wrote:

> We are using Foreman 1.15.3 and Katello 3.4.5
>
> I haven't had to create a Lifecycle environment for a while. When my
> colleague went to create a new one yesterday, it looked like there was no
> way to do this through the web anymore?
>
> Am I missing something basic, or is it hammer only?
>
> cheers
> L.
> --
> "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic
> civics is the insistence that we cannot ignore the truth, nor should we
> panic about it. It is a shared consciousness that our institutions have
> failed and our ecosystem is collapsing, yet we are still here — and we are
> creative agents who can shape our destinies. Apocalyptic civics is the
> conviction that the only way out is through, and the only way through is
> together. "
>
> *Greg Bloom* @greggish https://twitter.com/greggish/
> status/873177525903609857
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Katello::Errors::PulpError: PLP0000: /path/to/thing exists, but should be a symlink. Cannot find published directory.

[Lachlan Musicman]

On 30 August 2017 at 09:30, Lachlan Musicman <data...@gmail.com> wrote:

> Error per subject line, but no obvious method to resolve?
>
> Would be happy to stop task and delete that version - but even that is not
> an option?
>


Argh! My bad - found a very subtle "Skip" button in the Dynaflow. That
meant I could resume and delete when it completed.

cheers
L.






--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Katello::Errors::PulpError: PLP0000: /path/to/thing exists, but should be a symlink. Cannot find published directory.

[Lachlan Musicman]

Error per subject line, but no obvious method to resolve?

Would be happy to stop task and delete that version - but even that is not
an option?



cheers
L.


--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Re: subscription expected behaviour?

[Lachlan Musicman]

On 18 August 2017 at 12:58, Andrew Schofield  wrote:

> Activation keys are good for the initial host registration only. If you
> assign new products to a content view then you need to :
>
> a) Add these to the activation key (so newly provisioned servers get the
> new repos)
> b) Either manually / automatically subscribe servers to the new products
> from the host (command line / scripts / puppet etc) or use the web ui /
> hammer / api todo this
>
> Subscription manager (from memory I'm probably wrong on timings) will
> auto-refresh every 4 hrs or so.
>

Ah! This answers a question of mine from another thread.

Can someone give an example of the hammer command to update the
/etc/yum.repos.d/redhat.repo from the server?

Neither hammer repository nor hammer repository-set seem quite right.

Alternatively - and probably preferably (so that it can be scripted to run
via ansible) - the puppet command that would pull updates to the repo file?

cheers
L.





--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Katello 3.4 (Oud Bruin) Released!

[Lachlan Musicman]

On 30 May 2017 at 16:31, Evgeni Golov <evg...@redhat.com> wrote:

> On Tue, May 30, 2017 at 11:50:40AM +1000, Lachlan Musicman wrote:
> > On 30 May 2017 at 11:40, Lachlan Musicman <data...@gmail.com> wrote:
> >
> > > Great, thanks.
> > >
> > > I am seeing another issue:
> > >
> > >  - yum clean all, all good
> > >  - yum upgrade doesn't recognise new repos. If I look into
> > > /etc/yum.repos.d/redhat.repo and the new products aren't listed in that
> > > file.
> > >
> > > In order to get it to work, traditionally I've then performed:
> > >
> > > subscription-manager identity
> > > subscription-manager unsubscribe
> > > subscription-manager register --org="ACMI" --activationkey="Utility
> > > Server"
> >
> > I have discovered that my traditional method was finally deprecated and
> it
> > didn't work.
> >
> > But I also found that the slightly easier work around works:
> >
> > subscription-manager repos
> >
> > For whatever reason, that refreshes the redhat.repo.
>
> So would "subscription-manager refresh".
> When you change repos, your subscription changes, but it is not pulled
> in on every yum invocation.
>
> You can set full_refresh_on_yum = 1 in rhsm.conf, but even then not
> every aspect is properly updated [1].
>
> Also, I would suggest against using sub-man unregister && sub-man
> register as a cluebat workaround. The subscription certificate is also
> used for katello-agent, and if you don't restart it after doing the
> sub-man dance, you end up without the ability to apply errata via
> katello-agent.
>



Can I ask - since the unregister, reregister workaround is cluebat, what
are we to do when the subscription-manager refresh doesn't work as you
state it does?

We have systems - that I've just updated - but are not finding the new
redhat.repo or the updates therein.

Whereas the unregister, reregister workaround is shown to work,
consistently.

cheers
L.

--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Re: LCE or CV/CCV package differentials

[Lachlan Musicman]

Thanks Eric,

I'll take a look at the RFC/etc - but if you have some scripts I could look
at that would be appreciated too.

cheers
L.

--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

On 4 August 2017 at 10:49, Eric D Helms <eric.d.he...@gmail.com> wrote:

> There are existing issues around this large feature and an RFC if you'd
> like to contribute via review:
>
> https://github.com/theforeman/rfcs/pull/17
>
> I've written a script using both hammer and apipie to do comparisons I
> could share.
>
> On Aug 3, 2017 7:35 PM, "Lachlan Musicman" <data...@gmail.com> wrote:
>
>>
>> On 3 August 2017 at 22:42, Greg Sutcliffe <greg.sutcli...@gmail.com>
>> wrote:
>>
>>> On Wed, 2017-08-02 at 13:02 +1000, Lachlan Musicman wrote:
>>> > On the "I wish" pile.
>>>
>>> Maybe also add it to our "I wish" pile too? :)
>>>
>>> http://projects.theforeman.org/projects/katello/issues/new
>>>
>>
>> http://projects.theforeman.org/issues/20501
>>
>>
>>
>>
>> --
>> "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic
>> civics is the insistence that we cannot ignore the truth, nor should we
>> panic about it. It is a shared consciousness that our institutions have
>> failed and our ecosystem is collapsing, yet we are still here — and we are
>> creative agents who can shape our destinies. Apocalyptic civics is the
>> conviction that the only way out is through, and the only way through is
>> together. "
>>
>> *Greg Bloom* @greggish https://twitter.com/greggish/s
>> tatus/873177525903609857
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> Visit this group at https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Re: LCE or CV/CCV package differentials

[Lachlan Musicman]

On 3 August 2017 at 22:42, Greg Sutcliffe <greg.sutcli...@gmail.com> wrote:

> On Wed, 2017-08-02 at 13:02 +1000, Lachlan Musicman wrote:
> > On the "I wish" pile.
>
> Maybe also add it to our "I wish" pile too? :)
>
> http://projects.theforeman.org/projects/katello/issues/new
>

http://projects.theforeman.org/issues/20501




--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Re: LCE or CV/CCV package differentials

[Lachlan Musicman]

Yeah - even just that command I found took a long time to process, and that
CV has 4 Products in it, so it might be quite long.

I woke up at 3am wondering if I should teach myself ruby and build a module
that interrogates the database directly, but then I remembered my todo list.

On the "I wish" pile.

Thanks for the feedback.

cheers
L.

--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

On 2 August 2017 at 12:49, Andrew Schofield <a...@ourhavens.co.uk> wrote:

> There is no easy way to do this. We have the same issue and I'd think its
> a pretty basic use case!
>
> From memory, there is a compare API endpoint but that will only report on
> errata differences between two content view versions.
>
> We do this by grabbing all packages / puppet modules (as that's the two
> bits we're interested in) in the two content view versions and diff'ing.
> Its slow. Really slow - like 15 minutes or so slow.
>
> On Tuesday, August 1, 2017 at 12:59:02 AM UTC-4, Lachlan Musicman wrote:
>>
>> On 1 August 2017 at 14:14, Lachlan Musicman <dat...@gmail.com> wrote:
>>
>>> Hola,
>>>
>>> Is there an easy way to get a comprehensive list of package changes
>>> between two CV versions or two Lifecycle Environment versions?
>>>
>>> I'm looking into the hammer help now, and have found
>>> http://projects.theforeman.org/issues/20046
>>> <http://www.google.com/url?q=http%3A%2F%2Fprojects.theforeman.org%2Fissues%2F20046=D=1=AFQjCNH_wK1hwk8FkYio5FsGU7oQLi2VxQ>
>>> which suggests that a per CV package list is available. I could wrap up
>>> a couple of those in a bash script I guess?
>>>
>>> I presumed this would be a solved problem - being able to report on what
>>> packages will change should the LCE be promoted to the new CV version.
>>> That's the actual problem I'm trying to solve - am I doing it wrong again?
>>>
>>
>>
>> After some banging away, I found this:
>>
>> hammer package list --organization-id 1 --content-view-id 25
>> --content-view-version 25 --repository-id 2
>>
>> returned a list, but only after I'd tried
>>
>> hammer package list --organization-id 1 --content-view-id 25
>>
>> then
>>
>> hammer package list --organization-id 1 --content-view-id 25
>> --content-view-version 25
>>
>> It would be great to be able to iterate over the included repo versions
>> without necessarily needing to know what they were - so that
>>
>> hammer package list --organization-id 1 --content-view-id 25
>> --content-view-version 25
>>
>> returned a list of packages of all the repos in it? Am I missing
>> something simple?
>>
>> L.
>>
>>
>> --
>> "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic
>> civics is the insistence that we cannot ignore the truth, nor should we
>> panic about it. It is a shared consciousness that our institutions have
>> failed and our ecosystem is collapsing, yet we are still here — and we are
>> creative agents who can shape our destinies. Apocalyptic civics is the
>> conviction that the only way out is through, and the only way through is
>> together. "
>>
>> *Greg Bloom* @greggish https://twitter.com/greggish/s
>> tatus/873177525903609857
>>
>> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: LCE or CV/CCV package differentials

[Lachlan Musicman]

On 1 August 2017 at 14:14, Lachlan Musicman <data...@gmail.com> wrote:

> Hola,
>
> Is there an easy way to get a comprehensive list of package changes
> between two CV versions or two Lifecycle Environment versions?
>
> I'm looking into the hammer help now, and have found
> http://projects.theforeman.org/issues/20046
> which suggests that a per CV package list is available. I could wrap up a
> couple of those in a bash script I guess?
>
> I presumed this would be a solved problem - being able to report on what
> packages will change should the LCE be promoted to the new CV version.
> That's the actual problem I'm trying to solve - am I doing it wrong again?
>


After some banging away, I found this:

hammer package list --organization-id 1 --content-view-id 25
--content-view-version 25 --repository-id 2

returned a list, but only after I'd tried

hammer package list --organization-id 1 --content-view-id 25

then

hammer package list --organization-id 1 --content-view-id 25
--content-view-version 25

It would be great to be able to iterate over the included repo versions
without necessarily needing to know what they were - so that

hammer package list --organization-id 1 --content-view-id 25
--content-view-version 25

returned a list of packages of all the repos in it? Am I missing something
simple?

L.


--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] LCE or CV/CCV package differentials

[Lachlan Musicman]

Hola,

Is there an easy way to get a comprehensive list of package changes between
two CV versions or two Lifecycle Environment versions?

I'm looking into the hammer help now, and have found
http://projects.theforeman.org/issues/20046
which suggests that a per CV package list is available. I could wrap up a
couple of those in a bash script I guess?

I presumed this would be a solved problem - being able to report on what
packages will change should the LCE be promoted to the new CV version.
That's the actual problem I'm trying to solve - am I doing it wrong again?



Cheers
L.


--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users]

[Lachlan Musicman]

I updated to Katello 3.4.3 and it seems to now be working.

cheers
L.

--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

On 17 July 2017 at 08:38, Lachlan Musicman <data...@gmail.com> wrote:

> On 14 July 2017 at 21:33, Daniel Lobato Garcia <elobat...@gmail.com>
> wrote:
>
>> >
>> > I'm getting the error:
>> >
>> > RPM1015: Malformed repository: metadata is missing for some packages
>> > in filelists.xml and in other.xml
>> >
>> > There are a lot of pulp bugs reported to this end, but none with a
>> working
>> > fix.
>> >
>> > Any ideas on how to get past this?
>>
>> Please try again, we had to remove a package yesterday (rubygem-safemode
>> 1.3.2) and had to regenerate metadata, around 2h the metadata was wrong.
>> If you still get the error let us know.
>>
>> cc http://projects.theforeman.org/issues/20301
>>
>
> Still getting the same error.
>
> Tried advanced sync -> Complete Sync and Validate Complete Sync but
> neither fixes the problem - they both end with the same warning.
>
> cheers
> L.
>
>
> --
> "Mission Statement: To provide hope and inspiration for collective action,
> to build collective power, to achieve collective transformation, rooted in
> grief and rage but pointed towards vision and dreams."
>
>  - Patrisse Cullors, *Black Lives Matter founder*
>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users]

[Lachlan Musicman]

On 14 July 2017 at 21:33, Daniel Lobato Garcia  wrote:

> >
> > I'm getting the error:
> >
> > RPM1015: Malformed repository: metadata is missing for some packages
> > in filelists.xml and in other.xml
> >
> > There are a lot of pulp bugs reported to this end, but none with a
> working
> > fix.
> >
> > Any ideas on how to get past this?
>
> Please try again, we had to remove a package yesterday (rubygem-safemode
> 1.3.2) and had to regenerate metadata, around 2h the metadata was wrong.
> If you still get the error let us know.
>
> cc http://projects.theforeman.org/issues/20301
>

Still getting the same error.

Tried advanced sync -> Complete Sync and Validate Complete Sync but neither
fixes the problem - they both end with the same warning.

cheers
L.


--
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."

 - Patrisse Cullors, *Black Lives Matter founder*

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users]

[Lachlan Musicman]

With both

http://yum.theforeman.org/releases/1.15/el7/x86_64/

and

http://yum.theforeman.org/releases/latest/el7/x86_64/

I'm getting the error:

RPM1015: Malformed repository: metadata is missing for some packages
in filelists.xml and in other.xml

There are a lot of pulp bugs reported to this end, but none with a working
fix.

Any ideas on how to get past this?

Cheers
L.
--
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."

 - Patrisse Cullors, *Black Lives Matter founder*

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Hosts: One or more processes require restarting

[Lachlan Musicman]

Thanks Sean - perfect.

--
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."

 - Patrisse Cullors, *Black Lives Matter founder*

On 6 July 2017 at 18:18, Sean O'Keeffe <sokee...@redhat.com> wrote:

> It's coming from Katello...
>
> Go the Content host where packages & errata are you'll see an extra tab
> named "Traces" it will show you processes required to be restarted.
>
> You can also run "tracer -ea" on the client.
>
> On Wed, 5 Jul 2017 at 23:28, Lachlan Musicman <data...@gmail.com> wrote:
>
>> On 5 July 2017 at 23:38, Daniel Lobato Garcia <elobat...@gmail.com>
>> wrote:
>>
>>> On 07/05, Lachlan Musicman wrote:
>>> > When I look in the "all hosts" page of Foreman gui, some hosts are
>>> marked
>>> > as orange with the note "One or more processes require restarting":
>>> >
>>> > How do I find which process that is so I can restart it?
>>> >
>>>
>>> Could you share the logs in /var/log/foreman/production.log when loading
>>> the All hosts page? It seems that message is coming from somewhere else
>>> other than Foreman, but I'm not really sure where from
>>>
>>
>>
>> 2017-07-06 08:25:06 4c9f4157 [app] [I] Started GET
>> "/katello/sync_management/sync_status?repoids%5B%5D=73&_=1499293411615"
>> for 10.126.20.249 at 2017-07-06 08:25:06 +1000
>> 2017-07-06 08:25:06 4c9f4157 [app] [I] Processing by Katello::
>> SyncManagementController#sync_status as JSON
>> 2017-07-06 08:25:06 4c9f4157 [app] [I]   Parameters: {"repoids"=>["73"],
>> "_"=>"1499293411615"}
>> 2017-07-06 08:25:06 4c9f4157 [app] [I] Current user: admin (administrator)
>> 2017-07-06 08:25:06 4c9f4157 [app] [I] Completed 200 OK in 49ms (Views:
>> 0.2ms | ActiveRecord: 6.0ms)
>> 2017-07-06 08:25:11 8303606a [app] [I] Started GET "/node/
>> vmpr-linuxidm.unix.domain.com?format=yml" for 10.126.18.72 at 2017-07-06
>> 08:25:11 +1000
>> 2017-07-06 08:25:11 8303606a [app] [I] Processing by
>> HostsController#externalNodes as YML
>> 2017-07-06 08:25:11 8303606a [app] [I]   Parameters: {"name"=>"
>> vmpr-linuxidm.unix.domain.com"}
>> 2017-07-06 08:25:11 8303606a [app] [I] Current user: foreman_api_admin
>> (administrator)
>> 2017-07-06 08:25:11 8303606a [app] [I]   Rendered text template (0.0ms)
>> 2017-07-06 08:25:11 8303606a [app] [I] Completed 200 OK in 138ms (Views:
>> 0.6ms | ActiveRecord: 9.3ms)
>> 2017-07-06 08:25:12 ad665be4 [app] [I] Started POST "/api/hosts/facts"
>> for 10.126.18.72 at 2017-07-06 08:25:12 +1000
>> 2017-07-06 08:25:12 ad665be4 [app] [I] Processing by
>> Api::V2::HostsController#facts as JSON
>> 2017-07-06 08:25:12 ad665be4 [app] [I]   Parameters:
>> {"facts"=>"[FILTERED]", "name"=>"vmpr-linuxidm.unix.domain.com",
>> "certname"=>"vmpr-linuxidm.unix.domain.com", "apiv"=>"v2",
>> :host=>{"certname"=>"vmpr-linuxidm.unix.domain.com", "name"=>"
>> vmpr-linuxidm.unix.domain.com"}}
>> 2017-07-06 08:25:12 ad665be4 [app] [I] Current user: foreman_api_admin
>> (administrator)
>> 2017-07-06 08:25:12 ad665be4 [audit] [I] [vmpr-linuxidm.unix.domain.com]
>> deleted 0 (16.8ms)
>> 2017-07-06 08:25:12 ad665be4 [audit] [I] [vmpr-linuxidm.unix.domain.com]
>> updated 18 (493.3ms)
>> 2017-07-06 08:25:12 ad665be4 [audit] [I] [vmpr-linuxidm.unix.domain.com]
>> added 0 (4.1ms)
>> 2017-07-06 08:25:12 ad665be4 [app] [I] Import facts for '
>> vmpr-linuxidm.unix.domain.com' completed. Added: 0, Updated: 18, Deleted
>> 0 facts
>> 2017-07-06 08:25:12 ad665be4 [app] [I] Completed 201 Created in 582ms
>> (Views: 2.8ms | ActiveRecord: 84.8ms)
>> 2017-07-06 08:25:12 cd269e57 [app] [I] Started GET "/node/
>> vmpr-linuxidm.unix.domain.com?format=yml" for 10.126.18.72 at 2017-07-06
>> 08:25:12 +1000
>> 2017-07-06 08:25:12 cd269e57 [app] [I] Processing by
>> HostsController#externalNodes as YML
>> 2017-07-06 08:25:12 cd269e57 [app] [I]   Parameters: {"name"=>"
>> vmpr-linuxidm.unix.domain.com"}
>> 2017-07-06 08:25:13 cd269e57 [app] [I] Current user: foreman_api_admin
>> (administrator)
>> 2017-07-06 08:25:13 cd269e57 [app] [I]   Rendered text template (0.0ms)
>> 2017-

Re: [foreman-users] Hosts: One or more processes require restarting

[Lachlan Musicman]

On 5 July 2017 at 23:38, Daniel Lobato Garcia <elobat...@gmail.com> wrote:

> On 07/05, Lachlan Musicman wrote:
> > When I look in the "all hosts" page of Foreman gui, some hosts are marked
> > as orange with the note "One or more processes require restarting":
> >
> > How do I find which process that is so I can restart it?
> >
>
> Could you share the logs in /var/log/foreman/production.log when loading
> the All hosts page? It seems that message is coming from somewhere else
> other than Foreman, but I'm not really sure where from
>


2017-07-06 08:25:06 4c9f4157 [app] [I] Started GET
"/katello/sync_management/sync_status?repoids%5B%5D=73&_=1499293411615" for
10.126.20.249 at 2017-07-06 08:25:06 +1000
2017-07-06 08:25:06 4c9f4157 [app] [I] Processing by
Katello::SyncManagementController#sync_status as JSON
2017-07-06 08:25:06 4c9f4157 [app] [I]   Parameters: {"repoids"=>["73"],
"_"=>"1499293411615"}
2017-07-06 08:25:06 4c9f4157 [app] [I] Current user: admin (administrator)
2017-07-06 08:25:06 4c9f4157 [app] [I] Completed 200 OK in 49ms (Views:
0.2ms | ActiveRecord: 6.0ms)
2017-07-06 08:25:11 8303606a [app] [I] Started GET "/node/
vmpr-linuxidm.unix.domain.com?format=yml" for 10.126.18.72 at 2017-07-06
08:25:11 +1000
2017-07-06 08:25:11 8303606a [app] [I] Processing by
HostsController#externalNodes as YML
2017-07-06 08:25:11 8303606a [app] [I]   Parameters: {"name"=>"
vmpr-linuxidm.unix.domain.com"}
2017-07-06 08:25:11 8303606a [app] [I] Current user: foreman_api_admin
(administrator)
2017-07-06 08:25:11 8303606a [app] [I]   Rendered text template (0.0ms)
2017-07-06 08:25:11 8303606a [app] [I] Completed 200 OK in 138ms (Views:
0.6ms | ActiveRecord: 9.3ms)
2017-07-06 08:25:12 ad665be4 [app] [I] Started POST "/api/hosts/facts" for
10.126.18.72 at 2017-07-06 08:25:12 +1000
2017-07-06 08:25:12 ad665be4 [app] [I] Processing by
Api::V2::HostsController#facts as JSON
2017-07-06 08:25:12 ad665be4 [app] [I]   Parameters:
{"facts"=>"[FILTERED]", "name"=>"vmpr-linuxidm.unix.domain.com",
"certname"=>"vmpr-linuxidm.unix.domain.com", "apiv"=>"v2",
:host=>{"certname"=>"vmpr-linuxidm.unix.domain.com", "name"=>"
vmpr-linuxidm.unix.domain.com"}}
2017-07-06 08:25:12 ad665be4 [app] [I] Current user: foreman_api_admin
(administrator)
2017-07-06 08:25:12 ad665be4 [audit] [I] [vmpr-linuxidm.unix.domain.com]
deleted 0 (16.8ms)
2017-07-06 08:25:12 ad665be4 [audit] [I] [vmpr-linuxidm.unix.domain.com]
updated 18 (493.3ms)
2017-07-06 08:25:12 ad665be4 [audit] [I] [vmpr-linuxidm.unix.domain.com]
added 0 (4.1ms)
2017-07-06 08:25:12 ad665be4 [app] [I] Import facts for '
vmpr-linuxidm.unix.domain.com' completed. Added: 0, Updated: 18, Deleted 0
facts
2017-07-06 08:25:12 ad665be4 [app] [I] Completed 201 Created in 582ms
(Views: 2.8ms | ActiveRecord: 84.8ms)
2017-07-06 08:25:12 cd269e57 [app] [I] Started GET "/node/
vmpr-linuxidm.unix.domain.com?format=yml" for 10.126.18.72 at 2017-07-06
08:25:12 +1000
2017-07-06 08:25:12 cd269e57 [app] [I] Processing by
HostsController#externalNodes as YML
2017-07-06 08:25:12 cd269e57 [app] [I]   Parameters: {"name"=>"
vmpr-linuxidm.unix.domain.com"}
2017-07-06 08:25:13 cd269e57 [app] [I] Current user: foreman_api_admin
(administrator)
2017-07-06 08:25:13 cd269e57 [app] [I]   Rendered text template (0.0ms)
2017-07-06 08:25:13 cd269e57 [app] [I] Completed 200 OK in 132ms (Views:
0.7ms | ActiveRecord: 8.5ms)
2017-07-06 08:25:13 cf0d2136 [app] [I] Started POST "/api/config_reports"
for 10.126.18.72 at 2017-07-06 08:25:13 +1000
2017-07-06 08:25:13 cf0d2136 [app] [I] Processing by
Api::V2::ConfigReportsController#create as JSON
2017-07-06 08:25:13 cf0d2136 [app] [I]   Parameters:
{"config_report"=>"[FILTERED]", "apiv"=>"v2"}
2017-07-06 08:25:13 cf0d2136 [app] [I] Current user: foreman_api_admin
(administrator)
2017-07-06 08:25:13 cf0d2136 [app] [I] processing report for
vmpr-linuxidm.unix.domain.com
2017-07-06 08:25:13 cf0d2136 [app] [I] Imported report for
vmpr-linuxidm.unix.domain.com in 0.03 seconds
2017-07-06 08:25:13 cf0d2136 [app] [I]   Rendered
api/v2/config_reports/create.json.rabl (9.1ms)
2017-07-06 08:25:13 cf0d2136 [app] [I] Completed 201 Created in 166ms
(Views: 9.2ms | ActiveRecord: 20.9ms)
2017-07-06 08:25:14 eff41368 [app] [I] Started GET
"/katello/sync_management/sync_status?repoids%5B%5D=73&_=1499293411616" for
10.126.20.249 at 2017-07-06 08:25:14 +1000
2017-07-06 08:25:14 eff41368 [app] [I] Processing by
Katello::SyncManagementController#sync_status as JSON
2017-07-06 08:25:14 eff41368 [app] [I]   Parameters: {"repoids"=>["73"],
"_"=>&quo

[foreman-users] Hosts: One or more processes require restarting

[Lachlan Musicman]

When I look in the "all hosts" page of Foreman gui, some hosts are marked
as orange with the note "One or more processes require restarting":




How do I find which process that is so I can restart it?

cheers
L.
​
--
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."

 - Patrisse Cullors, *Black Lives Matter founder*

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Unable to add non-RHEL subscription to activation key

[Lachlan Musicman]

Make the Product into a Content View - then add that to the activation key,
then add the subscriptions.

Cheers
L.

--
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."

 - Patrisse Cullors, *Black Lives Matter founder*

On 4 July 2017 at 16:33, Stephen Odo  wrote:

> I'm running Katello 3.4.2. When creating an activation key, I click on the
> "Subscriptions" --> "Add" tab to add, say, EPEL (which I've set up as a
> product) to the activation key.
>
> The only choices that show up are the Red Hat subscriptions. None of the
> non-Red Hat products show up. Is there something special I need to do in
> order to add non-Red Hat subscriptions to an activation key?
>
> Thanks.
>
> --Stephen
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Couldn't find User with 'id'=3 [WHERE (1=0)]

[Lachlan Musicman]

Ah! Looks like I have stumbled across a bug that affects others.

A work around or fix would be appreciated - can't update a self hosted
katello while it's broken.

http://projects.theforeman.org/issues/20040
http://projects.theforeman.org/issues/20023

cheers
L.

--
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."

 - Patrisse Cullors, *Black Lives Matter founder*

On 19 June 2017 at 10:09, Lachlan Musicman <data...@gmail.com> wrote:

> All of my tasks are failing with the above error.
>
> I've tried clearing out the tasks, but they wont cancel, when I try to get
> to Dynaflow console, I get "Access forbidden"
>
> How do I kill those tasks and get back to a working state?
>
> cheers
> L.
>
>
>
> --
> "Mission Statement: To provide hope and inspiration for collective action,
> to build collective power, to achieve collective transformation, rooted in
> grief and rage but pointed towards vision and dreams."
>
>  - Patrisse Cullors, *Black Lives Matter founder*
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Listing all packages on all hosts?

[Lachlan Musicman]

FWIW, when I run

hammer host package list --host HOST_NAME

I get the error

SSL error: hostname "127.0.0.1" does not match the server certificate

cheers
L.

--
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."

 - Patrisse Cullors, *Black Lives Matter founder*

On 9 June 2017 at 08:10, Lachlan Musicman <data...@gmail.com> wrote:

> Is there a command line one liner that will list all packages installed on
> hosts?
>
> cheers
> L.
> --
> "Mission Statement: To provide hope and inspiration for collective action,
> to build collective power, to achieve collective transformation, rooted in
> grief and rage but pointed towards vision and dreams."
>
>  - Patrisse Cullors, *Black Lives Matter founder*
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Listing all packages on all hosts?

[Lachlan Musicman]

Is there a command line one liner that will list all packages installed on
hosts?

cheers
L.
--
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."

 - Patrisse Cullors, *Black Lives Matter founder*

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Katello 3.4 (Oud Bruin) Released!

[Lachlan Musicman]

On 30 May 2017 at 11:40, Lachlan Musicman <data...@gmail.com> wrote:

> Great, thanks.
>
> I am seeing another issue:
>
>  - add the various new products (pulp-3.4, katello-3.4, foreman-1.15 etc)
> to the Katello Content View (with or without removing pulp-3.3,
> katello-3.3, foreman-1.14) via (in UI) Yum Content, Repository Selection
>  - publish a new version of the Katello CV
>  - publish a new version of the Utility Server Composite Content View
> which includes the newly published Katello CV
>  - confirm they exist by going into Content Views -> Utility Server ->
> Versions -> Utility Server 38.0 -> Yum Content - Versions -> Yum
> repositories and confirm that the products are now in the new version
>  - promote the relevant host to the new Utility Server CCV
>  - yum clean all, all good
>  - yum upgrade doesn't recognise new repos. If I look into
> /etc/yum.repos.d/redhat.repo and the new products aren't listed in that
> file.
>
>
> In order to get it to work, traditionally I've then performed:
>
> subscription-manager identity
> subscription-manager unsubscribe
> subscription-manager register --org="ACMI" --activationkey="Utility
> Server"
>


I have discovered that my traditional method was finally deprecated and it
didn't work.

But I also found that the slightly easier work around works:


subscription-manager repos

For whatever reason, that refreshes the redhat.repo.

cheers
L.


--
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."

 - Patrisse Cullors, *Black Lives Matter founder*

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Katello 3.4 (Oud Bruin) Released!

[Lachlan Musicman]

Great, thanks.

I am seeing another issue:

 - add the various new products (pulp-3.4, katello-3.4, foreman-1.15 etc)
to the Katello Content View (with or without removing pulp-3.3,
katello-3.3, foreman-1.14) via (in UI) Yum Content, Repository Selection
 - publish a new version of the Katello CV
 - publish a new version of the Utility Server Composite Content View which
includes the newly published Katello CV
 - confirm they exist by going into Content Views -> Utility Server ->
Versions -> Utility Server 38.0 -> Yum Content - Versions -> Yum
repositories and confirm that the products are now in the new version
 - promote the relevant host to the new Utility Server CCV
 - yum clean all, all good
 - yum upgrade doesn't recognise new repos. If I look into
/etc/yum.repos.d/redhat.repo and the new products aren't listed in that
file.


In order to get it to work, traditionally I've then performed:

subscription-manager identity
subscription-manager unsubscribe
subscription-manager register --org="ACMI" --activationkey="Utility Server"


But I feel like this should be unnecessary.

If I promote the server to a new version I'd expect the changes to be
reflected in the repos available?

Am I doing something wrong with regard to how I'm managing my CV/CCVs or
pushing changes out?

Cheers
L.


--
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."

 - Patrisse Cullors, *Black Lives Matter founder*

On 30 May 2017 at 11:04, Eric D Helms <ericdhe...@gmail.com> wrote:

> The foreman-release-scl ensures that the necessary SCL epositories are
> setup and configured for a typical installation. If you are importing all
> the necessary repositories into Katello and using that yourself then I
> wouldn't worry about it.
>
> Eric
>
>
> On Mon, May 29, 2017 at 8:51 PM, Lachlan Musicman <data...@gmail.com>
> wrote:
>
>> Thanks for all the hard work.
>>
>> I'd like to ask a question about the upgrade instructions.
>>
>> In step 3, what does the line
>>
>>   yum update -y foreman-release-scl
>>
>> do?
>>
>> The other two lines make sense. This one, I don't quite understand.
>>
>> We host Katello on katello, so there is some jiggery-pokery with moving 
>> products and content views around,
>> and deploying them.
>>
>> Adding a new product (pulp-3.4, client-3.4, candlepin-3.4, katello-3.4, 
>> plugins-1.15, foreman-1.15 etc) is easy
>> enough as a sub for the other two lines in that instruction.
>>
>> I'm not 100% sure what the foreman-release-scl does? We are tracking the 
>> various extra repos as necessary,
>> I presume they are kept up to date, since they aren't as explicitly 
>> versioned. (rhsc, sig, passenger, puppet).
>>
>> I usually just ignore this step, but that is bad practice - what does it do?
>>
>> cheers
>>
>> L.
>>
>>
>>
>>
>>
>> --
>> "Mission Statement: To provide hope and inspiration for collective
>> action, to build collective power, to achieve collective transformation,
>> rooted in grief and rage but pointed towards vision and dreams."
>>
>>  - Patrisse Cullors, *Black Lives Matter founder*
>>
>> On 29 May 2017 at 14:32, Eric D Helms <ericdhe...@gmail.com> wrote:
>>
>>> All,
>>>
>>> We are happy to announce the GA of Katello 3.4. Highlights of the
>>> release:
>>>
>>>  * Better file repository content management
>>>  * Advanced repository syncing options for recovery and repair
>>>  * UI overhaul
>>>  * Content view force republishing
>>>  * Candlepin 2.0 support
>>>  * Pulp 2.12.2
>>>
>>> Release Notes:
>>> https://theforeman.org/plugins/katello/3.4/release_notes/rel
>>> ease_notes.html
>>>
>>> Installation:
>>> https://theforeman.org/plugins/katello/3.4/installation/index.html
>>>
>>> Upgrade:
>>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>>>
>>> See the changelog for detailed feature issues and bug fixes:
>>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md
>>>
>>> Bug reporting
>>> =
>>> If you come across a bug in your testing, please file it and note the
>>> version of Katello or Foreman that you're using in the report.
>>>
>>> http://projects.theforeman.org/projects/katello/issues/new
>>>
>>> --
>>> Eric D. Helms
>>

Re: [foreman-users] Katello 3.4 (Oud Bruin) Released!

[Lachlan Musicman]

Thanks for all the hard work.

I'd like to ask a question about the upgrade instructions.

In step 3, what does the line

  yum update -y foreman-release-scl

do?

The other two lines make sense. This one, I don't quite understand.

We host Katello on katello, so there is some jiggery-pokery with
moving products and content views around,
and deploying them.

Adding a new product (pulp-3.4, client-3.4, candlepin-3.4,
katello-3.4, plugins-1.15, foreman-1.15 etc) is easy
enough as a sub for the other two lines in that instruction.

I'm not 100% sure what the foreman-release-scl does? We are tracking
the various extra repos as necessary,
I presume they are kept up to date, since they aren't as explicitly
versioned. (rhsc, sig, passenger, puppet).

I usually just ignore this step, but that is bad practice - what does it do?

cheers

L.





--
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."

 - Patrisse Cullors, *Black Lives Matter founder*

On 29 May 2017 at 14:32, Eric D Helms  wrote:

> All,
>
> We are happy to announce the GA of Katello 3.4. Highlights of the release:
>
>  * Better file repository content management
>  * Advanced repository syncing options for recovery and repair
>  * UI overhaul
>  * Content view force republishing
>  * Candlepin 2.0 support
>  * Pulp 2.12.2
>
> Release Notes:
> https://theforeman.org/plugins/katello/3.4/release_
> notes/release_notes.html
>
> Installation:
> https://theforeman.org/plugins/katello/3.4/installation/index.html
>
> Upgrade:
> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>
> See the changelog for detailed feature issues and bug fixes:
> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md
>
> Bug reporting
> =
> If you come across a bug in your testing, please file it and note the
> version of Katello or Foreman that you're using in the report.
>
> http://projects.theforeman.org/projects/katello/issues/new
>
> --
> Eric D. Helms
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Katello 3.4 RC2 Available for Testing

[Lachlan Musicman]

Did Katello 3.4 get released yet - did I miss an announcement?

I feel like there has been movement on the github (3.4.0 released 11 days
ago, 3.4.0.1 released over the weekend?)

Cheers
L.

--
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."

 - Patrice Cullors, *Black Lives Matter founder*

On 28 April 2017 at 06:04, Eric D Helms  wrote:

> In conjunction with the release for Foreman 1.15 RC2, Katello 3.4 RC2 is
> now available for testing.
>
> Please help by testing and filing any issues that you find so that we may
> address them before the final release.
>
> Installation:
> https://theforeman.org/plugins/katello/3.4/installation/index.html
>
> Upgrade:
> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>
> See the preliminary changelog for detailed information:
> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md
>
> Bug reporting
> =
> If you come across a bug in your testing, please file it and note the
> version of Katello or Foreman that you're using in the report.
>
> http://projects.theforeman.org/projects/katello/issues/new
>
> --
> Eric D. Helms
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Foreman 1.14/Katello 3.3 upgrade make CCVs useless

[Lachlan Musicman]

Hi

I upgraded Foreman/Katello successfully (ie, without warning or error) from
1.13/3.2 -> 1.14/3.3

Now, when I go to a Composite Content Views, their "List/Remove Content
Views" has the right number of rows in the table, but there is no text nor
any ability to update to a newer version.

This makes them useless, and I'm not sure how to solve it?

I have rebooted the machine, and checked in Firefox and Chromium on Debian
Stretch, Chrome in Windows.

See attached images for eg

Also attached: the html source code for the table cell with the missing
value

How do I fix this?

cheers
L.
--
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."

 - Patrice Cullors, *Black Lives Matter founder*

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Filesystem changes for repositories after update?

[Lachlan Musicman]

Hi,

We recently (3 months ago?) updated from one version of Katello to the next
(Foreman 1.12 to 1.13; Katello 3.1 to 3.2). During that process I also
changed the structure of our Content Views and Composite Content Views to
better reflect our structures.

Last week we started to run out of room on the server in question and I
started to look around for what was using the space.

I noticed that there was a directory that contained a lot of data about CVs
that no longer existed.

/var/lib/pulp/published/yum/master has a lot of old data in it, and

/var/lib/pulp/published/yum/master/yum_distributor seems to have all the
newer data in it.


Since the CVs in question have been "deleted" from Katello, there is no
obvious way to clean this data up.

Is this a known change and can I delete the old data from this directory
(except from yum_distributor) or is there associated meta data stuck
somewhere that requires I use another method?

cheers
L.




--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Updating Subscriptions in Activation Key

[Lachlan Musicman]

When I update the subscriptions in an Activation Key, how do I get that
change pushed to the systems that are subscribed via that key?

I've tried yum clean all and subscription-manager refresh, but neither
works.

The only way I've had success is to subscription-manager unregister and
then re-register with the same key? That doesn't seem sensible or best
practice.

cheers
L.
--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Katello and Errata updates

[Lachlan Musicman]

Hola,

When one ticks off an Errata, a minor version of the Content View is
created (see att image).

How are they stored on the filesystem? Is it ok to delete any of the
versions an just keep the most recent?

For eg, if I make version 3.0 and then over a month there are 4 errata
updates, taking us to 3.4.

Can I delete the versions 3.1, 3.2 and 3.3? Can I delete version 3.0?

Are minor versions stored as a diff or as a snapshot of the whole CV?

cheers
L.
--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] CentOS foreman 1.12.4 puppet 3.7.x best Upgrade Procedure to puppet 4.x

[Lachlan Musicman]

The recommended steps in the docs are what I followed

https://theforeman.org/plugins/katello/3.2/upgrade/puppet.html


cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 2 March 2017 at 22:53, Karsten Horsmann  wrote:

> Hello List,
>
> i prepare my upgrade path to Puppet 4.x and i figure out the following
> steps:
>
> * Fresh new CentOS 7 Installation (because CentOS 6 is not longer
> supported by foreman)
> * Get my data from my old Installation to the new one
> * Get to the latest puppet 3.8.x version, enable future parse and see
> whats broken
> * Upgrade to the latest Foreman Version
> * Switch from passenger to puppet-server (java based) 1.xx in puppet 3.8.x
>
> Is there anybody out there, that can me hint to an good ressource for best
> upgrade/migrate strategy
> from 3.x to 4.x with an Foreman Setup? Would be a huge help in that kind
> of setup.
>
> And to make it even worst, i use puppetdb also.
>
> Kind Regards
> Karsten Horsmann
>
>
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Katello 3.3 building CentOS 7 hosts

[Lachlan Musicman]

I don't know if there's an automagic way to do it, but I use ansible to
change all files in /etc/yum.repos.d/ except "redhat.repo". In each file
change any enabled =1 to enabled = 0.

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 1 March 2017 at 21:55, Duncan Innes  wrote:

> Hi,
>
> I've built a new Katello 3.3 system and loaded it up with CentOS 7, EPEL,
> and Katello Client 3.3 channels.  The various repositories have been
> synched (although lazy sync). Content View, Activation Key etc created.
>
> When I build a new system, however, the installation of
> subscription-manager appears to be heading out to the internet rather than
> finding the relevant packages from the Katello server.  The top of my
> install.post.log reads:
>
> updating system time
> Loaded plugins: fastestmirror
> Determining fastest mirrors
>  * base: *mirror.sax.uk.as61049.net *
>  * extras: *mirror.bytemark.co.uk *
>  * updates: *mirrors.coreix.net *
> Resolving Dependencies
> --> Running transaction check
> ---> Package subscription-manager.x86_64 0:1.17.15-1.el7.centos will be
> installed
> --> Processing Dependency: python-rhsm >= 1.17.0 for package:
> subscription-manager-1.17.15-1.el7.centos.x86_64
> --> Processing Dependency: usermode for package:
> subscription-manager-1.17.15-1.el7.centos.x86_64
> --> Processing Dependency: python-ethtool for package:
> subscription-manager-1.17.15-1.el7.centos.x86_64
> --> Processing Dependency: python-dmidecode for package:
> subscription-manager-1.17.15-1.el7.centos.x86_64
> --> Processing Dependency: python-dateutil for package:
> subscription-manager-1.17.15-1.el7.centos.x86_64
> --> Running transaction check
> ---> Package python-dateutil.noarch 0:1.5-7.el7 will be installed
> ---> Package python-dmidecode.x86_64 0:3.10.13-11.el7 will be installed
> --> Processing Dependency: libxml2-python for package:
> python-dmidecode-3.10.13-11.el7.x86_64
> --> Processing Dependency: libxml2mod.so()(64bit) for package:
> python-dmidecode-3.10.13-11.el7.x86_64
> ---> Package python-ethtool.x86_64 0:0.8-5.el7 will be installed
> --> Processing Dependency: libnl.so.1()(64bit) for package:
> python-ethtool-0.8-5.el7.x86_64
> ---> Package python-rhsm.x86_64 0:1.17.9-1.el7 will be installed
> --> Processing Dependency: python-rhsm-certificates = 1.17.9-1.el7 for
> package: python-rhsm-1.17.9-1.el7.x86_64
> --> Processing Dependency: m2crypto for package:
> python-rhsm-1.17.9-1.el7.x86_64
> ---> Package usermode.x86_64 0:1.111-5.el7 will be installed
> --> Running transaction check
> ---> Package libnl.x86_64 0:1.1.4-3.el7 will be installed
> ---> Package libxml2-python.x86_64 0:2.9.1-6.el7_2.3 will be installed
> ---> Package m2crypto.x86_64 0:0.21.1-17.el7 will be installed
> ---> Package python-rhsm-certificates.x86_64 0:1.17.9-1.el7 will be
> installed
> --> Finished Dependency Resolution
>
> Dependencies Resolved
>
> 
> 
>  Package Arch  Version
>  Repository
>
>  Size
> 
> 
> Installing:
>  subscription-managerx86_641.17.15-1.el7.centos   base
>  883 k
> Installing for dependencies:
>  libnl   x86_641.1.4-3.el7base
>  128 k
>  libxml2-python  x86_642.9.1-6.el7_2.3base
>  247 k
>  m2cryptox86_640.21.1-17.el7  base
>  429 k
>  python-dateutil noarch1.5-7.el7  base
> 85 k
>  python-dmidecodex86_643.10.13-11.el7 base
> 82 k
>  python-ethtool  x86_640.8-5.el7  base
> 33 k
>  python-rhsm x86_641.17.9-1.el7   base
>  116 k
>  python-rhsm-certificatesx86_641.17.9-1.el7   base
> 38 k
>  usermodex86_641.111-5.el7base
>  193 k
>
> Transaction Summary
> 
> 
> Install  1 Package (+9 Dependent packages)
>
> Total download size: 2.2 M
> Installed size: 9.2 M
> Downloading packages:
> warning: 
> /var/cache/yum/x86_64/7/base/packages/python-dmidecode-3.10.13-11.el7.x86_64.rpm:
> Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY
> Public key for python-dmidecode-3.10.13-11.el7.x86_64.rpm is not installed
> 
> 
> Total  933 kB/s | 2.2 MB
>  00:02
> Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
> Importing GPG key 0xF4A80EB5:
>  Userid : "CentOS-7 Key (CentOS 7 Official Signing Key) <
> secur...@centos.org>"
>  Fingerprint: 6341 

Re: [foreman-users] Re: Sync is stuck in pending

[Lachlan Musicman]

Break or break through.

running

foreman-installer --scenario katello --upgrade

seems to have solved the issue.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 28 February 2017 at 11:39, Lachlan Musicman <data...@gmail.com> wrote:

> While I know it's deprecated, I've started looking at pulp-admin:
> https://www.mankier.com/1/pulp-admin#Tasks
>
> The task - in the GUI, the id, which I think is the Foreman task id, is
> dcbef693-85c3-4418-a189-6ebdb262d99f
>
> This returns
>
> [root@vmpr-res-utils ~]# pulp-admin -u admin tasks details --task-id
> dcbef693-85c3-4418-a189-6ebdb262d99f
> Enter password:
> +--+
>   Task Details
> +--+
>
> The following resource(s) could not be found:
>
>   dcbef693-85c3-4418-a189-6ebdb262d99f (resource_id)
>
>
> So this is the wrong id. I go looking in the dynaflow and see this in the
> "suspended" task
>
> pulp_task_group:
>   group_id: 9a8074c1-60ad-460d-80ad-9c6148d739ca
>
> [root@vmpr-res-utils ~]# pulp-admin -u admin tasks details --task-id 
> 9a8074c1-60ad-460d-80ad-9c6148d739ca
> +--+
>   Task Details
> +--+
>
> The following resource(s) could not be found:
>
>   9a8074c1-60ad-460d-80ad-9c6148d739ca (resource_id)
>
> Hmm. That's not ideal. Maybe I'm wrong - it does say "pulp_task_group" not
> "pulp_task":
>
> [root@vmpr-res-utils ~]# pulp-admin -u admin tasks list
> +--+
>  Tasks
> +--+
>
> No tasks found
>
> Hooh boy.
>
> Ok. So I've started seeing hints about a "force unlock" in some of the
> pulp/katello docs and bug reports, but can't find anything definitive.
>
> In desperation, I did, as per https://access.redhat.com/solutions/1381053
> :
>
> foreman-rake console
> ForemanTasks::Task.where(:state => :running).where(:label =>
> "Actions::Pulp::Repository::RegenerateApplicability").destroy_all
>
> And the sync status page in the GUI is returning 404.
>
>
> And now sync is failing on failed subtasks: RuntimeError: A sub task
> failed.
>
> pulp-admin returns
>
> Traceback (most recent call last):
>   File "/usr/bin/pulp-admin", line 9, in 
> load_entry_point('pulp-client-admin==2.9.3', 'console_scripts',
> 'pulp-admin')()
>   File "/usr/lib/python2.7/site-packages/pulp/client/admin/__init__.py",
> line 9, in main
> exit_code = launcher.main(read_config(), exception_handler_class=
> AdminExceptionHandler)
>   File "/usr/lib/python2.7/site-packages/pulp/client/launcher.py", line
> 115, in main
> code = cli.run(args)
>   File "/usr/lib/python2.7/site-packages/pulp/client/extensions/core.py",
> line 477, in run
> code = self.context.exception_handler.handle_exception(e)
>   File 
> "/usr/lib/python2.7/site-packages/pulp/client/extensions/exceptions.py",
> line 98, in handle_exception
> exit_code = handle_func(e)
>   File "/usr/lib/python2.7/site-packages/pulp_rpm/extensions/
> admin/rpm_admin_consumer/bind.py", line 64, in handle_not_found
> ExceptionHandler.handle_not_found(self, e)
>   File 
> "/usr/lib/python2.7/site-packages/pulp/client/extensions/exceptions.py",
> line 163, in handle_not_found
> for resource_type, resource_id in e.extra_data['resources'].items():
> KeyError: 'resources'
>
> foreman-rake returns
>
> [root@vmpr-res-utils ~]# foreman-rake katello:delete_orphaned_content
> --trace
> ** Invoke katello:delete_orphaned_content (first_time)
> ** Invoke environment (first_time)
> ** Execute environment
> ** Execute katello:delete_orphaned_content
> rake aborted!
> RestClient::ResourceNotFound: 404 Resource Not Found
> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.
> 8.0/lib/restclient/abstract_response.rb:74:in `return!'
> /opt/theforeman/tfm/root/usr/share/gems/gems/runcible-1.9.0/lib/runcible/base.rb:79:in
> `block in get_response'
> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.
> 8.0/lib/restclient/request.rb:493:in `call'
> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.
> 8.0/lib/restclient/request.rb:493:in `process_result'
> /opt/theforeman/tfm/root/usr/share/gems/gems/re

Re: [foreman-users] Re: Sync is stuck in pending

[Lachlan Musicman]

b/concurrent/actor/behaviour/abstract.rb:25:in
`pass'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/sets_results.rb:14:in
`on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
`pass'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/buffer.rb:38:in
`process_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/buffer.rb:31:in
`process_envelopes?'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/buffer.rb:20:in
`on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
`pass'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/termination.rb:55:in
`on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
`pass'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/removes_child.rb:10:in
`on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
`pass'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/sets_results.rb:14:in
`on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/core.rb:161:in
`process_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/core.rb:95:in
`block in on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/core.rb:118:in
`block (2 levels) in schedule_execution'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/synchronization/mri_lockable_object.rb:38:in
`block in synchronize'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/synchronization/mri_lockable_object.rb:38:in
`synchronize'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/synchronization/mri_lockable_object.rb:38:in
`synchronize'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/core.rb:115:in
`block in schedule_execution'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/executor/serialized_execution.rb:18:in
`call'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/executor/serialized_execution.rb:18:in
`call'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/executor/serialized_execution.rb:96:in
`work'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/executor/serialized_execution.rb:77:in
`block in call_job'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/executor/ruby_thread_pool_executor.rb:333:in
`call'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/executor/ruby_thread_pool_executor.rb:333:in
`run_task'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/executor/ruby_thread_pool_executor.rb:322:in
`block (3 levels) in create_worker'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/executor/ruby_thread_pool_executor.rb:305:in
`loop'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/executor/ruby_thread_pool_executor.rb:305:in
`block (2 levels) in create_worker'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/executor/ruby_thread_pool_executor.rb:304:in
`catch'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/executor/ruby_thread_pool_executor.rb:304:in
`block in create_worker'
/opt/theforeman/tfm/root/usr/share/gems/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in
`call'
/opt/theforeman/tfm/root/usr/share/gems/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in
`block in create_with_logging_context'


I've broken pulp, haven't I.

L.





--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 28 February 2017 at 09:29, Lachlan Musicman <data...@gmail.com> wrote:

> Thankyou - that worked in so much as it didn't throw an error.
>
> I still have the problem of four synchronisations that have stopped but
> aren't completing.
>
> By stopped I mean "are not advancing".
>
> As far as I can tell, they are in a running state - which is why the steps
> above didn't work, they were only for killing tasks in a paused state.
>
> Label: Actions::Katello::Repository::Sync
> Name: Synchroniz

Re: [foreman-users] Re: Sync is stuck in pending

[Lachlan Musicman]

Thankyou - that worked in so much as it didn't throw an error.

I still have the problem of four synchronisations that have stopped but
aren't completing.

By stopped I mean "are not advancing".

As far as I can tell, they are in a running state - which is why the steps
above didn't work, they were only for killing tasks in a paused state.

Label: Actions::Katello::Repository::Sync
Name: Synchronize
Owner: foreman_admin
Execution type: Delayed
Start at: 2017-02-25 03:01:08 +1100
Start before: -
Started at: 2017-02-25 03:01:08 +1100
Ended at:
State: running

So the task started a three days ago and hasn't advanced any more. This job
in particular is blocking the other three from completing according to the
relevant logs.

It looks like I have a suspended
Actions::Pulp::Repository::RegenerateApplicability:


16: Actions::Pulp::Repository::RegenerateApplicability (suspended) [
282330.29s / 1592.86s ]

but I see no documentation on how I might get it out of suspension?

cheers
L.


--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 27 February 2017 at 18:07, Sean O'Keeffe <sokee...@redhat.com> wrote:

> Try foreman-rake katello:reimport
>
> foreman-rake katello:reindex Has been renamed recently.
>
> On Mon, 27 Feb 2017 at 00:49, Lachlan Musicman <data...@gmail.com> wrote:
>
>> Search turned up this potential solution:
>>
>> https://access.redhat.com/discussions/2065363
>>
>> I tried restarting Katello service as noted, without success. I ended up
>> here
>>
>> https://access.redhat.com/solutions/1381053
>>
>> There's an error thrown on the last step:
>>
>> [root@vmpr-res-utils ~]# foreman-rake katello:reindex --trace
>> rake aborted!
>> Don't know how to build task 'katello:reindex'
>> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/task_manager.rb:62:in
>> `[]'
>> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:149:in
>> `invoke_task'
>> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:106:in
>> `block (2 levels) in top_level'
>> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:106:in
>> `each'
>> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:106:in
>> `block in top_level'
>> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:115:in
>> `run_with_threads'
>> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:100:in
>> `top_level'
>> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:78:in
>> `block in run'
>> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:176:in
>> `standard_exception_handling'
>> /opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:75:in
>> `run'
>> /opt/rh/rh-ruby22/root/usr/bin/rake:33:in `'
>>
>> That will teach me for trying to solve my own problems.
>>
>> The problem seems to have persisted - where do I look next?
>>
>> cheers
>> L.
>>
>>
>>
>> --
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> On 27 February 2017 at 09:39, Lachlan Musicman <data...@gmail.com> wrote:
>>
>> CentOS 7.3, Katello 3.2, Foreman 1.13.4
>>
>> And it's cascading - there are four other sync's that haven't finished
>> because one seems to be in a permanent pending state.
>>
>> I don't see any obvious cancel/resume function? The cancel link on the
>> sync status page bounces when clicked but...nothing.
>>
>> The logs/Dynaflow show no errors, it's just stopped at 71%.
>>
>> How to solve?
>>
>> (raw details below)
>>
>> cheers
>> L.
>>
>> {"repository"=>{"id"=>5, "name"=>"epel", "label"=>"epel"},
>>  "product"=>
>>   {"id"=>2,
>>"name"=>"Extra Packages for Enterprise Linux 7",
>>"label"=>"Extra_Packages_for_Enterprise_Linux_7_-_x86_64",
>>"cp_id"=>"1464869283627"},
>>  "provider"=>{"id"=>1, "name"=>"Anonymous"},
>>  "organization"=>
>>   {"id"=>1,
>>"name"=>"Peter MacCallum Cancer Centre",
>>"label"=>"Peter_MacCallum_Cancer_Centre"},
>>  "services_checked&quo

[foreman-users] Re: Sync is stuck in pending

[Lachlan Musicman]

Search turned up this potential solution:

https://access.redhat.com/discussions/2065363

I tried restarting Katello service as noted, without success. I ended up
here

https://access.redhat.com/solutions/1381053

There's an error thrown on the last step:

[root@vmpr-res-utils ~]# foreman-rake katello:reindex --trace
rake aborted!
Don't know how to build task 'katello:reindex'
/opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/task_manager.rb:62:in
`[]'
/opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:149:in
`invoke_task'
/opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:106:in
`block (2 levels) in top_level'
/opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:106:in
`each'
/opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:106:in
`block in top_level'
/opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:115:in
`run_with_threads'
/opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:100:in
`top_level'
/opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:78:in
`block in run'
/opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:176:in
`standard_exception_handling'
/opt/rh/rh-ruby22/root/usr/share/gems/gems/rake-10.4.2/lib/rake/application.rb:75:in
`run'
/opt/rh/rh-ruby22/root/usr/bin/rake:33:in `'

That will teach me for trying to solve my own problems.

The problem seems to have persisted - where do I look next?

cheers
L.



--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 27 February 2017 at 09:39, Lachlan Musicman <data...@gmail.com> wrote:

> CentOS 7.3, Katello 3.2, Foreman 1.13.4
>
> And it's cascading - there are four other sync's that haven't finished
> because one seems to be in a permanent pending state.
>
> I don't see any obvious cancel/resume function? The cancel link on the
> sync status page bounces when clicked but...nothing.
>
> The logs/Dynaflow show no errors, it's just stopped at 71%.
>
> How to solve?
>
> (raw details below)
>
> cheers
> L.
>
> {"repository"=>{"id"=>5, "name"=>"epel", "label"=>"epel"},
>  "product"=>
>   {"id"=>2,
>"name"=>"Extra Packages for Enterprise Linux 7",
>"label"=>"Extra_Packages_for_Enterprise_Linux_7_-_x86_64",
>"cp_id"=>"1464869283627"},
>  "provider"=>{"id"=>1, "name"=>"Anonymous"},
>  "organization"=>
>   {"id"=>1,
>"name"=>"Peter MacCallum Cancer Centre",
>"label"=>"Peter_MacCallum_Cancer_Centre"},
>  "services_checked"=>["pulp", "pulp_auth"],
>  "id"=>5,
>  "sync_result"=>
>   {"contents_changed"=>true,
>"pulp_tasks"=>
> [{"exception"=>nil,
>   "task_type"=>"pulp.server.managers.repo.sync.sync",
>   "_href"=>"/pulp/api/v2/tasks/5460a086-d7e8-4510-9549-c75766ec8fc2/",
>   "task_id"=>"5460a086-d7e8-4510-9549-c75766ec8fc2",
>   "tags"=>
>
> ["pulp:repository:Peter_MacCallum_Cancer_Centre-Extra_Packages_for_Enterprise_Linux_7_-_x86_64-epel",
> "pulp:action:sync"],
>   "finish_time"=>"2017-02-24T16:07:18Z",
>   "_ns"=>"task_status",
>   "start_time"=>"2017-02-24T16:01:23Z",
>   "traceback"=>nil,
>   "spawned_tasks"=>
>[{"_href"=>"/pulp/api/v2/tasks/a9843fac-51de-4fb0-a06d-31c0db9b108e/",
>  "task_id"=>"a9843fac-51de-4fb0-a06d-31c0db9b108e"}],
>   "progress_report"=>
>{"yum_importer"=>
>  {"content"=>
>{"items_total"=>22,
> "state"=>"FINISHED",
> "error_details"=>[],
> "details"=>
>  {"rpm_total"=>22,
>   "rpm_done"=>22,
>   "drpm_total"=>0,
>   "drpm_done"=>0},
> "size_total"=>16914540,
> "size_left"=>0,
> "items_left"=>0},
>   "comps"=>{"state"=>"FINISHED"},
>  

[foreman-users] Sync is stuck in pending

[Lachlan Musicman]

CentOS 7.3, Katello 3.2, Foreman 1.13.4

And it's cascading - there are four other sync's that haven't finished
because one seems to be in a permanent pending state.

I don't see any obvious cancel/resume function? The cancel link on the sync
status page bounces when clicked but...nothing.

The logs/Dynaflow show no errors, it's just stopped at 71%.

How to solve?

(raw details below)

cheers
L.

{"repository"=>{"id"=>5, "name"=>"epel", "label"=>"epel"},
 "product"=>
  {"id"=>2,
   "name"=>"Extra Packages for Enterprise Linux 7",
   "label"=>"Extra_Packages_for_Enterprise_Linux_7_-_x86_64",
   "cp_id"=>"1464869283627"},
 "provider"=>{"id"=>1, "name"=>"Anonymous"},
 "organization"=>
  {"id"=>1,
   "name"=>"Peter MacCallum Cancer Centre",
   "label"=>"Peter_MacCallum_Cancer_Centre"},
 "services_checked"=>["pulp", "pulp_auth"],
 "id"=>5,
 "sync_result"=>
  {"contents_changed"=>true,
   "pulp_tasks"=>
[{"exception"=>nil,
  "task_type"=>"pulp.server.managers.repo.sync.sync",
  "_href"=>"/pulp/api/v2/tasks/5460a086-d7e8-4510-9549-c75766ec8fc2/",
  "task_id"=>"5460a086-d7e8-4510-9549-c75766ec8fc2",
  "tags"=>
   
["pulp:repository:Peter_MacCallum_Cancer_Centre-Extra_Packages_for_Enterprise_Linux_7_-_x86_64-epel",
"pulp:action:sync"],
  "finish_time"=>"2017-02-24T16:07:18Z",
  "_ns"=>"task_status",
  "start_time"=>"2017-02-24T16:01:23Z",
  "traceback"=>nil,
  "spawned_tasks"=>
   [{"_href"=>"/pulp/api/v2/tasks/a9843fac-51de-4fb0-a06d-31c0db9b108e/",
 "task_id"=>"a9843fac-51de-4fb0-a06d-31c0db9b108e"}],
  "progress_report"=>
   {"yum_importer"=>
 {"content"=>
   {"items_total"=>22,
"state"=>"FINISHED",
"error_details"=>[],
"details"=>
 {"rpm_total"=>22,
  "rpm_done"=>22,
  "drpm_total"=>0,
  "drpm_done"=>0},
"size_total"=>16914540,
"size_left"=>0,
"items_left"=>0},
  "comps"=>{"state"=>"FINISHED"},
  "purge_duplicates"=>{"state"=>"FINISHED"},
  "distribution"=>
   {"items_total"=>0,
"state"=>"FINISHED",
"error_details"=>[],
"items_left"=>0},
  "errata"=>{"state"=>"FINISHED"},
  "metadata"=>{"state"=>"FINISHED"}}},
  "queue"=>
   "reserved_resource_worke...@vmpr-res-utils.unix.petermac.org.au.dq",
  "state"=>"finished",
  "worker_name"=>
   "reserved_resource_worke...@vmpr-res-utils.unix.petermac.org.au",
  "result"=>
   {"result"=>"success",
"importer_id"=>"yum_importer",
"exception"=>nil,
"repo_id"=>
 
"Peter_MacCallum_Cancer_Centre-Extra_Packages_for_Enterprise_Linux_7_-_x86_64-epel",
"traceback"=>nil,
"started"=>"2017-02-24T16:01:23Z",
"_ns"=>"repo_sync_results",
"completed"=>"2017-02-24T16:07:18Z",
"importer_type_id"=>"yum_importer",
"error_message"=>nil,
"summary"=>
 {"content"=>{"state"=>"FINISHED"},
  "comps"=>{"state"=>"FINISHED"},
  "purge_duplicates"=>{"state"=>"FINISHED"},
  "distribution"=>{"state"=>"FINISHED"},
  "errata"=>{"state"=>"FINISHED"},
  "metadata"=>{"state"=>"FINISHED"}},
"added_count"=>29,
"removed_count"=>-25,
"updated_count"=>14872,
"id"=>"58b05a36bdb1d60a7024bf11",
"details"=>
 {"content"=>
   {"size_total"=>16914540,
"items_left"=>0,
"items_total"=>22,
"state"=>"FINISHED",
"size_left"=>0,
"details"=>
 {"rpm_total"=>22,
  "rpm_done"=>22,
  "drpm_total"=>0,
  "drpm_done"=>0},
"error_details"=>[]},
  "comps"=>{"state"=>"FINISHED"},
  "purge_duplicates"=>{"state"=>"FINISHED"},
  "distribution"=>
   {"items_total"=>0,
"state"=>"FINISHED",
"error_details"=>[],
"items_left"=>0},
  "errata"=>{"state"=>"FINISHED"},
  "metadata"=>{"state"=>"FINISHED"}}},
  "error"=>nil,
  "_id"=>{"$oid"=>"58b058a1c47a37aeec805a43"},
  "id"=>"58b058a1c47a37aeec805a43"},
 {"exception"=>nil,
  "task_type"=>"pulp.server.managers.repo.publish.publish",
  "_href"=>"/pulp/api/v2/tasks/a9843fac-51de-4fb0-a06d-31c0db9b108e/",
  "task_id"=>"a9843fac-51de-4fb0-a06d-31c0db9b108e",
  "tags"=>
   
["pulp:repository:Peter_MacCallum_Cancer_Centre-Extra_Packages_for_Enterprise_Linux_7_-_x86_64-epel",
"pulp:action:publish"],
  "finish_time"=>"2017-02-24T16:09:45Z",
  "_ns"=>"task_status",
  "start_time"=>"2017-02-24T16:07:21Z",
  "traceback"=>nil,
  "spawned_tasks"=>[],
  "progress_report"=>
   
{"Peter_MacCallum_Cancer_Centre-Extra_Packages_for_Enterprise_Linux_7_-_x86_64-epel"=>
 [{"num_success"=>1,
   "description"=>"Initializing repo 

[foreman-users] Composite Content Views have become disassociated from CVs

[Lachlan Musicman]

Hola,

I seem to have a couple of CCVs that have become disassociated from their
relevantAs Content Views.

As can be seen in the screen shot, one CCV has completely unmoored and has
no CVs associated with it any more.

I have been aggressive in my cleaning up of old versions and views, but
I've always seen an error when trying to delete a version that was still
associated with a CCV or LCE, and presumed that error was an end point. IE,
nothing further happened, CV version wasn't deleted.

So, two questions, in order of importance.

1. How do I re-associate the CCV with it's CVs?
2. Any idea how this might have happened?

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Programmatic method for finding content views?

[Lachlan Musicman]

Oh, thank you. That's very helpful.

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 23 February 2017 at 09:47, 'Jason B. Nance' via Foreman users <
foreman-users@googlegroups.com> wrote:

> You have lots of options.
>
> The API:
> https:///apidoc/v2/content_views.html
>
> Nailgun:
> https://github.com/SatelliteQE/nailgun
>
> Various projects here:
> https://github.com/RedHatSatellite
>
>
>
> --
> *From: *"Lachlan Musicman" <data...@gmail.com>
> *To: *"Foreman Users" <foreman-users@googlegroups.com>
> *Sent: *Wednesday, February 22, 2017 4:39:58 PM
> *Subject: *[foreman-users] Programmatic method for finding content views?
>
> I have become comfortable with the Foreman/Katello GUI, but sometimes I
> want an easy way to find a list of Composite Content Views, their versions,
> what Content View is in each version of said Composite Content View, and
> what that version is.
>
> eg:
>
> list CCVs
>
> CCV Worker Node
> v5.0:
> - base centos 7.2 v4.0
> - extras v3.0
> - sssd@copr v2.0
>
> v4.0:
> - base centos 7.2 v3.0
> - extras v3.0
> - sssd@copr v2.0
>
> v3.0:
> - base centos 7.2 v3.0
> - extras v2.0
> - sssd@copr v1.0
>
> CCV Head Node
> v3.0:
> - base centos 7.2 v4.0
> - extras v3.0
> - sssd@copr v2.0
>
> CCV Utils
> v6.0
> - base centos 7.2 v4.0
> - extras v3.0
> - sssd@copr v2.0
> - forman v4.0
> - zabbix v2.0
>
> Is there a way to do that using a command line tool? (GUI is ok too)
>
> cheers
> L.
>
>
>
>
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Programmatic method for finding content views?

[Lachlan Musicman]

I have become comfortable with the Foreman/Katello GUI, but sometimes I
want an easy way to find a list of Composite Content Views, their versions,
what Content View is in each version of said Composite Content View, and
what that version is.

eg:

list CCVs

CCV Worker Node
v5.0:
- base centos 7.2 v4.0
- extras v3.0
- sssd@copr v2.0

v4.0:
- base centos 7.2 v3.0
- extras v3.0
- sssd@copr v2.0

v3.0:
- base centos 7.2 v3.0
- extras v2.0
- sssd@copr v1.0

CCV Head Node
v3.0:
- base centos 7.2 v4.0
- extras v3.0
- sssd@copr v2.0

CCV Utils
v6.0
- base centos 7.2 v4.0
- extras v3.0
- sssd@copr v2.0
- forman v4.0
- zabbix v2.0

Is there a way to do that using a command line tool? (GUI is ok too)

cheers
L.





--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] foreman-console throws rake error, fails to load console gems

[Lachlan Musicman]

Hi,

While trying to debug my other issues, I found this potential solution

https://access.redhat.com/solutions/1381053

after noticing that I had a "Package Profile Update" job in the planning
state but not moving to pending or doing anything.

Clicking on the job gave me

*Oops, we're sorry but something went wrong *plan_self has to be invoked
before being able to reference the output

(http://projects.theforeman.org/issues/16113)

On reflection, it's probably not the original bug report I found, but that
doesn't change the error I saw:

[root@utils ~]# foreman-rake console
/usr/share/foreman/lib/tasks/console.rake:6: warning: already initialized
constant ARGV
For some operations a user must be set, try User.current = User.first
Loading production environment (Rails 4.2.5.1)
Failed to load console gems, starting anyway
irb(main):001:0>


Is this a problem? How do I fix it?

cheers
L.


--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Pulp streamer is looking for non directory

[Lachlan Musicman]

Hola,

I am seeing a lot of errors because one repository seems to be off kilter.

The directory that it is publishing as being where the various rpms can be
found doesn't exist on the file system.

The symptoms I see on the content hosts are failures to update


https://katello.petermac.org.au/pulp/repos/PMCC/Worker/Node/custom/ELRepo_org_Community_Enterprise_Linux_Repository_for_el7/elrepo-mainline-kernel/kernel-ml-4.9.8-1.el7.elrepo.x86_64.rpm:
[Errno 14] HTTPS Error 404 - Not Found

https://access.redhat.com/articles/1320623

which ends with an "error downloading packages" error.

The repo exists and is syncing correctly.

On the server, in the messages, I'm seeing:

Feb 22 11:21:42 katello pulp_streamer: [-] 127.0.0.1 - -
[22/Feb/2017:00:21:41 +] "GET
/var/lib/pulp/content/units/rpm/43/697e454f4bd11a054a035a756afee9405c3f84882b7bdb3594ee9414e008c5/kernel-ml-4.9.8-1.el7.elrepo.x86_64.rpm
HTTP/1.1" 404 - "-" "urlgrabber/3.10 yum/3.4.3"

In this case the long string directory doesn't exist.

/var/lib/pulp/content/units/rpm/43 is there

697e454f4bd11a054a035a756afee9405c3f84882b7bdb3594ee9414e008c5 is not.

kernel-ml-4.9.8-1.el7.elrepo.x86_64.rpm is available in a couple of places,
but not

/var/lib/pulp/content/

only

/var/lib/pulp/published/

What has gone wrong and how can it be fixed?

cheers
L.
--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Promotion Errors: how to solve?

[Lachlan Musicman]

Hi,

Using CentOS 7.3 Katello 3.2 and Foreman 1.13.4

I'm getting an error while promoting a LCE. It is stuck on Paused. I can
skip the erroneous step, but then the repos are broken.

I'm confused about how to cancel, kill and/or unwind the job once it gets
into this state. I have been skipping, deleting and trying again, but that
seems like an awfully long way around?

When I look in dynaflow it's always this step that fails

85: Actions::Pulp::Repository::CopyYumMetadataFile (skipping) [ 57540.42s /
1.59s ]

I note that the error below has references to Katello 3.2.1.1:

/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.2.1.1/app/lib/actions/middleware/remote_action.rb:16:in
`block in run'


But I thought I was using Katello 3.2.2 - and, infact, if I look at the
about page I see the inconsistency there too - the plugins screen and the
"installed packages" screen disagree (see attached screenshots attached).
Could this be the issue?

Here is the error:
Action:

Actions::Pulp::Repository::CopyYumMetadataFile

Input:

{"source_pulp_id"=>
  "Peter_MacCallum_Cancer_Centre-GAFFA-3_0-_sssd-Copr_repository_for_sssd_1_15",
 "target_pulp_id"=>
  
"Peter_MacCallum_Cancer_Centre-Gaffa-dev-GAFFA-_sssd-Copr_repository_for_sssd_1_15",
 "clauses"=>nil,
 "remote_user"=>"admin",
 "remote_cp_user"=>"admin"}

Output:

{"pulp_tasks"=>
  [{"exception"=>nil,
"task_type"=>
 "pulp.server.managers.repo.unit_association.associate_from_repo",
"_href"=>"/pulp/api/v2/tasks/2a32001e-ed4d-4c83-9a02-cffd045b8f30/",
"task_id"=>"2a32001e-ed4d-4c83-9a02-cffd045b8f30",
"tags"=>
 
["pulp:repository:Peter_MacCallum_Cancer_Centre-Gaffa-dev-GAFFA-_sssd-Copr_repository_for_sssd_1_15",
  
"pulp:repository:Peter_MacCallum_Cancer_Centre-GAFFA-3_0-_sssd-Copr_repository_for_sssd_1_15",
  "pulp:action:associate"],
"finish_time"=>"2017-02-20T21:40:42Z",
"_ns"=>"task_status",
"start_time"=>"2017-02-20T21:40:41Z",
"traceback"=>
 "Traceback (most recent call last):\n  File
\"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 240, in
trace_task\nR = retval = fun(*args, **kwargs)\n  File
\"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line
484, in __call__\nreturn super(Task, self).__call__(*args,
**kwargs)\n  File
\"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line
103, in __call__\nreturn super(PulpTask, self).__call__(*args,
**kwargs)\n  File
\"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 437, in
__protected_call__\nreturn self.run(*args, **kwargs)\n  File
\"/usr/lib/python2.7/site-packages/pulp/server/managers/repo/unit_association.py\",
line 273, in associate_from_repo\nunits=transfer_units)\n  File
\"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/importer.py\",
line 58, in import_units\nreturn associate.associate(source_repo,
dest_repo, import_conduit, config, units)\n  File
\"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/associate.py\",
line 53, in associate\nassociated_units =
set([_associate_unit(dest_repo, unit) for unit in units])\n  File
\"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/associate.py\",
line 339, in _associate_unit\nreturn associate_copy_for_repo(unit,
dest_repo, True)\n  File
\"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/associate.py\",
line 379, in associate_copy_for_repo\n
new_unit.safe_import_content(unit._storage_path)\n  File
\"/usr/lib/python2.7/site-packages/pulp/server/db/model/__init__.py\",
line 905, in safe_import_content\nself.import_content(path,
location)\n  File
\"/usr/lib/python2.7/site-packages/pulp/server/db/model/__init__.py\",
line 879, in import_content\nstorage.put(self, path, location)\n
File \"/usr/lib/python2.7/site-packages/pulp/server/content/storage.py\",
line 123, in put\nmkdir(os.path.dirname(destination))\n  File
\"/usr/lib/python2.7/site-packages/pulp/server/content/storage.py\",
line 20, in mkdir\nos.makedirs(path)\n  File
\"/usr/lib64/python2.7/os.py\", line 157, in makedirs\nmkdir(name,
mode)\nPulpExecutionException: Pulp exception occurred:
PulpExecutionException\n",
"spawned_tasks"=>[],
"progress_report"=>{},
"queue"=>
 "reserved_resource_worke...@vmpr-res-utils.unix.petermac.org.au.dq",
"state"=>"error",
"worker_name"=>
 "reserved_resource_worke...@vmpr-res-utils.unix.petermac.org.au",
"error"=>
 {"code"=>"PLP",
  "data"=>{},
  "description"=>"Pulp exception occurred: PulpExecutionException",
  "sub_errors"=>[]},
"_id"=>{"$oid"=>"58ab62595ddf3db34f386add"},
"id"=>"58ab62595ddf3db34f386add"}],
 "poll_attempts"=>{"total"=>3, "failed"=>3}}

Exception:

Katello::Errors::PulpError: PLP: Pulp exception occurred:
PulpExecutionException

Backtrace:

/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.2.1.1/app/lib/actions/pulp/abstract_async_task.rb:121:in
`block in external_task='

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

[Lachlan Musicman]

It was the first thing I did after sending that email.

http://projects.theforeman.org/issues/18548

Let me know if you need any more information.

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 18 February 2017 at 13:44, Eric D Helms <eric.d.he...@gmail.com> wrote:

> Could you please file a bug report with this information including your
> fix or add it to an existing report so that we can look at getting this
> fixed in the upcoming 3.3 release?
>
> Thanks
> Eric
>
>
> On Feb 16, 2017 11:58 PM, "Lachlan Musicman" <data...@gmail.com> wrote:
>
> GOT IT.
>
> GADDAM.
>
> Edited
>
> /usr/share/katello-installer-base/hooks/pre/31-upgrade-puppet.rb
>
> commented out lines 21 and 22:
>
>   success << Kafo::Helpers.execute('mv /var/lib/puppet/ssl
> /etc/puppetlabs/puppet') if File.directory?('/var/lib/puppet/ssl')
>   success << Kafo::Helpers.execute('mv /var/lib/puppet/foreman_cache_data
> /opt/puppetlabs/puppet/cache/') if File.directory?('/var/lib/pupp
> et/foreman_cache_data')
>
> did a diff on the two folders in both, made sure they were matching.
>
> Ran foreman-installer --upgrade-puppet and it worked.
>
> Un commented to two lines,  ran Klass's 18131 bug solution after it, and
> all worked fine.
>
> cheers
> L.
>
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 17 February 2017 at 14:54, Lachlan Musicman <data...@gmail.com> wrote:
>
>> Daniel,
>>
>> running the instructions as per the puppet upgrade page failed again.
>>
>> On issue we kept running into was this, from
>> /var/log/foreman-installer/katello.log
>>
>> [ERROR 2017-02-17 13:44:48 main] mv: cannot move ‘/var/lib/puppet/ssl’ to
>> ‘/etc/puppetlabs/puppet/ssl’: File exists
>> [ERROR 2017-02-17 13:44:48 main] mv: cannot move
>> ‘/var/lib/puppet/foreman_cache_data’ to 
>> ‘/opt/puppetlabs/puppet/cache/foreman_cache_data’:
>> File exists
>> [ERROR 2017-02-17 13:44:48 main] Upgrade step copy_data failed. Check
>> logs for more information.
>>
>> If you could point me to the log file that this message is talking about,
>> I'd appreciate that. Note that physically removing the offending files
>> doesn't seem to work - obviously there is some part of the
>> --foreman-installer --update-puppet execution that  recreates them
>>
>> Moving onto the next page, we start to do the whole thing by hand, as per
>> http://projects.theforeman.org/projects/foreman/wiki/Upgradi
>> ng_from_Puppet_3_to_4
>>
>> Again, Step 1a and 1b completes fine, except for 1b.5 again - this time
>> we did a grep on the whole of /etc/httpd/conf.d - there is no mention of
>> /var/lib/puppet/ssl in there at all
>>
>>
>> Moving onto Step 2, I ran the instructions with the changes you suggested
>> - adding --forman to some of the command line options.
>>
>> ERROR: Unrecognised option '--foreman-puppet-server-implementation'
>>
>> See: 'foreman-installer --help'
>>
>> So I look at the help:
>>
>> # foreman-installer --help | grep implementation
>> --capsule-puppet-server-implementation  Puppet master
>> implementation, either "master" (traditional
>>
>> And then if I do a grep on reset, none of these commands exist?
>>
>> I tried noop with capsule-puppet-server-implementation=puppetserver with
>> both --foreman-reset-puppet-X (as per your recommendation) and
>> --reset-foreman-puppet-X (format in line with other options) and neither
>> worked - all died with "ERROR: Unrecognised option '--X-puppet-autosign'"
>>
>>
>> Any other pointers would be appreciated.
>>
>> cheers
>> L.
>>
>>
>> --
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> On 17 February 2017 at 11:18, Lachlan Musicman <data...@gmail.com> wrote:
>>
>>> Great - thanks all. VM snapshot from last week has been restored. We
>>> will try again now.
>>>
>>> cheers
>>> L.
>>>
>>> --
>>> The most dangerous phrase in the language is, "We've always done it this
>>> way."
>>>
>>> - Grace Hopper
>>>
>>> On 16 February 2017 at 22:06, Daniel Lobato Garcia <elobat...@gmail.com>
>>> wrote:
>>>
>>>> On 02/13, Lachlan Musicman wrote:
>>>> > Ok, 

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

[Lachlan Musicman]

GOT IT.

GADDAM.

Edited

/usr/share/katello-installer-base/hooks/pre/31-upgrade-puppet.rb

commented out lines 21 and 22:

  success << Kafo::Helpers.execute('mv /var/lib/puppet/ssl
/etc/puppetlabs/puppet') if File.directory?('/var/lib/puppet/ssl')
  success << Kafo::Helpers.execute('mv /var/lib/puppet/foreman_cache_data
/opt/puppetlabs/puppet/cache/') if
File.directory?('/var/lib/puppet/foreman_cache_data')

did a diff on the two folders in both, made sure they were matching.

Ran foreman-installer --upgrade-puppet and it worked.

Un commented to two lines,  ran Klass's 18131 bug solution after it, and
all worked fine.

cheers
L.


--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 17 February 2017 at 14:54, Lachlan Musicman <data...@gmail.com> wrote:

> Daniel,
>
> running the instructions as per the puppet upgrade page failed again.
>
> On issue we kept running into was this, from /var/log/foreman-installer/
> katello.log
>
> [ERROR 2017-02-17 13:44:48 main] mv: cannot move ‘/var/lib/puppet/ssl’ to
> ‘/etc/puppetlabs/puppet/ssl’: File exists
> [ERROR 2017-02-17 13:44:48 main] mv: cannot move 
> ‘/var/lib/puppet/foreman_cache_data’
> to ‘/opt/puppetlabs/puppet/cache/foreman_cache_data’: File exists
> [ERROR 2017-02-17 13:44:48 main] Upgrade step copy_data failed. Check logs
> for more information.
>
> If you could point me to the log file that this message is talking about,
> I'd appreciate that. Note that physically removing the offending files
> doesn't seem to work - obviously there is some part of the
> --foreman-installer --update-puppet execution that  recreates them
>
> Moving onto the next page, we start to do the whole thing by hand, as per
> http://projects.theforeman.org/projects/foreman/wiki/
> Upgrading_from_Puppet_3_to_4
>
> Again, Step 1a and 1b completes fine, except for 1b.5 again - this time we
> did a grep on the whole of /etc/httpd/conf.d - there is no mention of
> /var/lib/puppet/ssl in there at all
>
>
> Moving onto Step 2, I ran the instructions with the changes you suggested
> - adding --forman to some of the command line options.
>
> ERROR: Unrecognised option '--foreman-puppet-server-implementation'
>
> See: 'foreman-installer --help'
>
> So I look at the help:
>
> # foreman-installer --help | grep implementation
> --capsule-puppet-server-implementation  Puppet master implementation,
> either "master" (traditional
>
> And then if I do a grep on reset, none of these commands exist?
>
> I tried noop with capsule-puppet-server-implementation=puppetserver with
> both --foreman-reset-puppet-X (as per your recommendation) and
> --reset-foreman-puppet-X (format in line with other options) and neither
> worked - all died with "ERROR: Unrecognised option '--X-puppet-autosign'"
>
>
> Any other pointers would be appreciated.
>
> cheers
> L.
>
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 17 February 2017 at 11:18, Lachlan Musicman <data...@gmail.com> wrote:
>
>> Great - thanks all. VM snapshot from last week has been restored. We will
>> try again now.
>>
>> cheers
>> L.
>>
>> --
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> On 16 February 2017 at 22:06, Daniel Lobato Garcia <elobat...@gmail.com>
>> wrote:
>>
>>> On 02/13, Lachlan Musicman wrote:
>>> > Ok, I've found the itemized puppet upgrade instructions that are here:
>>> >
>>> > http://projects.theforeman.org/projects/foreman/wiki/
>>> > Upgrading_from_Puppet_3_to_4
>>> >
>>> > and the place where the doc'd process fails. I start there.
>>> >
>>> > When I get to Step 1b. Environments, SSL and Apache; part 5 states
>>> "Update
>>> > SSL paths in /etc/httpd/conf.d/05-foreman-ssl.conf or
>>> > /etc/apache2/sites-available/05-foreman-ssl.conf, changing
>>> > /var/lib/puppet/ssl to /etc/puppetlabs/puppet/ssl"
>>> >
>>> > but our /etc/httpd/conf.d/05-foreman-ssl.conf contains no reference to
>>> > *either* reference?
>>> >
>>> > Skip it.
>>> >
>>> > Go to next step, figuring we have little if any manual customisations,
>>> I do
>>> > step 2 and the first run give teh error
>>>
>>> I think all of these flags would be required and by removing them is why
>>> you see all of the 

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

[Lachlan Musicman]

Great - thanks all. VM snapshot from last week has been restored. We will
try again now.

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 16 February 2017 at 22:06, Daniel Lobato Garcia <elobat...@gmail.com>
wrote:

> On 02/13, Lachlan Musicman wrote:
> > Ok, I've found the itemized puppet upgrade instructions that are here:
> >
> > http://projects.theforeman.org/projects/foreman/wiki/
> > Upgrading_from_Puppet_3_to_4
> >
> > and the place where the doc'd process fails. I start there.
> >
> > When I get to Step 1b. Environments, SSL and Apache; part 5 states
> "Update
> > SSL paths in /etc/httpd/conf.d/05-foreman-ssl.conf or
> > /etc/apache2/sites-available/05-foreman-ssl.conf, changing
> > /var/lib/puppet/ssl to /etc/puppetlabs/puppet/ssl"
> >
> > but our /etc/httpd/conf.d/05-foreman-ssl.conf contains no reference to
> > *either* reference?
> >
> > Skip it.
> >
> > Go to next step, figuring we have little if any manual customisations, I
> do
> > step 2 and the first run give teh error
>
> I think all of these flags would be required and by removing them is why
> you see all of the errors. In order to use them, I think you can by
> appending --foreman to them, like:
>
>--foreman-puppet-server-implementation
>--foreman-reset-puppet-autosign
>etc...
>
> >
> > ERROR: Unrecognised option '--puppet-server-implementation'
> >
> > remove it, get
> >
> > ERROR: Unrecognised option '--reset-puppet-autosign'
> >
> > remove it, get
> >
> > ERROR: Unrecognised option '--reset-puppet-client-package'
> > (repeat for )...
> > ERROR: Unrecognised option '--reset-puppet-codedir'
> > ERROR: Unrecognised option '--reset-puppet-configtimeout'
> > ERROR: Unrecognised option '--reset-puppet-dir'
> >
> > At this point I remove all --reset-puppet directives and hope.
> >
> > There are errors. Oh, there it is, postgres isn't started but needs to be
> > started. The errors are now new errors, but the top error is the one that
> > we are warned about, so I run the command without the noop - I presume
> all
> > of these errors are related? See attached.
> >
> > cheers
> > L.
> >
> >
> > --
> > The most dangerous phrase in the language is, "We've always done it this
> > way."
> >
> > - Grace Hopper
> >
> > On 13 February 2017 at 11:28, Lachlan Musicman <data...@gmail.com>
> wrote:
> >
> > > I don't understand what I've done wrong - I am literally following the
> > > rule book here, but it seems to trip at every step.
> > >
> > > I read the logs, and discovered that there were only three files it
> > > couldn't find because katello was stopped (this still amazes me - "stop
> > > katello, then make foreman-installer get data from katello"???!!?!?!
> who
> > > designed/wrote this?)
> > >
> > > the files were:
> > >
> > > java-1.8.0-something_something
> > > puppet-agent-1.9.0-something-something
> > > puppetserver-2.7.2-something_something
> > >
> > > So I found them on the file system and installed them successfully by
> hand.
> > >
> > > I then repeated the above process of katello-services stop and
> > > foreman-installer --upgrade-puppet
> > >
> > > Now I get a fail on:
> > >
> > > Upgrade Step: copy_data...
> > >
> > > mv: cannot move ‘/var/lib/puppet/ssl’ to ‘/etc/puppetlabs/puppet/ssl’:
> > > File exists
> > >
> > > Upgrade step copy_data failed. Check logs for more information.
> > >
> > >
> > > So I moved those files out of the wayand tried again. Failed with
> the
> > > same message.
> > >
> > > Deleted the files, tried again - failed with the same message.
> > >
> > > Might I suggest that the puppet upgrade notes are not actually correct
> and
> > > that the foreman-installer --upgrade-puppet service needs a
> "--skip-broken"
> > > or "--skip-copy-data"
> > >
> > > Anyway - I guess my question now is do I even need to run the
> > > --upgrade-puppet?
> > >
> > > Cheers
> > > L.
> > >
> > >
> > >
> > >
> > >
> > > --
> > > The most dangerous phrase in the language is, "We've always done it
> this
> > > way."
> > >
> 

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

[Lachlan Musicman]

Klaas,

Thank you for this, much appreciated. We have decided to revert back to
snapshot taken last week and try again - your notes will be very helpful.

One thing in particular that has us confused is 18131 "foreman-installer
--upgrade-puppet fails to set new paths for foreman-installer"

http://projects.theforeman.org/issues/18131

In particular a full workflow.

ie, after running

foreman-installer --upgrade-puppet

you ran the listed solution in your comment?

I read the details on the Foreman/Puppet upgrade page, which was
interesting for background:
http://projects.theforeman.org/projects/foreman/wiki/Upgrading_from_Puppet_3_to_4
and it includes a similar, but not the same, step.

I presumed that the upgrade instructions listed on the Katello 3.2 page
would list any extra steps that might need to be taken.

I'll report back/take notes on how I go.

Cheers
L.



--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 15 February 2017 at 19:41, Klaas Demter  wrote:

> Hey,
> I've successfully upgraded to puppet4 on my katello. In the process I've
> fixed, reported and worked around several issues. Feel free to check the
> PRs/discussions of these tickets:
> http://projects.theforeman.org/issues/18123
> http://projects.theforeman.org/issues/18129
> http://projects.theforeman.org/issues/18131
> http://projects.theforeman.org/issues/18132
>
> After those workaround/fixes the upgrade katello 3.1.x to 3.2.3 worked for
> me including the puppet4 upgrade
>
>
> if you encounter different issues create a bugreport and maybe even try to
> fix it and create a pull request :)
>
> Greetings
> Klaas Demter
>
> ATIX - The Linux & Open Source Company
> www.atix.de
>
> - Ursprüngliche Mail -
> Von: "Mario Gamboa" 
> An: "Foreman users" 
> Gesendet: Mittwoch, 15. Februar 2017 09:18:54
> Betreff: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails
>
> Any solution ?
>
> Same  issues here the thing that is amazing the katello and foreman team
> they are planning to no support anymore puppet 3 on 1.15 foreman but how we
> are going to upgrade our current puppet 3 to 4 is ridiculous
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

[Lachlan Musicman]

and now yum update on the katello server fails on a certificate problem?

[Errno 14] curl#35 - "Peer does not recognize and trust the CA that issued
your certificate."

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 13 February 2017 at 12:56, Lachlan Musicman <data...@gmail.com> wrote:

> Ok, I've found the itemized puppet upgrade instructions that are here:
>
> http://projects.theforeman.org/projects/foreman/wiki/Upgradi
> ng_from_Puppet_3_to_4
>
> and the place where the doc'd process fails. I start there.
>
> When I get to Step 1b. Environments, SSL and Apache; part 5 states "Update
> SSL paths in /etc/httpd/conf.d/05-foreman-ssl.conf or
> /etc/apache2/sites-available/05-foreman-ssl.conf, changing
> /var/lib/puppet/ssl to /etc/puppetlabs/puppet/ssl"
>
> but our /etc/httpd/conf.d/05-foreman-ssl.conf contains no reference to
> *either* reference?
>
> Skip it.
>
> Go to next step, figuring we have little if any manual customisations, I
> do step 2 and the first run give teh error
>
> ERROR: Unrecognised option '--puppet-server-implementation'
>
> remove it, get
>
> ERROR: Unrecognised option '--reset-puppet-autosign'
>
> remove it, get
>
> ERROR: Unrecognised option '--reset-puppet-client-package'
> (repeat for )...
> ERROR: Unrecognised option '--reset-puppet-codedir'
> ERROR: Unrecognised option '--reset-puppet-configtimeout'
> ERROR: Unrecognised option '--reset-puppet-dir'
>
> At this point I remove all --reset-puppet directives and hope.
>
> There are errors. Oh, there it is, postgres isn't started but needs to be
> started. The errors are now new errors, but the top error is the one that
> we are warned about, so I run the command without the noop - I presume all
> of these errors are related? See attached.
>
> cheers
> L.
>
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 13 February 2017 at 11:28, Lachlan Musicman <data...@gmail.com> wrote:
>
>> I don't understand what I've done wrong - I am literally following the
>> rule book here, but it seems to trip at every step.
>>
>> I read the logs, and discovered that there were only three files it
>> couldn't find because katello was stopped (this still amazes me - "stop
>> katello, then make foreman-installer get data from katello"???!!?!?! who
>> designed/wrote this?)
>>
>> the files were:
>>
>> java-1.8.0-something_something
>> puppet-agent-1.9.0-something-something
>> puppetserver-2.7.2-something_something
>>
>> So I found them on the file system and installed them successfully by
>> hand.
>>
>> I then repeated the above process of katello-services stop and
>> foreman-installer --upgrade-puppet
>>
>> Now I get a fail on:
>>
>> Upgrade Step: copy_data...
>>
>> mv: cannot move ‘/var/lib/puppet/ssl’ to ‘/etc/puppetlabs/puppet/ssl’:
>> File exists
>>
>> Upgrade step copy_data failed. Check logs for more information.
>>
>>
>> So I moved those files out of the wayand tried again. Failed with the
>> same message.
>>
>> Deleted the files, tried again - failed with the same message.
>>
>> Might I suggest that the puppet upgrade notes are not actually correct
>> and that the foreman-installer --upgrade-puppet service needs a
>> "--skip-broken" or "--skip-copy-data"
>>
>> Anyway - I guess my question now is do I even need to run the
>> --upgrade-puppet?
>>
>> Cheers
>> L.
>>
>>
>>
>>
>>
>> --
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> On 13 February 2017 at 10:19, Lachlan Musicman <data...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Self hosted installation.
>>>
>>> The upgrade foreman-installer --upgrade-puppet fails because it can't
>>> find packages.
>>>
>>> Which would be because I've just turned off all services as asked to in
>>> the instructions found here
>>>
>>> https://www.theforeman.org/plugins/katello/3.2/upgrade/puppet.html
>>>
>>> under "in place migration".
>>>
>>>
>>> Seems like a chicken and an egg problem - how do I solve this issue?
>>>
>>> cheers
>>> L.
>>> --
>>> The most dangerous phrase in the language is, "We've always done it this
>>> way."
>>>
>>> - Grace Hopper
>>>
>>
>>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

[Lachlan Musicman]

Ok, I've found the itemized puppet upgrade instructions that are here:

http://projects.theforeman.org/projects/foreman/wiki/
Upgrading_from_Puppet_3_to_4

and the place where the doc'd process fails. I start there.

When I get to Step 1b. Environments, SSL and Apache; part 5 states "Update
SSL paths in /etc/httpd/conf.d/05-foreman-ssl.conf or
/etc/apache2/sites-available/05-foreman-ssl.conf, changing
/var/lib/puppet/ssl to /etc/puppetlabs/puppet/ssl"

but our /etc/httpd/conf.d/05-foreman-ssl.conf contains no reference to
*either* reference?

Skip it.

Go to next step, figuring we have little if any manual customisations, I do
step 2 and the first run give teh error

ERROR: Unrecognised option '--puppet-server-implementation'

remove it, get

ERROR: Unrecognised option '--reset-puppet-autosign'

remove it, get

ERROR: Unrecognised option '--reset-puppet-client-package'
(repeat for )...
ERROR: Unrecognised option '--reset-puppet-codedir'
ERROR: Unrecognised option '--reset-puppet-configtimeout'
ERROR: Unrecognised option '--reset-puppet-dir'

At this point I remove all --reset-puppet directives and hope.

There are errors. Oh, there it is, postgres isn't started but needs to be
started. The errors are now new errors, but the top error is the one that
we are warned about, so I run the command without the noop - I presume all
of these errors are related? See attached.

cheers
L.


--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 13 February 2017 at 11:28, Lachlan Musicman <data...@gmail.com> wrote:

> I don't understand what I've done wrong - I am literally following the
> rule book here, but it seems to trip at every step.
>
> I read the logs, and discovered that there were only three files it
> couldn't find because katello was stopped (this still amazes me - "stop
> katello, then make foreman-installer get data from katello"???!!?!?! who
> designed/wrote this?)
>
> the files were:
>
> java-1.8.0-something_something
> puppet-agent-1.9.0-something-something
> puppetserver-2.7.2-something_something
>
> So I found them on the file system and installed them successfully by hand.
>
> I then repeated the above process of katello-services stop and
> foreman-installer --upgrade-puppet
>
> Now I get a fail on:
>
> Upgrade Step: copy_data...
>
> mv: cannot move ‘/var/lib/puppet/ssl’ to ‘/etc/puppetlabs/puppet/ssl’:
> File exists
>
> Upgrade step copy_data failed. Check logs for more information.
>
>
> So I moved those files out of the wayand tried again. Failed with the
> same message.
>
> Deleted the files, tried again - failed with the same message.
>
> Might I suggest that the puppet upgrade notes are not actually correct and
> that the foreman-installer --upgrade-puppet service needs a "--skip-broken"
> or "--skip-copy-data"
>
> Anyway - I guess my question now is do I even need to run the
> --upgrade-puppet?
>
> Cheers
> L.
>
>
>
>
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 13 February 2017 at 10:19, Lachlan Musicman <data...@gmail.com> wrote:
>
>> Hi,
>>
>> Self hosted installation.
>>
>> The upgrade foreman-installer --upgrade-puppet fails because it can't
>> find packages.
>>
>> Which would be because I've just turned off all services as asked to in
>> the instructions found here
>>
>> https://www.theforeman.org/plugins/katello/3.2/upgrade/puppet.html
>>
>> under "in place migration".
>>
>>
>> Seems like a chicken and an egg problem - how do I solve this issue?
>>
>> cheers
>> L.
>> --
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
[ERROR 2017-02-13 12:47:40 main]  /Stage[main]/Certs/Privkey[/etc/pki/katello/private/katello-default-ca.key]: Could not evaluate: Execution of '/usr/bin/openssl rsa -in /root/ssl-build/katello-default-ca.key -out /root/ssl-build/katello-default-ca.key.tmp -passin file:/etc/pki/katello/private/katello-default-ca.pwd' returned 1: unable to load Private Key
[ERROR 2017-02-13 12:47:40 main] 139660402321312:error:06065064:digital envelope rout

[foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

[Lachlan Musicman]

I don't understand what I've done wrong - I am literally following the rule
book here, but it seems to trip at every step.

I read the logs, and discovered that there were only three files it
couldn't find because katello was stopped (this still amazes me - "stop
katello, then make foreman-installer get data from katello"???!!?!?! who
designed/wrote this?)

the files were:

java-1.8.0-something_something
puppet-agent-1.9.0-something-something
puppetserver-2.7.2-something_something

So I found them on the file system and installed them successfully by hand.

I then repeated the above process of katello-services stop and
foreman-installer --upgrade-puppet

Now I get a fail on:

Upgrade Step: copy_data...

mv: cannot move ‘/var/lib/puppet/ssl’ to ‘/etc/puppetlabs/puppet/ssl’: File
exists

Upgrade step copy_data failed. Check logs for more information.


So I moved those files out of the wayand tried again. Failed with the
same message.

Deleted the files, tried again - failed with the same message.

Might I suggest that the puppet upgrade notes are not actually correct and
that the foreman-installer --upgrade-puppet service needs a "--skip-broken"
or "--skip-copy-data"

Anyway - I guess my question now is do I even need to run the
--upgrade-puppet?

Cheers
L.





--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 13 February 2017 at 10:19, Lachlan Musicman <data...@gmail.com> wrote:

> Hi,
>
> Self hosted installation.
>
> The upgrade foreman-installer --upgrade-puppet fails because it can't
> find packages.
>
> Which would be because I've just turned off all services as asked to in
> the instructions found here
>
> https://www.theforeman.org/plugins/katello/3.2/upgrade/puppet.html
>
> under "in place migration".
>
>
> Seems like a chicken and an egg problem - how do I solve this issue?
>
> cheers
> L.
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Errno 14 404 not found

[Lachlan Musicman]

This seems to have solved itself when I published a new version and
promoted to that.

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 13 February 2017 at 09:40, Lachlan Musicman <data...@gmail.com> wrote:

> Hmnm, fixing by hand doesn't work - the /etc/yum.repos.d/redhat.repo
> updates/reverts itself every time?
>
> cheers
> L.
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 13 February 2017 at 09:39, Lachlan Musicman <data...@gmail.com> wrote:
>
>> I think I can see what the error is:
>>
>> we used to have a repo called Katello/client/ which held the client repo.
>>
>> Then, when I decided to upgrade to 3.2, I renamed the repo to
>> Katello/client-3.1 and added Katello/client-3.2
>>
>> This might be the first time that this content host/LCE/Activation key
>> has been associated with the newly named client repo.
>>
>> But I don't understand how the .repo file is made nor why the renaming
>> wouldn't click with any updates - is this a bug?
>>
>> Note: I'm pretty sure this is exactly what happened as the listed repo in
>> the error def doesn't work (browser gives 404)
>>
>> https://vmpr-res-utils.our.domain/pulp/repos/PMCC/Utility_
>> Prod/Utility_Server/custom/Katello/client
>>
>> but this definitely does show up in a browser (package list in browser)
>>
>> https://vmpr-res-utils.our.domain/pulp/repos/PMCC/Utility_
>> Prod/Utility_Server/custom/Katello/client-3_2
>>
>>
>> So - I can fix this by hand, but that is less than ideal. How do I fix it
>> more permanently?
>>
>> cheers
>> L.
>>
>>
>> --
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> On 13 February 2017 at 09:25, Lachlan Musicman <data...@gmail.com> wrote:
>>
>>> Hola,
>>>
>>> I promoted a LCE and when I tried updating the content host attached to
>>> it, I get the error
>>>
>>> [Errno 14] HTTPS Error 404 - Not Found
>>> Trying other mirror.
>>> To address this issue please refer to the below knowledge base article
>>>
>>> https://access.redhat.com/articles/1320623
>>>
>>> If above article doesn't help to resolve this issue please create a bug
>>> on https://bugs.centos.org/
>>>
>>>
>>>
>>>  One of the configured repositories failed (client),
>>>  and yum doesn't have enough cached data to continue. At this point the
>>> only
>>>  safe thing yum can do is fail. There are a few ways to work "fix" this:
>>>
>>>  1. Contact the upstream for the repository and get them to fix the
>>> problem.
>>>
>>>  2. Reconfigure the baseurl/etc. for the repository, to point to a
>>> working
>>> upstream. This is most often useful if you are using a newer
>>> distribution release than is supported by the repository (and the
>>> packages for the previous distribution release still work).
>>>
>>>  3. Run the command with the repository temporarily disabled
>>> yum --disablerepo=PMCC_Katello_client ...
>>>
>>>  4. Disable the repository permanently, so yum won't use it by
>>> default. Yum
>>> will then just ignore the repository until you permanently
>>> enable it
>>> again or use --enablerepo for temporary usage:
>>>
>>> yum-config-manager --disable PMCC_Katello_client
>>> or
>>> subscription-manager repos --disable=PMCC_Katello_client
>>>
>>>  5. Configure the failing repository to be skipped, if it is
>>> unavailable.
>>> Note that yum will try to contact the repo. when it runs most
>>> commands,
>>> so will have to try and fail each time (and thus. yum will be be
>>> much
>>> slower). If it is a very temporary problem though, this is often
>>> a nice
>>> compromise:
>>>
>>>
>>>
>>> Unfortunately, the page listed:
>>> https://access.redhat.com/articles/1320623
>>>
>>> is only available to RH subscribers. Is there a non subscriber version
>>> of this page?
>>>
>>> Alternatively, how do I fix the problem.
>>>
>>> cheers
>>> L.
>>> --
>>> The most dangerous phrase in the language is, "We've always done it this
>>> way."
>>>
>>> - Grace Hopper
>>>
>>
>>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Puppet upgrade from 3.x to 4.x fails

[Lachlan Musicman]

Hi,

Self hosted installation.

The upgrade foreman-installer --upgrade-puppet fails because it can't find
packages.

Which would be because I've just turned off all services as asked to in the
instructions found here

https://www.theforeman.org/plugins/katello/3.2/upgrade/puppet.html

under "in place migration".


Seems like a chicken and an egg problem - how do I solve this issue?

cheers
L.
--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Errno 14 404 not found

[Lachlan Musicman]

I think I can see what the error is:

we used to have a repo called Katello/client/ which held the client repo.

Then, when I decided to upgrade to 3.2, I renamed the repo to
Katello/client-3.1 and added Katello/client-3.2

This might be the first time that this content host/LCE/Activation key has
been associated with the newly named client repo.

But I don't understand how the .repo file is made nor why the renaming
wouldn't click with any updates - is this a bug?

Note: I'm pretty sure this is exactly what happened as the listed repo in
the error def doesn't work (browser gives 404)

https://vmpr-res-utils.our.domain/pulp/repos/PMCC/Utility_Prod/Utility_Server/custom/Katello/client

but this definitely does show up in a browser (package list in browser)

https://vmpr-res-utils.our.domain/pulp/repos/PMCC/Utility_Prod/Utility_Server/custom/Katello/client-3_2


So - I can fix this by hand, but that is less than ideal. How do I fix it
more permanently?

cheers
L.


--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 13 February 2017 at 09:25, Lachlan Musicman <data...@gmail.com> wrote:

> Hola,
>
> I promoted a LCE and when I tried updating the content host attached to
> it, I get the error
>
> [Errno 14] HTTPS Error 404 - Not Found
> Trying other mirror.
> To address this issue please refer to the below knowledge base article
>
> https://access.redhat.com/articles/1320623
>
> If above article doesn't help to resolve this issue please create a bug on
> https://bugs.centos.org/
>
>
>
>  One of the configured repositories failed (client),
>  and yum doesn't have enough cached data to continue. At this point the
> only
>  safe thing yum can do is fail. There are a few ways to work "fix" this:
>
>  1. Contact the upstream for the repository and get them to fix the
> problem.
>
>  2. Reconfigure the baseurl/etc. for the repository, to point to a
> working
> upstream. This is most often useful if you are using a newer
> distribution release than is supported by the repository (and the
> packages for the previous distribution release still work).
>
>  3. Run the command with the repository temporarily disabled
> yum --disablerepo=PMCC_Katello_client ...
>
>  4. Disable the repository permanently, so yum won't use it by
> default. Yum
> will then just ignore the repository until you permanently enable
> it
> again or use --enablerepo for temporary usage:
>
> yum-config-manager --disable PMCC_Katello_client
> or
> subscription-manager repos --disable=PMCC_Katello_client
>
>  5. Configure the failing repository to be skipped, if it is
> unavailable.
> Note that yum will try to contact the repo. when it runs most
> commands,
> so will have to try and fail each time (and thus. yum will be be
> much
> slower). If it is a very temporary problem though, this is often a
> nice
> compromise:
>
>
>
> Unfortunately, the page listed:
> https://access.redhat.com/articles/1320623
>
> is only available to RH subscribers. Is there a non subscriber version of
> this page?
>
> Alternatively, how do I fix the problem.
>
> cheers
> L.
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Unused Product lines?

[Lachlan Musicman]

Last week Edgars sent through the very useful repo of Sat6/Katello scripts
which I found excellent.

How might I discover which Products are unused?

By which I mean that no packages from them are installed on any content
hosts. I have a sneaking suspicion that there are some repositories in our
CVs that are artifacts of previous installations and may no longer be
necessary. I'd love to prune them.

Cheers
L.
--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Content View with status "Deletion from Library"

[Lachlan Musicman]

Ok - that completed successfully, but the CV remains. Hm.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 10 February 2017 at 15:25, 'Jason Nance' via Foreman users <
foreman-users@googlegroups.com> wrote:

> It probably would have helped had I said --upgrade. :-/
>
>
>
> On Feb 9, 2017, at 10:20 PM, Lachlan Musicman <data...@gmail.com> wrote:
>
> oooh. Big new world. Sorry, I mostly use the Katello/Foreman web gui. I'm
> just slowly coming to grips with the whole system. That's the command that
> I ran a couple of weeks ago when I updated.
>
> I'll run it again.
>
> cheers
> L.
>
>
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 10 February 2017 at 15:16, Lachlan Musicman <data...@gmail.com> wrote:
>
>> Great - one question, what is ?
>>
>>
>> --
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> On 10 February 2017 at 15:11, 'Jason Nance' via Foreman users <
>> foreman-users@googlegroups.com> wrote:
>>
>>> Running the reindex rake may help. Running foreman-installer >> flag> upgrade fixes weirdness for me sometimes as well.
>>>
>>> These are just shots in the dark. I haven't seen this particular issue.
>>>
>>> J
>>>
>>>
>>> On Feb 9, 2017, at 10:04 PM, Lachlan Musicman <data...@gmail.com> wrote:
>>>
>>> Foreman 1.13, Katello 3.2, Centos 7.3
>>>
>>> I tried to delete a CV, but it didn't want to delete. I tried numerous
>>> times.
>>>
>>> It finally seemed to work - but it remains in the list of CVs and when I
>>> select it, I can see it's status says Deletion from Library (2017-02-10
>>> 13:39:50 +1100) (which is 1.5 hrs ago).
>>>
>>> I get pulp timeouts on other actions, have restarted qpidd and all
>>> pulp-* are running.
>>>
>>> cheers
>>> L.
>>>
>>>
>>> --
>>> The most dangerous phrase in the language is, "We've always done it this
>>> way."
>>>
>>> - Grace Hopper
>>>
>>> --
>>> 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+unsubscr...@googlegroups.com.
>>> To post to this group, send email to foreman-users@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/foreman-users.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>>> 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+unsubscr...@googlegroups.com.
>>> To post to this group, send email to foreman-users@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/foreman-users.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Content View with status "Deletion from Library"

[Lachlan Musicman]

oooh. Big new world. Sorry, I mostly use the Katello/Foreman web gui. I'm
just slowly coming to grips with the whole system. That's the command that
I ran a couple of weeks ago when I updated.

I'll run it again.

cheers
L.



--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 10 February 2017 at 15:16, Lachlan Musicman <data...@gmail.com> wrote:

> Great - one question, what is ?
>
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 10 February 2017 at 15:11, 'Jason Nance' via Foreman users <
> foreman-users@googlegroups.com> wrote:
>
>> Running the reindex rake may help. Running foreman-installer > flag> upgrade fixes weirdness for me sometimes as well.
>>
>> These are just shots in the dark. I haven't seen this particular issue.
>>
>> J
>>
>>
>> On Feb 9, 2017, at 10:04 PM, Lachlan Musicman <data...@gmail.com> wrote:
>>
>> Foreman 1.13, Katello 3.2, Centos 7.3
>>
>> I tried to delete a CV, but it didn't want to delete. I tried numerous
>> times.
>>
>> It finally seemed to work - but it remains in the list of CVs and when I
>> select it, I can see it's status says Deletion from Library (2017-02-10
>> 13:39:50 +1100) (which is 1.5 hrs ago).
>>
>> I get pulp timeouts on other actions, have restarted qpidd and all pulp-*
>> are running.
>>
>> cheers
>> L.
>>
>>
>> --
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> Visit this group at https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> Visit this group at https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Content View with status "Deletion from Library"

[Lachlan Musicman]

Great - one question, what is ?


--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 10 February 2017 at 15:11, 'Jason Nance' via Foreman users <
foreman-users@googlegroups.com> wrote:

> Running the reindex rake may help. Running foreman-installer  flag> upgrade fixes weirdness for me sometimes as well.
>
> These are just shots in the dark. I haven't seen this particular issue.
>
> J
>
>
> On Feb 9, 2017, at 10:04 PM, Lachlan Musicman <data...@gmail.com> wrote:
>
> Foreman 1.13, Katello 3.2, Centos 7.3
>
> I tried to delete a CV, but it didn't want to delete. I tried numerous
> times.
>
> It finally seemed to work - but it remains in the list of CVs and when I
> select it, I can see it's status says Deletion from Library (2017-02-10
> 13:39:50 +1100) (which is 1.5 hrs ago).
>
> I get pulp timeouts on other actions, have restarted qpidd and all pulp-*
> are running.
>
> cheers
> L.
>
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: upgrading puppet

[Lachlan Musicman]

Ignore - I found the repo. The product it belonged to was added to the CV,
but tt was not added to the CV.

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 10 February 2017 at 13:56, Lachlan Musicman <data...@gmail.com> wrote:

> Foreman 1.13, katello 3.2
>
> We are self hosted.
>
> Following the instructions here:
>
> https://www.theforeman.org/plugins/katello/3.2/upgrade/puppet.html
>
> When I did this it told me I didn't have the puppet 4 repos in place.
>
> I look at the repos, and I can't see puppet 4 anywhere.
>
> Here http://yum.puppetlabs.com/el/7/products/x86_64/
>
> I can see puppet up to 3.8.7
>
> http://yum.puppetlabs.com/el/7/PC1/x86_64
>
> doesn't have a package in it call puppet?
>
> Is there a package called puppet 4 or does the long list of changes listed
> here
> https://docs.puppet.com/puppet/4.0/release_notes.html
> have a hidden line that says "we have moved from calling it puppet 4 to
> puppet-x?
>
> cheers
> L.
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] upgrading puppet

[Lachlan Musicman]

Foreman 1.13, katello 3.2

We are self hosted.

Following the instructions here:

https://www.theforeman.org/plugins/katello/3.2/upgrade/puppet.html

When I did this it told me I didn't have the puppet 4 repos in place.

I look at the repos, and I can't see puppet 4 anywhere.

Here http://yum.puppetlabs.com/el/7/products/x86_64/

I can see puppet up to 3.8.7

http://yum.puppetlabs.com/el/7/PC1/x86_64

doesn't have a package in it call puppet?

Is there a package called puppet 4 or does the long list of changes listed
here
https://docs.puppet.com/puppet/4.0/release_notes.html
have a hidden line that says "we have moved from calling it puppet 4 to
puppet-x?

cheers
L.
--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] CV publishing errors

[Lachlan Musicman]

Ah!

Thankfully, that worked for helping fix the issue that pulp-admin wouldn't
work.

Also, it meant that I could execute the instructions in the last post of
this thread to solver the "can't kill a promotion" problem:

https://groups.google.com/forum/#!topic/foreman-users/4p26hO1RDOU

Having said all that, I'm still having trouble deploying. Have deleted key,
LCE and CV. Will start again.

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 10 February 2017 at 12:28, 'Jason Nance' via Foreman users <
foreman-users@googlegroups.com> wrote:

> That's set automagically during foreman-installer. :)
>
> J
>
>
> On Feb 9, 2017, at 6:02 PM, Lachlan Musicman <data...@gmail.com> wrote:
>
> AH! No, I wasn't. Thank you - I don't remember setting that, but now I
> know.
>
> cheers
> L.
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 10 February 2017 at 10:08, 'Jason B. Nance' via Foreman users <
> foreman-users@googlegroups.com> wrote:
>
>> Are you using the user/pass from the "default_login" and
>> "default_password" in /etc/pulp/server.conf?
>>
>> j
>>
>>
>>
>> --
>> *From: *"Lachlan Musicman" <data...@gmail.com>
>> *To: *"Foreman Users" <foreman-users@googlegroups.com>
>> *Sent: *Thursday, February 9, 2017 4:58:03 PM
>> *Subject: *Re: [foreman-users] CV publishing errors
>>
>> /var/log/messages shows
>>
>> pulp.server.webservices.middleware.exception:INFO: Authentication with
>> username admin failed: invalid username or password
>>
>> cheers
>> L.
>>
>> --
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> On 10 February 2017 at 09:42, Lachlan Musicman <data...@gmail.com> wrote:
>>
>>> That didn't work either :/ same error.
>>>
>>>
>>> [root@vmpr-res-utils ~]# pulp-admin login -u admin -p admin
>>> The specified user does not have permission to execute the given command
>>>
>>>
>>> cheers
>>> L.
>>>
>>> --
>>> The most dangerous phrase in the language is, "We've always done it this
>>> way."
>>>
>>> - Grace Hopper
>>>
>>> On 10 February 2017 at 09:39, Tom McKay <thomasmc...@redhat.com> wrote:
>>>
>>>> Try including the -u admin -p admin on all the pulp-admin commands
>>>>
>>>> On Thu, Feb 9, 2017 at 5:30 PM, Lachlan Musicman <data...@gmail.com>
>>>> wrote:
>>>>
>>>>> CentOS 7.3.1611, foreman 1.13.4, katello 3.2.2, pulp* 2.9.3,
>>>>>
>>>>> When I try to publish a CV, I get this error
>>>>>
>>>>>
>>>>> Actions::Pulp::Repository::CopyYumMetadataFile
>>>>>
>>>>>
>>>>> {"source_pulp_id"=>
>>>>>   "Peter_MacCallum_Cancer_Centre-GAFFA-2_0-_sssd-Copr_reposito
>>>>> ry_for_sssd_1_15",
>>>>>  "target_pulp_id"=>
>>>>>   "Peter_MacCallum_Cancer_Centre-Gaffa-dev-GAFFA-_sssd-Copr_
>>>>> repository_for_sssd_1_15",
>>>>>  "clauses"=>nil,
>>>>>  "remote_user"=>"admin",
>>>>>  "remote_cp_user"=>"admin"}
>>>>>
>>>>> {"pulp_tasks"=>
>>>>>   [{"exception"=>nil,
>>>>> "task_type"=>
>>>>>  "pulp.server.managers.repo.unit_association.associate_from_repo",
>>>>> "_href"=>"/pulp/api/v2/tasks/39286b9b-7684-4b1c-b092-bc593d4
>>>>> ca46d/",
>>>>> "task_id"=>"39286b9b-7684-4b1c-b092-bc593d4ca46d",
>>>>> "tags"=>
>>>>>  ["pulp:repository:Peter_MacCallum_Cancer_Centre-Gaffa-dev-
>>>>> GAFFA-_sssd-Copr_repository_for_sssd_1_15",
>>>>>   "pulp:repository:Peter_MacCallum_Cancer_Centre-GAFFA-2_0-_
>>>>> sssd-Copr_repository_for_sssd_1_15",
>>>>>   "pulp:action:associate"],
>>>>> "finish_time"=>"2017-02-09T21:29:59Z",
>>>>> "_ns"=

Re: [foreman-users] CV publishing errors

[Lachlan Musicman]

/var/log/messages shows

pulp.server.webservices.middleware.exception:INFO: Authentication with
username admin failed: invalid username or password

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 10 February 2017 at 09:42, Lachlan Musicman <data...@gmail.com> wrote:

> That didn't work either :/ same error.
>
>
> [root@vmpr-res-utils ~]# pulp-admin login -u admin -p admin
> The specified user does not have permission to execute the given command
>
>
> cheers
> L.
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 10 February 2017 at 09:39, Tom McKay <thomasmc...@redhat.com> wrote:
>
>> Try including the -u admin -p admin on all the pulp-admin commands
>>
>> On Thu, Feb 9, 2017 at 5:30 PM, Lachlan Musicman <data...@gmail.com>
>> wrote:
>>
>>> CentOS 7.3.1611, foreman 1.13.4, katello 3.2.2, pulp* 2.9.3,
>>>
>>> When I try to publish a CV, I get this error
>>>
>>>
>>> Actions::Pulp::Repository::CopyYumMetadataFile
>>>
>>>
>>> {"source_pulp_id"=>
>>>   "Peter_MacCallum_Cancer_Centre-GAFFA-2_0-_sssd-Copr_reposito
>>> ry_for_sssd_1_15",
>>>  "target_pulp_id"=>
>>>   "Peter_MacCallum_Cancer_Centre-Gaffa-dev-GAFFA-_sssd-Copr_re
>>> pository_for_sssd_1_15",
>>>  "clauses"=>nil,
>>>  "remote_user"=>"admin",
>>>  "remote_cp_user"=>"admin"}
>>>
>>> {"pulp_tasks"=>
>>>   [{"exception"=>nil,
>>> "task_type"=>
>>>  "pulp.server.managers.repo.unit_association.associate_from_repo",
>>> "_href"=>"/pulp/api/v2/tasks/39286b9b-7684-4b1c-b092-bc593d4ca46d/",
>>> "task_id"=>"39286b9b-7684-4b1c-b092-bc593d4ca46d",
>>> "tags"=>
>>>  ["pulp:repository:Peter_MacCallum_Cancer_Centre-Gaffa-dev-G
>>> AFFA-_sssd-Copr_repository_for_sssd_1_15",
>>>   "pulp:repository:Peter_MacCallum_Cancer_Centre-GAFFA-2_0-_ss
>>> sd-Copr_repository_for_sssd_1_15",
>>>   "pulp:action:associate"],
>>> "finish_time"=>"2017-02-09T21:29:59Z",
>>> "_ns"=>"task_status",
>>> "start_time"=>"2017-02-09T21:29:59Z",
>>> "traceback"=>
>>>  "Traceback (most recent call last):\n  File
>>> \"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 240, in
>>> trace_task\nR = retval = fun(*args, **kwargs)\n  File
>>> \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line
>>> 484, in __call__\nreturn super(Task, self).__call__(*args, **kwargs)\n
>>>  File \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\",
>>> line 103, in __call__\nreturn super(PulpTask, self).__call__(*args,
>>> **kwargs)\n  File \"/usr/lib/python2.7/site-packages/celery/app/trace.py\",
>>> line 437, in __protected_call__\nreturn self.run(*args, **kwargs)\n
>>>  File 
>>> \"/usr/lib/python2.7/site-packages/pulp/server/managers/repo/unit_association.py\",
>>> line 273, in associate_from_repo\nunits=transfer_units)\n  File
>>> \"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/importer.py\",
>>> line 58, in import_units\nreturn associate.associate(source_repo,
>>> dest_repo, import_conduit, config, units)\n  File
>>> \"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/associate.py\",
>>> line 53, in associate\nassociated_units = 
>>> set([_associate_unit(dest_repo,
>>> unit) for unit in units])\n  File \"/usr/lib/python2.7/site-pack
>>> ages/pulp_rpm/plugins/importers/yum/associate.py\", line 339, in
>>> _associate_unit\nreturn associate_copy_for_repo(unit, dest_repo,
>>> True)\n  File \"/usr/lib/python2.7/site-pack
>>> ages/pulp_rpm/plugins/importers/yum/associate.py\", line 379, in
>>> associate_copy_for_repo\n
>>> new_unit.safe_import_content(unit._storage_path)\n
>>>  File \"/usr/lib/python2.7/site-packages/pulp/server/db/model/__init__.py\",
>>> line 905, in safe_import_content\nself.import_content(path, location)\

Re: [foreman-users] CV publishing errors

[Lachlan Musicman]

That didn't work either :/ same error.


[root@vmpr-res-utils ~]# pulp-admin login -u admin -p admin
The specified user does not have permission to execute the given command


cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 10 February 2017 at 09:39, Tom McKay <thomasmc...@redhat.com> wrote:

> Try including the -u admin -p admin on all the pulp-admin commands
>
> On Thu, Feb 9, 2017 at 5:30 PM, Lachlan Musicman <data...@gmail.com>
> wrote:
>
>> CentOS 7.3.1611, foreman 1.13.4, katello 3.2.2, pulp* 2.9.3,
>>
>> When I try to publish a CV, I get this error
>>
>>
>> Actions::Pulp::Repository::CopyYumMetadataFile
>>
>>
>> {"source_pulp_id"=>
>>   "Peter_MacCallum_Cancer_Centre-GAFFA-2_0-_sssd-Copr_reposito
>> ry_for_sssd_1_15",
>>  "target_pulp_id"=>
>>   "Peter_MacCallum_Cancer_Centre-Gaffa-dev-GAFFA-_sssd-Copr_
>> repository_for_sssd_1_15",
>>  "clauses"=>nil,
>>  "remote_user"=>"admin",
>>  "remote_cp_user"=>"admin"}
>>
>> {"pulp_tasks"=>
>>   [{"exception"=>nil,
>> "task_type"=>
>>  "pulp.server.managers.repo.unit_association.associate_from_repo",
>> "_href"=>"/pulp/api/v2/tasks/39286b9b-7684-4b1c-b092-bc593d4ca46d/",
>> "task_id"=>"39286b9b-7684-4b1c-b092-bc593d4ca46d",
>> "tags"=>
>>  ["pulp:repository:Peter_MacCallum_Cancer_Centre-Gaffa-dev-
>> GAFFA-_sssd-Copr_repository_for_sssd_1_15",
>>   "pulp:repository:Peter_MacCallum_Cancer_Centre-GAFFA-2_0-_
>> sssd-Copr_repository_for_sssd_1_15",
>>   "pulp:action:associate"],
>> "finish_time"=>"2017-02-09T21:29:59Z",
>> "_ns"=>"task_status",
>> "start_time"=>"2017-02-09T21:29:59Z",
>> "traceback"=>
>>  "Traceback (most recent call last):\n  File
>> \"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 240, in
>> trace_task\nR = retval = fun(*args, **kwargs)\n  File
>> \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line
>> 484, in __call__\nreturn super(Task, self).__call__(*args, **kwargs)\n
>>  File \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\",
>> line 103, in __call__\nreturn super(PulpTask, self).__call__(*args,
>> **kwargs)\n  File \"/usr/lib/python2.7/site-packages/celery/app/trace.py\",
>> line 437, in __protected_call__\nreturn self.run(*args, **kwargs)\n
>>  File 
>> \"/usr/lib/python2.7/site-packages/pulp/server/managers/repo/unit_association.py\",
>> line 273, in associate_from_repo\nunits=transfer_units)\n  File
>> \"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/importer.py\",
>> line 58, in import_units\nreturn associate.associate(source_repo,
>> dest_repo, import_conduit, config, units)\n  File
>> \"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/associate.py\",
>> line 53, in associate\nassociated_units = set([_associate_unit(dest_repo,
>> unit) for unit in units])\n  File \"/usr/lib/python2.7/site-pack
>> ages/pulp_rpm/plugins/importers/yum/associate.py\", line 339, in
>> _associate_unit\nreturn associate_copy_for_repo(unit, dest_repo,
>> True)\n  File \"/usr/lib/python2.7/site-pack
>> ages/pulp_rpm/plugins/importers/yum/associate.py\", line 379, in
>> associate_copy_for_repo\n
>> new_unit.safe_import_content(unit._storage_path)\n
>>  File \"/usr/lib/python2.7/site-packages/pulp/server/db/model/__init__.py\",
>> line 905, in safe_import_content\nself.import_content(path, location)\n
>>  File \"/usr/lib/python2.7/site-packages/pulp/server/db/model/__init__.py\",
>> line 879, in import_content\nstorage.put(self, path, location)\n  File
>> \"/usr/lib/python2.7/site-packages/pulp/server/content/storage.py\",
>> line 123, in put\nmkdir(os.path.dirname(destination))\n  File
>> \"/usr/lib/python2.7/site-packages/pulp/server/content/storage.py\",
>> line 20, in mkdir\nos.makedirs(path)\n  File
>> \"/usr/lib64/python2.7/os.py\", line 157, in makedirs\nmkdir(name,
>> mode)\nPulpExecutionException: Pulp exception occurred:
>> PulpExecutionException\n",
>> "spawned_tasks"=

Re: [foreman-users] Re: This thing itches me....

[Lachlan Musicman]

In the GUI, I would like to be able to group Content Views into Composite
Views and Non Composite views.

All of my servers are deployed using composite CVs. All non composite CVs
are single purpose for flexibility within the Composite CVs. It would be
handy to be able to visually separate them without resorting to naming
conventions.

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 20 December 2016 at 22:17, Baptiste Agasse <
baptiste.aga...@lyra-network.com> wrote:

> Hi,
>
> My wish-list:
>
> * Puppet smart class parameters and other config related parameters
> management like Content view:
>   The goal here is to manage multiple parameters changes as a transaction,
> for easy review and rollback
> * More integration with compute resources #10539, #10539, #10244, #5441...
> * Access compute resources via foreman proxies
> * Isolated foreman proxies #8172
> * Simple Errata import API (for CentOS errata management for example) #8656
> * Nested organizations in Katello #10789
>
> I'm working on  #10539 (PR 4095 and 4096) and on prerequisites for #5441
> (rbovirt part was merged and there is a PR3936 open on the fog part)
>
> Thanks for your work, foreman/katello devs, i've seen a lot of
> improvements since we started to use it few years ago, and i think the best
> is still to come :)
>
> Regards.
>
> - Le 19 Déc 16, à 22:28, Dirk Götz  a écrit :
>
> Hi,
>
> my wishlist:
>
> * Handling OS for provisioning is still complicated: What I mean in detail
> is every OS is listed also if not prepared for provisioning because every
> minor release is autocreated when an updated system shows up in a puppet
> run. Listing only the prepared once and/or add templates, media and so on
> when autocreate another minor release would make handling easier.
>
> * Katello adds to much complexity: As others mentioned Katello, I think
> its to complex by default. Not everyone needs multitenancy, docker, ...
> when he needs content staging. Having this things as separate plugins would
> be more helpful.
>
> * Having to use IDs in API/CLI instead of names
>
> * Redmine vs. Github: Having same issue in both trackers or having the
> feeling of added the bug to the wrong tracker is unsatisfactory
>
> * Long-standing bugs/feature request: As for all software seeing bugs many
> years old makes me sad, sometimes reviewing and closing as wont fix would
> be more honest
>
> And my +1 list:
>
> * A huge +1 for stability as updating the training material always ends in
> creating to many bugs.
>
> * Ability to add a new Lifecycle stage to the middle of a Lifecycle Path.
>
>
>> * Default Owner of Hosts (RM #14013)
>> The default owner of hosts should be configurable. The default user might
>> be a group where the user is a member of.
>>
>
> * Linking of Compute Resources VLANs to Subnet (RM #10539)
>> Foreman should know more about the Network of a Compute Resource. The
>> subnet should be linked to VLANs on the Compute Resource. That would
>> prevent a lot of errors when manually deploying a VM.
>>
>
> But with all the negative things mentioned I have to say Foreman is one of
> my favorite tools and developers do a great job. This is why I care about
> these details.
>
> Regards,
>  Dirk
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> Baptiste
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Re: [Katello] Katello 3.1 to 3.2 upgrade error

[Lachlan Musicman]

FWIW, I had errors thrown while upgrading from 3.1 to 3.2 on a self hosted
system. Each time I just re-ran the upgrade command and it got a little
further. There were three errors thrown and the last time it "just worked".

Now happily running 3.2

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 4 February 2017 at 13:52, Edson Manners  wrote:

> Similar Puppet 4 path issue when upgrading the Capsule??
>
> [root@katello3 ~]# capsule-certs-generate --capsule-fqdn
> "dns1.xxx.x.xxx" --certs-tar "~/capsule.dns1.xxx.x.-certs.tar"
> Installing Done
> [100%] [...
> ]
>   Success!
> /usr/share/ruby/vendor_ruby/puppet/vendor/safe_yaml/lib/safe_yaml.rb:188:in
> `initialize': No such file or directory - /opt/puppetlabs/puppet/cache/
> foreman_cache_data/oauth_consumer_key (Errno::ENOENT)
> from 
> /usr/share/ruby/vendor_ruby/puppet/vendor/safe_yaml/lib/safe_yaml.rb:188:in
> `open'
> from 
> /usr/share/ruby/vendor_ruby/puppet/vendor/safe_yaml/lib/safe_yaml.rb:188:in
> `unsafe_load_file'
> from 
> /usr/share/ruby/vendor_ruby/puppet/vendor/safe_yaml/lib/safe_yaml.rb:153:in
> `load_file_with_options'
> from /usr/share/katello-installer-base/hooks/boot/01-helpers.rb:30:in
> `read_cache_data'
> from 
> /usr/share/katello-installer-base/hooks/post/10-post_install.rb:48:in
> `block (4 levels) in load'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/hooking.rb:34:in
> `instance_eval'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/hooking.rb:34:in
> `block (4 levels) in load'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/hook_context.rb:13:in
> `instance_exec'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/hook_context.rb:13:in
> `execute'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/hooking.rb:51:in
> `block in execute'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/hooking.rb:49:in
> `each'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/hooking.rb:49:in
> `execute'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/kafo_configure.rb:454:in
> `block in run_installation'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/exit_handler.rb:27:in
> `call'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/exit_handler.rb:27:in
> `exit'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/kafo_configure.rb:160:in
> `exit'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/kafo_configure.rb:453:in
> `run_installation'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/kafo_configure.rb:147:in
> `execute'
> from /usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:68:in
> `run'
> from /usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:133:in
> `run'
> from /usr/share/gems/gems/kafo-0.9.8/lib/kafo/kafo_configure.rb:154:in
> `run'
> from /sbin/capsule-certs-generate:75:in `'
>
> On Friday, February 3, 2017 at 9:24:12 PM UTC-5, Edson Manners wrote:
>>
>> Thanks for replying Stephen. Here's what I found:
>>
>> [root@katello3 puppet]# rpm -q --whatprovides
>> /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/applicati
>> on/storeconfigs.rb
>> puppetdb-terminus-2.3.8-1.el7.noarch
>>
>> So maybe PuppetDB was the culprit.
>>
>> And yes even though I read in a Katello 3.2 changelog somewhere that that
>> grub2 bug was fixed it seems like it still fell through the cracks.
>>
>> I'm still trying to get the Katello back online. I'm upgrading the
>> external proxy to see if that'll get rid of the last errors but at this
>> point the server is pretty much unuseable. I don't want to bad mouth
>> Katello becasue I love it but I'd like to warn others about my experience
>> since spent weeks preparing for this upgrade and still got bitten by
>> unexpected errors/bugs.
>>
>> I'll report back any progress for completeness.
>>
>>  Feb 03 21:20:04 katello3.rcc.fsu.edu puppet-master[49870]: Report
>> processor failed: Could not send report to Foreman at
>> https://katello3.xxx.x.xxx/api/config_reports: Net::ReadTimeout
>> Feb 03 21:20:04 katello3.xxx.x.xxx puppet-master[49870]:
>> ["/usr/share/ruby/net/protocol.rb:158:in `rescue in rbuf_fill'",
>> "/usr/share/ruby/net/protocol.rb:152:in `rbuf_fill'",
>> "/usr/share/ruby/net/protocol.rb:134:in `readuntil'",
>> "/usr/share/ruby/net/protocol.rb:144:in `readline'",
>> "/usr/share/ruby/net/http/response.rb:39:in `read_status_line'",
>> "/usr/share/ruby/net/http/response.rb:28:in `read_new'",
>> "/usr/share/ruby/net/http.rb:1412:in `block in transport_request'",
>> "/usr/share/ruby/net/http.rb:1409:in `catch'",
>> "/usr/share/ruby/net/http.rb:1409:in `transport_request'",
>> "/usr/share/ruby/net/http.rb:1382:in `request'",
>> "/usr/share/ruby/net/http.rb:1375:in `block in request'",
>> 

[foreman-users] Changing Content hosts' Life Cycle Envs/Content Views

[Lachlan Musicman]

Hi,

I have decided that one of my Life Cycle Envs and Content Views is
extraneous, and I want to move the Content Hosts associated with those LCEs
into another.

Those hosts were added to the LCEs via Activation Keys.

I have followed the docs

https://theforeman.org/plugins/katello/3.1/user_guide/content_hosts/index.html#changing-the-lifecycle-environment-and-content-view-of-a-content-host

but I do not see the same result as the docs.

The Content Host currently only has a single Content View to choose from.
When I try to change the Environment, I get the message

"You must select a new content view before your change of environment can
be saved.

Use the cancel button on content view selection to revert your environment
selection."
But I have no other cv to change to?

Is it because I've subscribed using an activation key?

Given this is the case, how do I re-associate with a new Life Cycle? Is it
sufficient to just resubscribe with the appropriate activation key, or do I
need to unsubscribe from the old LCE before subscribing with the new?

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] This thing itches me....

[Lachlan Musicman]

Ability to add a new Lifecycle stage to the middle of a Lifecycle Path.
eg:
Old
Library -> Dev -> Prod

New
Library -> Dev -> UAT -> Prod

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 8 December 2016 at 01:51, 'Jason B. Nance' via Foreman users <
foreman-users@googlegroups.com> wrote:

> - Add ability to add config groups and parameters at the Host Collection
> level
> - Add ability to merge parameters that come from org/location/OS/host
> collection/host/etc,etc (like you can do with Class Parameters)
> - Performance improvements related to creating and promoting [Composite]
> Content View versions
> - Ability to go back to "normal" Foreman interface from the Dynflow
> console, or better integration (so that you can deal with failed tasks
> easier)
> - More consistency regarding version numbers (sometimes it is a string,
> sometimes it is an integer, why is the ".0" on there when that's never
> used, sorting in dropdown boxes like CV versions in Composite views, etc)
> - Add a parameter consumable by templates and Puppet for the FQDN of the
> capsule the host uses (similar to the puppetmaster parameter)
>
>
>
> --
> *From: *"Shlomi Zadok" 
> *To: *"Foreman users" 
> *Sent: *Wednesday, December 7, 2016 6:08:51 AM
> *Subject: *[foreman-users] This thing itches me
>
> Hey all,
> I am trying to collect and learn about the things that mostly {piss you
> off,itch} on Foreman.
> It could be little things like a misplaced button or big things. Anything.
>
> So let's start a thread of what are the things that mostly piss you off in
> Foreman.
>
> Here are my contributions to the thread:
>
> * We need to add "compute resource" select to hostgroup, so when I create
> new host(s) I do not have to select a compute resource each time.
> * Associating provisioning templates to an operating system is complicated
> and can be simplified
>
>
> Now: it's your turn :)
>
> Thanks !
>
>
>
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Lifecycle Environments ordering

[Lachlan Musicman]

Hola,

Is there any way to reorder Lifecycle Environments after they've been
created?

EG:

I created "Cluster Dev" and then "Cluster Prod"

Library - Cluster Dev - Cluster Prod

Now I realise I want a "Cluster UAT" that would go after Dev but before Prod

Library - Cluster Dev - Cluster UAT - Cluster Prod

Is that possible, or do I need to build a new LE?

cheers
L.
--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Re: Installing and updating Katello, Foreman

[Lachlan Musicman]

Denis,

I'm not fluent enough with rpm based linux to know what the difference is?

I know that the custom repo is working - there's only one file in
/etc/yum.repos.d/ (redhat.repo)
I did a yum info epel-release and it responded that version 7, release 8
was installed, so I uninstalled it but still got the same error?

cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 6 December 2016 at 23:53, 'Denis Müller' via Foreman users <
foreman-users@googlegroups.com> wrote:

> We had similar  Dependency Resolution problems if katello-server has
> epel-release and our custom epel-repo installed at the same time on the
> system. So after removing epel-releae, we got our problem solved.
>
>
> Am Dienstag, 6. Dezember 2016 04:29:52 UTC+1 schrieb Lachlan Musicman:
>>
>> Hi,
>>
>> We spent 3 months wrestling with Spacewalk before giving it up and moving
>> to Katello/Foreman early this year.
>>
>> Centos 7.2 is our main OS. Everything is up to date (or at least as up to
>> date as possible). Currently we have Foreman 1.12.4 w Katello 3.1.0,
>> "self-registered".
>>
>> I think I would like to update to Katello 3.2. The Katello update docs
>> implore us to make sure our system is up to date.
>>
>> One issue we have consistently had since we installed the system (on the
>> Katello server only) is a package conflict - every yum update gives us this
>> or something like it:
>>
>> 1063 packages excluded due to repository priority protections
>> Resolving Dependencies
>> --> Running transaction check
>> ---> Package python-qpid-proton.x86_64 0:0.13.1-1.el7 will be updated
>> ---> Package python-qpid-proton.x86_64 0:0.14.0-1.el7 will be an update
>> ---> Package python-qpid-qmf.x86_64 0:0.32-1.el7 will be updated
>> ---> Package python-qpid-qmf.x86_64 0:1.35.0-1.el7 will be an update
>> ---> Package qpid-cpp-client.x86_64 0:0.34-8.el7 will be updated
>> ---> Package qpid-cpp-client.x86_64 0:1.35.0-1.el7 will be an update
>> ---> Package qpid-cpp-client-devel.x86_64 0:0.34-8.el7 will be updated
>> ---> Package qpid-cpp-client-devel.x86_64 0:1.35.0-1.el7 will be an update
>> ---> Package qpid-cpp-server.x86_64 0:0.34-8.el7 will be updated
>> ---> Package qpid-cpp-server.x86_64 0:1.35.0-1.el7 will be an update
>> ---> Package qpid-cpp-server-linearstore.x86_64 0:0.34-8.el7 will be
>> updated
>> ---> Package qpid-cpp-server-linearstore.x86_64 0:1.35.0-1.el7 will be
>> an update
>> ---> Package qpid-proton-c.x86_64 0:0.13.1-1.el7 will be updated
>> --> Processing Dependency: libqpid-proton.so.7()(64bit) for package:
>> qpid-dispatch-router-0.6.0-2.katello.el7.x86_64
>> ---> Package qpid-proton-c.x86_64 0:0.14.0-1.el7 will be an update
>> ---> Package qpid-qmf.x86_64 0:0.32-1.el7 will be updated
>> ---> Package qpid-qmf.x86_64 0:1.35.0-1.el7 will be an update
>> ---> Package qpid-tools.noarch 0:0.32-9.el7 will be updated
>> ---> Package qpid-tools.noarch 0:1.35.0-1.el7 will be an update
>> --> Finished Dependency Resolution
>> Error: Package: qpid-dispatch-router-0.6.0-2.katello.el7.x86_64
>> (@Peter_MacCallum_Cancer_Centre_Katello_client)
>>Requires: libqpid-proton.so.7()(64bit)
>>Removing: qpid-proton-c-0.13.1-1.el7.x86_64
>> (@Peter_MacCallum_Cancer_Centre_Extra_Packages_for_Enterpris
>> e_Linux_7_-_x86_64_epel)
>>libqpid-proton.so.7()(64bit)
>>Updated By: qpid-proton-c-0.14.0-1.el7.x86_64
>> (Peter_MacCallum_Cancer_Centre_Extra_Packages_for_Enterprise
>> _Linux_7_-_x86_64_epel)
>>   ~libqpid-proton.so.8()(64bit)
>>  You could try using --skip-broken to work around the problem
>>  You could try running: rpm -Va --nofiles --nodigest
>>
>>
>> I have found this suggestion from many versions ago
>>
>> http://projects.theforeman.org/issues/10665
>>
>> But that hasn't worked for us (with EPEL on a lower priority)
>>
>> 1. What have we done wrong?
>> 2. Is there a way to stop this conflict/error or resolve this issue?
>> 3. Can I just upgrade over the top of this issue?
>> 4. Does the upgrade make this go away?
>>
>> Cheers
>> L.
>>
>> --
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving e

[foreman-users] Katello repositories

[Lachlan Musicman]

Hola,

Investigating the Katello repos, I see there are 4 - pulp, client,
candlepin and katello

At the moment my understanding of what these are:

katello - the foreman plugin, goes on the "foreman/katello server"
(satellite server in RHEL speak)
candlepin - used on the foreman/katello server, not needed on the clients
pulp - used on the foreman/katello server, not needed on the clients

client - the end point that goes on each "enrolled" system. Put onto
systems that have their software managed by Foreman/Katello.

Is that a roughly correct breakdown?

(I'm trying to improve our current Content Views and I want to put some
repos in 'client' and some in 'not client' for various services)

cheers
L.


--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Installing and updating Katello, Foreman

[Lachlan Musicman]

Hi,

We spent 3 months wrestling with Spacewalk before giving it up and moving
to Katello/Foreman early this year.

Centos 7.2 is our main OS. Everything is up to date (or at least as up to
date as possible). Currently we have Foreman 1.12.4 w Katello 3.1.0,
"self-registered".

I think I would like to update to Katello 3.2. The Katello update docs
implore us to make sure our system is up to date.

One issue we have consistently had since we installed the system (on the
Katello server only) is a package conflict - every yum update gives us this
or something like it:

1063 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package python-qpid-proton.x86_64 0:0.13.1-1.el7 will be updated
---> Package python-qpid-proton.x86_64 0:0.14.0-1.el7 will be an update
---> Package python-qpid-qmf.x86_64 0:0.32-1.el7 will be updated
---> Package python-qpid-qmf.x86_64 0:1.35.0-1.el7 will be an update
---> Package qpid-cpp-client.x86_64 0:0.34-8.el7 will be updated
---> Package qpid-cpp-client.x86_64 0:1.35.0-1.el7 will be an update
---> Package qpid-cpp-client-devel.x86_64 0:0.34-8.el7 will be updated
---> Package qpid-cpp-client-devel.x86_64 0:1.35.0-1.el7 will be an update
---> Package qpid-cpp-server.x86_64 0:0.34-8.el7 will be updated
---> Package qpid-cpp-server.x86_64 0:1.35.0-1.el7 will be an update
---> Package qpid-cpp-server-linearstore.x86_64 0:0.34-8.el7 will be updated
---> Package qpid-cpp-server-linearstore.x86_64 0:1.35.0-1.el7 will be an
update
---> Package qpid-proton-c.x86_64 0:0.13.1-1.el7 will be updated
--> Processing Dependency: libqpid-proton.so.7()(64bit) for package:
qpid-dispatch-router-0.6.0-2.katello.el7.x86_64
---> Package qpid-proton-c.x86_64 0:0.14.0-1.el7 will be an update
---> Package qpid-qmf.x86_64 0:0.32-1.el7 will be updated
---> Package qpid-qmf.x86_64 0:1.35.0-1.el7 will be an update
---> Package qpid-tools.noarch 0:0.32-9.el7 will be updated
---> Package qpid-tools.noarch 0:1.35.0-1.el7 will be an update
--> Finished Dependency Resolution
Error: Package: qpid-dispatch-router-0.6.0-2.katello.el7.x86_64
(@Peter_MacCallum_Cancer_Centre_Katello_client)
   Requires: libqpid-proton.so.7()(64bit)
   Removing: qpid-proton-c-0.13.1-1.el7.x86_64
(@Peter_MacCallum_Cancer_Centre_Extra_Packages_for_Enterprise_Linux_7_-_x86_64_epel)
   libqpid-proton.so.7()(64bit)
   Updated By: qpid-proton-c-0.14.0-1.el7.x86_64
(Peter_MacCallum_Cancer_Centre_Extra_Packages_for_Enterprise_Linux_7_-_x86_64_epel)
  ~libqpid-proton.so.8()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest


I have found this suggestion from many versions ago

http://projects.theforeman.org/issues/10665

But that hasn't worked for us (with EPEL on a lower priority)

1. What have we done wrong?
2. Is there a way to stop this conflict/error or resolve this issue?
3. Can I just upgrade over the top of this issue?
4. Does the upgrade make this go away?

Cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] No such file or directory: yum_repo_metadata_file causes sync to fail

[Lachlan Musicman]

Hola,

Centos 7, pulp-server 2.8.6, foreman 1.11.4, one of my repos wont
syncronise with the error:

PLP: [Errno 2] No such file or directory:
'/var/lib/pulp/content/units/yum_repo_metadata_file/-appstream.xml.gz'

Google search shows a couple of bug reports back when pulp-server was <
2.8.3

eg: https://bugzilla.redhat.com/show_bug.cgi?id=1334532

but I'm seeing this now.

How do I solve this? Do I need to remove and re-add the external repo?

cheers
L.



--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Katello, applying errata: "issue with the backend service pulp: 500 Internal Server Error"

[Lachlan Musicman]

I'm having trouble applying some Errata - after hitting confirm on applying 
the Errata to the content hosts, I get an error message:


There was an issue with the backend service pulp: 500 Internal Server 
Error



Centos 7.2, Katello 3.0 9.el7, Foreman 1.11.4

hammer ping tells me the pulp; Status is FAIL

systemctl says all pulp services are fine, except pulp-workers which exited 
with SUCCESS.

In /var/log/foreman/production.log I see lots of output, but this is the 
last dozen or so lines:

 | /opt/rh/rh-ror41/root/usr/share/gems/gems/rack-1.5.2/lib/rack/
methodoverride.rb:21:in `call'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/rack-1.5.2/lib/rack/runtime.rb:17:in 
`call'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/cache/strategy/local_cache_m
iddleware.rb:26:in `call'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/actionpack-4.1.5/lib/
action_dispatch/middleware/static.rb:64:in `ca
ll'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in
 
`call'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/railties-4.1.5/lib/rails/engine.rb:514:in
 
`call'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/railties-4.1.5/lib/rails/
application.rb:144:in `call'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/railties-4.1.5/lib/rails/railtie.rb:194:in
 
`public_send'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/railties-4.1.5/lib/rails/railtie.rb:194:in
 
`method_missing'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/rack-1.5.2/lib/rack/builder.rb:
138:in `call'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/rack-1.5.2/lib/rack/urlmap.rb:65:in 
`block in call'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in 
`each'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/rack-1.5.2/lib/rack/urlmap.rb:
50:in `call'
 | 
/usr/share/passenger/phusion_passenger/rack/thread_handler_extension.rb:74:in 
`process_request'
 | 
/usr/share/passenger/phusion_passenger/request_handler/thread_handler.rb:141:in 
`accept_and_process_next_requ
est'
 | /usr/share/passenger/phusion_passenger/request_handler/thread_handler.rb:
109:in `main_loop'
 | /usr/share/passenger/phusion_passenger/request_handler.rb:455:in `block (
3 levels) in start_threads'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in
 
`call'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/logging-1.8.2/lib/logging/
diagnostic_context.rb:323:in `block in create_with_logging_context'
2016-09-22 14:01:25 [app] [I] Completed 500 Internal Server Error in 378ms 
(Views: 0.2ms | ActiveRecord: 188.2ms)



How do I fix this problem?

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Should I upgrade regularly on Centos7?

[Lachlan Musicman]

We have an otherwise up to date Centos 7 vm running 
Katello/Foreman/"satellite 6". From the about page


   - foreman-installer-katello-3.0.2-1.el7.noarch
   - katello-3.0.0-9.el7.noarch
   - katello-agent-2.5.0-3.el7.noarch


I notice that katello is up to 3.1 and 3.0.2 and Foreman is up to 1.12.2  
(we have 1.11.4)

Is it worth upgrading regularly enough to get those fixes?
 (also, how can I subscribe to this group?)

cheers
L.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.