Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1825548

Summary:

restraint 0.2.0-2 aarch64 failing to start

Product:

[Retired] Restraint

Reporter:

John Villalovos <jvillalovos.ampere>

Component:

general

Assignee:

Daniel Rodríguez <danrodri>

Status:

CLOSED CURRENTRELEASE

QA Contact:

Severity:

urgent

Docs Contact:

Priority:

unspecified

Version:

0.2.0

CC:

asavkov, azelinka, bpeck, breilly, cbeer, danrodri, jvillalovos.ampere, mastyk, yoyang

Target Milestone:

0.2.1

Target Release:

---

Hardware:

aarch64

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2020-05-20 07:21:02 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
strace when running restraintd	none

Description John Villalovos 2020-04-18 19:04:40 UTC

After upgrading to restraint 0.2.0-2 on ARM 64, restraint no longer appears to start on boot. I do see that it is installed during the OS install process. But after the system reboots I never see any console log messages about restraint starting.

Comment 1 John Villalovos 2020-04-18 19:24:45 UTC

When I login to the system and attempt to run restraintd manually I get the following:

# restraintd

** (restraintd:1257): ERROR **: 12:23:46.049: Unable to listen on either ipV4 or ipV6 protocols, exiting...

Trace/breakpoint trap (core dumped)

# rpm -qi restraint
Name        : restraint
Version     : 0.2.0
Release     : 2.fc31eng
Architecture: aarch64
Install Date: Sat 18 Apr 2020 12:17:12 PM PDT
Group       : Applications/Internet
Size        : 21246527
License     : GPLv3+ and MIT
Signature   : (none)
Source RPM  : restraint-0.2.0-2.fc31eng.src.rpm
Build Date  : Tue 14 Apr 2020 11:31:41 PM PDT
Build Host  : arm64-041.build.eng.bos.redhat.com
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor      : Red Hat, Inc.
URL         : https://github.com/beaker-project/restraint
Summary     : Simple test harness which can be used with beaker
Description :
restraint harness which can run standalone or with beaker.  when provided a recipe xml it will execute
each task listed in the recipe until done.

Comment 2 John Villalovos 2020-04-18 19:35:15 UTC

Created attachment 1679898 [details]
strace when running restraintd

Maybe something useful in the strace. So attaching.

Comment 3 John Villalovos 2020-04-18 20:30:45 UTC

From a Fedora 32 snapshot run, names changed.

# journalctl  | grep restraint | cat
Apr 17 12:24:51 testsystem.example.com systemd[1]: Starting The restraint harness....
Apr 17 12:24:51 testsystem.example.com systemd[1]: Started The restraint harness..
Apr 17 12:24:51 testsystem.example.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=restraintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 17 12:24:51 testsystem.example.com restraintd[889]: Unable to listen on either ipV4 or ipV6 protocols, exiting...
Apr 17 12:24:51 testsystem.example.com audit[889]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=889 comm="restraintd" exe="/usr/bin/restraintd" sig=5 res=1
Apr 17 12:24:51 testsystem.example.com systemd[1]: restraintd.service: Main process exited, code=dumped, status=5/TRAP
Apr 17 12:24:51 testsystem.example.com systemd[1]: restraintd.service: Failed with result 'core-dump'.
Apr 17 12:24:51 testsystem.example.com audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=restraintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 17 12:24:51 testsystem.example.com systemd-coredump[893]: Process 889 (restraintd) of user 0 dumped core.
                                                                                              #1  0x0000000000676db4 _g_log_abort (restraintd + 0x276db4)
                                                                                              #2  0x0000000000678c94 g_log_structured_array (restraintd + 0x278c94)
                                                                                              #3  0x000000000067a9ac g_log_default_handler (restraintd + 0x27a9ac)
                                                                                              #4  0x000000000067804c g_logv (restraintd + 0x27804c)
                                                                                              #5  0x00000000006781f4 g_log (restraintd + 0x2781f4)
                                                                                              #6  0x0000000000407918 main (restraintd + 0x7918)
                                                                                              #8  0x0000000000407e20 _start (restraintd + 0x7e20)
                                                                                              #9  0x0000000000407e20 _start (restraintd + 0x7e20)
