On miércoles, 31 de julio de 2019 21:21:38 (CEST) David Mace wrote:
> Will there be a bug fix release afterwards? For example some important
> functionality is still broken like cobbler sync to proxies.
Not exactly. The model Uyuni intends to follow is that of a rolling release.
There will be a next release after this one (most probably 4.1.0) with
bugfixing and probably more features.
Regarding https://github.com/uyuni-project/uyuni/issues/1200 (cobbler sync to
proxy fails) it's part of the functionality provided by Uyuni, so should get a
fix.
Sadly we had a lot of work adapting Uyuni to openSUSE 15.1 because of the
switch of many components (JDK version, python2->python3, etc), and then
summer just caught us and we had less people available to get Uyuni stable
enough for a release. That is the reason it took us so long to get this
version ready.
However my expectation is to have a new release soon (let's say 4-6 weeks),
and meanwhile keep working on having a public CI with two things in mind:
1. Providing feedback to the contributors
2. Getting their help to get the product stable more quickly.
> Also although unsupported, will it be possible to zypper in --force a switch
> from 4.0.2-dev in master to this stable release?
It is a conditional "it depends". RPMs should be able to update, but you will
need to make sure on your own that the database schema is coherent.
Nothing official, but my suggestion is:
- Take note of your current susemanager-schema version (4.0.X, let's call it
current_version)
- Apply the upgrade procedure.
- Take note of the susemanager-schema version installed by the update (should
be 4.0.13)
- This will create a log at /var/log/spacewalk/schema-upgrade where you will
see lines like "SQL> select 'susemanager-schema-3.2.18-to-susemanager-
schema-3.2.19/002-alter-susesaltevent.sql.postgresql' from dual;" for each SQL
script applied.
- Then review /etc/sysconfig/rhn/schema-upgrade/ and verify if everything from
the migration path from current_version up to 4.0.13 was applied.
If something is missing, you will need to apply it manually:
$ sudo su - postgres
$ psql -f <SQL_SCRIPT> <yourdbname-usually-uyuni>
But of course, despite you already said it, I have to repeat it: it is not
supported in anyway and could bring problems in the future.
> Thanks
--
Julio González Gil
Release Engineer, SUSE Manager and Uyuni
jgonzalez(a)suse.com
On miércoles, 31 de julio de 2019 20:38:59 (CEST) Steve Moring wrote:
> Julio,
>
> On Tue, 2019-07-30 at 21:26 +0000, Julio Gonzalez wrote:
> > @Steve, I will have a second look tomorrow, but as 4.0.2 is really
> > near, I
> >
> > guess we'll just update the installation instructions on the site
> > [1]
>
> Think by next week or next month?
If nothing really bad happens tonight at OBS, or making the release itself
tomorrow morning, I hope that 4.0.2 will be finally out tomorrow before the
end of the day :-)
> -Steve
--
Julio González Gil
Release Engineer, SUSE Manager and Uyuni
jgonzalez(a)suse.com
uyuni:~ # zypper ar https://download.opensuse.org/repositories/systems
management:/Uyuni:/Stable/images/repo/Uyuni-Server-4.0-POOL-x86_64-
Media1/ uyuni-server-stable
Adding repository 'uyuni-server-stable'
......................................................................
....[done]
Repository 'uyuni-server-stable' successfully added
URI : https://download.opensuse.org/repositories/systemsmanage
ment:/Uyuni:/Stable/images/repo/Uyuni-Server-4.0-POOL-x86_64-Media1/
Enabled :
Yes
GPG Check :
Yes
Autorefresh :
No
Priority : 99 (default
priority)
Repository priorities are without effect. All enabled repositories
share the same priority.
uyuni:~ # zypper ref
Repository 'openSUSE-Leap-42.3-Non-Oss' is up to
date.
Repository 'openSUSE-Leap-42.3-Oss' is up to
date.
Repository 'openSUSE-Leap-42.3-Update' is up to
date.
Repository 'openSUSE-Leap-42.3-Update-Non-Oss' is up to
date.
Retrieving repository 'uyuni-server-stable' metadata
............................................................[error]
Repository 'uyuni-server-stable' is invalid.
[uyuni-server-stable|https://download.opensuse.org/repositories/system
smanagement:/Uyuni:/Stable/images/repo/Uyuni-Server-4.0-POOL-x86_64-
Media1/] Valid metadata not found at specified URL
Please check if the URIs defined for this repository are pointing to a
valid repository.
Skipping repository 'uyuni-server-stable' because of the above error.
Some of the repositories have not been refreshed because of an error.
uyuni:~ #
--
To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org
To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org
I had to change the id of minions in something:
fe-1.blabla.com => fe-1-prod.blabla,com
If I use previous names , they are not added to Uyuni any more.
Cristian Gherman
-------- Forwarded Message --------
Subject: Re: [uyuni-users] need assistance with debugging bootstrap issues
Date: Tue, 9 Jul 2019 13:55:59 +0000 (UTC)
From: Strahil Nikolov <hunter86_bg(a)yahoo.com>
To: Cristian Gherman <cristian.gherman(a)reea.net>
Hi Christian,
thanks for the fast reply.
Already done all of these.
The new key is accepted , but the machines are not added.
I even used "snapper" to rollback one of the VMs to openSUSE 15.0 in
order to check bootstraping.
The results are the same.
Rebooting Uyuni doesn't solve the issue :)
Any ideas appreciated.
Best Regards,
Strahil Nikolov
В вторник, 9 юли 2019 г., 9:52:05 ч. Гринуич-4, Cristian Gherman
<cristian.gherman(a)reea.net> написа:
Hello,
Can you try this:
- remove minion key from master
- stop the salt-minion on VM's
- remove minion key from /etc/salt/pki/
- change the minion id in /etc/minion_id
- change the machine id in /etc/machine-id with command
systemd-machine-id-setup
- start the salt-minion on VM's
- accept new keys, check if minons is added on Uyuni
This steps helped me with some stoborn minions some time ago.
Cristian Gherman
On 7/9/19 4:39 PM, Strahil Nikolov wrote:
> Hello All,
> can you assist me by guiding me in the correct direction?
> Yesterday I found out that all my clients (4 openSUSE 15.1) are not
reporting for the past 3 days.I tried to refresh , but it didn't do
anything .
>
> Then I removed the VMs and tried to add them, but after accepting the
salt key - the VM is not added as a system.
> I have checked the logs and I see a lot of errors , one of them is :
> 2019-07-09 16:26:24,719 [salt-event-thread-1] ERROR
com.suse.manager.reactor.PGEventListener - Unexpected exception while
executing a MessageAction com.google.gson.JsonSyntaxException:
java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at
path $
> at com.google.gson.Gson.fromJson(Gson.java:900)
> at com.google.gson.Gson.fromJson(Gson.java:953)
> at
com.suse.manager.reactor.messaging.JobReturnEventMessageAction.lambda$execute$7(JobReturnEventMessageAction.java:128)
> at java.util.Optional.ifPresent(Optional.java:159)
> at
com.suse.manager.reactor.messaging.JobReturnEventMessageAction.execute(JobReturnEventMessageAction.java:114)
> at
com.suse.manager.reactor.PGEventListener.lambda$null$1(PGEventListener.java:74)
> at
java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at
java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580)
> at
com.suse.manager.reactor.PGEventListener.lambda$notify$2(PGEventListener.java:72)
> at
java.util.stream.Streams$StreamBuilderImpl.forEachRemaining(Streams.java:419)
> at
java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580)
> at
com.suse.manager.reactor.PGEventListener.notify(PGEventListener.java:69)
> at
com.suse.salt.netapi.event.AbstractEventStream.notifyListeners(AbstractEventStream.java:64)
> at
com.suse.manager.reactor.PGEventStream.lambda$processEvents$3(PGEventStream.java:147)
> at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
> at java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:352)
> at java.util.stream.Sink$ChainedReference.end(Sink.java:258)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:483)
> at
java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
> at
java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
> at
com.suse.manager.reactor.PGEventStream.processEvents(PGEventStream.java:141)
> at
com.suse.manager.reactor.PGEventStream.lambda$null$0(PGEventStream.java:127)
> at
com.redhat.rhn.frontend.events.TransactionHelper.run(TransactionHelper.java:62)
> at
com.redhat.rhn.frontend.events.TransactionHelper.handlingTransaction(TransactionHelper.java:46)
> at
com.suse.manager.reactor.PGEventStream.lambda$notification$2(PGEventStream.java:126)
> at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but
was STRING at path $
> at
com.google.gson.internal.bind.JsonTreeReader.expect(JsonTreeReader.java:161)
> at
com.google.gson.internal.bind.JsonTreeReader.beginObject(JsonTreeReader.java:87)
> at
com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:183)
> at
com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:145)
> at com.google.gson.Gson.fromJson(Gson.java:888)
> ... 30 more
> 2019-07-09 16:26:24,719 [salt-event-thread-4] ERROR
com.redhat.rhn.frontend.events.TransactionHelper -
java.lang.ClassCastException 2019-07-09 16:26:24,719
[salt-event-thread-4] ERROR
com.redhat.rhn.frontend.events.TransactionHelper - Additional Exception
during Exception handling java.lang.ClassCastException
> 2019-07-09 16:26:24,720 [salt-event-thread-3] ERROR
com.redhat.rhn.frontend.events.TransactionHelper -
java.lang.ClassCastException 2019-07-09 16:26:24,719
[salt-event-thread-1] ERROR
com.redhat.rhn.frontend.events.TransactionHelper -
com.suse.manager.reactor.PGEventListenerException
> 2019-07-09 16:26:24,720 [salt-event-thread-5] ERROR
com.redhat.rhn.frontend.events.TransactionHelper -
com.google.gson.JsonSyntaxException: java.lang.IllegalStateException:
Expected NUMBER but was BEGIN_OBJECT at path $.retcode
>
> Any ideas how to debug this one? Which logs should I check ?
> Maybe someone has already had a similar situation...
>
> Best Regards,
> Strahil Nikolov
--
To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org
To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org
Hello All,
can you assist me by guiding me in the correct direction?
Yesterday I found out that all my clients (4 openSUSE 15.1) are not reporting for the past 3 days.I tried to refresh , but it didn't do anything .
Then I removed the VMs and tried to add them, but after accepting the salt key - the VM is not added as a system.
I have checked the logs and I see a lot of errors , one of them is :
2019-07-09 16:26:24,719 [salt-event-thread-1] ERROR com.suse.manager.reactor.PGEventListener - Unexpected exception while executing a MessageAction com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at path $
at com.google.gson.Gson.fromJson(Gson.java:900)
at com.google.gson.Gson.fromJson(Gson.java:953)
at com.suse.manager.reactor.messaging.JobReturnEventMessageAction.lambda$execute$7(JobReturnEventMessageAction.java:128)
at java.util.Optional.ifPresent(Optional.java:159)
at com.suse.manager.reactor.messaging.JobReturnEventMessageAction.execute(JobReturnEventMessageAction.java:114)
at com.suse.manager.reactor.PGEventListener.lambda$null$1(PGEventListener.java:74)
at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580)
at com.suse.manager.reactor.PGEventListener.lambda$notify$2(PGEventListener.java:72)
at java.util.stream.Streams$StreamBuilderImpl.forEachRemaining(Streams.java:419)
at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580)
at com.suse.manager.reactor.PGEventListener.notify(PGEventListener.java:69)
at com.suse.salt.netapi.event.AbstractEventStream.notifyListeners(AbstractEventStream.java:64)
at com.suse.manager.reactor.PGEventStream.lambda$processEvents$3(PGEventStream.java:147)
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
at java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:352)
at java.util.stream.Sink$ChainedReference.end(Sink.java:258)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:483)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at com.suse.manager.reactor.PGEventStream.processEvents(PGEventStream.java:141)
at com.suse.manager.reactor.PGEventStream.lambda$null$0(PGEventStream.java:127)
at com.redhat.rhn.frontend.events.TransactionHelper.run(TransactionHelper.java:62)
at com.redhat.rhn.frontend.events.TransactionHelper.handlingTransaction(TransactionHelper.java:46)
at com.suse.manager.reactor.PGEventStream.lambda$notification$2(PGEventStream.java:126)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at path $
at com.google.gson.internal.bind.JsonTreeReader.expect(JsonTreeReader.java:161)
at com.google.gson.internal.bind.JsonTreeReader.beginObject(JsonTreeReader.java:87)
at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:183)
at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:145)
at com.google.gson.Gson.fromJson(Gson.java:888)
... 30 more
2019-07-09 16:26:24,719 [salt-event-thread-4] ERROR com.redhat.rhn.frontend.events.TransactionHelper - java.lang.ClassCastException 2019-07-09 16:26:24,719 [salt-event-thread-4] ERROR com.redhat.rhn.frontend.events.TransactionHelper - Additional Exception during Exception handling java.lang.ClassCastException
2019-07-09 16:26:24,720 [salt-event-thread-3] ERROR com.redhat.rhn.frontend.events.TransactionHelper - java.lang.ClassCastException 2019-07-09 16:26:24,719 [salt-event-thread-1] ERROR com.redhat.rhn.frontend.events.TransactionHelper - com.suse.manager.reactor.PGEventListenerException
2019-07-09 16:26:24,720 [salt-event-thread-5] ERROR com.redhat.rhn.frontend.events.TransactionHelper - com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected NUMBER but was BEGIN_OBJECT at path $.retcode
Any ideas how to debug this one? Which logs should I check ?
Maybe someone has already had a similar situation...
Best Regards,
Strahil Nikolov
--
To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org
To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org
Hello All,
Can someone clarify if Uiuni supports SLES15 SP1?
It seems that my trial subscription is properly detected as I have SUSE Linux Enterprise Server 15/HPC , but the product for SLES 15 SP1 is missing from UI and mgr-sync:
uyuni:~ # mgr-sync list products
Please enter the credentials of SUSE Manager Administrator.
Login: admin
Password:
Available Products:
(R) - recommended extension
Status:
- [I] - product is installed
- [ ] - product is not installed, but is available
- [U] - product is unavailable
[ ] RHEL Expanded Support 5 (i386)
[ ] RHEL Expanded Support 5 (x86_64)
[ ] RHEL Expanded Support 6 (i386)
[ ] RHEL Expanded Support 6 (x86_64)
[ ] RHEL Expanded Support 7 (x86_64)
[ ] SUSE Linux Enterprise High Performance Computing 12 SP4 (x86_64)
[ ] SUSE Linux Enterprise High Performance Computing 15 (x86_64)
[ ] SUSE Linux Enterprise Server 10 SP3 (i586)
[ ] SUSE Linux Enterprise Server 10 SP3 (x86_64)
[ ] SUSE Linux Enterprise Server 10 SP4 (i586)
[ ] SUSE Linux Enterprise Server 10 SP4 (x86_64)
[ ] SUSE Linux Enterprise Server 11 SP1 (i586)
[ ] SUSE Linux Enterprise Server 11 SP1 (ia64)
[ ] SUSE Linux Enterprise Server 11 SP1 (ppc64)
[ ] SUSE Linux Enterprise Server 11 SP1 (s390x)
[ ] SUSE Linux Enterprise Server 11 SP1 (x86_64)
[ ] SUSE Linux Enterprise Server 11 SP2 (i586)
[ ] SUSE Linux Enterprise Server 11 SP2 (ia64)
[ ] SUSE Linux Enterprise Server 11 SP2 (ppc64)
[ ] SUSE Linux Enterprise Server 11 SP2 (s390x)
[ ] SUSE Linux Enterprise Server 11 SP2 (x86_64)
[ ] SUSE Linux Enterprise Server 11 SP3 (i586)
[ ] SUSE Linux Enterprise Server 11 SP3 (x86_64)
[ ] SUSE Linux Enterprise Server 11 SP4 (i586)
[ ] SUSE Linux Enterprise Server 11 SP4 (x86_64)
[ ] SUSE Linux Enterprise Server 12 (x86_64)
[ ] SUSE Linux Enterprise Server 12 SP1 (x86_64)
[ ] SUSE Linux Enterprise Server 12 SP2 (x86_64)
[ ] SUSE Linux Enterprise Server 12 SP3 (x86_64)
[ ] SUSE Linux Enterprise Server 12 SP4 (x86_64)
[I] SUSE Linux Enterprise Server 15 (x86_64)
[I] (R) Basesystem Module 15 (x86_64)
[I] (R) Server Applications Module 15 (x86_64)
[I] (R) SUSE Manager Tools 15 (x86_64)
[ ] Containers Module 15 (x86_64)
[ ] Desktop Applications Module 15 (x86_64)
[ ] Development Tools Module 15 (x86_64)
[ ] Legacy Module 15 (x86_64)
[ ] Public Cloud Module 15 (x86_64)
[ ] SUSE Cloud Application Platform Tools Module 15 (x86_64)
[I] SUSE Enterprise Storage 6 (x86_64)
[ ] SUSE Linux Enterprise High Availability Extension 15 (x86_64)
[ ] SUSE Package Hub 15 (x86_64)
[ ] Web and Scripting Module 15 (x86_64)
Best Regards,
Strahil Nikolov
--
To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org
To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org
