If you're using 1.2, it's a known issue:
http://projects.theforeman.org/issues/2519
You need to run this if you're on the 1.2 RPMs:
cd ~foreman && sudo -u foreman
ruby193-rake permissions:reset RAILS_ENV=production
Other users change "ruby193-rake" to "rake".
···
On 24/05/13 14:42, C�dric Dupont wrote:
> Hi,
>
> After an install (manual install with rpm and hand config), we get
> Foreman working without real issue.
> We set login : false from the beginning.
> Now we want to activate the login for production conditions.
>
> But if I use the admin/changeme, it's not working.
> I look at the foreman.users table and the password of admin is on UNSET.
> So I try without giving password, but authent is refused again.
>
> Is it a know issue ? (nothing on web for what I look)
> Is it possible to reset it from database ?
–
Dominic Cleal
Red Hat Engineering
Hi,
We are running 1.1.
I see the ' rake permissions:reset RAILS_ENV=production ' in another post
and try it without success.
In the table, the password_hash is at NULL (not UNSET like I say before)
As it's for password_salt, role_id, filter_on_owner
Also, the update colomn hasn't change date (same as creation) whatever I do
the rake permissions:reset
Cédric Dupont
···
Le vendredi 24 mai 2013 15:47:22 UTC+2, Dominic Cleal a écrit :
>
> On 24/05/13 14:42, C�dric Dupont wrote:
> > Hi,
> >
> > After an install (manual install with rpm and hand config), we get
> > Foreman working without real issue.
> > We set login : false from the beginning.
> > Now we want to activate the login for production conditions.
> >
> > But if I use the admin/changeme, it's not working.
> > I look at the foreman.users table and the password of admin is on UNSET.
> > So I try without giving password, but authent is refused again.
> >
> > Is it a know issue ? (nothing on web for what I look)
> > Is it possible to reset it from database ?
>
> If you're using 1.2, it's a known issue:
> http://projects.theforeman.org/issues/2519
>
> You need to run this if you're on the 1.2 RPMs:
> cd ~foreman && sudo -u foreman
> ruby193-rake permissions:reset RAILS_ENV=production
>
> Other users change "ruby193-rake" to "rake".
>
> --
> Dominic Cleal
> Red Hat Engineering
>
Did the rake task print out that it had changed your user and password,
or did it give an error?
I wonder if you're in the development rather than production environment
or something too. How do you run Foreman and to what file does it log?
···
--
Dominic Cleal
Red Hat Engineering
On 24/05/13 15:55, C�dric Dupont wrote:
Hi,
We are running 1.1.
I see the ’ rake permissions:reset RAILS_ENV=production ’ in another
post and try it without success.
In the table, the password_hash is at NULL (not UNSET like I say before)
As it’s for password_salt, role_id, filter_on_owner
Also, the update colomn hasn’t change date (same as creation) whatever I
do the rake permissions:reset
C�dric Dupont
Le vendredi 24 mai 2013 15:47:22 UTC+2, Dominic Cleal a �crit :
On 24/05/13 14:42, C�dric Dupont wrote:
> Hi,
>
> After an install (manual install with rpm and hand config), we get
> Foreman working without real issue.
> We set login : false from the beginning.
> Now we want to activate the login for production conditions.
>
> But if I use the admin/changeme, it's not working.
> I look at the foreman.users table and the password of admin is on
UNSET.
> So I try without giving password, but authent is refused again.
>
> Is it a know issue ? (nothing on web for what I look)
> Is it possible to reset it from database ?
If you're using 1.2, it's a known issue:
http://projects.theforeman.org/issues/2519
<http://projects.theforeman.org/issues/2519>
You need to run this if you're on the 1.2 RPMs:
cd ~foreman && sudo -u foreman
ruby193-rake permissions:reset RAILS_ENV=production
Other users change "ruby193-rake" to "rake".
--
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Rake did not print it changes anything. The only line printed was : email
format invalid
In Foreman we have only production environnement. Log file is
/var/log/foreman/production.log
Cédric
···
Le vendredi 24 mai 2013, Dominic Cleal a écrit :
Did the rake task print out that it had changed your user and password,
or did it give an error?
I wonder if you’re in the development rather than production environment
or something too. How do you run Foreman and to what file does it log?
–
Dominic Cleal
Red Hat Engineering
On 24/05/13 15:55, Cédric Dupont wrote:
Hi,
We are running 1.1.
I see the ’ rake permissions:reset RAILS_ENV=production ’ in another
post and try it without success.
In the table, the password_hash is at NULL (not UNSET like I say before)
As it’s for password_salt, role_id, filter_on_owner
Also, the update colomn hasn’t change date (same as creation) whatever I
do the rake permissions:reset
Cédric Dupont
Le vendredi 24 mai 2013 15:47:22 UTC+2, Dominic Cleal a écrit :
On 24/05/13 14:42, C�dric Dupont wrote:
> Hi,
>
> After an install (manual install with rpm and hand config), we get
> Foreman working without real issue.
> We set login : false from the beginning.
> Now we want to activate the login for production conditions.
>
> But if I use the admin/changeme, it's not working.
> I look at the foreman.users table and the password of admin is on
UNSET.
> So I try without giving password, but authent is refused again.
>
> Is it a know issue ? (nothing on web for what I look)
> Is it possible to reset it from database ?
If you're using 1.2, it's a known issue:
http://projects.theforeman.org/issues/2519
<http://projects.theforeman.org/issues/2519>
You need to run this if you're on the 1.2 RPMs:
cd ~foreman && sudo -u foreman
ruby193-rake permissions:reset RAILS_ENV=production
Other users change "ruby193-rake" to "rake".
--
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com <javascript:;>.
To post to this group, send email to foreman-users@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.
–
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 <javascript:;>.
To post to this group, send email to foreman-users@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.
> Rake did not print it changes anything. The only line printed was : email
> format invalid
this is probably the reason, your mail probably resolve to
root@localhostor somthing like that.
if you may, please open a bug about this, so we won't force mail validation
on rake tasks (not much point in hitting this error during initial setup).
Ohad
···
On Sat, May 25, 2013 at 2:02 PM, Cédric Dupont wrote:
In Foreman we have only production environnement. Log file is
/var/log/foreman/production.log
Cédric
Le vendredi 24 mai 2013, Dominic Cleal a écrit :
Did the rake task print out that it had changed your user and password,
or did it give an error?
I wonder if you’re in the development rather than production environment
or something too. How do you run Foreman and to what file does it log?
–
Dominic Cleal
Red Hat Engineering
On 24/05/13 15:55, Cédric Dupont wrote:
Hi,
We are running 1.1.
I see the ’ rake permissions:reset RAILS_ENV=production ’ in another
post and try it without success.
In the table, the password_hash is at NULL (not UNSET like I say before)
As it’s for password_salt, role_id, filter_on_owner
Also, the update colomn hasn’t change date (same as creation) whatever I
do the rake permissions:reset
Cédric Dupont
Le vendredi 24 mai 2013 15:47:22 UTC+2, Dominic Cleal a écrit :
On 24/05/13 14:42, C�dric Dupont wrote:
> Hi,
>
> After an install (manual install with rpm and hand config), we get
> Foreman working without real issue.
> We set login : false from the beginning.
> Now we want to activate the login for production conditions.
>
> But if I use the admin/changeme, it's not working.
> I look at the foreman.users table and the password of admin is on
UNSET.
> So I try without giving password, but authent is refused again.
>
> Is it a know issue ? (nothing on web for what I look)
> Is it possible to reset it from database ?
If you're using 1.2, it's a known issue:
http://projects.theforeman.org/issues/2519
<http://projects.theforeman.org/issues/2519>
You need to run this if you're on the 1.2 RPMs:
cd ~foreman && sudo -u foreman
ruby193-rake permissions:reset RAILS_ENV=production
Other users change "ruby193-rake" to "rake".
--
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://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.
–
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,
Ok I will open a bug, I check in the database and the admin password is set
There is no domain. Maybe it's related to the fact we didn't have domain on
this server but just a hostname used for fqdn
Do you know how I can fix this by hand to be able to log with login
activated and connect the server to a LDAP ?
Can I set the password directly in database ? (password hash ?) or by
modifying the email of admin user to something correct in database and
after use the rake command again ?
Cédric
···
to : root@
Le dimanche 26 mai 2013 09:18:23 UTC+2, ohad a écrit :
On Sat, May 25, 2013 at 2:02 PM, Cédric Dupont <lun...@gmail.com<javascript:> > > wrote:
Rake did not print it changes anything. The only line printed was : email
format invalid
this is probably the reason, your mail probably resolve to root@localhost
or somthing like that.
if you may, please open a bug about this, so we won’t force mail
validation on rake tasks (not much point in hitting this error during
initial setup).
Ohad
In Foreman we have only production environnement. Log file is
/var/log/foreman/production.log
Cédric
Le vendredi 24 mai 2013, Dominic Cleal a écrit :
Did the rake task print out that it had changed your user and password,
or did it give an error?
I wonder if you’re in the development rather than production environment
or something too. How do you run Foreman and to what file does it log?
–
Dominic Cleal
Red Hat Engineering
On 24/05/13 15:55, Cédric Dupont wrote:
Hi,
We are running 1.1.
I see the ’ rake permissions:reset RAILS_ENV=production ’ in another
post and try it without success.
In the table, the password_hash is at NULL (not UNSET like I say
before)
As it’s for password_salt, role_id, filter_on_owner
Also, the update colomn hasn’t change date (same as creation) whatever
I
do the rake permissions:reset
Cédric Dupont
Le vendredi 24 mai 2013 15:47:22 UTC+2, Dominic Cleal a écrit :
On 24/05/13 14:42, C�dric Dupont wrote:
> Hi,
>
> After an install (manual install with rpm and hand config), we
get
> Foreman working without real issue.
> We set login : false from the beginning.
> Now we want to activate the login for production conditions.
>
> But if I use the admin/changeme, it's not working.
> I look at the foreman.users table and the password of admin is on
UNSET.
> So I try without giving password, but authent is refused again.
>
> Is it a know issue ? (nothing on web for what I look)
> Is it possible to reset it from database ?
If you're using 1.2, it's a known issue:
http://projects.theforeman.org/issues/2519
<http://projects.theforeman.org/issues/2519>
You need to run this if you're on the 1.2 RPMs:
cd ~foreman && sudo -u foreman
ruby193-rake permissions:reset RAILS_ENV=production
Other users change "ruby193-rake" to "rake".
--
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users?hl=en
.
For more options, visit https://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.
–
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.