Apr 18 11:59:15 testsystem.example.com audit[5990]: ANOM_ABEND auid=0 uid=0 gid=0 ses=1 pid=5990 comm="restraintd" exe="/usr/bin/restraintd" sig=5 res=1
Apr 18 11:59:16 testsystem.example.com systemd-coredump[5993]: Process 5990 (restraintd) of user 0 dumped core.
                                                                                               #1  0x0000000000676db4 _g_log_abort (restraintd + 0x276db4)
                                                                                               #2  0x0000000000678c94 g_log_structured_array (restraintd + 0x278c94)
                                                                                               #3  0x000000000067a9ac g_log_default_handler (restraintd + 0x27a9ac)
                                                                                               #4  0x000000000067804c g_logv (restraintd + 0x27804c)
                                                                                               #5  0x00000000006781f4 g_log (restraintd + 0x2781f4)
                                                                                               #6  0x0000000000407918 main (restraintd + 0x7918)
                                                                                               #8  0x0000000000407e20 _start (restraintd + 0x7e20)
                                                                                               #9  0x0000000000407e20 _start (restraintd + 0x7e20)
Apr 18 13:26:19 testsystem.example.com audit[15309]: ANOM_ABEND auid=0 uid=0 gid=0 ses=5 pid=15309 comm="restraintd" exe="/usr/bin/restraintd" sig=5 res=1
Apr 18 13:26:20 testsystem.example.com systemd-coredump[15312]: Process 15309 (restraintd) of user 0 dumped core.
                                                                                                #1  0x0000000000676db4 _g_log_abort (restraintd + 0x276db4)
                                                                                                #2  0x0000000000678c94 g_log_structured_array (restraintd + 0x278c94)
                                                                                                #3  0x000000000067a9ac g_log_default_handler (restraintd + 0x27a9ac)
                                                                                                #4  0x000000000067804c g_logv (restraintd + 0x27804c)
                                                                                                #5  0x00000000006781f4 g_log (restraintd + 0x2781f4)
                                                                                                #6  0x0000000000407918 main (restraintd + 0x7918)
                                                                                                #8  0x0000000000407e20 _start (restraintd + 0x7e20)
                                                                                                #9  0x0000000000407e20 _start (restraintd + 0x7e20)

Comment 4 Daniel Rodríguez 2020-04-20 10:20:43 UTC

Thanks for the report, John.

I'm able to reproduce this issue, in my case, when the loopback interface doesn't support both, IPv4 and IPv6.

https://github.com/beaker-project/restraint/issues/42

Could you check if it's the case in your system?

Comment 5 John Villalovos 2020-04-20 15:23:28 UTC

(In reply to Daniel Rodríguez from comment #4)
> Thanks for the report, John.
> 
> I'm able to reproduce this issue, in my case, when the loopback interface
> doesn't support both, IPv4 and IPv6.
> 
> https://github.com/beaker-project/restraint/issues/42
> 
> Could you check if it's the case in your system?

I see the following:

# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever

Seems like only IPv4 is on the loopback.

Comment 6 Daniel Rodríguez 2020-04-20 16:00:07 UTC

Thanks for the update, John. I updated the GitHub issue with reference to this Bugzilla and I opened pull request with fix for this.

Comment 7 Daniel Rodríguez 2020-04-28 09:11:27 UTC

Fixed in https://github.com/beaker-project/restraint/pull/43

Comment 8 Carol Bouchard 2020-05-07 17:38:10 UTC

*** Bug 1832918 has been marked as a duplicate of this bug. ***

Comment 9 Martin Styk 2020-05-19 11:01:05 UTC

*** Bug 1837365 has been marked as a duplicate of this bug. ***