Bug 2170029

Summary:	rpm-ostree upgrade error in Fedora 38 Error binding to address (GUnixSocketAddress)
Product:	[Fedora] Fedora	Reporter:	Mario Cattamo <mcattamo>
Component:	rpm-ostree	Assignee:	Colin Walters <walters>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	38	CC:	amurdaca, dustymabe, jmarrero, jonathan, lucab, miabbott, philip.wyett, travier, walters
Target Milestone:	---	Flags:	fedora-admin-xmlrpc: mirror+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-02-15 13:41:34 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:

Description Mario Cattamo 2023-02-15 12:29:10 UTC

Description of problem:
After installing rpm-ostree in iot Fedora 38 vm, the rpm-ostree upgrade command fails with the following error:

[admin@localhost ~]$ sudo rpm-ostree upgrade
error: Error binding to address (GUnixSocketAddress): No such file or directory
[admin@localhost ~]$ sudo rpm-ostree upgrade --check
error: Error binding to address (GUnixSocketAddress): No such file or directory
[admin@localhost ~]$ sudo rpm-ostree upgrade --preview 
error: Error binding to address (GUnixSocketAddress): No such file or directory

Version-Release number of selected component (if applicable):
rpm-build 4.18.0-10.fc38
rpm-ostree 2023.1-3.fc38
rpm-ostree-libs 2023.1-3.fc38

How reproducible:
100%

Steps to Reproduce:
1. Deploy Fedora 38 VM from PSI openstack
2. git clone https://github.com/virt-s1/rhel-edge.git
3. cd rhel-edge
4. ./ostree.sh

Actual results:
rpm-ostree upgrade fails with error binding to address.

Expected results:
rpm-ostree upgrade successful.

Additional info:
Pending to check if Fedora Rawhide has the same error.

Comment 1 Micah Abbott 2023-02-15 13:41:34 UTC

This looks like a duplicate of 2169622

*** This bug has been marked as a duplicate of bug 2169622 ***