Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionQuique Llorente
2021-03-03 10:39:13 UTC
Description of problem:
As noted by kubernetes-nmstate bz [1], when an interface has a floa64 name nmstatectl does not quote the name like it does with other numeric values.
Version-Release number of selected component (if applicable):
nmstate-0.2.6-14.el8_2
How reproducible: Always
Steps to Reproduce:
1. ip link add 60e+02 type dummy
2. nmstatectl show
Actual results:
name: 60e+02
Expected results:
name: '60e+02'
Additional info:
Looks like the issue is expected at yaml 1.1 but fixed at yaml 1.2 [1] and yaml 1.2 is not implemented at pyyaml [3]
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1926986
[2] https://github.com/yaml/pyyaml/issues/173#issuecomment-763045432
[3] https://yaml.readthedocs.io/en/latest/pyyaml.html
(In reply to Fernando F. Mancera from comment #4)
> This depends on the pyyaml version installed. I think nmstate should not
> workaround it.. but we can include a warning for this. What do you think?
What version is that? I understood that nmstate would need to migrate to ruamel.yaml and then it would be good to declare the yaml interface of Nmstate to be using Yaml 1.2.
(In reply to Fernando F. Mancera from comment #2)
> I think we have already discussed this with Quique. Quique, can you confirm
> that the workaround in kubernetes-nmstate is enough? Thanks!
Yes it fixed it, although it would be good to migrate nmstate to yaml 1.2.
Comment 7Fernando F. Mancera
2021-05-06 08:19:15 UTC
(In reply to Till Maas from comment #5)
> (In reply to Fernando F. Mancera from comment #4)
> > This depends on the pyyaml version installed. I think nmstate should not
> > workaround it.. but we can include a warning for this. What do you think?
>
> What version is that? I understood that nmstate would need to migrate to
> ruamel.yaml and then it would be good to declare the yaml interface of
> Nmstate to be using Yaml 1.2.
Oops. Yes, sorry I misunderstood the issue with a different one. Yes I agree nmstate should migrate to ruamel.yaml in order to use Yaml 1.2. Let me assign this to me. Thanks!
Comment 15Fernando F. Mancera
2021-08-26 11:38:07 UTC
*** Bug 1994262 has been marked as a duplicate of this bug. ***