Installation

Does deleting or modifying license pool cause any loss of data?

josefper
Engager

Hi all,

we are trying to upgrade our SPlunk 7.2.3 to splunk 7.2.4 in our distributed envirnoment running on SUSE Enterprise Linux 15
and we are running into following Problem:

/var/tmp # rpm -U splunk-7.2.4-8a94541dcfac-linux-2.6-x86_64.rpm
warning: splunk-7.2.4-8a94541dcfac-linux-2.6-x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID b3cd4420: NOKEY
error: Failed dependencies:
shadow-utils is needed by splunk-7.2.4-8a94541dcfac.x86_64

/var/tmp # zypper se shadow
Loading repository data...
Reading installed packages...

S Name Summary Type
i shadow Utilities to Manage User and Group Accounts package
shadow Utilities to Manage User and Group Accounts srcpackage
i sysuser-shadow Tool to execute sysusers.d with shadow utilities package

there is no shadow-utils package in SUSE 15

any ideas ?

regards
Josef

Labels (1)
Tags (2)
0 Karma
1 Solution

vinkumar_splunk
Splunk Employee
Splunk Employee

This is known Splunk Issue and engineering team is working on it to resolve it in 7.2.6

Till then the workaround is to use --nodeps

View solution in original post

0 Karma

vinkumar_splunk
Splunk Employee
Splunk Employee

This is known Splunk Issue and engineering team is working on it to resolve it in 7.2.6

Till then the workaround is to use --nodeps

View solution in original post

0 Karma

graether
Path Finder

Hello Vinkumar,
in which release is it fixed? Unfortunately in contrast to rpm, zypper has no option --nodeps and I found no other working option (tried -n install --force). I need to use zypper to access a remote repo where the forwarder resides.
Thanks -Gerd

0 Karma

josefper
Engager

hi,

thanks for the answer

as our environment is just for testing, i used the --nodeps option
upgrade works fine on SLES 15, no issues found till now

regards

DMohn
Motivator

We have the same issue here with SLES 12 SP 3
https://answers.splunk.com/answers/725687/installationupdate-of-splunk-724-on-sles-12-failes.html

We already opened a case with Splunk support (case #1279359) and got the answer that this in fact might be a packaging problem. Splunk support is currently looking into it!

0 Karma
.conf21 CFS Extended through 5/20!

Don't miss your chance
to share your Splunk
wisdom in-person or
virtually at .conf21!

Call for Speakers has
been extended through
Thursday, 5/20!