Bug 1671406 - Image upload fails with connection refused
Summary: Image upload fails with connection refused
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-glance
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Cyril Roelandt
QA Contact: Mike Abrams
Tana
URL:
Whiteboard:
: 1671004 (view as bug list)
Depends On: 1670798
Blocks: 1665239 1666666 1671653 1776950
TreeView+ depends on / blocked
 
Reported: 2019-01-31 14:33 UTC by Michal Pryc
Modified: 2019-11-26 16:11 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1670798
Environment:
Last Closed: 2019-04-23 10:58:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 1 Cyril Roelandt 2019-02-06 16:48:21 UTC
*** Bug 1671004 has been marked as a duplicate of this bug. ***

Comment 2 Arie Bregman 2019-02-21 13:11:26 UTC
Can we progress with this bug?
It seems to be unrelated to what we are experiencing with libvirt on OSP 8 and 9.

Comment 3 Cyril Roelandt 2019-02-21 16:44:47 UTC
Can we have logs?

Can http://192.168.24.1:9292/v1/images/detail?limit=20 be reached?

Comment 12 Cyril Roelandt 2019-03-06 17:04:19 UTC
> This leads to the no getrandom call same as the https://bugzilla.redhat.com/show_bug.cgi?id=1670798#c14


So, on our machine, there is no sys/random.h, which probably explains why we cannot see any call to getrandom(2). 

# grep -ri getrandom /usr/include/*
/usr/include/asm/unistd_x32.h:#define __NR_getrandom (__X32_SYSCALL_BIT + 318)
/usr/include/asm/unistd_32.h:#define __NR_getrandom 355
/usr/include/asm/unistd_64.h:#define __NR_getrandom 318
/usr/include/asm-generic/unistd.h:#define __NR_getrandom 278
/usr/include/asm-generic/unistd.h:__SYSCALL(__NR_getrandom, sys_getrandom)
/usr/include/bits/syscall.h:#ifdef __NR_getrandom
/usr/include/bits/syscall.h:# define SYS_getrandom __NR_getrandom
/usr/include/linux/random.h: * Flags for getrandom(2)
#

Comment 16 Cyril Roelandt 2019-03-11 14:11:13 UTC
So, mutliple things here:

1) The patched RPMS all seem to be Nova-related, so how do they affect Glance?

2) Do you know how the Glance/pyOpenSSL/openssl/etc. packages are affected during the update?

3) About the "stuck at UPDATE" issue, isn't there any way to debug this? Why is the node not responding? What's happening there?

Comment 17 Nate Johnston 2019-03-12 11:38:17 UTC
This issue is blocking CI for two rhos-prio customer escalation fixes.  Please prioritize this issue.


Note You need to log in before you can comment on or make changes to this bug.