25 jul 2012 kl. 11.01 skrev Juan Hernandez:
On 07/25/2012 10:52 AM, Karli Sjöberg wrote:
1. Stop the engine service: systemctl stop ovirt-engine.service
2. Remove jboss-as, but not its dependencies: rpm -e jboss-as --nodeps
3. Make sure that the /usr/share/jboss-as directory is empty. If it i
On 07/25/2012 10:01 AM, Juan Hernandez wrote:
On 07/25/2012 10:52 AM, Karli Sjöberg wrote:
1. Stop the engine service: systemctl stop ovirt-engine.service
2. Remove jboss-as, but not its dependencies: rpm -e jboss-as --nodeps
3. Make sure that the /usr/share/jboss-as directory is empty. If it
On 07/25/2012 11:01 AM, Karli Sjöberg wrote:
> I have a work-around, but something is amiss with the latest jboss update.
You are right, using 7.1.1-3 should work as well.
> # systemctl stop ovirt-engine.service
> # rpm -e --nodeps jboss-as
> # nano /etc/yum.repos.d/fedora-updates.repo
> [updates
On 07/25/2012 10:52 AM, Karli Sjöberg wrote:
>
> 1. Stop the engine service: systemctl stop ovirt-engine.service
>
>
> 2. Remove jboss-as, but not its dependencies: rpm -e jboss-as --nodeps
>
> 3. Make sure that the /usr/share/jboss-as directory is empty. If it is
> not clean it manually.
>
>
I have a work-around, but something is amiss with the latest jboss update.
# systemctl stop ovirt-engine.service
# rpm -e --nodeps jboss-as
# nano /etc/yum.repos.d/fedora-updates.repo
[updates]
name=Fedora $releasever - $basearch - Updates
failovermethod=priority
#baseurl=http://download.fedorapro
1. Stop the engine service: systemctl stop ovirt-engine.service
2. Remove jboss-as, but not its dependencies: rpm -e jboss-as --nodeps
3. Make sure that the /usr/share/jboss-as directory is empty. If it is
not clean it manually.
4. Re-install the jboss-as package: yum install jboss-as
5. Star
On 07/25/2012 09:45 AM, Juan Hernandez wrote:
On 07/25/2012 10:37 AM, Juan Hernandez wrote:
On 07/25/2012 10:22 AM, jose garcia wrote:
On 07/25/2012 09:05 AM, Ofer Schreiber wrote:
- Original Message -
Good evening,
I had installed the 3.1 beta version. After an update of Fedo
On 07/25/2012 10:37 AM, Juan Hernandez wrote:
> On 07/25/2012 10:22 AM, jose garcia wrote:
>> On 07/25/2012 09:05 AM, Ofer Schreiber wrote:
>>>
>>> - Original Message -
Good evening,
I had installed the 3.1 beta version. After an update of Fedora
17,
the
On 07/25/2012 10:22 AM, jose garcia wrote:
> On 07/25/2012 09:05 AM, Ofer Schreiber wrote:
>>
>> - Original Message -
>>> Good evening,
>>>
>>> I had installed the 3.1 beta version. After an update of Fedora
>>> 17,
>>> the portal does not show any links. I reckon that ovirt-eng
On 07/25/2012 09:05 AM, Ofer Schreiber wrote:
- Original Message -
Good evening,
I had installed the 3.1 beta version. After an update of Fedora
17,
the portal does not show any links. I reckon that ovirt-engine
version
has been upgraded to 3.1.0-1.fc17.
Have I lost
- Original Message -
> Good evening,
>
> I had installed the 3.1 beta version. After an update of Fedora
> 17,
> the portal does not show any links. I reckon that ovirt-engine
> version
> has been upgraded to 3.1.0-1.fc17.
>
> Have I lost all the information in the database?
- Original Message -
> Good evening,
>
> I had installed the 3.1 beta version. After an update of Fedora
> 17,
> the portal does not show any links. I reckon that ovirt-engine
> version
> has been upgraded to 3.1.0-1.fc17.
>
> Have I lost all the information in the databa
Good evening,
I had installed the 3.1 beta version. After an update of Fedora 17,
the portal does not show any links. I reckon that ovirt-engine version
has been upgraded to 3.1.0-1.fc17.
Have I lost all the information in the database? Is there a way to
bring back the datacenters an
13 matches
Mail list logo
