July 2021 - ARCHIVED: Uyuni Users - openSUSE Mailing Lists

[uyuni-users] Fresh Install uyuni 2020.05 Error generating bootstrap repo
by Thomas Weis 24 Aug '22

24 Aug '22

Hello everyone we are configuring a fresh installation of Uyuni 2020.05 After a successful reposync of SUSE Linux Enterprise Server 15 SP1 x86_64 we get an error message: Type: Creating Bootstrap Repository failed Summary: Error generating bootstrap repo for: SLE-15-SP1-x86_64 show details said: ERROR: package 'hwdata' not found ERROR: package 'python3-hwdata' not found ERROR: package 'python3-rhnlib' not found ERROR: package 'spacewalk-check' not found ERROR: package 'spacewalk-client-setup' not found ERROR: package 'spacewalk-client-tools' not found ERROR: package 'python3-spacewalk-check' not found ERROR: package 'python3-spacewalk-client-setup' not found ERROR: package 'python3-spacewalk-client-tools' not found ERROR: package 'python3-uyuni-common-libs' not found ERROR: none of 'mgr-daemon', 'spacewalksd' found ERROR: package 'suseRegisterInfo' not found ERROR: package 'python3-suseRegisterInfo' not found ERROR: package 'zypp-plugin-spacewalk' not found ERROR: package 'python3-zypp-plugin-spacewalk' not found The installation was error-free, we proceeded exactly according to the documentation. What is our mistake? thanks for suggestions Regards Thomas-- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

3 2

Problems using Autoinstall Distro
by Heiner Wulfhorst 13 Aug '21

13 Aug '21

Hi List, i am trying to autoinstall SLES15 systems but my autoinstall distribution seems to have problems. After booting (PXE) i get a gray tui box on blue background saying " Please make sure your installation medium is available". The URL in "install" Kernel Parameter of the distro was generated automatically, i did not change it. When i try to accessit with browser i get an error message: Internal Server Error The server experienced a problem which prevented your request from being filled out. It may not be possible to execute this action at this time. Please help us correct this problem by contacting us with details of how you received this message. URLs of other Distros can be accessed w/o errors. I deleted and re-created the Distro, rebuilt the (staged/contentlifecycle) Repo, both without luck. Any hint is welcome! Thanks! Heiner PGP: C5160402C3F27014(a)keys.gnupg.net <http://keys.gnupg.net/pks/lookup?search=0xC5160402C3F27014&fingerprint=on&o…>

2 3

notify about staged channels that need to be synced to distribute (security) patches
by Heiner Wulfhorst 12 Aug '21

12 Aug '21

