Comment 6 for bug 1502242

On my locally deployed env, I see
root@node-2:~# apt-cache policy | grep -A3 aux
1150 http://10.20.0.2:8080/2015.1.0-8.0/ubuntu/auxiliary/ auxiliary/restricted amd64 Packages
     release o=Mirantis,a=auxiliary,n=auxiliary,l=auxiliary,c=restricted
     origin 10.20.0.2
1150 http://10.20.0.2:8080/2015.1.0-8.0/ubuntu/auxiliary/ auxiliary/main amd64 Packages
     release o=Mirantis,a=auxiliary,n=auxiliary,l=auxiliary,c=restricted
     origin 10.20.0.2

From that snapshot from the CI job, it's:
[mmosesohn@localhost commands]$ grep -A3 aux ubuntu_repo_list.txt
[node-1.test.domain.local] out: 500 http://10.109.5.2:8080/ubuntu/auxiliary/ auxiliary/main amd64 Packages
[node-1.test.domain.local] out: release c=main
[node-1.test.domain.local] out: origin 10.109.5.2

The regenerate-ubuntu-repo script is generating the wrong Release metadata.
currently it has :
release c=main

but it needs to have:
release o=Mirantis,a=auxiliary,n=auxiliary,l=auxiliary,c=main

The pinning file depends on generating the correct Release metadata