Bug 2219810

Summary:	Missing extack in case of failure adding or removing an IPv6 address
Product:	Red Hat Enterprise Linux 9	Reporter:	Beniamino Galvani <bgalvani>
Component:	kernel	Assignee:	Hangbin Liu <haliu>
kernel sub component:	Networking	QA Contact:	Jianlin Shi <jishi>
Status:	CLOSED MIGRATED	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	haliu, jiji, kzhang
Version:	9.3	Keywords:	MigratedToJIRA
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-15 08:37:53 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 Beniamino Galvani 2023-07-05 12:43:38 UTC

Description of problem:

These functions:

  inet6_addr_add()
  ipv6_add_addr()
  inet6_addr_del()

don't set the extack in case of failure. In some situations, the extack would be useful for users to understand the problem without having to read kernel code.


Version-Release number of selected component (if applicable):
any version (tested on 6.2)


Actual results:
# ip addr add dev enp1s0 fd01::1/60 mngtmpaddr
RTNETLINK answers: Invalid argument

# echo 1 > /proc/sys/net/ipv6/conf/enp7s0/disable_ipv6
# ip addr add dev enp7s0 fd01::1
RTNETLINK answers: Permission denied

# ip addr del dev enp1s0 fd01::1234/64
RTNETLINK answers: Cannot assign requested address


Expected results:
Something like:
# ip addr add dev enp1s0 fd01::1/60 mngtmpaddr
Error: ipv6: addresses with mngtmpaddr flag must have prefix length 64

# echo 1 > /proc/sys/net/ipv6/conf/enp7s0/disable_ipv6
# ip addr add dev enp7s0 fd01::1
Error: ipv6: IPv6 is disabled on the interface

# ip addr del dev enp1s0 fd01::1234/64
Error: ipv6: address not found

Comment 1 Hangbin Liu 2023-09-15 07:28:04 UTC

MigratedToJIRA

Comment 2 RHEL Program Management 2023-09-15 08:35:49 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-09-15 08:37:53 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.