On 21 Jan 2015, at 11:13, Madko wrote:
Hi,
Had the same problem about conf files renamed to .rpmsave, and
therefor
opennebula was enable to start. Hopefully I saw this thread ;)
Is it possible to change this behavior and have .rpmnew instead, to
prevent
breaking everything after an upgrade?
done :)
http://dev.opennebula.org/issues/3520
Le Wed Jan 21 2015 at 23:19:07, Jaime Melis a
écrit :
> Can you open a feature request?
>
> On Wed, Jan 21, 2015 at 6:48 PM, Madko wrote:
>
>> Here is the documentation on this point:
>> http://fedoraproject.org/wiki/Packaging:Guidelines#Configurati
Here is the documentation on this point:
http://fedoraproject.org/wiki/Packaging:Guidelines#Configuration_files
Should be great to have this on 4.12, thanks :)
Le Wed Jan 21 2015 at 17:53:42, Jaime Melis a
écrit :
> Hi Madko,
>
> I think we could do that for 4.12.
>
> Anyone else agrees with th
Can you open a feature request?
On Wed, Jan 21, 2015 at 6:48 PM, Madko wrote:
> Here is the documentation on this point:
> http://fedoraproject.org/wiki/Packaging:Guidelines#Configuration_files
> Should be great to have this on 4.12, thanks :)
>
>
> Le Wed Jan 21 2015 at 17:53:42, Jaime Melis a
Hi Madko,
I think we could do that for 4.12.
Anyone else agrees with this? I'd like to get a bunch more +1s on this ;-)
cheers,
Jaime
On Wed, Jan 21, 2015 at 5:13 PM, Madko wrote:
> Hi,
>
> Had the same problem about conf files renamed to .rpmsave, and therefor
> opennebula was enable to st
Hi,
Had the same problem about conf files renamed to .rpmsave, and therefor
opennebula was enable to start. Hopefully I saw this thread ;)
Is it possible to change this behavior and have .rpmnew instead, to prevent
breaking everything after an upgrade? %config(noreplace) in the spec file
should d
Hi,
as Joaquin mentioned the configuration files were replaced, so you simply
need to restore them (merge the conf changes you did on the *.rpmsave files
into the main files).
However the files under /var/lib/one/.one should not be replaced
automatically, I believe there was something in your man
Hi Joaqui,
I fixed it but in a different way, I did not had the .one folder backup
however I had another setup of opennebula and I copied sunstone_auth from
that setup to the non-working setup then retrived the password from mysql
(user_pool table) (Serveradmin user) from working setup and inserte
Hi Kiran,
I'm missed the important files for auth failing: restore the
/var/lib/one/.one auth files (one_auth, one_key,sunstone_auth, etc) from
your backup. Seems these files were also replaced by the package updates.
Regards,
Joaquin Villanueva
El 17/01/15 a las 04:52, kiran ranjane escribió
Hi Kiran,
Same issue here upgrading from centos repos. The oned.conf, sunstone, flow conf
files and vm rc files were replaced with stock ones.
Check your .conf files at /etc/one and replace the new ones with those from
your backup or the .rpmsave version (not sure how ubuntu saves the replaced
Hi,
I upgraded opennebula from 4.10.1 to 4.10.2 using ubuntu repo and after
upgrade I am unable to login to any users.
tried running onedb fsck and getting error - You need to specify the SQLite
or MySQL connection options.
Attached logs to this mail
Any idea how do I fix this issue.
Regards
K
11 matches
Mail list logo