Hi List, We use Content Lifecycle Management and have our systems in staged channels. To be informed about new patches for those systems we have to first sync the channels. How can we get this notification *before *syncing, so that we know when we have to sync? Or is it best to have one of each systems unstaged so we get to know about those updates? (i don't think so) Thanks, BR Heiner

3 3

Re: [EXTERNAL] Re: Error after upgrading to latest version
by Allen Beddingfield 23 Jul '21

23 Jul '21

This is the output of "zypper dup". Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... Nothing to do. I have a VM snapshot that I can revert. What I can't figure out how to do is to upgrade only to 2020.07, instead of the current version, as required. What would be the process to get to that intermediate version? I could revert the snapshot, upgrade to 2020.07, then to the current version, if I knew the steps to upgrade to that intermediate version. Thanks! Allen B. -- Allen Beddingfield Systems Engineer Office of Information Technology The University of Alabama Office 205-348-2251 allen(a)ua.edu <https://www.ua.edu/> ________________________________ From: Julio Gonzalez Sent: Friday, July 23, 2021 9:40 AM To: uyuni-users(a)opensuse.org; users(a)lists.uyuni-project.org Cc: Allen Beddingfield Subject: [EXTERNAL] Re: Error after upgrading to latest version On viernes, 23 de julio de 2021 16:31:16 (CEST) Allen Beddingfield wrote: > I have three Uyuni servers that I've updated to the latest version. The > first two went well. The third fails on the startup of Tomcat. This one > was from an older revision. The other two were running an Uyuni version at > Leap 15.2, but the one with the problem was old enough to be on 15.1. Not supported. That's why the release notes say: "You need at least Uyuni 2020.07 already installed to perform the upgrade." As that's the first version on top of openSUSE Leap 15.1 Let's see if we can help, but no promises :-) > I did > "zypper up susemanager" > Ran server-migrator.sh > Then ran pg-migrate-10-to-13.sh > All completed with no errors. > > On restart, there is an issue with Tomcat. This appears in the most recent > catalina log: > > 23-Jul-2021 09:23:03.806 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Server version name: > Apache Tomcat/9.0.36 23-Jul-2021 09:23:03.822 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Server built: > Mar 17 2021 12:00:00 UTC 23-Jul-2021 09:23:03.822 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Server version > number: 9.0.36.0 23-Jul-2021 09:23:03.823 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log OS Name: > Linux 23-Jul-2021 09:23:03.823 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log OS Version: > 5.3.18-59.16-default 23-Jul-2021 09:23:03.823 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Architecture: > amd64 23-Jul-2021 09:23:03.823 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Java Home: > /usr/lib64/jvm/java-11-openjdk-11 23-Jul-2021 09:23:03.823 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log JVM Version: > 11.0.11+9-suse-3.56.1-x8664 23-Jul-2021 09:23:03.823 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: > Oracle Corporation 23-Jul-2021 09:23:03.823 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: > /usr/share/tomcat 23-Jul-2021 09:23:03.823 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: > /usr/share/tomcat 23-Jul-2021 09:23:03.826 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -ea 23-Jul-2021 09:23:03.826 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Xms256m 23-Jul-2021 09:23:03.826 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Xmx1G 23-Jul-2021 09:23:03.827 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Djava.awt.headless=true 23-Jul-2021 09:23:03.827 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: > -Dorg.xml.sax.driver=com.redhat.rhn.frontend.xmlrpc.util.RhnSAXParser > 23-Jul-2021 09:23:03.827 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Dorg.apache.tomcat.util.http.Parameters.MAX_COUNT=1024 > 23-Jul-2021 09:23:03.827 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -XX:MaxNewSize=256 23-Jul-2021 09:23:03.827 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -XX:-UseConcMarkSweepGC 23-Jul-2021 09:23:03.827 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Dnet.sf.ehcache.skipUpdateCheck=true 23-Jul-2021 09:23:03.827 > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command > line argument: --add-modules=java.annotation,com.sun.xml.bind 23-Jul-2021 > 09:23:03.827 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: > --add-exports=java.annotation/javax.annotation.security=ALL-UNNAMED > 23-Jul-2021 09:23:03.827 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: --add-opens=java.annotation/javax.annotation.security=ALL-UNNAMED > 23-Jul-2021 09:23:03.827 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Dcatalina.base=/usr/share/tomcat 23-Jul-2021 09:23:03.828 INFO > [main] org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Dcatalina.home=/usr/share/tomcat 23-Jul-2021 09:23:03.828 INFO > [main] org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Djava.endorsed.dirs= 23-Jul-2021 09:23:03.828 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Djava.io.tmpdir=/var/cache/tomcat/temp 23-Jul-2021 09:23:03.828 > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command > line argument: > -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties > 23-Jul-2021 09:23:03.831 INFO [main] > org.apache.catalina.startup.VersionLoggerListener.log Command line > argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > 23-Jul-2021 09:23:03.832 INFO [main] > org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded Apache > Tomcat Native library [1.2.23] using APR version [1.6.3]. 23-Jul-2021 > 09:23:03.832 INFO [main] > org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR > capabilities: IPv6 [true], sendfile [true], accept filters [false], random > [true]. 23-Jul-2021 09:23:03.832 INFO [main] > org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL > configuration: useAprConnector [false], useOpenSSL [true] 23-Jul-2021 > 09:23:03.834 INFO [main] > org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL > successfully initialized [OpenSSL 1.1.1d 10 Sep 2019] 23-Jul-2021 > 09:23:05.159 INFO [main] org.apache.coyote.AbstractProtocol.init > Initializing ProtocolHandler ["ajp-nio-127.0.0.1-8009"] 23-Jul-2021 > 09:23:05.280 INFO [main] org.apache.coyote.AbstractProtocol.init > Initializing ProtocolHandler ["ajp-nio-0:0:0:0:0:0:0:1-8009"] 23-Jul-2021 > 09:23:05.305 INFO [main] org.apache.coyote.AbstractProtocol.init > Initializing ProtocolHandler ["http-nio-127.0.0.1-8080"] 23-Jul-2021 > 09:23:05.313 INFO [main] org.apache.catalina.startup.Catalina.load Server > initialization in [1,874] milliseconds 23-Jul-2021 09:23:05.631 INFO [main] > org.apache.catalina.core.StandardService.startInternal Starting service > [Catalina] 23-Jul-2021 09:23:05.631 INFO [main] > org.apache.catalina.core.StandardEngine.startInternal Starting Servlet > engine: [Apache Tomcat/9.0.36] 23-Jul-2021 09:23:05.680 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > application directory [/srv/tomcat/webapps/rhn] 23-Jul-2021 09:23:07.488 > SEVERE [main] org.apache.catalina.startup.HostConfig.deployDirectory Error > deploying web application directory [/srv/tomcat/webapps/rhn] > java.lang.IllegalStateException: Error starting child > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java: > 720) at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690) at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705) at > org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1132 > ) at > org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java: > 1865) at > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.jav > a:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutor > Service.java:75) at > java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecu > torService.java:118) at > org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:10 > 44) at > org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:429) at > org.apache.catalina.startup.HostConfig.start(HostConfig.java:1575) at > org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:309) > at > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.jav > a:123) at > org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java: > 423) at > org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366) at > org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:936 > ) at > org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1 > 384) at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1 > 374) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutor > Service.java:75) at > java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecu > torService.java:140) at > org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909 > ) at > org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:2 > 62) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) > at > org.apache.catalina.core.StandardService.startInternal(StandardService.java > :421) at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at > org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:9 > 30) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) > at org.apache.catalina.startup.Catalina.start(Catalina.java:633) at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethod > AccessorImpl.java:62) at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Delegati > ngMethodAccessorImpl.java:43) at > java.base/java.lang.reflect.Method.invoke(Method.java:566) at > org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:343) at > org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:474) Caused by: > org.apache.catalina.LifecycleException: Failed to start component > [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/rhn]] at > org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBas > e.java:440) at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198) at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java: > 717) ... 37 more > Caused by: java.lang.NullPointerException > at > org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.j > ava:382) at > org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java > :195) at > org.apache.catalina.startup.ContextConfig.processJarsForWebFragments(Contex > tConfig.java:1971) at > org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1129 > ) at > org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java > :775) > > at > org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java > :301) at > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.jav > a:123) at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java > :5044) at > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) ... 38 > more > 23-Jul-2021 09:23:07.492 INFO [main] > org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web > application directory [/srv/tomcat/webapps/rhn] has finished in [1,813] ms > 23-Jul-2021 09:23:07.524 INFO [main] > org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler > ["ajp-nio-127.0.0.1-8009"] 23-Jul-2021 09:23:07.752 INFO [main] > org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler > ["ajp-nio-0:0:0:0:0:0:0:1-8009"] 23-Jul-2021 09:23:07.880 INFO [main] > org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler > ["http-nio-127.0.0.1-8080"] 23-Jul-2021 09:23:07.913 INFO [main] > org.apache.catalina.startup.Catalina.start Server startup in [2,600] > milliseconds Can you provide the output of: `zypper dup`? I wonder if some of the Java dependencies didn't change to come from Leap. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

2 1

Error after upgrading to latest version
by Allen Beddingfield 23 Jul '21

23 Jul '21

I have three Uyuni servers that I've updated to the latest version. The first two went well. The third fails on the startup of Tomcat. This one was from an older revision. The other two were running an Uyuni version at Leap 15.2, but the one with the problem was old enough to be on 15.1. I did "zypper up susemanager" Ran server-migrator.sh Then ran pg-migrate-10-to-13.sh All completed with no errors. On restart, there is an issue with Tomcat. This appears in the most recent catalina log: 23-Jul-2021 09:23:03.806 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version name: Apache Tomcat/9.0.36 23-Jul-2021 09:23:03.822 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Mar 17 2021 12:00:00 UTC 23-Jul-2021 09:23:03.822 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version number: 9.0.36.0 23-Jul-2021 09:23:03.823 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Linux 23-Jul-2021 09:23:03.823 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 5.3.18-59.16-default 23-Jul-2021 09:23:03.823 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64 23-Jul-2021 09:23:03.823 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: /usr/lib64/jvm/java-11-openjdk-11 23-Jul-2021 09:23:03.823 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 11.0.11+9-suse-3.56.1-x8664 23-Jul-2021 09:23:03.823 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation 23-Jul-2021 09:23:03.823 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: /usr/share/tomcat 23-Jul-2021 09:23:03.823 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: /usr/share/tomcat 23-Jul-2021 09:23:03.826 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -ea 23-Jul-2021 09:23:03.826 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms256m 23-Jul-2021 09:23:03.826 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx1G 23-Jul-2021 09:23:03.827 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true 23-Jul-2021 09:23:03.827 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.xml.sax.driver=com.redhat.rhn.frontend.xmlrpc.util.RhnSAXParser 23-Jul-2021 09:23:03.827 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.tomcat.util.http.Parameters.MAX_COUNT=1024 23-Jul-2021 09:23:03.827 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:MaxNewSize=256 23-Jul-2021 09:23:03.827 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-UseConcMarkSweepGC 23-Jul-2021 09:23:03.827 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dnet.sf.ehcache.skipUpdateCheck=true 23-Jul-2021 09:23:03.827 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: --add-modules=java.annotation,com.sun.xml.bind 23-Jul-2021 09:23:03.827 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: --add-exports=java.annotation/javax.annotation.security=ALL-UNNAMED 23-Jul-2021 09:23:03.827 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: --add-opens=java.annotation/javax.annotation.security=ALL-UNNAMED 23-Jul-2021 09:23:03.827 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/usr/share/tomcat 23-Jul-2021 09:23:03.828 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/usr/share/tomcat 23-Jul-2021 09:23:03.828 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.endorsed.dirs= 23-Jul-2021 09:23:03.828 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=/var/cache/tomcat/temp 23-Jul-2021 09:23:03.828 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties 23-Jul-2021 09:23:03.831 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 23-Jul-2021 09:23:03.832 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded Apache Tomcat Native library [1.2.23] using APR version [1.6.3]. 23-Jul-2021 09:23:03.832 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. 23-Jul-2021 09:23:03.832 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true] 23-Jul-2021 09:23:03.834 INFO [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized [OpenSSL 1.1.1d 10 Sep 2019] 23-Jul-2021 09:23:05.159 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-127.0.0.1-8009"] 23-Jul-2021 09:23:05.280 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-0:0:0:0:0:0:0:1-8009"] 23-Jul-2021 09:23:05.305 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-127.0.0.1-8080"] 23-Jul-2021 09:23:05.313 INFO [main] org.apache.catalina.startup.Catalina.load Server initialization in [1,874] milliseconds 23-Jul-2021 09:23:05.631 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina] 23-Jul-2021 09:23:05.631 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.36] 23-Jul-2021 09:23:05.680 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/srv/tomcat/webapps/rhn] 23-Jul-2021 09:23:07.488 SEVERE [main] org.apache.catalina.startup.HostConfig.deployDirectory Error deploying web application directory [/srv/tomcat/webapps/rhn] java.lang.IllegalStateException: Error starting child at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:720) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1132) at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1865) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1044) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:429) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1575) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:309) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423) at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:936) at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909) at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.StandardService.startInternal(StandardService.java:421) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:930) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.startup.Catalina.start(Catalina.java:633) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:343) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:474) Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/rhn]] at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:717) ... 37 more Caused by: java.lang.NullPointerException at org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:382) at org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:195) at org.apache.catalina.startup.ContextConfig.processJarsForWebFragments(ContextConfig.java:1971) at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1129) at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:775) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:301) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5044) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) ... 38 more 23-Jul-2021 09:23:07.492 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/srv/tomcat/webapps/rhn] has finished in [1,813] ms 23-Jul-2021 09:23:07.524 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-127.0.0.1-8009"] 23-Jul-2021 09:23:07.752 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-0:0:0:0:0:0:0:1-8009"] 23-Jul-2021 09:23:07.880 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-127.0.0.1-8080"] 23-Jul-2021 09:23:07.913 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [2,600] milliseconds -- Allen Beddingfield Systems Engineer Office of Information Technology The University of Alabama Office 205-348-2251 allen(a)ua.edu

2 1

AW: SLES15SP2-Clients: salt-minion problem
by Crefeld, Tobias LKV Bayern e.V. 23 Jul '21

23 Jul '21

Hi Victor, I never have heard of this rule. At least I would expect an hint in the logs that salt versions are incompatible if there are dependencies. Regards, Tobias. Von: Victor Zhestkov [mailto:Victor.Zhestkov@suse.com] Gesendet: Freitag, 23. Juli 2021 15:19 Hi Tobias. I suppose your server running salt-master 3000 before. It's not possible to handle newer minion version with old master. Victor

1 0

AW: AW: SLES15SP2-Clients: salt-minion problem
by Crefeld, Tobias LKV Bayern e.V. 23 Jul '21

23 Jul '21

Hi Viktor, meanwhile I upgraded our Uyuni server (2020.11 -> 2021.06) and now salt 3002.2 works on all our SLES15-SP2 clients. Actually I had to repeat the patch because the first attempt to patch via Uyuni failed and the log of the respective salt-minion showed the following entries: 2021-07-23 13:24:44,487 [salt.loaded.int.module.cmdmod:836 ][ERROR ][18655] Command 'systemd-run' failed with return code: 103 2021-07-23 13:24:44,488 [salt.loaded.int.module.cmdmod:838 ][ERROR ][18655] stdout: Loading repository data... Reading installed packages... Patch 'SUSE-SLE-Module-Server-Applications-15-SP2-2021-2106-1' is not needed. Resolving package dependencies... The following NEW patch is going to be installed: SUSE-SLE-Module-Basesystem-15-SP2-2021-2106 The following 3 packages are going to be upgraded: python3-salt salt salt-minion 3 packages to upgrade. Overall download size: 8.7 MiB. Already cached: 0 B. After the operation, additional 699.1 KiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving package salt-3002.2-37.1.x86_64 (1/3), 175.9 KiB ( 49.9 KiB unpacked) Retrieving: salt-3002.2-37.1.x86_64.rpm [done] Retrieving package python3-salt-3002.2-37.1.x86_64 (2/3), 8.4 MiB ( 45.3 MiB unpacked) Retrieving: python3-salt-3002.2-37.1.x86_64.rpm [.done (1.6 MiB/s)] Retrieving package salt-minion-3002.2-37.1.x86_64 (3/3), 170.8 KiB ( 41.7 KiB unpacked) Retrieving: salt-minion-3002.2-37.1.x86_64.rpm [done] Checking for file conflicts: [......done] (1/3) Installing: salt-3002.2-37.1.x86_64 [...............done] (2/3) Installing: python3-salt-3002.2-37.1.x86_64 [...................done] (3/3) Installing: salt-minion-3002.2-37.1.x86_64 [..........done] Executing %posttrans script 'python3-salt-3002.2-37.1.x86_64.rpm' [....done] Warning: One of the installed patches affects the package manager itself. Run this command once more to install any other needed patches. 2021-07-23 13:24:44,488 [salt.loaded.int.module.cmdmod:840 ][ERROR ][18655] stderr: Running scope as unit: run-rb22f00149355472aaa170fd01ea9b47b.scope 2021-07-23 13:24:44,488 [salt.loaded.int.module.cmdmod:842 ][ERROR ][18655] retcode: 103 2021-07-23 13:24:51,647 [salt.state :323 ][ERROR ][18655] An exception occurred in this state: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/salt/state.py", line 1999, in call # duration in milliseconds.microseconds File "/usr/lib/python3.6/site-packages/salt/loader.py", line 2036, in wrapper # improperly loaded File "/usr/lib/python3.6/site-packages/salt/states/pkg.py", line 2368, in patch_installed targets = _find_advisory_targets(name, advisory_ids, **kwargs) File "/usr/lib/python3.6/site-packages/salt/states/pkg.py", line 411, in _find_advisory_targets cur_patches = __salt__["pkg.list_installed_patches"](**kwargs) File "/usr/lib/python3.6/site-packages/salt/modules/zypperpkg.py", line 2939, in list_installed_patches return _get_patches(installed_only=True, root=root) File "/usr/lib/python3.6/site-packages/salt/modules/zypperpkg.py", line 2885, in _get_patches .nolock.xml.call("se", "-t", "patch") File "/usr/lib/python3.6/site-packages/salt/modules/zypperpkg.py", line 355, in __call self.__call_result = __salt__["cmd.run_all"](cmd, **kwargs) File "/usr/lib/python3.6/site-packages/salt/loader.py", line 1269, in __getitem__ File "/usr/lib/python3.6/site-packages/salt/utils/lazy.py", line 111, in __getitem__ KeyError: 'cmd.run_all' Repeating the job at Uyuni was successful. Thanks for your efforts! Regards, Tobias. Von: Victor Zhestkov [mailto:Victor.Zhestkov@suse.com] Gesendet: Montag, 19. Juli 2021 15:44 It's very confusing. Just tried `salt-call state.apply util.systeminfo` on my testing SLE15SP2 system with salt-minion-3002.2-37.1 and it works fine. But in your case it seems `salt-call state.apply util.systeminfo` will fail. Please check if it's failing. If so, please collect the output of `salt-call -l trace state.apply util.systeminfo` and send me as a file. Thanks for advance. Regards, Victor

2 1

Issue while upgrading Uyuni proxies to 2021.06
by Bidault, Philippe 22 Jul '21

22 Jul '21

Hi all ¡! I am stuck with the upgrade of Uyuni 2021.06 (from Uyuni 2021.04). I have followed the steps there https://www.uyuni-project.org/uyuni-docs/en/uyuni/upgrade/proxy-uyuni.html, however the step 8 (Click Software Packages Upgrade, and select all the packages to be updated on the proxy, and then apply the selection.) failed with the following errors (seen on the GUI, Schedule -> Failed Actions): Refreshing service 'spacewalk'. Loading repository data... Reading installed packages... Resolving package dependencies... 9 Problems: Problem: nothing provides kmod = 25-6.7.1 needed by kmod-compat-2 [...] s systemd-bash-completion provided by systemd-bash-completion-234-24.90.1.noarch Problem: product:openSUSE-Addon-NonOss-15.2-0.x86_64 requires product(openSUSE-Addon-NonOss) = 15.2-0, but this requirement cannot be provided Problem: product:Uyuni-Proxy-2021.04-0.x86_64 requires product(openSUSE) >= 15.2, but this requirement cannot be provided Problem: product:Leap-15.3-1.x86_64 requires product(Leap) = 15.3-1, but this requirement cannot be provided Problem: patterns-uyuni_proxy-2021.04-1.2.uyuni.x86_64 requires Uyuni-Proxy-release, but this requirement cannot be provided Problem: nothing provides kmod = 25-6.7.1 needed by kmod-compat-25-6.7.1.x86_64 Solution 1: do not install kmod-compat-25-6.7.1.x86_64 Solution 2: break kmod-compat-25-6.7.1.x86_64 by ignoring some of its dependencies Removing kmon-compat no really seems to be an option, to many dependencies: # zypper rm kmod-compat Reading installed packages... Resolving package dependencies... The following 22 packages are going to be REMOVED: dracut kmod-compat libbd_mdraid2 lvm2 mdadm os-prober patterns-base-apparmor patterns-base-apparmor_opt patterns-base-base patterns-base-enhanced_base patterns-base-minimal_base patterns-uyuni_proxy plymouth plymouth-branding-openSUSE plymouth-dracut plymouth-scripts supportutils supportutils-plugin-salt supportutils-plugin-susemanager-client supportutils-plugin-susemanager-proxy udisks2 udisks2-lang The following 6 patterns are going to be REMOVED: apparmor apparmor_opt base enhanced_base minimal_base uyuni_proxy 22 packages to remove. After the operation, 8.7 MiB will be freed. Continue? [y/n/v/...? shows all options] (y): n Strangely, can't see kmod-compat installed on the Uyuni server, so not sure where it is coming from. Regards, Philippe. Philippe Bidault | Unix Engineer | Getronics ________________________________ M. 34617301667 | E. Philippe.Bidault(a)Getronics.com | W. www.getronics.com<https://www.getronics.com> [cid:3-lines_7512e235-163a-4853-8e4f-b0d4fc62ce73.png]<https://getronics.com/> Getronics CMC Service Desk Iberia S.L - VAT No:S.L.: B66686262. Registered Office - Getronics CMC Service Desk Iberia S.L, C/Rosselloi, Porcel, 21 planta 11, 08016 Barcelona, Spain. The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you. Legal disclaimer: http://www.getronics.com/legal/

2 5

Missing Repositories for Open Enterprise Server 2018 SP3
by Thomas Weis 22 Jul '21

22 Jul '21

Hello there, SP3 for Open Enterprise Server 2018 has been released for some time. We receive the repos for OES2018 SP1 and OES2018 SP2 via the subscriptions in the SCC, but not the repos for OES2018 SP3. Is there a time when the repositories are available or is that not planned? Many thanks to the project team! Regards Thomas

3 5

Error while syncing EPEL 8 repository
by jordi＠priscoelectronica.com 22 Jul '21

22 Jul '21

Hello, Since nine days ago I'm observing an error while syncing EPEL 8 repository. This error has appeared on different days with different instances of the same kind (rhnerrata pgsql table constraint violation): 2021/07/06 -> Initial EPEL 8 sync, no errors. All errata in. 2021/07/11 -> first error appears psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8678, FEDORA-EPEL-2021-360b258add, Product Enhancement Advisory, FEDORA-EPEL-2021-360b258add, 200, pending, Fedora EPEL 8, Initial package , rnnoise-0-0.3.20210312git7f449bf.el8, , , 2021-07-09 07:48:35-02, 2021-07-09 07:48:52-02, null, null, 1, null, updates(a)fedoraproject.org, 2021-07-10 22:02:40.365219-02, 2021-07-10 22:02:40.365219-02, 2021-07- 10 22:02:40.365219-02, null). 2021/07/19 -> the same with different data psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8715, FEDORA-EPEL-2021-41eeae14d9, Product Enhancement Advisory, FEDORA-EPEL-2021-41eeae14d9, 200, pending, Fedora EPEL 8, Initial package, python-nagiosplugin-1.3.2- 1.el8, , , 2021-07-18 17:55:58-02, 2021-07-18 17:55:58-02, null, null, 1, null, updates(a)fedoraproject.org, 2021-07-19 04:22:00.854661- 02, 2021-07-19 04:22:00.854661-02, 2021-07-19 04:22:00.854661-02, null). 2021/07/21 -> third occurrence, this time repeating "python- nagiosplugin" instance. psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8735, FEDORA-EPEL-2021-41eeae14d9, Product Enhancement Advisory, FEDORA-EPEL-2021-41eeae14d9, 200, pending, Fedora EPEL 8, Initial package, python-nagiosplugin-1.3.2- 1.el8, , , 2021-07-18 17:55:58-02, 2021-07-18 17:55:58-02, null, null, 1, null, updates(a)fedoraproject.org, 2021-07-19 22:02:34.756984- 02, 2021-07-19 22:02:34.756984-02, 2021-07-19 22:02:34.756984-02, null). This is from last night: psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8752, FEDORA-EPEL-2021-a5a0c05adf, Product Enhancement Advisory, FEDORA-EPEL-2021-a5a0c05adf, 200, pending, Fedora EPEL 8, Initial package, python-jdcal-1.4.1-1.el8, , , 2021-07-19 16:46:28-02, 2021-07-19 16:46:28-02, null, null, 1, null, updates(a)fedoraproject.org, 2021-07-20 04:05:53.484279-02, 2021-07-20 04:05:53.484279-02, 2021-07-20 04:05:53.484279-02, null). Full log: # LANG=C spacewalk-repo-sync -c epel8-almalinux8-x86_64 08:46:02 ====================================== 08:46:02 | Channel: epel8-almalinux8-x86_64 08:46:02 ====================================== 08:46:02 Sync of channel started. Retrieving repository 'epel8-almalinux8-x86_64' metadata ...............................[done] Building repository 'epel8-almalinux8-x86_64' cache ....................................[done] All repositories have been refreshed. 08:46:06 08:46:06 Importing comps file 96d01da780a309a1803ea903a9f2a33b1c239a265847c6a86718acb9ef85f06e-comps- Everything.x86_64.xml. 08:46:06 Renaming non-standard filename 96d01da780a309a1803ea903a9f2a33b1c239a265847c6a86718acb9ef85f06e-comps- Everything.x86_64.xml to comps.x86_64.xml. 08:46:06 *** NOTE: Importing comps file for the channel 'epel8- almalinux8-x86_64'. Previous comps will be discarded. 08:46:06 Repo URL: https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64/ 08:46:06 Packages in repo: 7558 08:46:14 No new packages to sync. 08:46:15 08:46:15 Patches in repo: 3017. 08:46:15 Add Patch FEDORA-EPEL-2021-3ec3998292 08:46:16 Add Patch FEDORA-EPEL-2021-7dc78a18ca 08:46:16 Add Patch FEDORA-EPEL-2021-d33da662e7 08:46:16 Add Patch FEDORA-EPEL-2021-87b303b50e 08:46:17 Add Patch FEDORA-EPEL-2021-7ed6a63b7b 08:46:17 Add Patch FEDORA-EPEL-2021-a5a0c05adf 08:46:17 Add Patch FEDORA-EPEL-2021-f77315a931 08:46:17 Add Patch FEDORA-EPEL-2021-333cf44938 08:46:17 Add Patch FEDORA-EPEL-2021-fdb6cf1e3a 08:46:17 Add Patch FEDORA-EPEL-2021-b3771b0cd1 08:46:18 Add Patch FEDORA-EPEL-2021-15c5b7660c 08:46:18 Add Patch FEDORA-EPEL-2021-384d2492fa 08:46:18 Add Patch FEDORA-EPEL-2021-247500b671 08:46:18 Add Patch FEDORA-EPEL-2021-d4c3bbff96 08:46:19 Add Patch FEDORA-EPEL-2021-a60d1222d2 08:46:19 Add Patch FEDORA-EPEL-2021-ec70035a87 08:46:19 Add Patch FEDORA-EPEL-2021-d48e8d2d55 08:46:19 Add Patch FEDORA-EPEL-2021-293195e59b 08:46:19 Add Patch FEDORA-EPEL-2021-41eeae14d9 08:46:19 Add Patch FEDORA-EPEL-2021-ec2a0a616a 08:46:19 Add Patch FEDORA-EPEL-2021-b8960f6143 08:46:19 Add Patch FEDORA-EPEL-2021-20a66b3776 08:46:20 Add Patch FEDORA-EPEL-2020-7c3fde7f74 08:46:20 Add Patch FEDORA-EPEL-2021-ac096c00b0 08:46:20 Add Patch FEDORA-EPEL-2021-aa67d44d29 08:46:20 Add Patch FEDORA-EPEL-2021-d3d8cfc98d 08:46:20 Syncing 25 new patch(es) to channel. 08:46:20 Unexpected error: <class 'psycopg2.errors.CheckViolation'> 08:46:20 Traceback (most recent call last): File "/usr/lib/python3.6/site- packages/spacewalk/satellite_tools/reposync.py", line 600, in sync self.import_updates(plugin) File "/usr/lib/python3.6/site- packages/spacewalk/satellite_tools/reposync.py", line 741, in import_updates processed_updates_count = self.upload_updates(notices) File "/usr/lib/python3.6/site- packages/spacewalk/satellite_tools/reposync.py", line 967, in upload_updates importer.run() File "/usr/lib/python3.6/site- packages/spacewalk/server/importlib/importLib.py", line 778, in run self.submit() File "/usr/lib/python3.6/site- packages/spacewalk/server/importlib/errataImport.py", line 217, in submit dml = self.backend.processErrata(self.batch) File "/usr/lib/python3.6/site- packages/spacewalk/server/importlib/backend.py", line 1011, in processErrata transactional=1) File "/usr/lib/python3.6/site- packages/spacewalk/server/importlib/backend.py", line 2151, in __processObjectCollection return self.__processObjectCollection__(objColl, parentTable, childDict, **kwargs) File "/usr/lib/python3.6/site- packages/spacewalk/server/importlib/backend.py", line 2322, in __processObjectCollection__ return self.__doDML(dml) File "/usr/lib/python3.6/site- packages/spacewalk/server/importlib/backend.py", line 2427, in __doDML self.__doInsert(dml.insert, dml.tables) File "/usr/lib/python3.6/site- packages/spacewalk/server/importlib/backend.py", line 2434, in __doInsert self.__doInsertTable(tname, dict) File "/usr/lib/python3.6/site- packages/spacewalk/server/importlib/backend.py", line 2449, in __doInsertTable insertObj.query(hash) File "/usr/lib/python3.6/site- packages/spacewalk/server/importlib/backendLib.py", line 453, in query statement.execute_values(self._buildQuery(None), value_list, fetch=False, page_size=10_000) File "/usr/lib/python3.6/site- packages/spacewalk/server/rhnSQL/sql_base.py", line 166, in execute_values return self._execute_wrapper(self._execute_values, sql, argslist, template, page_size, fetch) File "/usr/lib/python3.6/site- packages/spacewalk/server/rhnSQL/driver_postgresql.py", line 299, in _execute_wrapper retval = function(*p, **kw) File "/usr/lib/python3.6/site- packages/spacewalk/server/rhnSQL/driver_postgresql.py", line 353, in _execute_values results = psycopg2.extras.execute_values(self._real_cursor, sql, argslist, template=template, page_size=page_size, fetch=fetch) File "/usr/lib64/python3.6/site-packages/psycopg2/extras.py", line 1289, in execute_values cur.execute(b''.join(parts)) psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (8816, FEDORA-EPEL-2021-a5a0c05adf, Product Enhancement Advisory, FEDORA-EPEL-2021-a5a0c05adf, 200, pending, Fedora EPEL 8, Initial package, python-jdcal-1.4.1-1.el8, , , 2021-07-19 16:46:28-02, 2021-07-19 16:46:28-02, null, null, 1, null, updates(a)fedoraproject.org, 2021-07-20 04:46:02.984641-02, 2021-07-20 04:46:02.984641-02, 2021-07-20 04:46:02.984641-02, null). 08:46:20 Total time: 0:00:17 Any ideas ? Thank you, Jordi.

4 5