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:
When going from one stream of nodejs to another (especially going up 10 -> 12, but ideally also when going down), the user experience should be nice. This is a specific requirement from PM (Brian), so we should make sure it works fine and that it is also tested.

So far, this looks quite good to me, so this bug might turn into testing only one, but leave developers and QE to re-consider whether we can do something more.

Steps I used to upgrade from stream 10 to 12:
1. yum -y install node\*
2. yum -y module reset nodejs
3. yum -y module enable nodejs:12
4. yum -y update

Steps I used to downgrade from stream 12 to 10:
1. yum -y module reset nodejs
2. yum -y module enable nodejs:10
3. yum -y distro-sync

Actual results:
After upgrade, all packages were updated.
After downgrade (distro-sync), nodejs-libs was left, which is probably not a problem (at least I don't see a problem with that, if the package only includes a dynamic library).

Expected results:
So far it looks expected, but we should make sure it is the best UX we can offer to users with the current tooling (i.e. what yum provides).

It looks like the following two commands do pretty good job as well, although it is not clear to me whether they do everything we need when switching the streams, but they are very simple:

# dnf install @nodejs:10
# dnf install @nodejs:12

(In reply to Honza Horak from comment #1)
> # dnf install @nodejs:10
> # dnf install @nodejs:12

I meant `yum` ^^^ of course...

Anyway, one issue I spotted is that when going 12 -> 10 using just `yum install @nodejs:10`, then `nodejs-packaging` is not downgraded and I had to run `yum distro-sync` to get nodejs-packaging from nodejs:10 module. This is probably not a big issue, it should just be documented maybe..

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.