Hide Forgot
Description of problem: Customer subscribed OSP Platform & RHCI in separate orders, so these subscriptions are not in same pool. When we deploy OpenStack via Director, we can only use one pool in /home/stack/templates/rhel-registration/environment-rhel-registration.yaml. Due to this reason, we can't deploy enough hypervisors according to customer's subscription Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: issue now is we can't fully utilize customer's subscriptions via OSP Director Expected results: support multiple pools when deploy OpenStack using Director Additional info:
Customer has to scale-out environment but due to this issue he cant scale it , & onsite SA has a deadline to finish & handover this setup . i am testing below in test env to add another pool-id 1- modify environment-rhel-registration.yaml rhel_reg_pool_id: "xxx-xxx" rhel_reg_pool_id1: "yyy-yyy" 2 -modify rhel-registration.yaml to add new variables type: string rhel_reg_pool_id: type: string rhel_reg_pool_id1: - name: REG_POOL_ID - name: REG_POOL_ID1 REG_POOL_ID: {get_param: rhel_reg_pool_id} REG_POOL_ID1: {get_param: rhel_reg_pool_id1} 3 - modify scripts/rhel-registration if [ -n "${REG_POOL_ID:-}" ]; then attach_opts="$attach_opts --pool=$REG_POOL_ID --pool=$REG_POOL_ID1" fi not sure if this work
The above might work, but is pretty risky since you're modifying a bunch of files that we ship and they'll get changed back when you update. I'm not sure if this is the best way, but here's another option. Instead of using the built in registration code, you can write a custom template to do the explicit registration you need. A guide to this is here: https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/paged/director-installation-and-usage/614-customizing-overcloud-pre-configuration The example simply adds a nameserver into /etc/resolv.conf but it shows how to run a random command. You could do the subscription-manager command there instead. You could also look at the post-config example for how to run a static script.
Thanks Mike -will this pre-config scrip will run on existing nodes too and try to attach to new pool . - do we need to use new pool id and this script will run only on new scale-out nodes.
(In reply to Anil Dhingra from comment #5) > Thanks Mike > -will this pre-config scrip will run on existing nodes too and try to attach > to new pool . I'm not an expert, but I think pre-config runs on the deploy of each node and not again. It would not run on existing nodes. > - do we need to use new pool id and this script will run only on new > scale-out nodes. I'm not following this question. You have 2 pool-ids today. I'm suggesting that you have a template that does something like: ... ... template: | #!/bin/sh subscription-manager register ... subscription-manager attach --pool <pool1> <pool2> ... ... ...
Anil, did the workaround work for your case?
The customer had to postpone the workaround. Still waiting for feedback.
*** Bug 1322915 has been marked as a duplicate of this bug. ***