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.

Description of problem:
I've just added ip to new ethernet connection, and was asked if I want to switch to manual, I answered yes, saved, quitted. When connection started, it was dhcp again. When I add static/manual manually everything works correctly.

Version-Release number of selected component (if applicable):
NetworkManager-0.9.9.0-9.git20130807.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.add ethernet connection via nmcli connection add type ethernet...
2.edit that connection via nmcli connection edit id ..
3.submit set ipv4.address 192.168.122.253 for example
4.when asked if you want to switch to manual answer yes
5.start connection by nmcli connection up id..

Actual results:
dhcp used

Expected results:
ip set correctly

Additional info:
if I set yes or no it behaves the same

I can't reproduce this bug. When I set ipv4.address, I am asked "Do you also want to set 'ipv4.method' to 'manual'? [yes]:". When I answer "yes", the method is properly set to manual. And no DHCP is used while activating the connection.
Maybe, you answered "no" and method was left 'auto'.

(In reply to Jirka Klimes from comment #2)
> I can't reproduce this bug. When I set ipv4.address, I am asked "Do you also
> want to set 'ipv4.method' to 'manual'? [yes]:". When I answer "yes", the
> method is properly set to manual. And no DHCP is used while activating the
> connection.
> Maybe, you answered "no" and method was left 'auto'.

try IP w/o prefix.. and as description says: "Missing prefix is regarded as prefix of 32." it should work