Hi,
I have installed foreman 1.1 using the installer, then copied over our
development, stable and testing modules and then imported them. I then
copied over the all the clients facts and then imported these. The
resulting foreman installation looked ok. I then added a couple of
locations and a couple of organizations. During the creation of these
locations/organizations the wizard tried to import some hosts into the
relevant container but this would never succeed unless I ticked the "Fix
location on mismatch" even though I have made all resources available in
all locations and organizations. I now find that whenever I edit a host,
the location and organization fields are greyed out. Is this expected
behavior? Have I simply not understood how this should work?
If I select the host in the host list page then move it to another
organization or location then I always get a failure because of a mismatch
in settings. What are these setting that are not matched? The containers
have "all" ticked on all tabs and all resources are in the "selected items"
column and I am admin.
Thanks for any tips.
Hi There, welcome back!
> Hi,
> I have installed foreman 1.1 using the installer, then copied over our
> development, stable and testing modules and then imported them. I then
> copied over the all the clients facts and then imported these. The
> resulting foreman installation looked ok. I then added a couple of
> locations and a couple of organizations. During the creation of these
> locations/organizations the wizard tried to import some hosts into the
> relevant container but this would never succeed unless I ticked the "Fix
> location on mismatch" even though I have made all resources available in
> all locations and organizations.
Can you give me an example of something that did not fit? (you could also
see the mismatches if you edit a location, they should be highlighted in
red).
> I now find that whenever I edit a host, the location and organization
> fields are greyed out. Is this expected behavior? Have I simply not
> understood how this should work?
>
They are greyed out on purpose, you can only edit location and orgs via
the mass assignenment (multiple checkboxes on the host list page).
The reason that they are greyed out, is that when changing the host form,
all of the relevant drop downs change as well, which might yield an
unexpected change, further more, sometime you know that a given host is at
a given location, so you might want to ensure that all of its attributes
(e.g. domain) really belong to the location, so you could force the change
and later on fix mismatches to follow.
If I select the host in the host list page then move it to another
> organization or location then I always get a failure because of a mismatch
> in settings. What are these setting that are not matched? The containers
> have "all" ticked on all tabs and all resources are in the "selected items"
> column and I am admin.
> Thanks for any tips.
You have the ability (see the radio button when importing) to force to
update mismatches or to fail on mismatches, if you force it, you should not
get that error.
Hope this helps,
Ohad
···
On Thu, Feb 28, 2013 at 6:45 PM, paul kelly wrote:–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
>
> Hi There, welcome back!
> Thanks. I am a little rusty. Everything has changed. However, it is
> finally time to get Foreman online!!
>
>> Hi,
>> I have installed foreman 1.1 using the installer, then copied over our
>> development, stable and testing modules and then imported them. I then
>> copied over the all the clients facts and then imported these. The
>> resulting foreman installation looked ok. I then added a couple of
>> locations and a couple of organizations. During the creation of these
>> locations/organizations the wizard tried to import some hosts into the
>> relevant container but this would never succeed unless I ticked the "Fix
>> location on mismatch" even though I have made all resources available in
>> all locations and organizations.
>
> Can you give me an example of something that did not fit? (you could also
> see the mismatches if you edit a location, they should be highlighted in
> red).
>
I am not sure what you mean here. When I created the
organization/location I jumped over the "assign all hosts" option and just
went to the host list page. The very first attempt to add anything, (even
though all hosts were not in any org or location,) it said there were
mismatches. I then went to all orgs/locs and clicked the "all" tickbox. I
still could not add a host to anything. I added the hosts but used the "fix
on mismatch" button and this allowed me to perform the action. At no point
was anything highlighted in red and that is still the case.
>
>
>> I now find that whenever I edit a host, the location and organization
>> fields are greyed out. Is this expected behavior? Have I simply not
>> understood how this should work?
>>
> They are greyed out on purpose, you can only edit location and orgs via
> the mass assignenment (multiple checkboxes on the host list page).
>
> The reason that they are greyed out, is that when changing the host form,
> all of the relevant drop downs change as well, which might yield an
> unexpected change, further more, sometime you know that a given host is at
> a given location, so you might want to ensure that all of its attributes
> (e.g. domain) really belong to the location, so you could force the change
> and later on fix mismatches to follow.
>
I see. This is fine then.
>
> If I select the host in the host list page then move it to another
>> organization or location then I always get a failure because of a mismatch
>> in settings. What are these setting that are not matched? The containers
>> have "all" ticked on all tabs and all resources are in the "selected items"
>> column and I am admin.
>> Thanks for any tips.
>
>
> You have the ability (see the radio button when importing) to force to
> update mismatches or to fail on mismatches, if you force it, you should not
> get that error.
>
I can only change a host when this button is clicked. This is my real
issue then. Under what circumstances is it possible to change a host's
loc/org without clicking this button. It seems to me that you are saying
this button is not required if all the host's resources are available in
both source and destination. As I have all resources applied to all
orgs/locs then why do I need to click the fix button?
···
On Thursday, 28 February 2013 21:51:17 UTC, ohad wrote: > On Thu, Feb 28, 2013 at 6:45 PM, paul kelly <paul.ia...@gmail.com > > wrote:Hope this helps,
Ohad–
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-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com<javascript:>
.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
>
>
>>
>> Hi There, welcome back!
>> Thanks. I am a little rusty. Everything has changed. However, it is
>> finally time to get Foreman online!!
>>
>>
>>> Hi,
>>> I have installed foreman 1.1 using the installer, then copied over our
>>> development, stable and testing modules and then imported them. I then
>>> copied over the all the clients facts and then imported these. The
>>> resulting foreman installation looked ok. I then added a couple of
>>> locations and a couple of organizations. During the creation of these
>>> locations/organizations the wizard tried to import some hosts into the
>>> relevant container but this would never succeed unless I ticked the "Fix
>>> location on mismatch" even though I have made all resources available in
>>> all locations and organizations.
>>
>> Can you give me an example of something that did not fit? (you could also
>> see the mismatches if you edit a location, they should be highlighted in
>> red).
>>
> I am not sure what you mean here. When I created the
> organization/location I jumped over the "assign all hosts" option and just
> went to the host list page. The very first attempt to add anything, (even
> though all hosts were not in any org or location,) it said there were
> mismatches. I then went to all orgs/locs and clicked the "all" tickbox. I
> still could not add a host to anything. I added the hosts but used the "fix
> on mismatch" button and this allowed me to perform the action. At no point
> was anything highlighted in red and that is still the case.
>
This might be a bug where mismatch detection ignores the all override, if
it is, do you mind opening a bug?
>
>>
>>> I now find that whenever I edit a host, the location and organization
>>> fields are greyed out. Is this expected behavior? Have I simply not
>>> understood how this should work?
>>>
>> They are greyed out on purpose, you can only edit location and orgs via
>> the mass assignenment (multiple checkboxes on the host list page).
>>
>> The reason that they are greyed out, is that when changing the host form,
>> all of the relevant drop downs change as well, which might yield an
>> unexpected change, further more, sometime you know that a given host is at
>> a given location, so you might want to ensure that all of its attributes
>> (e.g. domain) really belong to the location, so you could force the change
>> and later on fix mismatches to follow.
>>
> I see. This is fine then.
>
>>
>> If I select the host in the host list page then move it to another
>>> organization or location then I always get a failure because of a mismatch
>>> in settings. What are these setting that are not matched? The containers
>>> have "all" ticked on all tabs and all resources are in the "selected items"
>>> column and I am admin.
>>> Thanks for any tips.
>>
>>
>> You have the ability (see the radio button when importing) to force to
>> update mismatches or to fail on mismatches, if you force it, you should not
>> get that error.
>>
> I can only change a host when this button is clicked. This is my
> real issue then. Under what circumstances is it possible to change a host's
> loc/org without clicking this button. It seems to me that you are saying
> this button is not required if all the host's resources are available in
> both source and destination. As I have all resources applied to all
> orgs/locs then why do I need to click the fix button?
>
I assume that the first time you import a host, it would update the
org/loc, the next time, it wont be required ( assuming the two hosts have
similar attributes).
Ohad
···
On Fri, Mar 1, 2013 at 2:07 PM, paul kelly wrote: > On Thursday, 28 February 2013 21:51:17 UTC, ohad wrote: >> On Thu, Feb 28, 2013 at 6:45 PM, paul kelly wrote:Hope this helps,
Ohad–
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-user…@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.Visit this group at http://groups.google.com/**group/foreman-users?hl=enhttp://groups.google.com/group/foreman-users?hl=en
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
>
>>
>>
>>>
>>> Hi There, welcome back!
>>> Thanks. I am a little rusty. Everything has changed. However, it is
>>> finally time to get Foreman online!!
>>>
>>>
>>>> Hi,
>>>> I have installed foreman 1.1 using the installer, then copied over
>>>> our development, stable and testing modules and then imported them. I then
>>>> copied over the all the clients facts and then imported these. The
>>>> resulting foreman installation looked ok. I then added a couple of
>>>> locations and a couple of organizations. During the creation of these
>>>> locations/organizations the wizard tried to import some hosts into the
>>>> relevant container but this would never succeed unless I ticked the "Fix
>>>> location on mismatch" even though I have made all resources available in
>>>> all locations and organizations.
>>>
>>> Can you give me an example of something that did not fit? (you could
>>> also see the mismatches if you edit a location, they should be highlighted
>>> in red).
>>>
>> I am not sure what you mean here. When I created the
>> organization/location I jumped over the "assign all hosts" option and just
>> went to the host list page. The very first attempt to add anything, (even
>> though all hosts were not in any org or location,) it said there were
>> mismatches. I then went to all orgs/locs and clicked the "all" tickbox. I
>> still could not add a host to anything. I added the hosts but used the "fix
>> on mismatch" button and this allowed me to perform the action. At no point
>> was anything highlighted in red and that is still the case.
>>
>
> This might be a bug where mismatch detection ignores the all override, if
> it is, do you mind opening a bug?
>
I do not think that this is the issue because even now, after the
import and allocation to a location and organization, no machine can be
moved from any location to another or from an organization to another,
without setting force button. I have even removed all the "all" buttons and
explicitly moved all the resources from the left pane to the right pane.
···
On Monday, 4 March 2013 07:31:20 UTC, ohad wrote: > On Fri, Mar 1, 2013 at 2:07 PM, paul kelly <paul.ia...@gmail.com > > wrote: >> On Thursday, 28 February 2013 21:51:17 UTC, ohad wrote: >>> On Thu, Feb 28, 2013 at 6:45 PM, paul kelly wrote:I now find that whenever I edit a host, the location and organization
fields are greyed out. Is this expected behavior? Have I simply not
understood how this should work?They are greyed out on purpose, you can only edit location and orgs via
the mass assignenment (multiple checkboxes on the host list page).The reason that they are greyed out, is that when changing the host
form, all of the relevant drop downs change as well, which might yield an
unexpected change, further more, sometime you know that a given host is at
a given location, so you might want to ensure that all of its attributes
(e.g. domain) really belong to the location, so you could force the change
and later on fix mismatches to follow.I see. This is fine then.If I select the host in the host list page then move it to another
organization or location then I always get a failure because of a mismatch
in settings. What are these setting that are not matched? The containers
have “all” ticked on all tabs and all resources are in the "selected items"
column and I am admin.
Thanks for any tips.You have the ability (see the radio button when importing) to force to
update mismatches or to fail on mismatches, if you force it, you should not
get that error.I can only change a host when this button is clicked. This is myreal issue then. Under what circumstances is it possible to change a host’s
loc/org without clicking this button. It seems to me that you are saying
this button is not required if all the host’s resources are available in
both source and destination. As I have all resources applied to all
orgs/locs then why do I need to click the fix button?I assume that the first time you import a host, it would update the
org/loc, the next time, it wont be required ( assuming the two hosts have
similar attributes).Ohad
Hope this helps,
Ohad–
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-user…@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.Visit this group at http://groups.google.com/**
group/foreman-users?hl=enhttp://groups.google.com/group/foreman-users?hl=en
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.–
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-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com<javascript:>
.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Hello,
What are the logs we can check to understand what are the mismatches?
I know it works when we click the "Fix" Button, but its not notify what are
the changes it is making in the background.
- Can anyone put some light how can we check the mismatches for why it is
failing ? - What is the unique situation when we can move a host from one Org to
another ORG without clicking "Fix" button ?
Thanks