Re: [foreman-users] Remote Execution Job Failed : Error initializing command: Net::SSH::AuthenticationFailed

[Ohad Levy]

On Tue, Mar 7, 2017 at 9:07 AM, Pradeep Antil 
wrote:

>
> Hello Foreman Users,
>
> I am trying to execute commands on the register hosts on my Katello
> Server, for this i have already enabled the "remote execution plugin" by
> following the URL 'https://theforeman.org/plugins/foreman_remote_
> execution/0.3/'.
>
> But when i try to execute any command from Katello / foreman Dashboard ,
> getting below error
>
> Error initializing command: Net::SSH::AuthenticationFailed -
> Authentication failed for user root@x.x.x.x
> Exit status: EXCEPTION
>
> Any idea or suggestions to resolve such issues.
>

this means your foreman server can't access your hosts, did you deploy the
ssh key as described in the manual above?

>
> Thanks in advance
>
> Regards
> Pradeep
>
> --
> 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] 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] Re: Foreman Discovery 8.0.1 release

[Lukas Zapletal]

We have a working workaround:

https://github.com/theforeman/foreman_discovery/pull/331/files

but this is short-term patch, we are working on proper patch which may
require more changes in core and plugin. If you are affected by the
bug, you can hotfix your instance untiil the fix is delivered in
8.0.2.

LZ

On Thu, Mar 2, 2017 at 10:02 AM, Lukas Zapletal  wrote:
> Looks like we have report that the patch for #18106 did not work, I am
> retesting this. It was not working on FOSDEM for me, but I thought I
> was doing it wrong...
>
> Update is safe, it might not help in this particular case. I will get
> back to you.
>
> LZ
>
> On Thu, Mar 2, 2017 at 9:47 AM, Lukas Zapletal  wrote:
>> Hello,
>>
>> better later then never, I am finally announcing 8.0.1 bugfix minor
>> release which contains two important changes:
>>
>> Fixes #18106 - Attribute Error when provisioning with Katello plugin 
>> installed
>> Fixes #16890 - Prevent discovery of managed hosts
>>
>> It took a little bit longer to release this due to various things
>> namely FOSDEM, recovery and my struggle with building process. I
>> highly recommend to update to all of users because the #16890 bug is
>> causing discovered hosts in undeletable state and maintainance task
>> must be performed to delete them (it only happens if MAC address is
>> already used as managed host - re-discovery).
>>
>> --
>> Later,
>>   Lukas @lzap Zapletal
>
>
>
> --
> Later,
>   Lukas @lzap Zapletal



-- 
Later,
  Lukas @lzap Zapletal

-- 
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 server migration

[James Denton]

Hi

As later versions of Foreman are no longer supported on RHEL6 we have 
decided to build a new Foreman/Puppet master server on RHEL7 with the 
latest versions. Is there any documentation, previous questions on how to 
migrate current Foreman specific files/data including for example - nodes, 
host groups, config groups, puppet modules etc... from the existing Foreman 
installation to the new server?

Any help would be appreciated. 

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.