# Qsub -V, env vars not exported after upgrade

**URL:** <https://community.openpbs.org/t/qsub-v-env-vars-not-exported-after-upgrade/3993>\
**Category:** Users/Site Administrators\
**Created:** [September 17, 2024, 11:12am UTC](https://community.openpbs.org/t/qsub-v-env-vars-not-exported-after-upgrade/3993 "2024-09-17T11:12:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gmc99](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/gmc99/32/754_2.png) [@gmc99](https://community.openpbs.org/u/gmc99)\
**Post date:** [September 17, 2024, 11:12am UTC](https://community.openpbs.org/t/qsub-v-env-vars-not-exported-after-upgrade/3993/1 "2024-09-17T11:12:29Z")

</div>

Hi,  
we’re using pbs as part of SOCA

> **[GitHub - awslabs/scale-out-computing-on-aws: Scale-Out Computing on AWS is a solution that...](https://github.com/awslabs/scale-out-computing-on-aws)**
>
> Scale-Out Computing on AWS is a solution that helps customers deploy and operate a multiuser environment for computationally intensive workflows.

we are now upgrading SOCA and it has come with a new version of pbs  
pbs\_version = 20.0.1 -\>.23.06.06, also we’ve moved from CentOS7 to RHEL8

Previous jobs would take the qsub -V flag and bring all variables across to the run but it has stopped working. I can explicitly bring variables into the new job using -v, though that’s impractical to do it for all. Looking at qstat I can see that the Variable\_List just contains several PBS\_O\* vars, and in the working version it shows all env vars.

I see that 23.06.06 is supported on Rocky 8.8 - but SOCA uses RHEL8.10, if this is likely to be the issue is there a way around it? Otherwise any help on trying to debug this would be great.

thanks

---

<div class="post-metadata">

**Author:** ![vchlum](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/vchlum/32/93_2.png) [@vchlum](https://community.openpbs.org/u/vchlum)\
**Post date:** [September 20, 2024, 4:51pm UTC](https://community.openpbs.org/t/qsub-v-env-vars-not-exported-after-upgrade/3993/2 "2024-09-20T16:51:09Z")

</div>

Hi @gmc99 !

It has been fixed on the master branch [fix environmental variables with qsub parameter -V by vchlum · Pull Request #2602 · openpbs/openpbs · GitHub](https://github.com/openpbs/openpbs/pull/2602)  
The future release will include this fix.

V.

---

<div class="post-metadata">

**Author:** ![gmc99](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/gmc99/32/754_2.png) [@gmc99](https://community.openpbs.org/u/gmc99)\
**Post date:** [September 23, 2024, 9:40am UTC](https://community.openpbs.org/t/qsub-v-env-vars-not-exported-after-upgrade/3993/3 "2024-09-23T09:40:42Z")

</div>

Hi @vchlum

Thanks for the update, have you got a rough date for the fixed release? - it would help us work out what to do next

cheers  
G.

---

<div class="post-metadata">

**Author:** ![vchlum](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/vchlum/32/93_2.png) [@vchlum](https://community.openpbs.org/u/vchlum)\
**Post date:** [September 24, 2024, 6:24am UTC](https://community.openpbs.org/t/qsub-v-env-vars-not-exported-after-upgrade/3993/4 "2024-09-24T06:24:21Z")

</div>

Sorry, I have no idea. I am just a contributor.

---

<div class="post-metadata">

**Author:** ![gmc99](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/gmc99/32/754_2.png) [@gmc99](https://community.openpbs.org/u/gmc99)\
**Post date:** [September 24, 2024, 9:12am UTC](https://community.openpbs.org/t/qsub-v-env-vars-not-exported-after-upgrade/3993/5 "2024-09-24T09:12:55Z")

</div>

no problem,  
thanks for your help