Description of problem: Last I heard, tokens were only waiting on some backend stuff to be put in place. Not that I know precisely what that means, but is there any way to bump the priority of it up a bit? Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. register system 2. manually entitle 3. manually add to channel 4. manually add to group Additional info:
The website functionality obviously works; which client version has the option to use it? rhn_register-2.7.21-7.x.3 doesn't appear to have a rhnreg_ks that knows about it.
Please make note in the manual page for rhnreg_ks that --serial and --serialnumber in older clients are the token/activation key option. Thanks!
version for errata currently has a man page indicating to use "--activationkey" (that what the version of rhnreg wants...) using rhnreg_ks --serialnumber with that version will work as well, but will issue a warning to use "--actionvationkey"
RHN shows my 7.3 system as up-to-date. The manual page for rhnreg_ks from rhn_register-2.7.21-7.x.3 says nothing about activationkey.
pending errata...
Adrian will close this one when the pending up2date errata makes it out.
This is done. Closing.