# Issue with chef-upgrade role

**URL:** <https://discourse.chef.io/t/issue-with-chef-upgrade-role/1245>\
**Category:** Chef Infra (archive)\
**Created:** [August 25, 2009, 11:42pm UTC](https://discourse.chef.io/t/issue-with-chef-upgrade-role/1245 "2009-08-25T23:42:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joshua\_Timberman](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/joshua_timberman/32/424_2.png) [@Joshua\_Timberman](https://discourse.chef.io/u/Joshua_Timberman)\
**Post date:** [August 25, 2009, 11:42pm UTC](https://discourse.chef.io/t/issue-with-chef-upgrade-role/1245/1 "2009-08-25T23:42:56Z")

</div>

-----BEGIN PGP SIGNED MESSAGE-----  
Hash: SHA1

All,

I fixed an issue with the opscode/chef-repo, where the chef-upgrade  
role name didn’t match the filename, chef\_upgrade and caused the webui  
to not get updated if an existing role had the same name. This is  
noted in ticket CHEF-514.

Helpful hint: make sure your role names match the file’s basename w/o  
extension, ie:

$ grep name roles/chef-upgrade.rb  
name “chef-upgrade”

* * *

Opscode, Inc  
Joshua Timberman, Senior Solutions Engineer  
C: 720.878.4322 E: [joshua@opscode.com](mailto:joshua@opscode.com)

-----BEGIN PGP SIGNATURE-----  
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkqUdwAACgkQO97WSdVpzT3JFgCcDiPbYxEoaMFZZVHyNWyRjcH2  
eX4AnjrdWuJKgKvajXVvFTY+gjjkoSFJ  
=+Qiq  
-----END PGP SIGNATURE-----
